[TinyOWS-users] Inconsistent coordinate order with WFS 1.1.0 and srsName=EPSG:2393

[Rahkonen Jukka]

Hi,

See the output of this:
http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs&version=1.1.0&request=GetFeature&typename=lv:municipalities&srsName=urn:ogc:def:crs:EPSG::2393&maxfeatures=1&propertyname=the_geom

The boundedBy coordinates and geometry coordinates are both in northing-easting order, which is the official definition for 2393 so this output is definitely OK
Compare with
http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs&version=1.1.0&request=GetFeature&typename=lv:municipalities&srsName=EPSG:2393&maxfeatures=1&propertyname=the_geom

BoundedBy comes now still as northing-easting but the geometry is using easting-northings. With EPSG:4326 this seems to be the case already
http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs&version=1.1.0&request=GetFeature&typename=lv:municipalities&srsName=EPSG:4326&maxfeatures=1&propertyname=the_geom

Geoserver folks have decided to output always easting-northings also with WFS 1.1.0 if srsName is given with plain EPSG:xxxx and only consider flipping the coordinates if srsName is given in the urn: style. Deegree is perhaps doing the same but I an not sure. I am not sure either if that it a good or bad thing to do.

Have you ever felt yourself frustrated with this stupid axis order play?

-Jukka Rahkonen-