Behavior might be unstable as msOWSGetEPSGProj() returns a pointer to a character buffer on the local stack frame. While WFS 1.0.0 code uses the result directly the WFS 1.1.0 code uses msOWSGetProjURN() as a wrapper around it which might disrupt the character buffer. I'm wondering how this could ever work at all...
> -----Ursprüngliche Nachricht----- > > If you use &version=1.1.0 you'll see the warnings: > > http://194.66.252.155/cgi- > bin/BGS_OGE_Bedrock_and_Surface_Geology_in2/ows?service=WFS&request=GetCap > abilities&VERSION=1.1.0 > > You are missing the required parameter VERSION in your request. If I add > it to your request I get no warnings: > http://194.66.252.155/cgi- > bin/BGS_OGE_Bedrock_and_Surface_Geology_in2/ows?service=WFS&request=GetCap > abilities&VERSION=1.0.0 _______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
