Opened 14 years ago

Last modified 14 years ago

#3319 new defect

WFS 1.1 property names, mandatory, optional attributes

Reported by: assefa Owned by: mapserverbugs
Priority: normal Milestone:
Component: WFS Server Version: unspecified
Severity: normal Keywords:
Cc: nsavard, tomkralidis

Description

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.

Change History (2)

comment:1 by nsavard, 14 years ago

Post request: wfs-1.1.0-Basic-GetFeature-tc16.4

comment:2 by nsavard, 14 years ago

Also the following post requests:

wfs-1.1.0-Basic-GetFeature-tc5.2 wfs-1.1.0-Basic-GetFeature-tc5.3 wfs-1.1.0-Basic-GetFeature-tc15.1 wfs-1.1.0-Basic-GetFeature-tc35.5

Note: See TracTickets for help on using tickets.