From 1f1fe49ec974c9b00cc16cf2b6d52ae5ef726dfc Mon Sep 17 00:00:00 2001 From: Miko Date: Wed, 25 Dec 2024 21:49:48 +0100 Subject: [PATCH] update readme for encoding option --- docs/config.rst | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/config.rst b/docs/config.rst index 4020026..cb84e46 100644 --- a/docs/config.rst +++ b/docs/config.rst @@ -275,10 +275,6 @@ For example:: "source1": { "url": "mbtiles://source1.mbtiles", "type": "vector" - }, - "terrain": { - "url": "mbtiles://terrain.mbtiles", - "encoding": "mapbox" } } @@ -286,8 +282,6 @@ Alternatively, you can use ``mbtiles://{source1}`` to reference existing data ob In this case, the server will look into the ``config.json`` to determine what file to use by data id. For the config above, this is equivalent to ``mbtiles://source1.mbtiles``. -If you use terrain tiles, it is possible to configure an ``encoding`` with ``mapbox`` or ``terrarium`` to enable a terrain preview mode and the ``elevation`` api for the ``data`` endpoint. - PMTiles -------