Copyright © 2010 Open Geospatial Consortium Inc.
53
Name and example
a
Optionality and use Definition and format
Sample dimensions
b
Optional Value allowed for this dimension
Layer, Style, Format,
Sample dimensions,
TileMatrixSet, TileMatrix, TileRow,
and TileCol
Optionality and use of these parameters SHALL match
those in the corresponding GetTile request described in
Table 29 The values of these parameters
SHALL match those in the corresponding GetTile request
described in Table 29
J
Mandatory Row index of a pixel in the tile
I
Mandatory Column index of a pixel in the tile
InfoFormat
Mandatory Output format of the retrieved
information
a All parameter names are here listed using mostly lower case letters. However, any parameter name capitalization SHALL
be allowed in KVP encoding, see subclause 11.5.2 of OWS Common [OGC 06-121r3]. b
Names for these parameters SHALL be the names indicated in the ServiceMetadata document. Typical examples are Time, Elevation and Band.
Parameters in a GetFeatureInfo request may be specified in any order. However, in order to facilitate the caching mechanisms already available on the web, the parameters
SHOULD be specified in the exact order that appears in Table 30
8.3.2 GetFeatureInfo request HTTP KVP encoding example
An example GetFeatureInfo operation request KVP encoded for HTTP GET is:
http:www.maps.bobmaps.cgi?service=WMTSrequest=GetFeatureInfo version=1.0.0layer=coastlinesstyle=defaultformat=imagepng
TileMatrixSet=WholeWorld_CRS_84 TileMatrix=10mTileRow=1TileCol=3J=86I=132
InfoFormat=applicationgml+xml; version=3.1
8.3.3 GetFeatureInfo HTTP KVP encoding response
The normal response to a valid GetFeatureInfo operation request SHALL be a FeatureInfo document as described in subclause 7.3.1.
8.3.4 GetFeatureInfo HTTP KVP encoding response example
A GetFeatureInfo operation response for the GetFeatureInfo request example in subclause 8.3.1 may look like this:
?xml version=1.0 encoding=UTF-8? ReguralGriddedElevations
xmlns =
http:www.maps.bobetopo2 xmlns:gml
= http:www.opengis.netgml
xmlns:xsi =
http:www.w3.org2001XMLSchema-instance xsi:schemaLocation
= http:www.maps.bobetopo2
GetFeatureInfoExampleSchema.xsd featureMember
GridPoint_etopo2 elevation
503.0 elevation
TileRow 1
TileRow TileCol
2 TileCol
J 86
J I
132 I
GridPoint_etopo2
54
Copyright © 2010 Open Geospatial Consortium Inc. featureMember
ReguralGriddedElevations
8.4 Exceptions in HTTP KVP encoded operations
If an error is detected while processing an operation request encoded with KVP over HTTP, the WMTS server SHALL generate an ExceptionReport element as defined in
clause 8.5 of OWS Common [OGC 06-121r3] and which conforms to the schemas described in Annex B.
9 WMTS using SOAP encoding
A WMTS server SHALL declare support for SOAP encoding for each operation by means of the OperationsMetadata section of its ServiceMetadata document as explained
in subclause 7.1.1.1.1. An example of this practice for GetCapabilities operation can be seen in subclause 9.1.2. Annex F contains information on how to write a WSDL
description document of the service.
9.1 GetCapabilities
9.1.1 GetCapabilities request SOAP encoding
Servers may also implement SOAP encoding using HTTP POST transfer of the GetCapabilities operation request, using SOAP version 1.2 encoding.
9.1.2 GetCapabilities request SOAP encoding example
To request a WMTS ServiceMetadata document, a client could issue the following SOAP encoded GetCapabilities operation request:
?xml version=1.0 encoding=UTF-8? soap:Envelope
xmlns:soap =
http:www.w3.org200305soap-envelope soap:Body
GetCapabilities service
= WMTS
xmlns =
http:www.opengis.netows1.1 AcceptVersions
Version 1.0.0
Version AcceptVersions
AcceptFormats OutputFormat
applicationxml OutputFormat
AcceptFormats GetCapabilities
soap:Body soap:Envelope
9.1.3 GetCapabilities SOAP encoding response
In response to GetCapabilities operation request in SOAP encoding, a WMTS server SHALL generate a document that looks like the one in subclause 7.1.1.3 wrapped in the
SOAP version 1.2 envelope.
