Closed doublebyte1 closed 11 months ago
@doublebyte1 The definition link needs to be retrievable as application/json
following the JSON schema defined in 2DTMS (it cannot just point to an HTML or PDF document).
It also should not point to https://schemas.opengis.net/tms/2.0/json/examples/tilematrixset/ because these are examples.
It should not point to the 2DTMS repository hosted on GitHub either (e.g., https://raw.githubusercontent.com/opengeospatial/2D-Tile-Matrix-Set/master/registry/json/WorldCRS84Quad.json) because unfortunately, it does not support returning a proper application/json
Content-Type: response header:
curl -H "Accept: application/json" -v https://raw.githubusercontent.com/opengeospatial/2D-Tile-Matrix-Set/master/registry/json/WorldCRS84Quad.json
Ideally, the link should be from the server itself so as not to rely on a third-party.
As a second best choice, the link should be to a definition provided by the OGC definition server, if the definition server was able to acommodate this need. Unfortunately, the OGC definition server is still not capable of serving this purpose, as discussed in https://github.com/opengeospatial/NamingAuthority/issues/198 .
For these reasons, servers really should provide their own definitions until the OGC Definition Server is fixed to support this capability.
@jerstlouis understood, thank you!
Requirements class 2 establishes the following essential elements:
If a server uses a well-known TMS, is it acceptable to link to one of the definitions on Annex D of OGC 2D TMS? https://docs.ogc.org/is/17-083r4/17-083r4.html#toc48