GetTile request HTTP KVP encoding GetTile request HTTP KVP encoding example

52 Copyright © 2010 Open Geospatial Consortium Inc.

8.2.3 GetTile HTTP KVP encoding response

The normal response to a valid GetTile operation request SHALL be a tile map that complies with the requested parameters and as described in subclause 7.2.1.

8.2.4 GetTile HTTP KVP encoding response example

A GetTile operation response for the GetTile request example in subclause 8.2.1 that corresponds with the ServiceMetadata document shown in subclause 7.1.1.3 is shown on Figure 12. Figure 12 — GetTile response example

8.3 GetFeatureInfo

WMTS servers may support KVP requests for representations of documents furnishing information related to the features at particular pixel positions on particular image Tiles by declaring support for and correctly handling GetFeatureInfo requests.

8.3.1 GetFeatureInfo request HTTP KVP encoding

Servers may implement HTTP GET transfer of the GetFeatureInfo operation request, using KVP encoding. The KVP encoding of the GetFeatureInfo operation request SHALL follow the requirements for operation parameters specified in Table 30 that follows the abstract description specified in Table 25 above. Table 30 — GetFeatureInfo operation request URL parameters Name and example a Optionality and use Definition and format Service=WMTS Mandatory Service type identifier Request=GetFeatureInfo Mandatory Operation name Version=1.0.0 Mandatory Standard and schema version for this operation 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