Alvaro Huarte

Hi @LHolst, I fixed a bug, I hope it works now

It would be useful more information to try help you. What command parameters did you used? or what raster file did you used?

Ok I see, the error comes from Cesium no from CTB. Do you have defined the `Content-Encoding: gzip` content negotiation header? https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding

I would use [gdal_translate](https://www.gdal.org/gdal_translate.html) with `-projwin` parameter to clip the raster to (-180 / -29.98)

Do those walls match the limits of your input raster? If you do not have data outside that borders you have to set the nodata flag of these raster cells...

You have to add the '-l' parameter and execute again, you can read this parameters help[here](https://github.com/tum-gis/cesium-terrain-builder-docker#create-cesium-layer-description-file)

Hi, I have implemented the quantized-mesh output to the CTB (ctb-tile tool). It provides two new features: - New quantized-mesh format ouput. - New metadata file output. It is free...

Very interesting report, thanks for sharing Mark

Hi, I had the same problem, @epifanio is right, I removed the extra argument and CTB runs fine

Just now I am changing the code to create the Json metadata file when the tile set is created first time. It avoids to execute CTB twice.