[Requests] Flexible and open URL templating for RESTful WMTS

Joan Maso joan.maso at uab.es
Wed Apr 1 13:43:51 EDT 2009


1. Evaluator:
        Joan Masó joan.maso at uab.es

2. Submission: 07-057 Candidate to Web Map Tiling Service


1. Requirement: REST Encoding modification

2. Implementation Specification Section number: [7.2.2]

3. Criticality: Major

4. Comments/justifications for changes:
A propose to accept flexible and open URL templating
and document it on the ServiceMetadata document.

I have demonstrated on the "Google maps emulator" that
it is possible to easily use several URL patterns in
a single client (WMTS and Google patterns) if the semantics
of the parameters is compatible.

A totally flexible pattern can be coded as a "search and
replace" function over the string URL.

Google becomes automatically a WMTS RESTful service:

Almost no performance side effects.

We need a new section on the Capabilities document:

ResourceMetadata that Describes the resource types
Resources are: tiles,FeatureInfos ..
The URL template is.

This gives the service addressability and some
degree of connectness.

This DO NOT interfere with Contents section. It complements it.
Contents deals with resources instances
Layer: coastlines, digitalElevation

In the URL template {layer} means one of the layer\ows:identifier values in 
Content section.

A possible way of doing this is:

  <Resource name="ServiceMetadata">
    <ows:Operation name="GetResourceRepresentation">
xlink:href="http://www.miramon.uab.es/wmts/1.0.0/GetCapabilities.xml" />
  <Resource name="Tile">
    <ows:Operation name="GetResourceRepresentation">

I has commented in the service subcomitte meeting of the OGC TC in Athens 
and there where no
objections to that.

This request complements a previous one of sean.gillies at gmail.com

Joan Maso

More information about the Requests mailing list