update readme for encoding option
This commit is contained in:
parent
4d33886f72
commit
1f1fe49ec9
1 changed files with 0 additions and 6 deletions
|
@ -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
|
||||
-------
|
||||
|
||||
|
|
Loading…
Reference in a new issue