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.
AFAIK, when it comes to tiles, there is a file with the metadata. For example, while we tile a raster, there is always a layer.json file that gets used by OL or Cesium initially. But the dem2tintiles does not create that file. Is that intended or am I missing something?
The text was updated successfully, but these errors were encountered:
It seems that the dem2tintiles tool doesn't generate the layer.json file. Just like it doesn't produce the first-levels tiles so that Cesium can load it, see this thread: #51
The solution seems to be using their other tool: https://github.com/heremaps/quantized-mesh-viewer
Which handle these "missing bits". But when you try their viewer example (by adding your own Cesium ION Access key in the source code, bit annoying), the terrain is loaded and the browser never tries to download a "layer.json" file so I guess it is not needed
hope it helps,
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
AFAIK, when it comes to tiles, there is a file with the metadata. For example, while we tile a raster, there is always a layer.json file that gets used by OL or Cesium initially. But the
dem2tintiles
does not create that file. Is that intended or am I missing something?The text was updated successfully, but these errors were encountered: