[Geoserver-users] Geoserver 2.11.2

GeoServer GeoServer User
1

Guys,

Can anyone please shed some light on this geoserver problem for me?

Cheers, Brad….

From: Brad Spencer brad@anonymised.com
Sent: 06 February 2020 10:44
To: ‘geoserver-users@lists.sourceforge.net’ geoserver-users@lists.sourceforge.net
Subject: Geoserver 2.11.2

I am trying to do a getFeature request using a CQL_FILTER. The filter has two components a spatial filter defined as Within(geometry,POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) plus an attribute filter component persons_usually_resident > 400. This should return over 100 polygon features. I get zero features returned when I should get over 100 returned.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434) -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) AND persons_usually_resident > 400

I have also trued URL encoded CQL_Filter:

http://13.55.5.169:8008/geoserver/abs/wms?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry%2CPOLYGON((144.7434%20-37.9707%2C144.7434%20-37.6572%2C145.1608%20-37.6572%2C145.1608%20-37.9707%2C144.7434%20-37.9707)))%20AND%20component%20persons_usually_resident%20%3E%20400

I know the spatial data is correct as I have used a BBOX CQL_FILTER with the same geometry and it works fine returning the correct data number of features and no urlencoding. That also validates we are looking at the correct layer and geometry. This also returns about the same number of features as the spatial filters should be returning - there will be minor differences tho due to the Within is a little different to BBOX.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400)

I have also checked the syntax of the WKT POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707)) via https://arthur-e.github.io/Wicket/sandbox-gmaps3.html so I feel confident that is correct.

In addition I tried an OGC filter with no luck.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=<Filter><And><PropertyIsGreaterThan><PropertyName>persons_usually_resident</PropertyName><Literal>400</Literal></PropertyIsGreaterThan><Within><PropertyName>geometry</PropertyName><Polygon><outerBoundaryIs><LinearRing><coordinates](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=%3cFilter%3e%3cAnd%3e%3cPropertyIsGreaterThan%3e%3cPropertyName%3epersons_usually_resident%3c/PropertyName%3e%3cLiteral%3e400%3c/Literal%3e%3c/PropertyIsGreaterThan%3e%3cWithin%3e%3cPropertyName%3egeometry%3c/PropertyName%3e%3cPolygon%3e%3couterBoundaryIs%3e%3cLinearRing%3e%3ccoordinates) decimal='.' cs=':' ts=' '>144.7434:-37.9707 144.7434:-37.6572 145.1608:-37.6572 145.1608:-37.9707 144.7434:-37.9707</coordinates></LinearRing></outerBoundaryIs></Polygon></Within></And></Filter>

I need to be able to support either a OGC or CQL spatial filter with a variable sized search polygon which could be a circle of 40 points or a user digitized arbitrary area. I can do this on a Cubewerx WFS service using OGC Filter but am really struggling with Geoserver 2.11.2.

The only thing I can think of is that the access control setting on our geoserver may be set incorrectly.

[http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS](http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS)

specifically…

<fes:Constraint name="ImplementsSpatialFilter">

<ows:NoValues/>

<ows:DefaultValue>FALSE</ows:DefaultValue>

</fes:Constraint>

If this is a problem how can I change this default constraint?

We are also thinking of upgrading to a newer version of geoserver but cannot understand why these requests are ignoring the spatial filters?

Cheers,

Brad Spencer

Managing Director

cid:image001.png@anonymised.com.10288...

http://www.numaps.com.au/

mob: 0404 841 131

BradArt

2

Can you increase the logging and check what query is being generated. What data store are you using?

image001.png

···

–
Jody Garnett

3

Jody,

Sorry about that I was not aware of these rules.

Cheers, Brad….

From: Jody Garnett jody.garnett@anonymised.com
Sent: 10 February 2020 16:55
To: Brad Spencer brad@anonymised.com
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Please keep our policy in mind about keeping communication on the list. I am sorry I accidentally replied to you directly (made a mistake using my phone).

Many folks, including my employer, offer direct email support commercially.

By keeping thing on the list, like how to figure out the logs, we help people doing a web search and participate in the community.

On Mon, Feb 10, 2020 at 5:06 AM Brad Spencer <brad@anonymised.com> wrote:

Jody,

I simply do not understand the Geoserver logs. They make no sense to me. Would it help if I just cut and pasted to you into an email?

Cheers, Brad….

From: Jody Garnett <jody.garnett@anonymised.com>
Sent: 10 February 2020 12:23
To: Brad Spencer <brad@anonymised.com>
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Can you increase the logging and check what query is being generated. What data store are you using?

On Sun, Feb 9, 2020 at 11:48 PM Brad Spencer <brad@anonymised.com> wrote:

Guys,

Can anyone please shed some light on this geoserver problem for me?

Cheers, Brad….

From: Brad Spencer <brad@anonymised.com.10286…>
Sent: 06 February 2020 10:44
To: ‘geoserver-users@lists.sourceforge.net’ <geoserver-users@anonymised.comrge.net>
Subject: Geoserver 2.11.2

I am trying to do a getFeature request using a CQL_FILTER. The filter has two components a spatial filter defined as Within(geometry,POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) plus an attribute filter component persons_usually_resident > 400. This should return over 100 polygon features. I get zero features returned when I should get over 100 returned.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434) -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) AND persons_usually_resident > 400

I have also trued URL encoded CQL_Filter:

http://13.55.5.169:8008/geoserver/abs/wms?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry%2CPOLYGON((144.7434%20-37.9707%2C144.7434%20-37.6572%2C145.1608%20-37.6572%2C145.1608%20-37.9707%2C144.7434%20-37.9707)))%20AND%20component%20persons_usually_resident%20%3E%20400

I know the spatial data is correct as I have used a BBOX CQL_FILTER with the same geometry and it works fine returning the correct data number of features and no urlencoding. That also validates we are looking at the correct layer and geometry. This also returns about the same number of features as the spatial filters should be returning - there will be minor differences tho due to the Within is a little different to BBOX.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400)

I have also checked the syntax of the WKT POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707)) via https://arthur-e.github.io/Wicket/sandbox-gmaps3.html so I feel confident that is correct.

In addition I tried an OGC filter with no luck.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=<Filter><And><PropertyIsGreaterThan><PropertyName>persons_usually_resident</PropertyName><Literal>400</Literal></PropertyIsGreaterThan><Within><PropertyName>geometry</PropertyName><Polygon><outerBoundaryIs><LinearRing><coordinates](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=%3cFilter%3e%3cAnd%3e%3cPropertyIsGreaterThan%3e%3cPropertyName%3epersons_usually_resident%3c/PropertyName%3e%3cLiteral%3e400%3c/Literal%3e%3c/PropertyIsGreaterThan%3e%3cWithin%3e%3cPropertyName%3egeometry%3c/PropertyName%3e%3cPolygon%3e%3couterBoundaryIs%3e%3cLinearRing%3e%3ccoordinates) decimal='.' cs=':' ts=' '>144.7434:-37.9707 144.7434:-37.6572 145.1608:-37.6572 145.1608:-37.9707 144.7434:-37.9707</coordinates></LinearRing></outerBoundaryIs></Polygon></Within></And></Filter>

I need to be able to support either a OGC or CQL spatial filter with a variable sized search polygon which could be a circle of 40 points or a user digitized arbitrary area. I can do this on a Cubewerx WFS service using OGC Filter but am really struggling with Geoserver 2.11.2.

The only thing I can think of is that the access control setting on our geoserver may be set incorrectly.

[http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS](http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS)

specifically…

<fes:Constraint name="ImplementsSpatialFilter">

<ows:NoValues/>

<ows:DefaultValue>FALSE</ows:DefaultValue>

</fes:Constraint>

If this is a problem how can I change this default constraint?

We are also thinking of upgrading to a newer version of geoserver but cannot understand why these requests are ignoring the spatial filters?

Cheers,

Brad Spencer

Managing Director

cid:image001.png@anonymised.com..

http://www.numaps.com.au/

mob: 0404 841 131

BradArt

Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

–

Jody Garnett

–

–

Jody Garnett

4

Hi Brad,
while subscribing you should have got a mail suggesting to check out a document and a presentation.
It’s ok to overlook them, happens to everyone sooner or later.

The docs are also linked in the signature of every post made in this list (the list manager adds them):

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

Nobody if forcing you to read them, but it would be nice if you could have a look.

Cheers
Andrea

image001.png

···

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

5

No worries, in this case it was me making the initial mistake :stuck_out_tongue:

As for this trouble with CQL, please keep in mind that once the filter is parsed for your request, it is then packaged up by the data source (for example translated to SQL for a database request).

So we really need to know what data source you are using to have a better idea what is going on :slight_smile:

The other common thing is to make sure the coordinates in your request match the coordinates in your data.

image001.png

···

–
Jody Garnett

6

See below…

No worries, in this case it was me making the initial mistake :stuck_out_tongue:

As for this trouble with CQL, please keep in mind that once the filter is parsed for your request, it is then packaged up by the data source (for example translated to SQL for a database request).

So we really need to know what data source you are using to have a better idea what is going on :slight_smile:

The other common thing is to make sure the coordinates in your request match the coordinates in your

Did you try my URL links? Won’t the data source be specified in the full link that includes the CQL filter. Also be aware that one of these links shows a BBOX spatial filter in the CQL which works correctly. The BBOX filter’s geometry is used in the CQL Within filter to create a wkt Polygon that does not work. This makes no sense to me. I must be doing something wrong?

brad…

···

–
Jody Garnett

7

The data source is internal to your configuration of geoserver (shapefile, postgis, geomesa, etc…).

  • I don’t think you are doing something wrong, I am suspecting that the data source is not doing a good job of combining a within filter and an attribute filter.

I can see something unusual, your time name may not be valid for WFS:

  • abs:2016meshblocks
  • XML Element names must start with a letter or underscore, and this one starts with “2”

–
Jody Garnett

On Mon, 10 Feb 2020 at 10:26, Brad Spencer <brad@anonymised.com> wrote:

See below…

Sent from my iPhone

On 10 Feb 2020, at 20:11, Jody Garnett <jody.garnett@anonymised.com> wrote:

No worries, in this case it was me making the initial mistake :stuck_out_tongue:

As for this trouble with CQL, please keep in mind that once the filter is parsed for your request, it is then packaged up by the data source (for example translated to SQL for a database request).

So we really need to know what data source you are using to have a better idea what is going on :slight_smile:

The other common thing is to make sure the coordinates in your request match the coordinates in your

Did you try my URL links? Won’t the data source be specified in the full link that includes the CQL filter. Also be aware that one of these links shows a BBOX spatial filter in the CQL which works correctly. The BBOX filter’s geometry is used in the CQL Within filter to create a wkt Polygon that does not work. This makes no sense to me. I must be doing something wrong?

brad…

–
Jody Garnett

On Mon, 10 Feb 2020 at 09:45, Brad Spencer <brad@anonymised.com> wrote:

Jody,

Sorry about that I was not aware of these rules.

Cheers, Brad….

From: Jody Garnett <jody.garnett@anonymised.com>
Sent: 10 February 2020 16:55
To: Brad Spencer <brad@anonymised.com…10286…>
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Please keep our policy in mind about keeping communication on the list. I am sorry I accidentally replied to you directly (made a mistake using my phone).

Many folks, including my employer, offer direct email support commercially.

By keeping thing on the list, like how to figure out the logs, we help people doing a web search and participate in the community.

On Mon, Feb 10, 2020 at 5:06 AM Brad Spencer <brad@anonymised.com> wrote:

Jody,

I simply do not understand the Geoserver logs. They make no sense to me. Would it help if I just cut and pasted to you into an email?

Cheers, Brad….

From: Jody Garnett <jody.garnett@anonymised.com>
Sent: 10 February 2020 12:23
To: Brad Spencer <brad@anonymised.com>
Cc: geoserver-users@anonymised.comsts.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Can you increase the logging and check what query is being generated. What data store are you using?

On Sun, Feb 9, 2020 at 11:48 PM Brad Spencer <brad@anonymised.com286…> wrote:

Guys,

Can anyone please shed some light on this geoserver problem for me?

Cheers, Brad….

From: Brad Spencer <brad@anonymised.com>
Sent: 06 February 2020 10:44
To: ‘geoserver-users@anonymised.comt’ <geoserver-users@lists.sourceforge.net>
Subject: Geoserver 2.11.2

I am trying to do a getFeature request using a CQL_FILTER. The filter has two components a spatial filter defined as Within(geometry,POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) plus an attribute filter component persons_usually_resident > 400. This should return over 100 polygon features. I get zero features returned when I should get over 100 returned.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434) -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) AND persons_usually_resident > 400

I have also trued URL encoded CQL_Filter:

http://13.55.5.169:8008/geoserver/abs/wms?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry%2CPOLYGON((144.7434%20-37.9707%2C144.7434%20-37.6572%2C145.1608%20-37.6572%2C145.1608%20-37.9707%2C144.7434%20-37.9707)))%20AND%20component%20persons_usually_resident%20%3E%20400

I know the spatial data is correct as I have used a BBOX CQL_FILTER with the same geometry and it works fine returning the correct data number of features and no urlencoding. That also validates we are looking at the correct layer and geometry. This also returns about the same number of features as the spatial filters should be returning - there will be minor differences tho due to the Within is a little different to BBOX.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400)

I have also checked the syntax of the WKT POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707)) via https://arthur-e.github.io/Wicket/sandbox-gmaps3.html so I feel confident that is correct.

In addition I tried an OGC filter with no luck.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=<Filter><And><PropertyIsGreaterThan><PropertyName>persons_usually_resident</PropertyName><Literal>400</Literal></PropertyIsGreaterThan><Within><PropertyName>geometry</PropertyName><Polygon><outerBoundaryIs><LinearRing><coordinates](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=%3cFilter%3e%3cAnd%3e%3cPropertyIsGreaterThan%3e%3cPropertyName%3epersons_usually_resident%3c/PropertyName%3e%3cLiteral%3e400%3c/Literal%3e%3c/PropertyIsGreaterThan%3e%3cWithin%3e%3cPropertyName%3egeometry%3c/PropertyName%3e%3cPolygon%3e%3couterBoundaryIs%3e%3cLinearRing%3e%3ccoordinates) decimal='.' cs=':' ts=' '>144.7434:-37.9707 144.7434:-37.6572 145.1608:-37.6572 145.1608:-37.9707 144.7434:-37.9707</coordinates></LinearRing></outerBoundaryIs></Polygon></Within></And></Filter>

I need to be able to support either a OGC or CQL spatial filter with a variable sized search polygon which could be a circle of 40 points or a user digitized arbitrary area. I can do this on a Cubewerx WFS service using OGC Filter but am really struggling with Geoserver 2.11.2.

The only thing I can think of is that the access control setting on our geoserver may be set incorrectly.

[http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS](http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS)

specifically…

<fes:Constraint name="ImplementsSpatialFilter">

<ows:NoValues/>

<ows:DefaultValue>FALSE</ows:DefaultValue>

</fes:Constraint>

If this is a problem how can I change this default constraint?

We are also thinking of upgrading to a newer version of geoserver but cannot understand why these requests are ignoring the spatial filters?

Cheers,

Brad Spencer

Managing Director

<image001.png>

http://www.numaps.com.au/

mob: 0404 841 131

BradArt

Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

–

Jody Garnett

–

–

Jody Garnett

8

For reference here is describe feature type:

As a result the following xml output has an error:

This page contains the following errors:
error on line 1 at column 633: Failed to parse QName ‘abs:’
Below is a rendering of the page up to the first error.

While you can name your layers anything in geoserver, the different protocols each have different restrictions on what is possible. The same content may work just fine as json output for example.

···

–
Jody Garnett

9

look at this error

http://13.55.5.169:8008/geoserver/abs/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=abs%3A2016MBmeshblocks&CQL_FILTER=within(geometry%2CPOLYGON((144.7434%20-37.9707%2C144.7434%20-37.6572%2C145.1608%20-37.6572%2C145.1608%20-37.9707%2C144.7434%20-37.9707)))&CRS=EPSG%3A4326&WIDTH=768&HEIGHT=373&BBOX=-42.71484375%2C-95.625%2C88.41796875%2C174.375

maybe the the problem is in the underlying data in postgis

Jody Garnett <jody.garnett@anonymised.com> escreveu no dia segunda, 10/02/2020 à(s) 09:46:

···

www.vfonsecaz.pt

10

And it solves the issue: “Operation on mixed SRID geometries”.

Brad it appears either:

  • Your table is using one SRID and the request is coming in another?
  • Or possibly (very rare) your table was created without an SRID constrain on the geometry column and you have managed to add geometries with different SRIDs to the same table
···

–
Jody Garnett

11

Ok we are using postgis.
Re the typename, we could look at renaming these layers as we are on development right now, however, how come the CQL filter using a BBOX spatial filter works?
Also, have any thoughts about the Getcapabilities constraints settings?

<fes:Constraint name="ImplementsSpatialFilter">

Sent from my iPhone

On 10 Feb 2020, at 20:40, Jody Garnett jody.garnett@anonymised.com wrote:

The data source is internal to your configuration of geoserver (shapefile, postgis, geomesa, etc…).

  • I don’t think you are doing something wrong, I am suspecting that the data source is not doing a good job of combining a within filter and an attribute filter.

I can see something unusual, your time name may not be valid for WFS:

  • abs:2016meshblocks
  • XML Element names must start with a letter or underscore, and this one starts with “2”

–
Jody Garnett

On Mon, 10 Feb 2020 at 10:26, Brad Spencer <brad@anonymised.com> wrote:

See below…

Sent from my iPhone

On 10 Feb 2020, at 20:11, Jody Garnett <jody.garnett@anonymised.com> wrote:

No worries, in this case it was me making the initial mistake :stuck_out_tongue:

As for this trouble with CQL, please keep in mind that once the filter is parsed for your request, it is then packaged up by the data source (for example translated to SQL for a database request).

So we really need to know what data source you are using to have a better idea what is going on :slight_smile:

The other common thing is to make sure the coordinates in your request match the coordinates in your

Did you try my URL links? Won’t the data source be specified in the full link that includes the CQL filter. Also be aware that one of these links shows a BBOX spatial filter in the CQL which works correctly. The BBOX filter’s geometry is used in the CQL Within filter to create a wkt Polygon that does not work. This makes no sense to me. I must be doing something wrong?

brad…

–
Jody Garnett

On Mon, 10 Feb 2020 at 09:45, Brad Spencer <brad@anonymised.com> wrote:

Jody,

Sorry about that I was not aware of these rules.

Cheers, Brad….

From: Jody Garnett <jody.garnett@anonymised.com>
Sent: 10 February 2020 16:55
To: Brad Spencer <brad@anonymised.com>
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Please keep our policy in mind about keeping communication on the list. I am sorry I accidentally replied to you directly (made a mistake using my phone).

Many folks, including my employer, offer direct email support commercially.

By keeping thing on the list, like how to figure out the logs, we help people doing a web search and participate in the community.

On Mon, Feb 10, 2020 at 5:06 AM Brad Spencer <brad@anonymised.com> wrote:

Jody,

I simply do not understand the Geoserver logs. They make no sense to me. Would it help if I just cut and pasted to you into an email?

Cheers, Brad….

From: Jody Garnett <jody.garnett@anonymised.com>
Sent: 10 February 2020 12:23
To: Brad Spencer <brad@anonymised.com>
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Can you increase the logging and check what query is being generated. What data store are you using?

On Sun, Feb 9, 2020 at 11:48 PM Brad Spencer <brad@anonymised.com> wrote:

Guys,

Can anyone please shed some light on this geoserver problem for me?

Cheers, Brad….

From: Brad Spencer <brad@anonymised.com>
Sent: 06 February 2020 10:44
To: ‘geoserver-users@lists.sourceforge.net’ <geoserver-users@lists.sourceforge.net>
Subject: Geoserver 2.11.2

I am trying to do a getFeature request using a CQL_FILTER. The filter has two components a spatial filter defined as Within(geometry,POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) plus an attribute filter component persons_usually_resident > 400. This should return over 100 polygon features. I get zero features returned when I should get over 100 returned.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434) -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) AND persons_usually_resident > 400

I have also trued URL encoded CQL_Filter:

http://13.55.5.169:8008/geoserver/abs/wms?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry%2CPOLYGON((144.7434%20-37.9707%2C144.7434%20-37.6572%2C145.1608%20-37.6572%2C145.1608%20-37.9707%2C144.7434%20-37.9707)))%20AND%20component%20persons_usually_resident%20%3E%20400

I know the spatial data is correct as I have used a BBOX CQL_FILTER with the same geometry and it works fine returning the correct data number of features and no urlencoding. That also validates we are looking at the correct layer and geometry. This also returns about the same number of features as the spatial filters should be returning - there will be minor differences tho due to the Within is a little different to BBOX.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400)

I have also checked the syntax of the WKT POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707)) via https://arthur-e.github.io/Wicket/sandbox-gmaps3.html so I feel confident that is correct.

In addition I tried an OGC filter with no luck.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=<Filter><And><PropertyIsGreaterThan><PropertyName>persons_usually_resident</PropertyName><Literal>400</Literal></PropertyIsGreaterThan><Within><PropertyName>geometry</PropertyName><Polygon><outerBoundaryIs><LinearRing><coordinates](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=%3cFilter%3e%3cAnd%3e%3cPropertyIsGreaterThan%3e%3cPropertyName%3epersons_usually_resident%3c/PropertyName%3e%3cLiteral%3e400%3c/Literal%3e%3c/PropertyIsGreaterThan%3e%3cWithin%3e%3cPropertyName%3egeometry%3c/PropertyName%3e%3cPolygon%3e%3couterBoundaryIs%3e%3cLinearRing%3e%3ccoordinates) decimal='.' cs=':' ts=' '>144.7434:-37.9707 144.7434:-37.6572 145.1608:-37.6572 145.1608:-37.9707 144.7434:-37.9707</coordinates></LinearRing></outerBoundaryIs></Polygon></Within></And></Filter>

I need to be able to support either a OGC or CQL spatial filter with a variable sized search polygon which could be a circle of 40 points or a user digitized arbitrary area. I can do this on a Cubewerx WFS service using OGC Filter but am really struggling with Geoserver 2.11.2.

The only thing I can think of is that the access control setting on our geoserver may be set incorrectly.

[http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS](http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS)

specifically…

<fes:Constraint name="ImplementsSpatialFilter">

<ows:NoValues/>

<ows:DefaultValue>FALSE</ows:DefaultValue>

</fes:Constraint>

If this is a problem how can I change this default constraint?

We are also thinking of upgrading to a newer version of geoserver but cannot understand why these requests are ignoring the spatial filters?

Cheers,

Brad Spencer

Managing Director

<image001.png>

http://www.numaps.com.au/

mob: 0404 841 131

BradArt

Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Geoserver-users@anonymised.comts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

–

Jody Garnett

–

–

Jody Garnett

12

bbox spatial filter uses the && operator (working on the index) rather than within which uses the geometries.

Check the WMS spec for ImplementsSpatialFilter, think this is a flag indicating spatial filters are available.

···

–
Jody Garnett

13

See below

bbox spatial filter uses the && operator (working on the index) rather than within which uses the geometries.

I don’t understand what you are saying here? Can you elaborate a tad please?

Check the WMS spec for ImplementsSpatialFilter, think this is a flag indicating spatial filters are available.

The getcapabilities shows this set to false. How can I change this in geoserver?

···

–
Jody Garnett

14

On 10 Feb 2020, at 22:14, Jody Garnett <jody.garnett@anonymised.com> wrote:

bbox spatial filter uses the && operator (working on the index) rather than within which uses the geometries.

I don’t understand what you are saying here? Can you elaborate a tad please?

This refers to the SQL query generated on your behalf to the backend PostGIS database.
a) BBOX query accesses the bounding box
b) Within accesses the geometry

The real point is that your table contains geometry that is not in SRID=4326 so your query is failing.

Check the WMS spec for ImplementsSpatialFilter, think this is a flag indicating spatial filters are available.

The getcapabilities shows this set to false. How can I change this in geoserver?

Going to have to let someone else answer here, one of the reasons we are on the user list.

15

Jody,

Your observation about TYPENAME starting with numeric appears to be the problem. I changed the layer in geoserver to be ‘abs:MB2016meshblocks’ and voila!

The CQL_FILTER containing a WKT spatial component plus an attribute component worked in Geoserver CQL Filter viewer and as a URL as expected – 141 features.

http://13.55.5.169:8008/geoserver/abs/wms?REQUEST=Getfeature&SERVICE=WFS&TYPENAME=abs:MB2016meshblocks&OUTPUTFORMAT=application/json&srsName=EPSG:4326&VERSION=1.0.0&CQL_FILTER=Within(geometry,POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) AND persons_usually_resident > 400

However, I get zero returns if I use version 1.1.0 or 2.0.0 but it works a treat with 1.0.0 and that will do me for now.

I am not sure if this is a bug in 2.11.2 or not and maybe we should look to upgrade.

But things to note is that if you have a non OGC compliant TYPENAME (starting with a numeric was my case), the CQL_FILTER using BBOX spatial filter works but when you use a CQL_FILTER using a WKT object (Polygon, Linestring, Point, etc) as your spatial filter it may not work.

Thanks for all your help and patience, now I have some work my end!

Cheers,

Brad Spencer

Managing Director

cid:image001.png@anonymised.com

http://www.numaps.com.au/

mob: 0404 841 131

BradArt

From: Jody Garnett jody.garnett@anonymised.com
Sent: 10 February 2020 22:14
To: Brad Spencer brad@anonymised.com
Cc: GeoServer Users geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver 2.11.2

bbox spatial filter uses the && operator (working on the index) rather than within which uses the geometries.

Check the WMS spec for ImplementsSpatialFilter, think this is a flag indicating spatial filters are available.

–

Jody Garnett

On Mon, 10 Feb 2020 at 11:29, Brad Spencer <brad@anonymised.com> wrote:

Ok we are using postgis.

Re the typename, we could look at renaming these layers as we are on development right now, however, how come the CQL filter using a BBOX spatial filter works?

Also, have any thoughts about the Getcapabilities constraints settings?

<fes:Constraint name="ImplementsSpatialFilter">

Sent from my iPhone

On 10 Feb 2020, at 20:40, Jody Garnett <jody.garnett@anonymised.com> wrote:

The data source is internal to your configuration of geoserver (shapefile, postgis, geomesa, etc…).

  • I don’t think you are doing something wrong, I am suspecting that the data source is not doing a good job of combining a within filter and an attribute filter.

I can see something unusual, your time name may not be valid for WFS:

  • abs:2016meshblocks

  • XML Element names must start with a letter or underscore, and this one starts with “2”

–

Jody Garnett

On Mon, 10 Feb 2020 at 10:26, Brad Spencer <brad@anonymised.com…> wrote:

See below…

Sent from my iPhone

On 10 Feb 2020, at 20:11, Jody Garnett <jody.garnett@anonymised.com> wrote:

No worries, in this case it was me making the initial mistake :stuck_out_tongue:

As for this trouble with CQL, please keep in mind that once the filter is parsed for your request, it is then packaged up by the data source (for example translated to SQL for a database request).

So we really need to know what data source you are using to have a better idea what is going on :slight_smile:

The other common thing is to make sure the coordinates in your request match the coordinates in your

Did you try my URL links? Won’t the data source be specified in the full link that includes the CQL filter. Also be aware that one of these links shows a BBOX spatial filter in the CQL which works correctly. The BBOX filter’s geometry is used in the CQL Within filter to create a wkt Polygon that does not work. This makes no sense to me. I must be doing something wrong?

brad…

–

Jody Garnett

On Mon, 10 Feb 2020 at 09:45, Brad Spencer <brad@anonymised.com> wrote:

Jody,

Sorry about that I was not aware of these rules.

Cheers, Brad….

From: Jody Garnett <jody.garnett@anonymised.com>
Sent: 10 February 2020 16:55
To: Brad Spencer <brad@anonymised.com>
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Please keep our policy in mind about keeping communication on the list. I am sorry I accidentally replied to you directly (made a mistake using my phone).

Many folks, including my employer, offer direct email support commercially.

By keeping thing on the list, like how to figure out the logs, we help people doing a web search and participate in the community.

On Mon, Feb 10, 2020 at 5:06 AM Brad Spencer <brad@anonymised.com> wrote:

Jody,

I simply do not understand the Geoserver logs. They make no sense to me. Would it help if I just cut and pasted to you into an email?

Cheers, Brad….

From: Jody Garnett <jody.garnett@anonymised.com>
Sent: 10 February 2020 12:23
To: Brad Spencer <brad@anonymised.com>
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver 2.11.2

Can you increase the logging and check what query is being generated. What data store are you using?

On Sun, Feb 9, 2020 at 11:48 PM Brad Spencer <brad@anonymised.com> wrote:

Guys,

Can anyone please shed some light on this geoserver problem for me?

Cheers, Brad….

From: Brad Spencer <brad@anonymised.com>
Sent: 06 February 2020 10:44
To: ‘geoserver-users@lists.sourceforge.net’ <geoserver-users@lists.sourceforge.net>
Subject: Geoserver 2.11.2

I am trying to do a getFeature request using a CQL_FILTER. The filter has two components a spatial filter defined as Within(geometry,POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) plus an attribute filter component persons_usually_resident > 400. This should return over 100 polygon features. I get zero features returned when I should get over 100 returned.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry,POLYGON((144.7434) -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707))) AND persons_usually_resident > 400

I have also trued URL encoded CQL_Filter:

http://13.55.5.169:8008/geoserver/abs/wms?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=Within(geometry%2CPOLYGON((144.7434%20-37.9707%2C144.7434%20-37.6572%2C145.1608%20-37.6572%2C145.1608%20-37.9707%2C144.7434%20-37.9707)))%20AND%20component%20persons_usually_resident%20%3E%20400

I know the spatial data is correct as I have used a BBOX CQL_FILTER with the same geometry and it works fine returning the correct data number of features and no urlencoding. That also validates we are looking at the correct layer and geometry. This also returns about the same number of features as the spatial filters should be returning - there will be minor differences tho due to the Within is a little different to BBOX.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&CQL_FILTER=BBOX(geometry,144.7434,-37.9707,145.1608,-37.6572)%20AND%20persons_usually_resident%20%3E%20400)

I have also checked the syntax of the WKT POLYGON((144.7434 -37.9707,144.7434 -37.6572,145.1608 -37.6572,145.1608 -37.9707,144.7434 -37.9707)) via https://arthur-e.github.io/Wicket/sandbox-gmaps3.html so I feel confident that is correct.

In addition I tried an OGC filter with no luck.

[http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=<Filter><And><PropertyIsGreaterThan><PropertyName>persons_usually_resident</PropertyName><Literal>400</Literal></PropertyIsGreaterThan><Within><PropertyName>geometry</PropertyName><Polygon><outerBoundaryIs><LinearRing><coordinates](http://13.55.5.169:8008/geoserver/abs/wfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.1.0&TYPENAME=2016MBmeshblocks&OUTPUTFORMAT=application/json&FILTER=%3cFilter%3e%3cAnd%3e%3cPropertyIsGreaterThan%3e%3cPropertyName%3epersons_usually_resident%3c/PropertyName%3e%3cLiteral%3e400%3c/Literal%3e%3c/PropertyIsGreaterThan%3e%3cWithin%3e%3cPropertyName%3egeometry%3c/PropertyName%3e%3cPolygon%3e%3couterBoundaryIs%3e%3cLinearRing%3e%3ccoordinates) decimal='.' cs=':' ts=' '>144.7434:-37.9707 144.7434:-37.6572 145.1608:-37.6572 145.1608:-37.9707 144.7434:-37.9707</coordinates></LinearRing></outerBoundaryIs></Polygon></Within></And></Filter>

I need to be able to support either a OGC or CQL spatial filter with a variable sized search polygon which could be a circle of 40 points or a user digitized arbitrary area. I can do this on a Cubewerx WFS service using OGC Filter but am really struggling with Geoserver 2.11.2.

The only thing I can think of is that the access control setting on our geoserver may be set incorrectly.

[http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS](http://13.55.5.169:8008/geoserver/abs/wfs?request=getcapabilities&service=WFS)

specifically…

<fes:Constraint name="ImplementsSpatialFilter">

<ows:NoValues/>

<ows:DefaultValue>FALSE</ows:DefaultValue>

</fes:Constraint>

If this is a problem how can I change this default constraint?

We are also thinking of upgrading to a newer version of geoserver but cannot understand why these requests are ignoring the spatial filters?

Cheers,

Brad Spencer

Managing Director

<image001.png>

http://www.numaps.com.au/

mob: 0404 841 131

BradArt

Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

–

Jody Garnett

–

–

Jody Garnett

16

I saw an answer by Jukka on this topic: WFS 1.0 defaults to lon/lat axis order, while 1.1 and 2.0 default to lat/lon axis order,
in order to get results in 1.1 and 2.0 you’ll have to flip the coordinates in your filter

Cheers
Andrea

image001.png

···

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

17

Andrea, got it thanks.

Brad…

···

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.