Bug report #1589
problem visualizing WMS defined with a EPSG:NONE srs
|Category:||Web Services clients/WMS|
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||duplicate|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||11649|
Hello all !
We have small problem, with our WMS service and qGis.
We expose some data in WMS, but we have a customized reference system,
so we don't have a standard EPSG number.
We expose, then, these data with the "EPSG: NONE" declaration.
We are aware that the OGC directive on the WMS 1.1.1 defines only the
declaration "SRS=NONE", but in the Esri products (WMS server and
client) define the SRS="EPSG:NONE" declaration (for the 9.2 version)
and SRS="EPSG:0" for the 9.3 version.
For example, if I call a WMS with this layer definition in his
<LatLonBoundingBox minx="9.1600714390999993" miny="43.672498615800002"
maxx="12.9109804049" maxy="45.156071086600001" />
<BoundingBox SRS="EPSG:NONE" minx="512973.566244238" miny="842599.75"
maxx="807851.62554267596" maxy="1000499.3733534738" />
<Abstract>158_UTMA_ORTOAGEA2008 (Cellsize=0.5, BitsPerPixel=8)</Abstract>
then qGis calls this layer with this request:
It seems that qGis is not recognizing the EPSG:NONE, while with others
WMS clients (ArcMap, Gaia, uDig, GvSig) this layer is requested
calling the EPSG:NONE and it is visualized correctly.
Would be nice that also qGis keeps the SRS definition in the
Capabilities file and calls the request GetMap with that SRS.