EPSG:6706 WMS wrongly reprojected in 3.10

[pcav]

Layers from
https://wms.cartografia.agenziaentrate.gov.it/inspire/wms/ows01.php
when added to QGIS take EPSG:6706 by default. In QGIS 3.4 they are reprojected correctly, whereas in 3.10 they are not, possibly because of inverted axes. Selecting the relavant options in the connection params does not solve the issue. Adding the same layers as EPSG:3046 is OK.

[pcav]

Confirmed in Debian and Windows.

[pigreco]

confirm

QGIS 3.10.1 OSGeo4W64b

Versione di QGIS 3.10.1-A Coruña
Revisione codice QGIS ef24c526da
Compilato con Qt 5.11.2
Esecuzione con Qt 5.11.2
Compilato con GDAL/OGR 3.0.2
Esecuzione con GDAL/OGR 3.0.2
Compilato con GEOS 3.8.0-CAPI-1.13.1
Esecuzione con GEOS 3.8.0-CAPI-1.13.1 
Compiled against SQLite 3.29.0
Running against SQLite 3.29.0
Versione client PostgreSQL 11.5
Versione SpatiaLite 4.3.0
Versione QWT 6.1.3
Versione QScintilla2 2.10.8
Compiled against PROJ 6.2.1
Running against PROJ Rel. 6.2.1, November 1st, 2019
OS Version Windows 10 (10.0)

[roya0045]

Is this valid for master/nightly or is it only a side effect of the proj transition that will be fixed in the next release?

[pigreco]

the problem is related only to EPSG 6706

OSGeo4W64b master

[gioman]

@pcav @pigreco On Windows I tested:

3.4.14 > GDAL 2.4.3
3.10.1 > GDAL 3.0.2
3.10.1 nightly > GDAL 3.1.0-dev
master > GDAL 3.1.0-dev

in ALL cases activating the option "ignore axis orientation" make the layers (added with CRS 6706) are reprojected to the right place.

This means that also on 3.4.14 without this option active the layers (add with CRS 6706) are not reprojected to the right place.

[rouault]

I don't think this is related at all with PROJ >= 6, but this is just a defect of the server regarding axis order with WMS 1.3.0. If in the URL, you add ?VERSION=1.1.0 things will work

If you look at the https://wms.cartografia.agenziaentrate.gov.it/inspire/wms/ows01.php?SERVICE=WMS&REQUEST=GetCapabilities response (which defaults to WMS 1.3.0), you'll see:

<EX_GeographicBoundingBox>
<westBoundLongitude>6</westBoundLongitude>
<eastBoundLongitude>19</eastBoundLongitude>
<southBoundLatitude>35</southBoundLatitude>
<northBoundLatitude>48</northBoundLatitude>
</EX_GeographicBoundingBox>
<BoundingBox CRS="EPSG:6706" minx="6" miny="35" maxx="19" maxy="48"/>

The BoundingBox is incorrect. In WMS 1.3.0, the BoundingBox should take into account EPSG axis order, so minx should be the minimum latitude whereas here it is longitude. So basically this server declares WMS 1.3.0 capabilities but got axis order wrong (at least for EPSG:6706)

[gioman]

Closing as invalid?

[pigreco]

@rouault thank you

URL:

https://wms.cartografia.agenziaentrate.gov.it/inspire/wms/ows01.php?VERSION=1.1.0

[pcav]

thanks a lot @rouault !
sorry for the noise