You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This server is a bit special in that in the response to GetCapabilities it requests using https://wmts.marine.copernicus.eu/teroWmts as the WMTS service endpoint for GetTile:
works as expected. However, this seems to be supported by the WMTS standard, as libraries like GDAL or owslib produce the right requests (I didn't read the standard text, though, so I may be wrong on that).
Would it be possible to fix that? I unfortunately don't know enough about JavaScript / TypeScript to open a PR myself.
Hi @keevis thanks for reporting the bug.
After checking the specification this is definitely the bug in Terria's implementation of WMTS. According to the specification, we should respect the value defined in OperationsMetadata for GetTile and GetFeatureInfo. The operations metadata also specifies the encoding type of KVP or RESTFul and the KVP we can use directly but the RESTful doesn't specify the entire URL template so we have to fallback to layer ResourceURL. There is also part of the specification that specifies POST request but I don't think this is of interest for terria implementation as most of WMTS support either KVP or REST format
I'm trying to add tiles from this WMTS link to the terria instance at nationalmap.gov.au (share link)
While this allows me to see the list of available layers, adding a layer to the map does not actually display anything, and I see tile requests like
failing with status code 400.
This server is a bit special in that in the response to
GetCapabilities
it requests usinghttps://wmts.marine.copernicus.eu/teroWmts
as the WMTS service endpoint forGetTile
:works as expected. However, this seems to be supported by the WMTS standard, as libraries like GDAL or
owslib
produce the right requests (I didn't read the standard text, though, so I may be wrong on that).Would it be possible to fix that? I unfortunately don't know enough about JavaScript / TypeScript to open a PR myself.
cc @rsignell-usgs, @mdsumner
demonstration using the owslib.wmts python library
The text was updated successfully, but these errors were encountered: