WMS 1.0.0-1.1.1 GetCapabilities should skip CRS: codes

[mapserver-bot]

Reporter: dmorissette
Date: 2009/09/15 - 18:33
Trac URL: http://trac.osgeo.org/mapserver/ticket/3126
New CRS:xx codes were introduced in WMS 1.3.0, but Is it okay to return CRS:xx codes in WMS 1.0.0-1.1.1 GetCapabilities as well since those codes did not exist in those versions of the WMS spec?

Should we not filter out all CRS:xx codes in the generation of GetCapabilites for WMS 1.0.0 to 1.1.1?

[mapserver-bot]

Author: nsavard
Date: 2009/09/15 - 20:18
see #2979

[mapserver-bot]

Author: assefa
Date: 2009/09/15 - 20:41
make sense to me.

[jratike80]

WMS 1.1.1 specifies only EPSG and AUTO namespaces. It does not directly deny the use of other namespaces so perhaps including CRS:84 in the WMS 1.1.1 GetCapabilities in not a critical bug.

What is critical is that if WMS client is picking CRS:84 from the list or supported SRSs the service will fail with GetMap:

localhost:8060/cgi-bin/mapserv.exe?map=c:/ms4w/apps/wms-wfs.map&REQUEST=GetMap&SERVICE=WMS&VERSION=1.1.1&WIDTH=1204&HEIGHT=605&LAYERS=states_table&TRANSPARENT=TRUE&FORMAT=image%2Fpng&BBOX=-125.96365349999999,22.032190226328904,-65.73714650000001,52.295509773671085&SRS=CRS:84&STYLES=

msWMSLoadGetMapParams(): WMS server error. Unsupported SRS namespace (only EPSG and AUTO currently supported)

So we should either filter CRS:84 out as suggested, or to make older WMS versions to work with it.