[Geoserver-users] WFS URL Unexpected Behaviour

Hi everyone,

I’m seeing an irregular behaviour with a WFS I’m working with when I apply a BBOX filter to it. The WFS is hosted by a government’s open data catalogue.

The link itself is working:
https://openmaps.gov.bc.ca/geo/pub/wfs?request=GetFeature&outputFormat=json&sortBy=OBJECTID&typeName=WHSE_BASEMAPPING.DRA_DGTL_ROAD_ATLAS_MPAR_SP

When I add a bbox to filter out the data, it is also working:
https://openmaps.gov.bc.ca/geo/pub/wfs?request=GetFeature&outputFormat=json&sortBy=OBJECTID&typeName=WHSE_BASEMAPPING.DRA_DGTL_ROAD_ATLAS_MPAR_SP&bbox=715319.37219999917,1028613.3681000005,735025.99269999936,1041407.1950000003

However, if I want to apply some pagination with count and startIndex, the request would error out.
https://openmaps.gov.bc.ca/geo/pub/wfs?request=GetFeature&outputFormat=json&sortBy=OBJECTID&typeName=WHSE_BASEMAPPING.DRA_DGTL_ROAD_ATLAS_MPAR_SP&bbox=715319.37219999917,1028613.3681000005,735025.99269999936,1041407.1950000003&count=1&startIndex=0

What really confused me is that if I get rid of the bbox and only use count and startIndex, the link is working again and it did return the number of feature I requested.

I’ve tried a bbox + count + startIndex filtering with other datasets from the same catalogue and they were all working. I’m wondering if something could stop bbox and count+startIndex from working together in this particular case?

Thank you!

Oscar

That server seems sad; could not get GetCapabilities from it… was trying to figure out what version of WFS is being used:

Adjusting your query with startIndex and maxFeatures seems to work

image.png

···


Jody Garnett