Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WFS 1.1.0 broken by inverted axis in QGIS Server #26235

Closed
qgib opened this issue Mar 5, 2018 · 13 comments
Closed

WFS 1.1.0 broken by inverted axis in QGIS Server #26235

qgib opened this issue Mar 5, 2018 · 13 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Regression Something which used to work, but doesn't anymore Server Related to QGIS server

Comments

@qgib
Copy link
Contributor

qgib commented Mar 5, 2018

Author Name: Alessandro Pasotti (@elpaso)
Original Redmine Issue: 18345
Affected QGIS version: 3.0.0
Redmine category:qgis_server
Assignee: René-Luc ReLuc


Apparently QGIS Server supports WFS 1.1.0 as advertised by its getcapabilities, but when requested to getcapabilities for VERSION=1.1.0 it does no return anything different from the default (which is 1.0).

The result is that QGIS WFS client gets confused and you get inverted axis.

Specifying WFS version 1.1 in the client, does not help while setting it to 1.0 does.

Note that the default setting for WFS is AUTO which also fails.

@qgib
Copy link
Contributor Author

qgib commented Mar 5, 2018

Author Name: Alessandro Pasotti (@elpaso)


To be more precise: the returned XML is different, what does not change is the SRS specification: according to the specs, it should be urn:x-ogc:def:crs:EPSG:xxxx instead of EPSG: , a WFS 1.1 server returning EPSG:xxxx is not really expected, and a source of confusion

This confuses the client and it is probably a violation of the specifications (not 100% sure about that).

See also: http://docs.geoserver.org/latest/en/user/services/wfs/basics.html#axis-ordering

@qgib
Copy link
Contributor Author

qgib commented Mar 5, 2018

Author Name: Alessandro Pasotti (@elpaso)


Another evidence: getFeature call always return 1.1 format but coordinates are not inverted and epsg code is not URN prefixed.

I believe this is the real problem: when using WFS 1.1 the coordinates should be lat/lon and the srsName should be prefixed with urn:ogc:def:crs:

GeoServer fully respect this and Mapserver does it partially: see http://mapserver.org/ogc/wfs_server.html#axis-orientation-in-wfs-1-1-and-2-0

@qgib
Copy link
Contributor Author

qgib commented Mar 6, 2018

Author Name: Alessandro Pasotti (@elpaso)


Things looks more complicated than it seems,

This email exchange is enlightning:
http://lists.osgeo.org/pipermail/standards/2016-October/000994.html

See also:
https://tools.ietf.org/html/rfc5165

And:
http://www.ogcnetwork.net/axisorder

the bottomline is that we should probably change WFS 1.1.0 getfeature response to:

  • use urn: prefixed srsName
  • return lat/lon instead of lon/lat in GML

  • subject was changed from WFS 1.1.0 broken in QGIS Server to WFS 1.1.0 broken by inverted axis in QGIS Server

@qgib
Copy link
Contributor Author

qgib commented Mar 6, 2018

Author Name: Giovanni Manghi (@gioman)


Is this a regression or is also true for 2.*?


  • priority_id was changed from Normal to High
  • version was changed from master to 3.1(master)
  • regression was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented Mar 6, 2018

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Mar 6, 2018

Author Name: Alessandro Pasotti (@elpaso)


I don't think this applies to 2.x: the server code has changed completely and AFAIK WFS 1.1 was not supported in 2.x

@qgib
Copy link
Contributor Author

qgib commented Mar 10, 2018

Author Name: Alessandro Pasotti (@elpaso)


Some more info about other softwares: https://github.com/deegree/deegree3/wiki/Axis-order-handling

@qgib
Copy link
Contributor Author

qgib commented Mar 20, 2018

Author Name: René-Luc ReLuc (@rldhont)


Is the master 3.1 or the release 3.0 affected by this issue ?


  • assigned_to_id was configured as René-Luc ReLuc

@qgib
Copy link
Contributor Author

qgib commented Mar 20, 2018

Author Name: Alessandro Pasotti (@elpaso)


Both.

But you'd better wait for #6644 if you want to fix it.

@qgib
Copy link
Contributor Author

qgib commented Mar 20, 2018

Author Name: René-Luc ReLuc (@rldhont)


I'm waiting for #6644


  • version was changed from 3.1(master) to 3.0.0

@qgib
Copy link
Contributor Author

qgib commented Mar 21, 2018

Author Name: Alessandro Pasotti (@elpaso)


Merged: let me know if you need help.

@qgib
Copy link
Contributor Author

qgib commented Jun 14, 2018

Author Name: Alessandro Pasotti (@elpaso)


Can we close this one?

@qgib
Copy link
Contributor Author

qgib commented Dec 27, 2018

Author Name: Nyall Dawson (@nyalldawson)


  • status_id was changed from Feedback to Closed
  • resolution was changed from to no timely feedback

@qgib qgib closed this as completed Dec 27, 2018
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Server Related to QGIS server Regression Something which used to work, but doesn't anymore labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Regression Something which used to work, but doesn't anymore Server Related to QGIS server
Projects
None yet
Development

No branches or pull requests

1 participant