-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to use filter in wfs getfeature request url ? #235
Comments
if they were supported in deegree? |
Yes, this is supported as defined in the WFS specification (otherwise deegree WFS wouldn't be compliant). The filter can be specified via the FILTER parameter in a KVP GetFeature request. There are two common caveats:
Example Filter: <Filter xmlns="http://www.opengis.net/ogc">
<And>
<BBOX>
<PropertyName>app:geometry</PropertyName>
<Envelope xmlns="http://www.opengis.net/gml">
<coord>
<X>432604.0</X>
<Y>4647889.0</Y>
</coord>
<coord>
<X>5647889.0</X>
<Y>5647889.0</Y>
</coord>
</Envelope>
</BBOX>
<Or>
<PropertyIsEqualTo>
<PropertyName>OBJECTID</PropertyName>
<Literal>446</Literal>
</PropertyIsEqualTo>
<PropertyIsGreaterThan>
<PropertyName>SHAPE_LEN</PropertyName>
<Literal>10000</Literal>
</PropertyIsGreaterThan>
</Or>
</And>
</Filter> URL-encoded XML:
Full KVP-request: |
lgoltz
added a commit
to lat-lon/deegree3
that referenced
this issue
Jan 28, 2017
lgoltz
added a commit
to lat-lon/deegree3
that referenced
this issue
Dec 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i can get feature by featureid and bbox.
example:
1 by featureid
http://127.0.0.1:8088/services/wfs?service=WFS&request=GetFeature&version=1.1.0&TypeName=topp:hztl&featureid=HZTL_0
2 by bbox
http://127.0.0.1:8088/services/wfs?service=WFS&request=GetFeature&version=1.1.0&TypeName=topp:hztl&BBOX=120.200000,30.3,120.080000,30.500000,EPSG:4326
but i can't use other filter (Disjoint Intersects Crosses Within DWithin and so on) correctly.
Are they supported by deegree ?
Thank you for your time!
The text was updated successfully, but these errors were encountered: