Hi Ben,
Thank you for clarification. Here is the query part of the GET request:
The query that does not work:
?VERSION=2.0SERVICE=WFSREQUEST=GetFeatureTYPENAME=ns1:db_entriesFILTER=NotDisjointValueReferencens1:geometry/ValueReferencegml:Polygon
Nhan,
because WFS 2.0 no longer depends on any version of GML, when GeoServer
is parsing your request it cannot deduce what version of GML or filter
you are using. One solution that works is to specify the namespaces; I
added an fes:Filter element as a place where I could put the xmlns
Hi Ben,
After I wrap the filter in the Filter tags with namespaces everything
works as expected. Thanks for the detailed explanation! Including your
example together with some explanation in the documentation would be
helpful for others.
Cheers,
Nhan
On 9/11/2013 11:20 AM, Ben
Hi list,
I've tried the following filter in the Demo request page and it works
(even though some elements do not have namespace prefix):
?xml version=1.0 encoding=UTF-8?
wfs:GetFeature
service=WFS
version=2.0.0
xmlns:wfs=http://www.opengis.net/wfs/2.0;
On Tue, Sep 10, 2013 at 1:50 PM, Nhan Vo nha...@smileconsult.de wrote:
I've done the same thing in URLs with other filter 2.0 elements like
PropertyIsLike and PropertyIsEqualTo and they work for me. Could someone
give me a hint? Thanks!
Making a guess here, did you remember to add
Hi Andrea,
Thanks for the reply! Yes I've added version=2.0.0, and as I
said it works for other elements like PropertyIsLike and
PropertyIsEqualTo, but for this spatial filter it does not work.
Here's the stack trace from geoserver log:
Nhan,
GeoServer is by default permissive when it comes to namespaces.
Please paste the entire request GET URL into an email so we can see it.
Or the query part (after ?) at least if you do not want to disclose
the host.
Also, note that the schemaLocation in your request is wrong: the WFS 2
