Incorrect axis order in GetCaps BoundingBox

[asedgmen]

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

Description

This is a re-submission of the axis order problem reported in issue #4, whereby the coordinate axis order in WMS 1.3.0 GetCapabilities document BoundingBox elements with CRS=”EPSG:4326” is incorrect, 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" />

What I Did

I inspected the GetCapabilities statement obtained from https://nrt-au.wms.gadevs.ga/?service=WMS&request=GetCapabilities (I understand that this implementation of the WMS has the latest code updates, including changes made when issue #4 was closed).

I believe this is causing the WMS layers to fail to load in QGIS, as it appears to use the BoundingBox elements to determine how to make the GetMap requests.

[SpacemanPaul]

Oh I see. Previous fix just addressed the coordinate ordering in the BBOX request parameter.

Commit 325ce9f addresses the coordinate ordering in the GetCaps response.