Add gml description and name support for a WFS 1.0.0 GetFeature and DescribeFeatureType requests

[nsavard]

When a GetFeature or DescribeFeatureType request is sent to a WFS 1.0.0 server, the gml description and name must be sent in the response. These elements are described in the AbstractFeatureType class of ​http://schemas.opengis.net/gml/2.1.2/feature.xsd.

We need to add two metadata (something like): ows_description_item and ows_name_item.

[nsavard]

To be compliant we need that a layer extends base="gml:AbstractFeatureType"> (see "layer defined in dataFeatures.xsd") which in turn defines description and name elements (see "AbstractFeatureType in feature.xsd").

GetFeature should look like this:

<gml:featureMember>

<cdf:Other fid="Other.1">

<gml:description>A layer defined in dataFeatures.xsd</gml:description> <gml:name>A layer defined in dataFeatures.xsd</gml:name> <gml:boundedBy>

<gml:Box srsName="EPSG:32615">

<gml:coordinates>500050.000000,500050.000000 500050.000000,500050.000000</gml:coordinates>

</gml:Box>

</gml:boundedBy> <gml:pointProperty> <gml:Point srsName="EPSG:32615">

<gml:coordinates>500050.000000,500050.000000</gml:coordinates>

</gml:Point> </gml:pointProperty> <cdf:string1>always</cdf:string1> <cdf:string2>sometimes</cdf:string2> <cdf:integers>7</cdf:integers> <cdf:dates>2002-12-02</cdf:dates>

</cdf:Other>

</gml:featureMember>

---

AbstractFeatureType in feature.xsd:

<complexType name="AbstractFeatureType" abstract="true">

<annotation>

<documentation>

An abstract feature provides a set of common properties. A concrete feature type must derive from this type and specify additional properties in an application schema. A feature may optionally possess an identifying attribute ('fid').

</documentation>

</annotation> <sequence>

<element ref="gml:description" minOccurs="0"/> <element ref="gml:name" minOccurs="0"/> <element ref="gml:boundedBy" minOccurs="0"/> <!-- additional properties must be specified in an application schema -->

</sequence> <attribute name="fid" type="ID" use="optional"/>

</complexType>

---

A layer defined in dataFeatures.xsd:

<xsd:complexType name="OtherFeatureType">

<xsd:complexContent>

<xsd:extension base="gml:AbstractFeatureType">

<xsd:sequence>

<xsd:element ref="gml:pointProperty" minOccurs="0"/> <xsd:element name="string1" type="xsd:string"/> <xsd:element name="string2" type="xsd:string" minOccurs="0"/> <xsd:element name="integers" type="xsd:integer" minOccurs="0"/> <xsd:element name="dates" type="xsd:date" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

[tomkralidis]

Norm: both gml:name and gml:description are optional elements from what I can see from within the definition of AbstractFeatureType. Can you confirm that these are indeed required when the schema calls them as optional?

[nsavard]

Replying to tomkralidis:

Norm: both gml:name and gml:description are optional elements from what I can see from within the definition of AbstractFeatureType. Can you confirm that these are indeed required when the schema calls them as optional?

Tom: You're right. I misinterpret the schema. I though eventhough these elements were optionals we have to provide a mechanism for a user to specify a value for them.

[tomkralidis]

Norm: thanks for the verification. Should we close this one, then?

[nsavard]

Replying to tomkralidis:

Norm: thanks for the verification. Should we close this one, then?

Tom: Yes, you can close this one.