CTOD is a service designed to fetch Cesium terrain tiles (quantized mesh) dynamically generated from a Cloud Optimized GeoTIFF (COG). The core concept behind this service is to eliminate the need for creating an extensive cache, thereby saving time and storage space. Traditional caching methods often involve generating and storing numerous files, many of which may never be requested, resulting in unnecessary resource consumption. CTOD addresses this issue by generating terrain tiles on the fly, optimizing efficiency and reducing the burden on file storage.

Don't care about on-demand? You can use CTOD to generate a cache for you aswell.

TL;DR

docker run -p 5000:5000 \
-v ./ctod_cache:/cache \
-e CTOD_PORT=5000 \
-e CTOD_LOGGING_LEVEL=info \
-e CTOD_TILE_CACHE_PATH=/cache \
ghcr.io/sogelink-research/ctod:latest

Open the local running demo viewer

Features

• Generate and fetch a layer.json derived from COG, accommodating all projections.
• Retrieve .terrain tiles by tile index, currently supporting grid and martini based mesh.
• Support for extension octvertexnormals
• Support for .vrt and (custom) mosaic
• Averaging of heights and normals on shared edge vertices among terrain tiles.
• Empty tiles with geodetic surface normals.
• Caching for seamlessly stitching neighboring tiles and preventing redundant requests.
• CogProcessor and TerrainGenerator for diverse terrain serving implementations (grid, martini, custom).
• Basic tile caching implementation
• Basic Cesium viewer included for debugging and result visualization.
• Scripts to partly seed cache and generate mosaic dataset.
• Works with Cesium for Unity

Wiki

• Meshing methods
• Tile stitching
• COG Optimization
• Seeding the cache
• VRT and Mosaic ToDo

Example result in Cesium

Wireframe and mesh in Cesium using grid based meshing

Future work (V1.1.0)

• Option to disable preview/homepage
• Mosaic dataset priority
• Support multiple workers
• Disable GIL with new Python version?
• Profiling to see where we can gain some performance
• Extension support: Metadata, Watermask

Settings

The following options can be set by supplying args to app.py or setting the environment variables.

Run CTOD

Run CTOD using docker or from source, see Settings for configuration options.

Using Docker

Example running CTOD using the docker image with a mounted volume and caching enabled.

docker run -p 5000:5000 \
-v ./ctod_cache:/cache \
-e CTOD_TILE_CACHE_PATH=/cache \
ghcr.io/sogelink-research/ctod:latest

From source

Install and run CTOD in a virtual environment using poetry.

poetry env use python3.10
poetry install
poetry shell
poetry run start

To enable caching, supply --tile-cache-path path with the start command.

poetry run start --tile-cache-path ./ctod_cache

--no-dynamic

The idea is that an user can use every COG that the CTOD service can access with the parameters the user wants, this can expose a problem when CTOD is available on the internet. A random user can use your CTOD instance to generate his own .terrain tiles or even mess up a cache by supplying weird grid sized.

To prevent a user to use any cog with any parameter the endpoints are split up into /tiles/dynamic/.. and /tiles/{dataset}/... The dynamic endpoint accepts parameters and is flexible to use where the /tiles/{dataset} endpoint can only be configured with a config file and ignores parameters.

The dynamic endpoint can be disabled by supplying the option --no-dynamic to CTOD or set the environment variable CTOD_NO_DYNAMIC to TRUE. This way only configured datasets can be used with set parameters.

Endpoints

Endpoint documentation for your running CTOD service can also be found under /doc.

Endpoint: /

Shows the available datasets and a link to open a preview viewer using the dataset.

Request

• Method: GET
• URL: http://localhost:5000

Endpoint: /docs

The CTOD OpenAPI documentation with Swagger UI

Request

• Method: GET
• URL: http://localhost:5000/docs

Endpoint: /status

Can be used to check if CTOD is online

Request

• Method: GET
• URL: http://localhost:5000/status

Endpoint: /tiles/dynamic/layer.json

Dynamically generates a layer.json based on the COG. The supplied parameters will be picked up by Cesium when using this url for the CesiumTerrainProvider and passed down to the .terrain requests.

Request

• Method: GET
• URL: http://localhost:5000/tiles/dynamic/layer.json

Parameters

See Parameters

Example

http://localhost:5000/tiles/dynamic/layer.json?maxZoom=18&cog=./ctod/files/test_cog.tif

Endpoint: /tiles/{dataset}/layer.json

Dynamically generates a layer.json for a configured dataset, replace {dataset} with a dataset configured in datasets.json, all supplied url parameters will be ignored.

Request

• Method: GET
• URL: http://localhost:5000/tiles/{dataset}/layer.json

Example

http://localhost:5000/tiles/demo/layer.json

Endpoint: /tiles/dynamic/{z}/{x}/{y}.terrain

Get a quantized mesh for tile index z, x, y. Set the minZoom value to retrieve empty tiles for zoom levels lower than minZoom. maxZoom is handled in the generated layer.json.

Request

• Method: GET
• URL: http://localhost:5000/tiles/dynamic/{z}/{x}/{y}.terrain

Parameters

See Parameters

Example

http://localhost:5000/tiles/dynamic/17/134972/21614.terrain?minZoom=1&cog=./ctod/files/test_cog.tif

Endpoint: /tiles/{dataset}/{z}/{x}/{y}.terrain

Get a quantized mesh for tile index z, x, y. Replace {dataset} with a dataset configured in datasets.json, all supplied url parameters will be ignored.

Request

• Method: GET
• URL: http://localhost:5000/tiles/{dataset}/{z}/{x}/{y}.terrain

Example

http://localhost:5000/tiles/demo/17/134972/21614.terrain

Parameters

• cog: Path or URL to COG file.
• minZoom : The min zoomlevel for the terrain. Default (0)
• maxZoom : The max zoomlevel for the terrain. Default (18)
• noData : The value to use for NoData in COG. Default (0)
• resamplingMethod : Resampling method for COG: 'nearest', 'bilinear', 'cubic', 'cubic_spline', 'lanczos', 'average', 'mode', 'gauss', 'rms'. Default 'none'
• skipCache : Set to true to prevent loading tiles from the cache. Default (False)
• meshingMethod: The Meshing method to use: 'grid', 'martini', 'delatin'

Parameters for meshing method: grid

• defaultGridSize: The default grid size (amount of rows/cols) to use if there is no specific zoomGridSizes defined for a requested tile, Default (20)
• zoomGridSizes: Per level defined grid size, when requested zoom for tile not specified use defaultGridSize. Default when defaultGridSize and zoomGridSizes not set ({"15": 25, "16": 25, "17": 30, "18": 35, "19": 35, "20": 35, "21": 35, "22": 35})

Parameters for meshing method: martini

• defaultMaxError: The default max triangulation error in meters to use, Default (4)
• zoomMaxErrors: Per level defined max error, when requested zoom for tile is not specified use defaultMaxError. Default when defaultMaxError and zoomMaxError not set ({"15": 8, "16": 5, "17": 3, "18": 2, "19": 1, "20": 0.5, "21": 0.3, "22": 0.1})

Dataset configuration

It may be usefull to preconfigure a dataset in a config file, this makes the url cleaner and a user cannot override settings which can result in different configured tiles in the cache. When the option --no-dynamic is supplied to CTOD only datasets from the config can be used and the dynamic datasets are disabled.

By default CTOD tries to look for the dataset config at ./config/datasets.json, this can be overwritten with --dataset-config-path or environment variable CTOD_DATASET_CONFIG_PATH. When the config could not be found or has an error CTOD continues and logs an error.

The exact same parameters as described in the topic parameters can be used in the .json file for a dataset.

Example config

{
    "datasets": [
        {
            "name": "demo",
            "options": {
                "cog": "./ctod/files/test_cog.tif",
                "minZoom": 13,
                "maxZoom": 17,
                "noData": 0,
                "meshingMethod": "grid",
                "skipCache": false,
                "zoomGridSizes": {"13": 5, "14": 10, "15": 15, "16": 20, "17": 25, "18": 30, "19": 35}
            }
        },
        ...
    ]
}

More info

How to use in Cesium

To use the CTOD terrain tiles in Cesium, create and set a CesiumTerrainProvider initialized with the url to the CTOD service. The layer.json file will be requested on the /tiles endpoint followed by .terrain requests while passing the options to the endpoints.

viewer.terrainProvider = new Cesium.CesiumTerrainProvider({
    url: `https://ctod-service/tiles/dynamic/?minZoom=1&maxZoom=18&cog=MyCogPath`,
    requestVertexNormals: true
});

Caching

The CTOD service has a very basic tile caching option, tiles can be retrieved and saved by supplying a cache path when starting app.py or setting the environment variable CTOD_TILE_CACHE_PATH. Based on this path and the requested cog, meshing method and resampling method a tile can be saved and retrieved from disk. the cog path/url will be encoded into a hex string. When a service is started with caching the cache can be circumvented by adding ignoreCache=True to the terrain request.

Nodata

Nodata values in the COG are automatically set to 0 else it is likely that the meshing will go wrong, for now nodata should be handled in the source data (COG) or pass noData={value} to the .terrain request to overwrite the default value 0

Used libraries

• rio-tiler: Rasterio plugin to read raster datasets. (BSD-3-Clause)
• pydelatin: Terrain mesh generation. (MIT)
• pymartini: Terrain mesh generation. (MIT/ISC)
• quantized-mesh-encoder: A fast Python Quantized Mesh encoder. (MIT)
• morecantile: Construct and use OGC TileMatrixSets. (MIT)