GetCapabilities Response |
When calling WMTS service, requests the ServiceMetadata resource through GetCapabilities operation, then WMTS will return a response file containing service metadata documents.
WMTS Capabilities XML mainly includes these components of ServiceIdentification, ServiceProvider, OperationsMetadata, Contents and Themes. Moreover, each service metadata document should contain the only one version number, URI parameters getting service metadata (ServiceMetadataURL) and the version parameter of service metadata document (UpdataSequence).
ServiceIdentification is the specific service metadata, a whole description for the service. It consists of ServiceType, ServiceType Version, Title and so on, and also contains some optional elements, such as Profile, Abstract, Keywords, Fees and AccessConstraints.
Table 1 ServiceIdentification elements
Element name | O/M | Description |
ServiceType |
Optional |
Type of the service. Due to WMTS service, its value is WMTS. |
ServiceTypeVersion |
Optional |
Version of the service. Now WMTS has only one version, the value is 1.0.0. |
Profile |
Mandatory |
Identifier of WMTS application introduction. Now SuperMap iServer don't support this element. |
Title |
Mandatory |
Service title. It could be one or multiple. |
Abstract |
Mandatory |
Service abstract. It provides the brief description of relative server informations. |
Keywords |
Mandatory |
Keywords. Common words or phrases in the server. |
Fees |
Mandatory |
Fees. If the server doesn't use fees, this element can be ignored. If using this element, 'none' (case insensitive) means being free, such as '<Fees>none</Fees>'. |
AccessConstraints |
Mandatory |
Access constraints. If the server doesn't use access constraints, it can be ignored. If the server uses this element, 'none' (case insensitive) means no access constrains, such as '<AccessConstraints>none</AccessConstraints>'. If it uses this element, this element doesn't have the accurate grammar definition, and then the user's information and action content can be shown in the client. |
ServiceProvider(optional)is the information about Service Provider, contains elements of ProviderName, ProviderSite , ServiceContact
Table 2 ServiceProvider elements.
Element name | O/M | Description |
ProviderName |
mandatory |
Name of Service Provider. Only one identifier of Service Provider. |
ProviderSite |
Mandatory |
Provider address. |
ServiceContact |
Mandatory |
Contact information of Service Provider. |
OperationsMetadata describes all operations supported by the current service and URI that operations request. OperationsMetadata elements should contain one or multiple Operation nodes, each Operation node corresponding to an operation. The introductions of OperationsMetadata elements are shown in Table 3.
Table 3 OperationsMetadata elements
Element name | O/M | Description |
Operation |
Optional |
Operation. It is used to identify the operations supported by this service, and every Operation node corresponds to one operation, identified by the name attribute, such as <Operation name="GetCapabilities">. The specific details of Operation are shown in Table4. |
Parameter |
Mandatory |
Parameter. It is used to specify the effective range of one or more parameters in the operation, using the name attribute to identify parameters, giving the effective value in the label of Value, and these paramters may be input parameters and output parameters of operations, such as <Parameter name="Format"> <Value>text/xml</Value> </Parameter>. SuperMap iServer doesn't support this element temporarily. |
Constraint |
Mandatory |
Constraint. It corresponds to the effective range constraint of the attributes of all parameters except Parameter in the server, using the name attribute to identify the attribute names of all parameters except Parameter, giving the constraint value in the label of Value, such as <Constraint name="MaximumLayerLevels"> <Value>5</Value> </Constraint>. SuperMap iServer doesn't support this element temporarily. |
ExtendedCapabilities |
Mandatory |
Extended capabilities. It concerns descriptions of additional abilities of the server and the software, and SuperMap iServer doesn't support this element temporarily. |
Each Operation node should contain one or multiple DCP(Distributed Computing Platform) information of this operation. Moreover, it also contains elements of Parameter, Constraint, Metadata.
Table 4 Operation elements
Element name | O/M | Description |
name |
Optional |
Operation name. Each Operation element has an operation name, such as GetCapabilities. The expressional method is <Operation name="GetCapabilities">. |
DCP |
Optional |
Distributed computation platform information of this operation. Each Operation element contains one or multiple DCP nodes, because now only HTTP DCP is defined, each Operation only contains one DCP node, that is, HTTP. Usually, one HTTP node in WMTS service should contain one Get or one Post node at least. Specific information of each request method element is shown in Table 5. |
Parameter |
Mandatory |
Parameter. It is used to specify the effective range of one or multiple parameters in the operation, identifying the parameter name by name attribute, and these parameters may be input parameters and output parameters in the operation, such as <Parameter name="Format"> <Value>text/xml</Value> </Parameter> If the effective range of one parameter is specified in the specific Operation, the effective range of the parameters with the same parameter names in OperationsMetadata will be covered. SuperMap iServer doesn't support this element temporarily. |
Constraint |
Mandatory |
Constraint. It corresponds to the effective range constraint of the attributes of all parameters except Parameter in the server, using name attribute to identify the attribute names of all parameters except Parameter, giving the constraint value in the label of Value, such as <Constraint name="MaximumLayerLevels"> <Value>5</Value> </Constraint> If the effective range of one parameter is specified in the specific Operation, the effective range of the parameters with the same parameter names in OperationsMetadata will be covered. SuperMap iServer doesn't support this element temporarily. |
Metadata |
Mandatory |
Metadata. It concerns current operations and the implementing metadata. SuperMap iServer doesn't support this element temporarily. |
Table 5 Request method elements
Element name | Description |
URI | URI. The client accesses the service through this address, consisting of this elements necessarily. |
Constraint | Constraint. It corresponds to the effective range constraint of the attributes of all parameters except Parameter. It necessarily consists of the encoding mode constraint, that is, the Constraint elements of GetEncoding and PostEncoding. If the request method is Get, name is GetEncoding. If the request method is Post, name is PostEncoding. If some effective range constraint of the attributes of all parameters except Parameter is constrained in the request method, the effective range constraint of the attributes of all parameters except Parameter with the same name in OperationMetadata and Operation will be covered. |
An example of DCP elements is shown below:
<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 are the whole descriptions of the available layer in the service, including three part elements of Layer, OtherSource and TileMatrixSet.
Table 6 Contents elements
Element name | O/M | Description |
Layer |
Mandatory |
Layer. Each map corresponds to one layer, and it is optional, but only when it contains the parameter of OtherSource and these services are available, the parameter of Layer is null. Each Layer corresponds to one tile matrix, seeing Table 7 for part elements of Layer. |
OtherSource |
Mandatory |
Other source. It is a citation of other service data source. SuperMap iServer doesn't support this element temporarily. |
TileMatrixSet |
Mandatory |
Tile Matrix set. It is the description about the geometry of tiles. See Table 8 for its part elements. |
Table 7 Layer elements
Element name | O/M | Description |
Identifier |
Optional |
Identifier. It is the layer name, and it is sole. |
Title |
Mandatory |
Title. |
Abstract |
Mandatory |
Abstract. It is the brief description of the current layer. |
Keywords |
Mandatory |
Keywords. It is the description of common words and phrases of the current dataset. |
WGS84BoundingBox |
Mandatory |
Bounding box of WGS 84. It is the minimum rectangle of the bounding dataset defined in WGS 84 coordinate system, representing by the longitude value and the latitude value, the longitude value ahead. The bounding box of WGS 84 can be the approximate value, but should be as accurate as possible. |
BoundingBox |
Mandatory |
Bounding box. It is the minimum rectangle of the bounding layer in the supportive coordinate system. |
Style |
Optional |
Style. It is the style description of this layer, please see Table 9 for the specific content. |
Format |
Optional |
Format. It is the output format of the supportive tile, such as JPG and so on. It can be multiple formats. |
InfoFormat |
Mandatory |
Element information format. It is the output format of supportive FeatureInfo documents, and an optional parameter. If it doesn't specify InfoFormat, this layer can't be requested. |
Dimension |
Mandatory |
Dimension. It applies to multidimensional data. SuperMap iServer doesn't support this element temporarily. |
Metadata |
Mandatory |
Metadata. It concerns the additional metadata of the current dataset. SuperMap iServer doesn't support this element temporarily. |
TileMatrixSetLink |
Optional |
Link of tile matrix set. It contains elements below:
|
ResourceURL |
Mandatory |
Resource URL. URL templates of resources of Tile or FeatureInfoTile. It contains three part elements of Format, ResourceType and Template. |
Table 8 TileMatrixSet elements
Element name | O/M | Description |
Identifier |
Optional |
Identifier. It is the name. |
Title |
Mandatory |
Title. |
Abstract |
Mandatory |
Abstract. It is the brief description of the tile matrix set. |
Keywords |
Mandatory |
Keywords. It is an unordered list of common words and phrases in datasets. |
BoundingBox |
Mandatory |
Bounding box. It is a minimum rectangle of the bounding tile matrix set in the supportive coordinate system. |
SupportedCRS |
Optional |
Supportive coordinate system. |
WellKnownScaleSet |
Mandatory |
Well-known scale set. |
TileMatrix |
Optional |
Tile matrix. Each tile matrix set can contain one or multiple tile matrix. |
Table 9 Style elements
Element name | O/M | Description |
Identifier |
Optional |
Identifier. It is the style name. |
Title |
Mandatory |
Title. |
Abstract |
Mandatory |
Abstract. |
Keywords |
Mandatory |
Keywords. |
LegendURL |
Mandatory |
Legend URL. It applies to map legend URL of current Style. |
IsDefault |
Mandatory |
Default or not. It is whether the client should set the specified style as the first choice, and false is its default value. |
Themes is the description of the metadata of thematic layer, and this element is optional, one Themes can contain multiple Theme. Themes elements consist of part elements of Identifier, Title, Abstract, Keywords, Theme and LayerRef and so on. Now SuperMap iServer doesn't support elements of Themes.
Table 10 Themes elements
Element name | Description |
Identifier | Identifier. It is the thematic map name, if the server use the Theme elements, it must contain part element of Identifier, and sole. |
Title | Title. It is an optional parameter, if not specify title, the client can show Identifier values to replace. |
Abstract | Abstract. It is the brief description of the thematic map, an optional parameter. |
Keywords | Keywords. It describes common words and phrases of the dataset, and it is an optional parameter. |
Theme | Theme. It describes part layer of the thematic map graded availably in the server, and it is an optional parameter. |
LayerRef | Layer reference. It is an optional parameter. |
Implement GetCapabilities operation, and get Request example request results below: