Opened 13 years ago

#3305 new bug

lat and lon swapped in WMS 1.3.0 GetMap request?

Reported by: johnolulu Owned by: mhugent
Priority: major: does not work as expected Milestone: Version 1.7.0
Component: WMS Version: 1.0.2
Keywords: WMS 1.3.0, empty map Cc: jmaurer@…
Must Fix for Release: No Platform: Windows
Platform Version: Vista 32-bit Awaiting user input: no

Description

When testing my service with WMS 1.3.0 in Quantum GIS, I get a blank map. When switching to WMS 1.1.1 for the same layer, the map is fine:

WMS 1.3.0 URL: http://oos.soest.hawaii.edu/thredds/wms/hioos/roms_forec/hiig/HI-ROMS_Forecast_Model_Run_Collection_best.ncd?service=WMS&version=1.3.0&request=GetCapabilities

WMS 1.1.1 URL: http://oos.soest.hawaii.edu/thredds/wms/hioos/roms_forec/hiig/HI-ROMS_Forecast_Model_Run_Collection_best.ncd?service=WMS&version=1.1.1&request=GetCapabilities

I have tested this layer as version WMS 1.3.0 in other clients successfully (ENVI Zoom and Godiva2) so I suspect it is a bug in Quantum GIS and not with my data (coming through a Unidata THREDDS Data Server). If the bug is the same as what I discovered in Gaia 3, then the following may be the problem: the resulting GetMap request URLs in 1.3.0 have a BBOX parameter with the latitudes and longitudes erroneously swapped. Gaia does not take into account CRS84 (lon/lat) order, but assumes the urn:ogc:def:crs:EPSG::4326 order (lat/lon) instead--which they are now correcting. Possibly Quantum GIS has a similar artifact of spec changes by OGC?

Thanks for your attention to this. Cheers, John Maurer Hawaii Ocean Observing System University of Hawaii at Mano

Change History (0)

Note: See TracTickets for help on using tickets.