schema-element function Parameter discussion

Copyright © 2010 Open Geospatial Consortium 35 EXAMPLE 2 typeNames=myns:Feat1 myns:Feat1 aliases=a b This XML-encoded example show the encoding of the typeName parameter. The first feature type, myns:Feat1, is aliased to the name a and the second feature type, myns:Feat1, is aliased to the name b. Thus properties from the first instance of myns:Feat1 can be referenced in a request as aproperty_name and properties from the second instance of myns:Feat1 can be referenced in a request as bproperty_name where the token property_name is used as a place holder for the name of any property of the feature myns:Feat1.

7.9.2.4.4 srsName parameter

The optional srsName attribute may be used to assert a specific WFS-supported CRS transformation to be applied to the geometries of the features returned in a response document. The value of the srsName parameter may be the wfs:DefaultCRS or any of the wfs:OtherCRS values listed for the feature type in a servers capabilities document see 8.3.3. If no srsName value is supplied, then the feature geometries shall be encoded in the response document using the advertised wfs:DefaultCRS value. This attribute has no meaning for feature types with no spatial properties and shall be ignored. Servers that advertise more than one wfs:OtherCRS value in their capabilities document see 8.3.3 shall be able to transform between the CRS used to store features and any CRS requested using the srsName attribute. Servers that implement this International Standard shall be able to process srsName attribute values using the following format model: urn:ogc:def:objectType:authority:version:EPSG code see OGC 07-092r2 In this format model, objectType shall have the value of crs, authority shall have the value crs and the value EPSG Code is a placeholder for the actual EPSG code value. EXAMPLE srsName=urn:ogc:def:crs:EPSG::26986”.

7.9.2.4.5 Projection clause

7.9.2.4.5.1 Request Semantics

Every feature representation generated by a WFS shall include all the mandatory properties for the feature type according to the schema description see Clause 9, and then may include a selection of the other properties, according to the schema description. The projection clause enumerates which of the non-mandatory properties of a feature shall be included in the response to a query.