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.

Sign up for GitHub

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

Jump to bottom

Requesting features with WFS returns features outside BBOX #1687

Open

dstenger opened this issue May 16, 2024 · 0 comments

Labels

bug

Contributor

dstenger commented May 16, 2024 •

edited

Loading

This issue was already reported in deegree/deegree-ogcapi#100 but it also affects deegree3 (e.g. WFS).

Requesting this BBOX 177.0000000,65.0000000,-177.0000000,70.0000000 with WFS returns features which are not located inside the bounding box.

This can be reproduced with WFS 2.0 reference implementation:

https://cite.deegree.org/deegree-webservices-3.5.6/services/wfs200?service=WFS&request=GetFeature&version=2.0.0&typenames=ps:ProtectedSite&bbox=177.0000000,65.0000000,-177.0000000,70.0000000

Additional context: WFS 1.1. and WFS 1.0 also behave incorrect:

WFS 1.1: https://cite.deegree.org/deegree-webservices-3.5.6/services/wfs110?service=WFS&request=GetFeature&version=1.1.0&typename=sf:ComplexGeoFeature&bbox=65.0000000,177.0000000,70.0000000,-177.0000000
- Axis of coordinates is switched
WFS 1.0: https://cite.deegree.org/deegree-webservices-3.5.6/services/wfs100?service=WFS&request=GetFeature&version=1.0.0&typename=cgf:Polygons&bbox=177.0000000,65.0000000,-177.0000000,70.0000000
- Same BBOX as used with WFS 2.0

The text was updated successfully, but these errors were encountered:

dstenger added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment