Closed jarped closed 8 years ago
The current implementation already adds the CRS to the BBOX, so you can use a different CRS.
bbox=5393820.5525,4437734.86009,5410050.9275,4471285.70991,urn:ogc:def:crs:EPSG::31468
Do you have examples requests which fail using deegree 3? Please also check: https://github.com/deegree/deegree3/pull/556
Had not seen that bugfix. That being said, deegree 3.4 has been long in the waiting by now.
Here's one with BBOX in filter against a dataset that uses EPSG:4258 as default: http://wfs.geonorge.no/skwms1/wfs.elf-au?service=WFS&request=GetFeature&version=2.0.0&srsName=urn:ogc:def:crs:EPSG::32633&typeNames=elf-au%3AAdministrativeUnit&filter=%3Cfes%3AFilter+xmlns%3Afes%3D%22http%3A%2F%2Fwww.opengis.net%2Ffes%2F2.0%22+xmlns%3Agml%3D%22http%3A%2F%2Fwww.opengis.net%2Fgml%2F3.2%22%3E%3Cfes%3ABBOX%3E%3Cgml%3AEnvelope+srsName%3D%22urn%3Aogc%3Adef%3Acrs%3AEPSG%3A%3A32633%22%3E%3Cgml%3AlowerCorner%3E244908.219868+6625745.85798%3C%2Fgml%3AlowerCorner%3E%3Cgml%3AupperCorner%3E301351.862663+6645317.44063%3C%2Fgml%3AupperCorner%3E%3C%2Fgml%3AEnvelope%3E%3C%2Ffes%3ABBOX%3E%3C%2Ffes%3AFilter%3E&namespaces=xmlns(elf-au,http%3A%2F%2Fwww.locationframework.eu%2Fschemas%2FAdministrativeUnits%2F0.2)&count=1&
Hi @jarped ,
the issue has been fixed in deegree 3.3.16
, so I have closed this PR.
https://github.com/deegree/deegree3/pulls?q=is:pr+is:closed+milestone:3.3.16
Best regards Jürgen
By default, Deegree3 will assume that your BBOX is in the default CRS of the featuretype. This way of querying assures that you can have a BBOX in different CRS.
Commit now only contains changes relevant to this.