You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reporter: assefa Date: 2010/02/16 - 18:07 Trac URL:http://trac.osgeo.org/mapserver/ticket/3319
WFS 1.1 GetFeature request uses the Propertyname parameter to retrive non-mandatory attributes.
section 9.2 of the WFS 1.1.0 specs (OGC 04-094)
"The response to a GetFeature request must be valid according to the structure described by the XML Schema description of the feature type. Thus the WFS must report all the mandatory properties of each feature, as well any properties requested through the wfs:PropertyName element. In the event that a WFS encounters a query that does not select all mandatory properties of a feature, the WFS will internally augment the property name list to include all mandatory property names. A WFS client must thus be prepared to deal with a situation where it receives more property values than it requests through wfs:PropertyName elements."
Right now we do not have any mechanism to allow use to specify mandatory and optional attributes (we use what is specified in gml_inlcide/exclude_items, to list the attributes in a DescriberDeature).
When a PROPERTYNAME parameter is sent witha GetFeature, It basically over-writes the gml_include metadata.
The text was updated successfully, but these errors were encountered:
Reporter: assefa
Date: 2010/02/16 - 18:07
Trac URL: http://trac.osgeo.org/mapserver/ticket/3319
WFS 1.1 GetFeature request uses the Propertyname parameter to retrive non-mandatory attributes.
section 9.2 of the WFS 1.1.0 specs (OGC 04-094)
"The response to a GetFeature request must be valid according to the structure described by the XML Schema description of the feature type. Thus the WFS must report all the mandatory properties of each feature, as well any properties requested through the wfs:PropertyName element. In the event that a WFS encounters a query that does not select all mandatory properties of a feature, the WFS will internally augment the property name list to include all mandatory property names. A WFS client must thus be prepared to deal with a situation where it receives more property values than it requests through wfs:PropertyName elements."
Right now we do not have any mechanism to allow use to specify mandatory and optional attributes (we use what is specified in gml_inlcide/exclude_items, to list the attributes in a DescriberDeature).
When a PROPERTYNAME parameter is sent witha GetFeature, It basically over-writes the gml_include metadata.
The text was updated successfully, but these errors were encountered: