[mapserver-users] WFS 1.1.0 Namespace quirk for PropertyName attribute restricting

[bteluk at gmail.com]

Hi,

I think I've found a quirk in MapServer V5.6.0 WFS behaviour - but I'm not
really sure as I don't understand enough about reading an XSD to know
whether or not this is "expected behaviour".  This particular issue is not
causing me any grief at the moment as I know the work-around, but perhaps it
might be of interest to others.  I noticed the problem when hand-crafting a
WFS request for an Intersect Filter - I specified some PropertyName elements
at the head of the request in order to retrieve only a select set of
attributes.  I specified the namespace (because I based the XML on what I
read in the WFS 1.1.0 recommendation) and because it had apparently worked
in another previous request.  However this time it didn't work in as much as
the request responded with only the spatial data and not the attributes. 
With a bit of mucking around I noticed that apparently this version of
MapServer allows namespace to be specified on "PropertyName" elements within
the "Filter" section, but not outside it.  My XML below:



The XML above works fine and responds with the spatial info and the
attributes.  However, if you code the namespace into say the elements like
"<wfs:PropertyName>ms:esa_code</wfs:PropertyName>" - it no longer returns
the attributes (and yet it works fine if the namespace is removed.)

I think if I read ticket 1350 correctly, it indicates the MSv5.2 strips out
namespaces ?  Maybe that was changed later?

It's not really a problem to me.  But just a quirk that took me a hour or
two of mucking around to find what caused the problem.

(Is there a recommended approach on writing WFS XML requests for MapServer
eg. should all namespaces be removed?)

-----
Regards, Bill Teluk
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/WFS-1-1-0-Namespace-quirk-for-PropertyName-attribute-restricting-tp6842768p6842768.html
Sent from the Mapserver - User mailing list archive at Nabble.com.