Standard resolve parameters Parameter discussion

38 Copyright © 2010 Open Geospatial Consortium A value specified for the resolvePath parameter shall only be used if the value of the nearest in scope resolve parameter is not set to none. If the value of the nearest resolve attribute is set to none any value specified for the resolvePath parameter shall be ignored. The value of the resolvePath parameter is a path expression but its specific encoding depends on how features are encoded. For GML, which is the canonical feature encoding in this International Standard, the value of the resolutionPath parameter shall be an XPath see W3C XML Path Language expression that results in an object element. Value resolution shall stop at these instances and the value of the resolveDepth parameter shall be ignored. EXAMPLE 1 The following is an example of the resolvePath attribute used in a query on the feature type Parcel: Feature Instance examples: Parcel gml:id=DEXXXX00000000 registerEntry LandRegisterEntry gml:id=DEXXXX00000001 relatedTo xlink:href=DEXXXX00000002 LandRegisterEntry registerEntry Parcel LandRegisterEntry gml:id=DEXXXX00000002 sequenceNumber1sequenceNumber LandRegisterEntry Query example: wfs:Query typeNames=Parcel wfs:PropertyName resolve=all resolvePath=valueOfrelatedTovalueOfregisterEntrywfs:PropertyName fes:Filter -- some filter expression -- fes:Filter wfs:Query Specifying the resolvePath attribute has the effect that besides all the Parcel features meeting the criteria, also all their associated LandRegisterEntry features and the LandRegisterEntry features associated with them along the “relatedTo” property are returned, as well. If the schema-element function is supported by a server in XPath expressions, it shall also be supported in resolvePath parameter. If used, it shall match not only the element name that is the parameter of the schema- element function, but also all elements directly or indirectly in its substitution group. EXAMPLE 2 schema-elementgml:AbstractFeature would match all features.

7.9.2.5 Selection clause

7.9.2.5.1 XML Encoding

For XML-encoded requests, the selection clause shall be encoded using the fes:Filter element see ISO 19143, Clause 7.

7.9.2.5.2 KVP encoding

For KVP-encoded requests the selection clause shall be encoded using one of the keywords FILTER, RESOURCEID or BBOX see ISO 19143, Table 2.