[QGIS-Developer] QGIS WFS Bug

[Richard Duivenvoorde]

Hi Chris,

Can you share the url, is it public?

Please test our wfs: https://geodata.nationaalgeoregister.nl/bestuurlijkegrenzen/wfs and load 'provincies' ( provinces, just 12 :-) ).
That server handles 1.0.0 till 2.0.0.

But if I get features from it using 1.0.0 (forcing QGIS use 1.0.0 in the provider dialog, the "VERSION=1.0.0" is always eaten from it if I am correct). I see "EPSG:28992" (plain, NOT the urn version) (in case you use our national crs). And if I am correct, THAT is correct in that the urn-version was (in my memory, others please correct me) introduced in later WFS versions.

Could it be that you server is actually presenting the urn version to QGIS (if requesting capabilities in 1.0.0 format) and that QGIS actually just 'uses' what it receives from the capabilities?

The server(!) above returns different forms in capabilities (and QGIS seems to use those):

<SRS>EPSG:28992</SRS> for 1.0.0 (did you find notion of the use of urn crs identifiers in the 1.0.0 spec?)

<DefaultSRS>urn:x-ogc:def:crs:EPSG:28992</DefaultSRS> for 1.1.0

<DefaultCRS>urn:ogc:def:crs:EPSG::28992</DefaultCRS> for 2.0.0

NOTE all the different types and number of colons!!!

OGC did mess too much with the src/crs/x/y etc etc in my opinion between versions :-)

Regards,

Richard Duivenvoorde

On 8/6/21 3:45 PM, C Hamilton wrote:
> I believe there is a bug in the QGIS WFS GetFeature request. Can someone verify?  I have tested this on Windows with QGIS 3.16 up through 3.20.  I found it because QGIS is failing with one of our WFS servers. The WFS specification for 1.0.0 and 1.1.0 specifies that one form of the SRSNAME urn looks like
> 
> SRSNAME=urn:ogc:def:crs:EPSG:4326
> 
> Note that there is one colon between EPSG and 4326. The WFS 2.0.0 specification has two colons between EPSG and 4326.
> 
> SRSNAME=urn:ogc:def:crs:EPSG::4326
> 
> The server I am working with does not support the 2.0.0 specification and strictly enforces the one colon rule.
> 
> Unfortunately, QGIS is sending out two colons for the 1.1.0 GetFeature request which the WFS server immediately rejects. There is another oddity, if I specifically add VERSION=1.0.0 to the WFS URL, QGIS does not seem to respect that I really want to use 1.0.0 and sees that the server supports 1.1.0 and uses it instead. I tried this to see if the 1.0.0 protocol had the same problem.
> 
> Can someone verify that this is a bug and that I am not missing something?
> 
> Thanks,
> 
> Calvin
> 
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>