GetCapabilities Response |
When the WMTS service is called, the ServiceMetadata is requested through the GetCapabilities operation Resource, WMTS will return a response file containing the service metadata document.
WMTS Capabilities XML mainly includes ServiceIdentification , ServiceProvider , OperationsMetadata , Contents , and Themes . In addition, each service metadata document must also contain a unique version number, as well as the ServiceMetadataURL parameter used to obtain the service metadata. It can also include the Service Metadata document version parameter, UpdateSequence.
ServiceIdentification is the metadata about a specific service, which is an overall description of the service. It contains elements such as ServiceType, ServiceType Version, Title, and some optional elements such as Profile, Abstract, Keywords, Fees, and AccessConstraints.
Table 1 Service Identification elements
| The name of the element | Whether it is required | Description |
| ServiceType |
Yes |
service type. Due to it is a WMTS service, its value is WMTS. |
| ServiceTypeVersion |
Yes |
service type version. There is currently only one version of WMTS, with a value of 1.0.0. |
| Profile |
No |
Identifier for the WMTS Application Profile. This element is not currently supported by SuperMap iServer. |
| Title |
No |
Service title. Can be one or more. |
| Abstract |
No |
Summary of services. Provides a brief description of the server information. |
| Keywords |
No |
Key words. A word or phrase commonly used in the server. |
| Fees |
No |
Cost. If the server has no usage charges, this element can be ignored. If this element is used, "none" (case insensitive) means free, as in "<Fees>none</Fees>". |
| AccessConstraints |
No |
Access restrictions. If no access restrictions are applied by the server, they can be ignored. If this element is used, "none" (case insensitive) indicates no access restrictions, as in "<AccessConstraints>none</AccessConstraints>". If this element is used, the content of the element does not have a precise syntax definition, and the client can display user information and behavior content. |
Service Provider (optional) is information about the service provider, including ProviderName, ProviderSite, and ServiceContact elements.
Table 2 Service Provider elements
| The name of the element | Whether it is required | Description |
| ProviderName |
Yes |
Provider name. It is a unique identifier for the service provider. |
| ProviderSite |
No |
Provider address. |
| ServiceContact |
Yes |
Contact information for the service provider. |
The OperationsMetadata describes all the operations supported in the current service and the URI of the operation request. OperationsMetadata element must contain one or more operation child nodes, one for each operation. The element descriptions for OperationsMetadata are shown in Table 3.
Table 3 Operations Metadata element
| The name of the element | Whether it is required | Description |
| Operation |
Yes |
Operation. It is used to identify the operation supported by the service. Each Operation node corresponds to an operation, which is identified by the name attribute, such as <Operation name="GetCapabilities">. The details of Operation are shown in Table 4 below. |
|
Parameter |
No |
Parameter. Use to specify the valid domain for one or more of the parameters in the operation. The name attribute identifies the parameter name. The valid values for the parameters are given in the Value tag. These parameters may be input or output parameters in the operation, such as <Parameter name="Format"> <Value>text/xml</Value> </Parameter> This element is not supported by SuperMap iServer at this time. |
| Constraint |
No |
Constraints. A restriction on the domain of validity of non-parametric attributes that apply to this server. The name attribute identifies the name of the non-parametric attribute. The qualifying value is given in the Value tag, as in <Constraint name="MaximumLayerLevels"> <Value>5</Value> </Constraint> This element is not supported by SuperMap iServer at this time. |
| ExtendedCapabilities |
No |
Scalability. Regarding the description of the additional capabilities of the server and software, SuperMap iServer does not support this element at this time. |
Each Operation node must contain one or more for this operation DCP (Distributed Computing Platform) information. You can also include Parameter, Constraint, And Metadata parameters.
Table 4 Operation element
| The name of the element | Whether it is required | Description |
| name |
Yes |
Operation name. Each Operation element has an operation name, such as GetCapabilities. The notation is <Operation name="GetCapabilities">. |
| DCP |
Yes |
Information of the distributed computing platform of the operation. Each Operation element can contain one or more DCP nodes. Currently, only DCP nodes defined HTTP DCP, so each Operation contains only one DCP node, HTTP. Typically, one of the WMTS services HTTP node should contain at least a Get and/or a Post node indicating the request methods supported by the service. See Table 5 for the details of each request method element. |
| Parameter |
No |
Parameter. Use to specify the valid domain for one or more of the parameters in the operation. The name attribute identifies the parameter name. The valid values for the parameters are given in the Value tag. These parameters may be input or output parameters in the operation, such as <Parameter name="Format"> <Value>text/xml</Value> </Parameter> If a valid domain for a parameter is specified in a concrete Operation, the valid domain of the OperationsMetadata parameter with the same name will be overwritten. This element is not supported by SuperMap iServer at this time. |
| Constraint |
No |
Constraint. A restriction on the domain of validity of non-parametric attributes that apply to this server. The name attribute identifies the name of the non-parametric attribute. The qualifying value is given in the Value tag, as in <Constraint name="MaximumLayerLevels"> <Value>5</Value> </Constraint> If the valid domain of a non-parameter attribute is restricted in a specific Operation, the valid domain limit of the OperationsMetadata parameter for a non-parameter attribute with the same name will be overridden. This element is not supported by SuperMap iServer at this time. |
| Metadata |
No |
Metadata. Metadata about the current operation and its implementation. This element is not supported by SuperMap iServer at this time. |
Table 5 Elements of the request method
| The name of the element | Description |
| URI | URI. The client accesses the service through this address. This element is required. |
| Constraint | Limitations. Restriction on valid domains for non-parametric attributes that apply to this server. You must include a restriction on the encoding method, that is, you must include a Constraint element of GetEncoding or PostEncoding. If the request method is Get, the name Is GetEncoding. If the request method is Post, the name is PostEncoding. If the valid domain of a nonparametric attribute is restricted in the request method, the valid domain limit of the non-parameter attribute in OperationsMetadata with the same name will be overridden. |
An example of a DCP element is as follows:
<ows:DCP>
<ows:HTTP>
<ows:Get xlink:href="http://localhost:8090/iserver/services/map-world/wmts100">
<ows:Constraint name="GetEncoding">
<ows:AllowedValues>
<ows:Value>RESTful</ows:Value>
</ows:AllowedValues>
</ows:Constraint>
</ows:Get>
</ows:HTTP>
</ows:DCP>
Contents is an overall description of the layers available in the service, including Layer, OtherSource, and TileMatrixSet three child elements.
Table 6 Contents element
| The name of the element | Whether it is required | Description |
| Layer |
No |
Layer. Each map corresponds to a layer, which is an optional parameter, but only if the parameter OtherSource is included and those services are available, the Layer parameter can be empty. Each layer corresponds to a tile matrix set, and the sub-elements of Layer are detailed in Table 7. |
| OtherSource |
No |
Other sources. It is a reference to another service data source. This parameter is not yet supported by SuperMap iServer. |
| TileMatrixSet |
No |
Set of tile matrices. It is a description of the tile geometry. Its sub-elements are detailed in Table 8. |
Table 7 Layer Element
| The name of the element | Whether it is required | Description |
| Identifier |
Yes |
Identifier. That is, the name of the layer, the identifier is unique. |
| Title |
No |
Title. |
| Abstract |
No |
Summary. A short description of the current layer. |
| Keywords |
No |
Key words. Common words and phrases that describe the current dataset. |
| WGS84BoundingBox |
No |
WGS 84 bounding box. The smallest rectangle defined in the WGS 84 coordinate system that encloses the data set, expressed in latitude and longitude coordinates, with longitude first. The WGS 84 bounding box may be approximate, but should be as accurate as possible. |
| BoundingBox |
No |
Bounding box. The smallest rectangle that encloses the layer in the supported coordinate system. |
| Style |
Yes |
Style. See Table 9 for a description of the style applied to the layer. |
| Format |
Yes |
Format. Supported tile output formats, such as JPG. Can be in multiple formats. |
| InfoFormat |
No |
Feature information format. The supported output format for FeatureInfo documents, and is an optional parameter. If InfoFormat is not specified, the layer cannot be requested. |
| Dimension |
No |
Dimension. Applies to multidimensional data. This element is not supported by SuperMap iServer at this time. |
| Metadata |
No |
Metadata. Additional metadata about the current data set. This element is not supported by SuperMap iServer at this time. |
| TileMatrixSetLink |
Yes |
The tile matrix set is linked. It contains the following elements:
|
| ResourceURL |
No |
Resource URL. URL template for a Tile or FeatureInfo resource. It includes format, resourceType, and template. |
Table 8 TileMatrixSet element
| The name of the element | Whether it is required | Description |
| Identifier |
Yes |
Identifier. The name. |
| Title |
No |
Title. |
| Abstract |
No |
Summary. A short description of the tile matrix set. |
| Keywords |
No |
Key words. An unordered list of common words or phrases in the data set. |
| BoundingBox |
No |
Bounding box. The smallest rectangle that encloses the set of tile matrices in the supported coordinate system. |
| SupportedCRS |
Yes |
Supported coordinate systems. |
| WellKnownScaleSet |
No |
Generic matrix set. |
| TileMatrix |
Yes |
The tile matrix. Each tile matrix set can contain one or more tile matrices. |
Table 9 Style Element
| The name of the element | Whether it is required | Description |
| Identifier |
Yes |
Identifier. The name of the style. |
| Title |
No |
Title. |
| Abstract |
No |
Summary. |
| Keywors |
No |
Key words. |
| LegendURL |
No |
Legend URL. Map legend URL appropriate to the current Style. |
| IsDefault |
No |
Default or not. That is, whether the client should specify the style as the first choice. The default value is false. |
Themes is metadata that describes a theme layer. This element is optional. A theme can contain multiple themes. The Themes element contains child elements such as Identifier, Title, Abstract, Keywords, Theme, and LayerRef. SuperMap IServer does not currently support the Themes element.
Table 10 Themes element
| The name of the element | Description |
| Identifier | Identification. It is the name of the thematic map. If the server applies the theme element, it must contain the identifier child element, which is unique. |
| Title | Title. It is an optional parameter. If no title is specified, the client can display the value of the Identifier instead. |
| Abstract | Summary. A short description of the thematic map. It is an optional parameter. |
| Keywords | Key words. A common word or phrase that describes the data set, which is an optional parameter. |
| Theme | Special topic. A description of the sub-layer of the thematic map that can be graded on the server. It is an optional parameter. |
| LayerRef | Layer reference. It is an optional parameter. |
Execute the GetCapabilities operation, and the response result of the request sample is as follows: