Incorrect CRS axis order

[asedgmen]

• datacube-wms version: Testing carried out using WMS endpoint http://wms.datacube.org.au
• Python version: N/A
• Operating System: N/A

Description

Service does not adhere to EPSG coordinate axis order specifications, a requirement introduced in WMS 1.3.0 (most geographic CRSs in the EPSG database specify an axis order of y,x rather than x,y order used for all CRSs in WMS versions prior to 1.3.0).

Incorrect coordinate axis order in WMS 1.3.0 GetCapabilities document BoundingBox elements with CRS=”EPSG:4326”, e.g:
<BoundingBox CRS="EPSG:4326" minx="129.28" maxx="136.42" miny="-32.81" maxy="-10.51" />
should be
<BoundingBox CRS="EPSG:4326" minx="-32.81" maxx="-10.51" miny="129.28" maxy="136.42" />

BBOX URL parameter in WMS 1.3.0 GetMap requests for EPSG:4326 should be of form:
BBOX=<min_lat>,<min_lon>,<max_lat>,<max_lon>
Although this service only accepts requests with the following (incorrect) form:
BBOX=<min_lon>,<min_lat>,<max_lon>,<max_lat>

What I Did

Issue was identified using an in-house conformance testing script, and by physically inspecting the GetCapabilities statement at http://wms.datacube.org.au/?service=WMS&request=GetCapabilities. The issue was confirmed by attempting to make GetMap requests against the service, both manually in a browser and using QGIS.

Example GetMap request - incorrect BBOX axis order, image returned:
http://wms.datacube.org.au/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&LAYERS=ls8_level1_usgs__110&STYLES=&WIDTH=1000&HEIGHT=1000&FORMAT=image/png&CRS=EPSG:4326&DPI=120&MAP_RESOLUTION=120&FORMAT_OPTIONS=dpi:120&TRANSPARENT=TRUE&BBOX=121.8,-24.8,122.48,-24.18

Same request with correct BBOX axis order, no image returned:
http://wms.datacube.org.au/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&LAYERS=ls8_level1_usgs__110&STYLES=&WIDTH=1000&HEIGHT=1000&FORMAT=image/png&CRS=EPSG:4326&DPI=120&MAP_RESOLUTION=120&FORMAT_OPTIONS=dpi:120&TRANSPARENT=TRUE&BBOX=-24.8,121.8,-24.18,122.48

[SpacemanPaul]

Fixed in commit 51852f6

Requires manually specifying "vertical_coord_first": True for EPSG:4326 in the service config. See wms_cfg_example.py.