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
On Mon, 10 Feb 2020 at 10:57, Vitor Fonseca <vfonse...@gmail.com> wrote: > > 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.garn...@gmail.com> escreveu no dia segunda, 10/02/2020 > à(s) 09:46: > >> For reference here is describe feature type: >> - >> http://13.55.5.169:8008/geoserver/abs/wfs?request=DescribeFeatureType&service=WFS&typename=abs:2016meshblocks >> >> As a result the following xml output has an error: >> - >> http://13.55.5.169:8008/geoserver/abs/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=abs:2016meshblocks&maxFeatures=50 >> >> 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 >> >> >> On Mon, 10 Feb 2020 at 10:39, Jody Garnett <jody.garn...@gmail.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 <b...@numaps.com.au> wrote: >>> >>>> See below.... >>>> >>>> Sent from my iPhone >>>> >>>> On 10 Feb 2020, at 20:11, Jody Garnett <jody.garn...@gmail.com> wrote: >>>> >>>> >>>> No worries, in this case it was me making the initial mistake :P >>>> >>>> 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 :) >>>> >>>> >>>> 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 <b...@numaps.com.au> wrote: >>>> >>>>> Jody, >>>>> >>>>> >>>>> >>>>> Sorry about that I was not aware of these rules. >>>>> >>>>> >>>>> >>>>> Cheers, Brad…. >>>>> >>>>> >>>>> >>>>> *From:* Jody Garnett <jody.garn...@gmail.com> >>>>> *Sent:* 10 February 2020 16:55 >>>>> *To:* Brad Spencer <b...@numaps.com.au> >>>>> *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 <b...@numaps.com.au> >>>>> 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.garn...@gmail.com> >>>>> *Sent:* 10 February 2020 12:23 >>>>> *To:* Brad Spencer <b...@numaps.com.au> >>>>> *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 <b...@numaps.com.au> >>>>> wrote: >>>>> >>>>> Guys, >>>>> >>>>> >>>>> >>>>> Can anyone please shed some light on this geoserver problem for me? >>>>> >>>>> >>>>> >>>>> Cheers, Brad…. >>>>> >>>>> >>>>> >>>>> *From:* Brad Spencer <b...@numaps.com.au> >>>>> *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 >>>>> -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 >>>>> >>>>> 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 >>>>> 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 >>>>> >>>>> 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 >>>>> <https://www.facebook.com/pg/numaps.com.au/photos/?ref=page_internal> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Geoserver-users mailing list >>>>> >>>>> 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 >>>>> >>>>> 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 >>>>> >>>> _______________________________________________ >> Geoserver-users mailing list >> >> 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 >> >> 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 >> > > > -- > > www.vfonsecaz.pt > >
_______________________________________________ Geoserver-users mailing list 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 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
