Open cglusky opened 6 years ago
I'm assuming this is taken care of inherently by the cesium 3d terrain sets?
Not sure. There was some work done to ry to standardize things like buildings. Lost track.
Might need to abstract the title of the issue once i get more info.
This is like organised squirreling.
@fnoop yes, it should be part of the data set used by cesium as far as i can tell. which i guess means we just need a way to query elevation data for whatever time and space you need.
here's the building 3d standard i was talking about... https://www.citygml.org/
path planning and safety checks on min/max altitude etc would be the use case.
This could have a big impact on speed of adoption by removing some barriers. it can be hard to generate good 3D maps.
@cglusky I have a cesium.com beta account. The new thing for rendering cities and other details is 3D tiles. http://www.aero3dpro.com.au/adelaide_3D_city_model_2017 https://cesium.com/blog/2017/07/12/the-next-generation-of-3d-tiles/ Having a workflow to generate and serve 3D tiles from Maverick would be hugely useful
Cesium has its own terrain data, You can also compile your own for your own use, its a bit of a pain though. The buildings and such should be other 3D tiles not related to terrain.
To make this a 4D experience - 3D Space and Time - then we need to support 3D data.
DTED, Digital Terrain Elevation Data. May go by other names in other places.
It appears NASA ASTER Missions now have DTED at 1 arc second (30m) for much of the globe.
https://earthexplorer.usgs.gov/?