add documentation for elevation api
This commit is contained in:
parent
8412c0842b
commit
02210f0bb8
1 changed files with 6 additions and 0 deletions
|
@ -275,6 +275,10 @@ For example::
|
||||||
"source1": {
|
"source1": {
|
||||||
"url": "mbtiles://source1.mbtiles",
|
"url": "mbtiles://source1.mbtiles",
|
||||||
"type": "vector"
|
"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.
|
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``.
|
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
|
PMTiles
|
||||||
-------
|
-------
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue