📄 wfs.xsd
字号:
response to a GetFeature request, a Web Feature Service must be able to generate a GML3 response that validates using a schema generated by the DescribeFeatureType request. A Web Feature Service may support other possibly non-XML (and even binary) output formats as long as those formats are advertised in the capabilities document. </xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:extension base="wfs:BaseRequestType"> <xsd:sequence> <xsd:element ref="wfs:Query" maxOccurs="unbounded"/> </xsd:sequence> <xsd:attribute name="resultType" type="wfs:ResultTypeType" use="optional" default="results"> <xsd:annotation> <xsd:documentation> The resultType attribute is used to indicate what response a WFS should return to user once a GetFeature request is processed. Possible values are: results - meaning that the full response set (i.e. all the feature instances) should be returned. hits - meaning that an empty response set should be returned (i.e. no feature instances should be returned) but the "numberOfFeatures" attribute should be set to the number of feature instances that would be returned. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="outputFormat" type="xsd:string" use="optional" default="text/xml; subtype=gml/3.1.1"> <xsd:annotation> <xsd:documentation> The outputFormat attribute is used to specify the output format that the Web Feature Service should generate in response to a GetFeature or GetFeatureWithLock element. The default value of 'text/xml; subtype=gml/3.1.1' indicates that the output is an XML document that conforms to the Geography Markup Language (GML) Implementation Specification V3.1.1. For the purposes of experimentation, vendor extension, or even extensions that serve a specific community of interest, other acceptable output format values may be used to specify other formats as long as those values are advertised in the capabilities document. For example, the value WKB may be used to indicate that a Well Known Binary format be used to encode the output. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="maxFeatures" type="xsd:positiveInteger" use="optional"> <xsd:annotation> <xsd:documentation> The maxFeatures attribute is used to specify the maximum number of features that a GetFeature operation should generate (regardless of the actual number of query hits). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="traverseXlinkDepth" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> This attribute indicates the depth to which nested property XLink linking element locator attribute (href) XLinks are traversed and resolved if possible. A value of "1" indicates that one linking element locator attribute (href) Xlink will be traversed and the referenced element returned if possible, but nested property XLink linking element locator attribute (href) XLinks in the returned element are not traversed. A value of "*" indicates that all nested property XLink linking element locator attribute (href) XLinks will be traversed and the referenced elements returned if possible. The range of valid values for this attribute consists of positive integers plus "*". If this attribute is not specified then no xlinks shall be resolved and the value of traverseXlinkExpiry attribute (if it specified) may be ignored. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="traverseXlinkExpiry" type="xsd:positiveInteger" use="optional"> <xsd:annotation> <xsd:documentation> The traverseXlinkExpiry attribute value is specified in minutes. It indicates how long a Web Feature Service should wait to receive a response to a nested GetGmlObject request. This attribute is only relevant if a value is specified for the traverseXlinkDepth attribute. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:simpleType name="ResultTypeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="results"> <xsd:annotation> <xsd:documentation> Indicates that a complete response should be generated by the WFS. That is, all response feature instances should be returned to the client. </xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="hits"> <xsd:annotation> <xsd:documentation> Indicates that an empty response should be generated with the "numberOfFeatures" attribute set (i.e. no feature instances should be returned). In this manner a client may determine the number of feature instances that a GetFeature request will return without having to actually get the entire result set back. </xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleType> <xsd:element name="Query" type="wfs:QueryType"> <xsd:annotation> <xsd:documentation> The Query element is used to describe a single query. One or more Query elements can be specified inside a GetFeature element so that multiple queries can be executed in one request. The output from the various queries are combined in a wfs:FeatureCollection element to form the response document. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexType name="QueryType"> <xsd:annotation> <xsd:documentation> The Query element is of type QueryType. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:choice minOccurs="0" maxOccurs="unbounded"> <xsd:element ref="wfs:PropertyName"> <xsd:annotation> <xsd:documentation> The Property element is used to specify one or more properties of a feature whose values are to be retrieved by a Web Feature Service. While a Web Feature Service should endeavour to satisfy the exact request specified, in some instance this may not be possible. Specifically, a Web Feature Service must generate a valid GML3 response to a Query operation. The schema used to generate the output may include properties that are mandatory. In order that the output validates, these mandatory properties must be specified in the request. If they are not, a Web Feature Service may add them automatically to the Query before processing it. Thus a client application should, in general, be prepared to receive more properties than it requested. Of course, using the DescribeFeatureType request, a client application can determine which properties are mandatory and request them in the first place. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element ref="wfs:XlinkPropertyName"/> <xsd:element ref="ogc:Function"> <xsd:annotation> <xsd:documentation> A function may be used as a select item in a query. However, if a function is used, care must be taken to ensure that the result type matches the type in the </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:choice> <xsd:element ref="ogc:Filter" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> The Filter element is used to define spatial and/or non-spatial constraints on query. Spatial constrains use GML3 to specify the constraining geometry. A full description of the Filter element can be found in the Filter Encoding Implementation Specification. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element ref="ogc:SortBy" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> The SortBy element is used specify property names whose values should be used to order (upon presentation) the set of feature instances that satisfy the query. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> <xsd:attribute name="handle" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> The handle attribute allows a client application to assign a client-generated identifier for the Query. The handle is included to facilitate error reporting. If one Query in a GetFeature request causes an exception, a WFS may report the handle to indicate which query element failed. If the a handle is not present, the WFS may use other means to localize the error (e.g. line numbers). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="typeName" type="wfs:TypeNameListType" use="required"> <xsd:annotation> <xsd:documentation> The typeName attribute is a list of one or more feature type names that indicate which types of feature instances should be included in the reponse set. Specifying more than one typename indicates that a join operation is being performed. All the names in the typeName list must be valid types that belong to this query's feature content as defined by the GML Application Schema. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="featureVersion" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> For systems that implement versioning, the featureVersion attribute is used to specify which version of a particular feature instance is to be retrieved. A value of ALL means that all versions should be retrieved. An integer value 'i', means that the ith version should be retrieve if it exists or the most recent version otherwise. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="srsName" type="xsd:anyURI" use="optional"> <xsd:annotation> <xsd:documentation> This attribute is used to specify a specific WFS-supported SRS that should be used for returned feature geometries. The value may be the WFS StorageSRS value, DefaultRetrievalSRS value, or one of AdditionalSRS values. If no srsName value is supplied, then the features will be returned using either the DefaultRetrievalSRS, if specified, and StorageSRS otherwise. For feature types with no spatial properties, this attribute must not be specified or ignored if it is specified. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:complexType> <xsd:simpleType name="Base_TypeNameListType"> <xsd:list itemType="xsd:QName"/> </xsd:simpleType> <xsd:simpleType name="TypeNameListType"> <xsd:restriction base="wfs:Base_TypeNameListType"> <xsd:pattern value="((\w:)?\w(=\w)?){1,}"> <xsd:annotation>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -