Enumeration representing the possible request encoding values supported by a WMTS server.

2024.1

Enumeration Members

Enumeration Members

KVP

This is the most common encoding used for WMTS requests. The WMTS requests in this encoding are made through URLs. The parameters are passed as key-value pairs in the query string of the URL. These parameters explicitly define the requested tile matrix, layer, format, and so on. You may select KVP over REST if your goal is:

  • Simplicity: KVP encoding is straightforward, making it a good choice for simple applications or for users who are new to WMTS.
  • Compatibility: KVP is widely supported by many servers, ensuring broad compatibility.
REST

This encoding is more concise than KVP. The WMTS requests in this type of encoding rely on a simpler, hierarchical URL structure. Parameters like the tile matrix, layer, and format are encoded directly into the URL path instead of using key-value pairs. You may select REST over KVP if your goal is:

  • Readability: RESTful URLs are often more readable and can be more intuitive, representing the resource hierarchy clearly.