From 02210f0bb80a5287f70bbd9bebbe66eaad6bdf81 Mon Sep 17 00:00:00 2001
From: Miko <miko@none>
Date: Sun, 13 Oct 2024 22:46:00 +0200
Subject: [PATCH] add documentation for elevation api

---
 docs/config.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/config.rst b/docs/config.rst
index cb84e46..4020026 100644
--- a/docs/config.rst
+++ b/docs/config.rst
@@ -275,6 +275,10 @@ For example::
     "source1": {
       "url": "mbtiles://source1.mbtiles",
       "type": "vector"
+    },
+    "terrain": {
+      "url": "mbtiles://terrain.mbtiles",
+      "encoding": "mapbox"
     }
   }
 
@@ -282,6 +286,8 @@ 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
 -------