You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
I'm not sure if this is helpful for you: I did not try Cesium but generated .obj files instead. I guess the workflow is the same. Let's say you want to model the area between latitude 47.90 and 47.66, longitude 11.53 and 11.88:
And you will get a nice model of the famous Watzmann mountain :) This is such a cool tool. If you run into issues take a look at gdalinfo output. It gives a lot of useful information. Be careful to set the overwrite flag. It took me hours to debug until I found that gdalwarp will reuse wrong coordinates from an existing file from a previous run until you set this flag or delete the file before.
This is not what I need. I need an alternative to Cesium terrain builder. The final result must be terrain files in a zoom level folder structure with one json file.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Can you provide an example on how to generate Cesium terrain from *.hgt ( or *.vrt ) just like cesium-terrain-builder ?
The text was updated successfully, but these errors were encountered: