[mapserver-users] What to do with WMS 1.3.0 and axis order of EPSG:2393?

[Rahkonen Jukka]

Hi,
 
The Finnish KKJ projection EPSG:2393 belongs to those with axis order
Northing-Easting
http://www.epsg-registry.org/report.htm?type=selection&entity=urn:ogc:de
f:crs:EPSG::2393&reportDetail=short&style=urn:uuid:report-style:default-
with-code&style_name=OGP%20Default%20With%20Code&title=EPSG:2393
 
However, Mapserver WMS 1.3.0 from MS version 5.6.5 does not honour the
official axis order but it is assuming the Easting-Northing BBOX also
with WMS 1.3.0. Any suggestions about how to solve this?  In addition to
the two I have, to stay with WMS 1.1.1 or to start using UTM projection
with a real Easting-Northing axis order.
 
Problem is not only with Mapserver, GDAL based clients like QGis are
creating WMS 1.3.0 request with Easting-Northing BBOX for EPSG:2393.
Good is that QGIS and Mapserver play nicely together with WMS 1.3.0.
Bad is that it is not a fair play because they  both are fooling with
the rules.
 
I was wondering if this could be handled somehow in a similar way than
Geoserver and deegree are doing it.  They are following the traditional
Easting-Northing axis order if CRS is given as EPSG:2393.  But if CRS is
given as 
urn:ogc:def:crs:EPSG::2393 they are using the axis order that is defined
in the EPSG database.  This is a little bit fiddling with the standard,
but the urn-format is the official one and the alternative short format
gives better possibilities for success for the end user of ready made
WMS/WFS clients.
 
-Jukka Rahkonen-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20101124/588b5937/attachment.htm>