Cesium Terrain Large Dataset Serving

CesiumJS
1

Hello,

I need to integrate terrain support for my cesium app.
I’ve tiff files that the terrain is encoded in.
I can’t serve terrain in Cesium Ion or any other third party service since my app wil be run on local.

My Steps:
1.) I used cesium terrain builder image from: (GitHub - tum-gis/cesium-terrain-builder-docker: Dockerfile for the geo-data/cesium-terrain-builder app with quantized mesh support.. Created terrain folder structure of level 0 to 14. (~7GB of result)

2.) I created an nginx docker container to serve the files, using bind mount to local filesystem

There is no problem in these two steps. However when I need to deploy the server into another device I either need to use a volume or directly embed into a docker image.

If I use a volume containing .terrain files, although the volume is 7GB the docker allocates nearly 42GB disk space for only this volume and high RAM usage when I run the container

If I embed the data into image directly I have the same diskspace problem as well.

I’ve tried disk optimization techniiques (VHD Optimize etc.) but they were partially optimal.

I believe that this is due to there are 10 million small files created by ctb-tile and docker filesystem is having a hard time managing it. Also directly copying (or zip extracting) this files takes more than 20 hours!!!

Is there any way to use cesium terrain provider from tiff without using any online servers. Also I’ve looked at kaktus40’s repository but it was buggy.

Thanks for your support,
Best,
Umut

2

Hi @Umut_Yunusoglu,

Thanks for posting - welcome to the community! This question is a little outside the wheelhouse of CesiumJS, but you might be able to find useful information in our offline guide. Otherwise, I might recommend referring to / making an issue with the repository you mentioned cesium-terrain-builder-docker, which isn’t a repo we own or support!

Best,
Matt