Enhancement #1064

Add support for WMTS REST encoding

Added by Blatti Yves about 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:07/28/2015
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:SERVICE
Target version:4.4.1
Sponsor:ASIT-VD (CH) Ergonomic impact:

None

Functional impact:

Only the negociation function of physical service definition is affected


Description

We should add support for WMTS with REST encoding in physical service definition, to use it in the MAP.
(I'm not proposing to add proxy features and virtual services here)

We currently cannot negotiate with a RESTful only WMTS server*.

I would propose to try the restful encoding if the KVP fails.

OGC says:

A capabilities resource shall have a URI of the following form:
{wmtsBaseUrl}/{wmtsVersion}/WMTSCapabilities{formatExtension}

For example: http://wmts.geo.admin.ch/1.0.0/WMTSCapabilities.xml?lang=fr

*Note: as far as I know, the XML, SOAP and REST interfaces are all optional in 1.0.0 WMTS

History

#1 Updated by Van Hoecke Hélène about 4 years ago

  • Assignee changed from Technical Committee to Portier Thomas

Thomas, can you check if Leaflet support WMTS with REST?
Implement this implies that this has to be compatible with all kinds of MAP libraries.

#2 Updated by Van Hoecke Hélène over 3 years ago

  • Status changed from Request For Comments to Accepted
  • Assignee deleted (Portier Thomas)
  • Target version set to 4.4.1
  • % Done changed from 0 to 100
  • Functional impact set to Only the negociation function of physical service definition is affected
  • Ergonomic impact set to None

#3 Updated by Van Hoecke Hélène over 3 years ago

  • Status changed from Accepted to Affected

#4 Updated by Van Hoecke Hélène over 3 years ago

  • Status changed from Affected to Resolved
  • Sponsor ASIT-VD (CH) added

#5 Updated by Van Hoecke Hélène over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF