<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""></blockquote>Dear all,<br class="">I am facing a serious problem with Mapserver (both 6.2 and 6.4.1) and data retrieval via WFS 1.1.0.<br class="">We have a client running which is taking the data as GML and importing it into GRASS. The switched order of axis makes it impossible to overlay and thus process data.<br class=""><font color="#5856d6" class=""><br class=""></font>The following request gets back data in yx axis order:<br class=""><font color="#5856d6" class=""><br class=""></font><a href="http://mapservices-ludwigsburg.tudor.lu/cgi-bin/mapserv?map=/srv/mapserv/ludwigsburg/map_file/LB_MUSIC_OWS.map&" class="">http://mapservices-ludwigsburg.tudor.lu/cgi-bin/mapserv?map=/srv/mapserv/ludwigsburg/map_file/LB_MUSIC_OWS.map&</a><br class="">SERVICE=WFS&<br class="">VERSION=1.1.0&<br class="">REQUEST=GetFeature&<br class="">TYPENAME=LB_city_boundary&<br class="">BBOX=48,9,49,10,urn:x-ogc:def:crs:EPSG::4326&<br class="">SRSNAME=EPSG:31467<br class=""><font color="#5856d6" class=""><br class=""></font>I wonder if this is a bug or feature due to the WFS 1.1.0 axis order specification?<br class=""><font color="#5856d6" class=""><br class=""><br class=""></font>If I send the same request to a instance of Geoserver, what I get back is xy axis order:<br class=""><font color="#5856d6" class=""><br class=""></font><a href="http://geoserver.tudor.lu/geoserver/ludwigsburg/ows?SERVICE=wfs&" class="">http://geoserver.tudor.lu/geoserver/ludwigsburg/ows?SERVICE=wfs&</a><br class="">VERSION=1.1.0&<br class="">REQUEST=GetFeature&<br class="">TYPENAME=ludwigsburg:lb_city_boundary&<br class="">BBOX=48,9,49,10,urn:x-ogc:def:crs:EPSG::4326&<br class="">SRSNAME=EPSG:31467<br class=""><font color="#5856d6" class=""><br class=""></font>I also found the master thesis of Weichand [1] where in Section 4.3.5 he is describing this issue as well. But Geoserver has a mechanism to treat EPSG:31467 as xy. The correct order of the CRS (by definition) is yx, but this is not used like that in Germany.<br class=""><font color="#5856d6" class=""><br class=""></font>Can you give any ideas about the behaviour of Mapserver and how to get around this axis order issue?<br class=""><font color="#5856d6" class=""><br class=""></font>Thanks,<br class="">Christian Braun<br class=""><font color="#5856d6" class=""><br class=""><br class=""></font>Luxembourg Institute of Science and Technology (LIST)<br class="">Environmental Research and Innovation (ERIN) Department<br class="">41, rue du Brill<br class="">L-4422 Belvaux<br class=""><font color="#5856d6" class=""><br class=""></font>Tel: +352 42 59 91 - 6608<br class="">Fax : +352 275 885<br class="">E-mail : <a href="mailto:christian.braun@list.lu" class="">christian.braun@list.lu</a><br class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div apple-content-edited="true" class=""><div class="" style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Web: <a href="http://www.list.lu/" class="">www.list.lu</a></div></div></div></div><br class=""></body></html>