1

I have a WFS with two different feature types and I am trying to work with BBox.

This KVP is working: http://inspire.maaamet.ee/arcgis/rest/services/public/au/MapServer/exts/InspireFeatureDownload/service?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAMES=au:AdministrativeUnit&BBOX=59.664,26.3415,58.6268,26.3677,urn:ogc:def:crs:EPSG::4258&COUNT=10 for the feature type called au:AdministrativeUnit.

But this one does not work:http://inspire.maaamet.ee/arcgis/rest/services/public/au/MapServer/exts/InspireFeatureDownload/service?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAMES=mu:MaritimeBoundary&BBOX=59.664,26.3415,58.6268,26.3677,urn:ogc:def:crs:EPSG::4258 for the feature type called mu:MaritimeBoundary

Why this is happening when I change only the feature type name? Could it be a problem from the server itself?

Improve this question
0
3

Having a look at the whole data of the mu:MaritimeBoundary feature type and BBOX gives a hint. The red geometry is your BBOX and green line is the maritime boundary.

enter image description here

The WfS server does not return data because your BBOX does not intersect with any feature. This request with a BBOX the goes further to the North returns data.

http://inspire.maaamet.ee/arcgis/rest/services/public/au/MapServer/exts/InspireFeatureDownload/service?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAMES=mu:MaritimeBoundary&BBOX=60.664,26.3415,58.6268,26.3677,urn:ogc:def:crs:EPSG::4258

Some servers (for example GeoServer) do the comparison with BBOX filter through a faster path, by comparing if the envelopes of the features intersect with the BBOX. However, the OGC Filter Encoding standard defines is so that ther should be real intersections:

> The <BBOX> element is defined as a convenient and more compact way of
> encoding the very common bounding box constraint based on the
> gml:Envelope geometry. It is equivalent to the spatial operation
> <Not><Disjoint> … </Disjoint></Not> meaning that the <BBOX> operator
> should identify all geometries that spatially interact with the box.

BTW. Your BBOX is wrong because the first coordinate pair should have the minimum values and the second one the maximum values. 59.664,26.3415,58.6268,26.3677 should be 58.6268,26.3415,59.664,26.3677

Improve this answer
2
  • Thanks for the comments about the BBOX, sorry for bothering with my mistake. With which software did you visualize this feature type and the BBox?
    – Floni
    Apr 26 '18 at 6:47
  • OpenJUMP openjump.org.
    – user30184
    Apr 26 '18 at 11:49
1

There is no feature inside your bounding box:

http://inspire.maaamet.ee/arcgis/services/public/au/MapServer/WMSServer?

enter image description here

Improve this answer
3

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.