Generating a TerrainRGB file

[acalcutt]

Hi Everyone,

I started some questions about generating a TerrainRGB file that will be compatible with the 3d Terrain discussed here ( #165 ), but I wanted to start my own thread so I'm not polluting that discussion.

I am trying to take the (Jaxa aw3d30 ) greyscale GeoTiffs and use 'rio rgbify' to make a TerrainRGB file out of them. After some discussion in the other thread and several failed attempts, I ended up with the following commands.

gdalbuildvrt -overwrite -srcnodata -9999 -vrtnodata -9999 ${vrtfile} ${INPUT_DIR}/*_DSM.tif
gdalwarp -r cubicspline -t_srs EPSG:3857 -dstnodata 0 -co COMPRESS=DEFLATE ${vrtfile} ${vrtfile2}
rio rgbify -b -10000 -i 0.1 --min-z 0 --max-z 12 -j 20 --format png ${vrtfile2} ${mbtiles}

With these commands, the processes seemed to complete and I now have a 446GB mbtiles file. However, when I try to use it in my TileServer GL instance, this does not show up as a dataset and I don't see any errors when I restart TileServer GL.

Should Tileserver GL be able to host this file or should I be using something else to host it? If it should work in Tileserver GL, does anyone see anything wrong in the commands I used? As commented by @kylebarron in the other thread, the commands I used were based on these (https://github.com/nst-guide/terrain#terrain-rgb), in combination with the jaxa example scripts.

---

@acalcutt For more discussion about creating your own terrain-rgb tiles, I'd suggest creating a new discussion thread: https://github.com/maplibre/maplibre-gl-js/discussions/new. I'll just quickly add here: you definitely shouldn't need that much RAM to create a terrain-rgb tileset. You might be interested in some notes of mine on creating terrain-rgb tilesets here that worked as of 2 years ago.

Originally posted by @kylebarron in #165 (comment)

[acalcutt]

I opened up the file in a sqllite browser and was able to look at a few of the images inside. the images I looked at seem to be what I would expect. I saw images for the different zoom levels.

However in the metadata I noticed it was missing minzoom/maxzoom/bounds and some name/desc information. I am trying to add that now to see if maybe this is why it doesn't show.

[acalcutt]

After adding in minzoom,maxzoom,and bounds it seems to be mostly working. I was able to use the TerrainRGB to make hillshade and it looks good. However I seem to keep locking up mu TileServer GL instance when i am browsing around looking at it. not quite sure whats up with that.

EDIT: I added an index to mbtiles like mentioned in the mbtiles spec with "CREATE UNIQUE INDEX tile_index on tiles (zoom_level, tile_column, tile_row);" and it seems to have fixed my performance issues

For my test using hillshade, I specified the source as

      "jaxa_terrainrgb": {
         "type": "raster-dem",
         "url": "mbtiles://{jaxa_terrainrgb}"
      },

and then made a hillshade layer with

      {
         "id":"jaxa_terrainrgb",
         "type":"hillshade",
         "paint":{
            "hillshade-shadow-color":"hsl(39, 21%, 33%)"
         },
         "source":"jaxa_terrainrgb"
      },