Bug report #4443

WMS 1.3.0 axis order

Added by Jeff Konnen about 13 years ago. Updated about 12 years ago.

Status:Closed
Priority:High
Assignee:Marco Hugentobler
Category:QGIS Server
Affected QGIS version:master Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:fixed
Crashes QGIS or corrupts data:No Copied to github as #:14375

Description

In WMS 1.3.0 the axis order of a lot of SRS has changed.

Several GIS Packages have been modified to correctly implement WMS 1.3.0 with regard to the changed axis orders.
The ones I know that are correct as of today is ArcGIS 10 and Mapserver 6.

qGIS does not seem to have implemented the correct definition of the axis orders.

(cf http://trac.osgeo.org/mapserver/ticket/3582)

WMS - Services served with Mapserver 6 or ArcGIS Server 10 in one of the concerned SRS (e.g. EPSG:2169 for me) are not displayed correctly in qGIS.

The only workaround is to include the version number ?VERSION=1.1.0 in the URL..


Related issues

Related to QGIS Application - Bug report #9345: WMS axis ordering depending on CRS a 2.0 rollout stopper Closed 2014-01-15

History

#1 Updated by Paolo Cavallini almost 13 years ago

  • Category set to Web Services clients/WMS

#2 Updated by Bernhard Ströbl almost 13 years ago

I can add geoserver 2.1 to the list of WMS servers that have changed the axis order for 1.3.0

#3 Updated by Giovanni Manghi almost 13 years ago

  • Target version set to Version 1.7.4

#4 Updated by Giovanni Manghi almost 13 years ago

  • Crashes QGIS or corrupts data set to No
  • Affected QGIS version set to master
  • Assignee set to Marco Hugentobler
  • Category changed from Web Services clients/WMS to QGIS Server

#5 Updated by Paolo Cavallini over 12 years ago

  • Target version changed from Version 1.7.4 to Version 1.8.0

#6 Updated by Jürgen Fischer over 12 years ago

  • Status changed from Open to Feedback

Is this still valid? 949b2f0 could have fixed this.

#7 Updated by Jeff Konnen over 12 years ago

Where can this be tested? In QGIS 1.7.4 the bug is still present

#8 Updated by Jürgen Fischer over 12 years ago

Jeff Konnen wrote:

Where can this be tested? In QGIS 1.7.4 the bug is still present

For nightly builds of master refer to the download page

#9 Updated by Paolo Cavallini about 12 years ago

  • Target version changed from Version 1.8.0 to Version 2.0.0

#10 Updated by Giovanni Manghi about 12 years ago

  • Status changed from Feedback to Closed
  • Resolution set to fixed

Closing for lack of feedback and it should be fixed. Please reopen if necessary.

Also available in: Atom PDF