Re: [mapserver-users] use of srsName in wfs 1.1

2009-10-22 Thread Yewondwossen Assefa
Martin Kofahl wrote: ... leads to msWFSGetFeature(): WFS server error. Invalid GetFeature Request: SRSNAME value should be valid for all the TYPENAMES. Please check the capabilities and reformulate your request. Having the capabilities in mind it's correct as there are no OtherSRS listed. But

Re: [mapserver-users] use of srsName in wfs 1.1

2009-10-21 Thread Martin Kofahl
Oct 2009 15:32:21 +0300 Von: Rahkonen Jukka jukka.rahko...@mmmtike.fi An: Martin Kofahl m.kof...@gmx.net, mapserver-users@lists.osgeo.org Betreff: Re: [mapserver-users] use of srsName in wfs 1.1 Hi, It would be much easier to repeat your situation if you could mail us the whole GetFeature

[mapserver-users] use of srsName in wfs 1.1

2009-10-20 Thread Martin Kofahl
Hi, I'm interested in querying a MapServer 5.6-beta4 WFS 1.1 service with different projection parameters. According to chapter 14.3.3 of the wfs 1.1 spec one can define different reference systems for the bbox (GET-style) bbox=4393767,5877790,4673506,6071483,epsg:31468 and for the gml

Re: [mapserver-users] use of srsName in wfs 1.1

2009-10-20 Thread Rahkonen Jukka
Hi, It would be much easier to repeat your situation if you could mail us the whole GetFeature requests you have been trying. First thing that comes into my mind is that it would be good to try to follow the standard text as strictly as possible. For example, while using epsg:31469 instead of

Re: [mapserver-users] use of srsName in wfs 1.1

2009-10-20 Thread Yewondwossen Assefa
Martin, The BBOX parameter at this time only supports reading the upper and lower coordinates and is missing the reading of the optional srs parameter. I have added a bug on ot and will add it in the coming weeks (http://trac.osgeo.org/mapserver/ticket/3183) Note that you should be also able