From 8e1c2bba81d4136f81d62c0e32422b9f3bc0d861 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?V=C3=A1clav=20Bla=C5=BEek?= Date: Tue, 19 Mar 2019 13:15:12 +0100 Subject: [PATCH] link fix --- docs/resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/resources.md b/docs/resources.md index 28b74fd..c4de9a4 100644 --- a/docs/resources.md +++ b/docs/resources.md @@ -228,7 +228,7 @@ Nota bene: While it is possible to add the TMS extension to any reference frame Nota bene: Please, do not use the `tms-global-geodetic` reference frame for anything else than terrain provider support. This reference frame is absolutely inappropriate for the VTS system because the underlying [projection (eqc)](https://en.wikipedia.org/wiki/Equirectangular_projection) is neither equal area nor [conformal](https://en.wikipedia.org/wiki/Conformal_map_projection). -However, the only other use the `tms-global-geodetic` reference frame in VTS is the `tms` driver when generating data for [Cesium Imagery Provider](https://cesiumjs.org/Cesium/Build/Documentation/ImageryProvider.html); bear in mind that that there is no extra imagery provider interface and the URL translation must be done in the javascript driver. Introspection interface does it automatically, though. +However, the only other use the `tms-global-geodetic` reference frame in VTS is the `tms` driver when generating data for [Cesium Imagery Provider](https://cesiumjs.org/Cesium/Build/Documentation/UrlTemplateImageryProvider.html); please, bear in mind that there is no extra imagery provider interface and the URL translation must be done manually in the javascript code. Introspection interface does it automatically, though. ### Common surface driver configuration options