TGIS_LayerWMTS class

DK11 for Delphi | GisLayerWMTS.TGIS_LayerWMTS | Classes | Constructors | Fields | Methods | Properties

Encapsulation of an OpenGIS WMTS layer.

Available also on: .NET | Java | ActiveX.

// Delphi
type
  TGIS_LayerWMTS = class( TGIS_LayerWebTiles )
  end;

// C++ Builder
class PASCALIMPLEMENTATION TGIS_LayerWMTS : public TGIS_LayerWebTiles
{
};

→ TObject → TGIS_BaseObjectDisposable → TGIS_LayerAbstract → TGIS_Layer → TGIS_LayerPixel → TGIS_LayerWebTiles

This layer can be opened by opening the file name_of_layer.ttkwp or embedding all parameters to the Path property as CRLF or '\n' delimited string. The structure of this file must be:

  [TatukGIS Layer]
  Storage=WMTS
  Layer=layer name
  Caption=layer caption
  Info=additional layer info
  Copyright=copyright information
  Url=wmts server url with capabilities
  TileMatrixSet=layer matrixset
  Dimensions=layer dimension
  ImageFormat=image format
  InfoFormat=feature info format
  UserAgent=user agent in the meaning of the HTTP protocol
  TimeOut=time out in milliseconds for fetching single layer
  InvertAxis=reverse coordinates of axis for some coordinate systems (obsolete)
  AxisOrderReversed=reverse coordinates of axis for some coordinate systems
  AxisOrderIgnored=ignore axis order from the coordinate system 
  MaxThreads=maximum number of working threads
  ...
  Parameters key=value
  ...

  [TatukGIS Layer]
  Storage=WMTS
  Layer=layer name
  Caption=layer caption
  Url=server url
  ...

Parameters:

A layer can also be opened by providing the path with the server URL to read capabilities. The default parameters will be used for a first found layer. The URL must contain either the Service parameter WMTS :

http://myserver.domain.com/map?SERVICE=WMTS&Request=GetCapabilities

or “/WMTS” text

http://myserver.domain.com/map/wmts

or point directly to xml document for REST :

http://myserver.domain.com/services/wmts/1.0.0/WMTSGetCapabilities.xml

to be correctly recognized as a WMTS layer.

Some services may return xml data of the Capabilities request with missing ows:OperationsMetadata and the layer is unable to recognize which Encoding (KVP or RESTful) to use. In this case, the rest encoding is used if the Path ends with WMTSCapabilities.xml text.

By embedding <#password#> string into the url PasswordEvent even will be activated and value will be filled with provided user credentials.
For example:

http://myserver.domain.com/MapServer/WMTS?<!token=<#my_user_token#>!>

Expression '<!xyz!> means that the parameter will be embedded into any call within the service.

For basic authentication add User and Pass parameters to a configuration:

http://myserver.domain.com/MapServer/WMTS?User=me&Pass=secret

Some parameters can be also embedded into URL.
For example:

http://myserver.domain.com/MapServer/WMTS&TileMatrixSet=my%20matix%20identifier

Such parameters will be to define the layer but will be removed upon actual server queries.

The layer should properly recognize axis order. However, axis order can be modified to:

• force reversed axis order use AxisOrderReversed=true definition and:
  • embed into a URL
  • store in a .ttkwp file
  • store in a layer configuration file or project file
  • use Metadata TGIS_LayerWMTS.AxisOrderReversed=true
• ignore axis order recognition use AxisOrderIgnored=true definition and:
  • embed into a URL
  • store in a .ttkwp file
  • store in a layer configuration file or project file
  • use Metadata TGIS_LayerWMTS.AxisOrderIgnored=true

• WMTSManager sample