QGIS » QGIS Application

We have this national OWS services. One of them is municipality borders:

If I add a WFS server via this url:

https://geodata.nationaalgeoregister.nl/bestuurlijkegrenzen/wfs?request=GetCapabilities
or
https://geodata.nationaalgeoregister.nl/bestuurlijkegrenzen/wfs

I get a:

Layer bestuurlijkegrenzen:gemeenten: Download of features for layer bestuurlijkegrenzen:gemeenten failed or partially failed: Error when parsing GetFeature response : Error: not well-formed (invalid token) on line 2096, column 20. You may attempt reloading the layer with F5

Looking into this line it is a character encoding issue:

<bestuurlijkegrenzen:gemeentenaam>Súdwest-Fryslân</bestuurlijkegrenzen:gemeentenaam>

BUT exactly the same url returns perfectly fine in one of my plugins.

First I thought it had something to do with the headers sent by the WFS server:

curl -s -D - "https://geodata.nationaalgeoregister.nl/bestuurlijkegrenzen/wfs?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=bestuurlijkegrenzen:gemeenten&COUNT=15000&SRSNAME=urn:ogc:def:crs:EPSG::28992&" -o /dev/null

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, HEAD
Access-Control-Max-Age: 1000
Access-Control-Allow-Headers: SOAPAction,X-Requested-With,Content-Type,Origin,Authorization,Accept
Content-Disposition: inline; filename=geoserver-GetFeature.text
X-Cnection: close
Content-Type: text/xml; subtype=gml/3.2
Transfer-Encoding: chunked
Date: Mon, 06 Jun 2016 13:47:20 GMT

curl -s -D - "https://geodata.nationaalgeoregister.nl/bestuurlijkegrenzen/wfs?request=GetCapabilities&SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=bestuurlijkegrenzen:gemeenten&COUNT=15000&SRSNAME=urn:ogc:def:crs:EPSG::28992&BBOX=99491.91838273697067052,532089.02270954963751137,216836.14587102248333395,582859.78376076021231711" -o /dev/null

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, HEAD
Access-Control-Max-Age: 1000
Access-Control-Allow-Headers: SOAPAction,X-Requested-With,Content-Type,Origin,Authorization,Accept
Content-Disposition: inline; filename=geoserver-GetFeature.text
X-Cnection: close
Content-Type: text/xml; subtype=gml/3.2
Transfer-Encoding: chunked
Date: Mon, 06 Jun 2016 13:58:18 GMT

BUT that turned out NOT to be the case.

BUT looking into the url's fired, it apparently is the route taken into the wfs provider.

Both these requests have all municipalities in the netherlands and return the same xml on the commandline, the first one without bbox clause, the second one with:

curl "https://geodata.nationaalgeoregister.nl/bestuurlijkegrenzen/wfs?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=bestuurlijkegrenzen:gemeenten&COUNT=15000&SRSNAME=urn:ogc:def:crs:EPSG::28992&" > wfsnobbox.xml

curl "https://geodata.nationaalgeoregister.nl/bestuurlijkegrenzen/wfs?request=GetCapabilities&SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=bestuurlijkegrenzen:gemeenten&COUNT=15000&SRSNAME=urn:ogc:def:crs:EPSG::28992&BBOX=0,300000,300000,600000" > wfswithbbox2.xml

The first one I use to programmatically use (the same wfs provider).
BUT the second one I see in the debug of QGIS and is used by the WFS provider, if used via the 'Add WFS Layer' route.

So my theory: the parsing route of the gml via the 'with bbox' clause is different from the one via the 'old route'.

The parsing (I think done to be able to incrementally load the features) does not take character encoding into account?

Thanks for looking into this.