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
When providing input data to NoiseModelling it is not clear how NoiseModelling is integrating all the assets in the 3D scene.
We already have google earth export but there is some issues with the height and the result is not the same between desktop or web rendering. The customisation of rendering is also very limited with this format.
Being able to export the post-processed input data into a 3D model would make easier to the user to debug input data.
This format GLTF is supporting also animation, so it could be used for animation of noisemaps with vehicles or any 3d objects.
The format is JSON based, so it is easy to generate without using any library.
When providing input data to NoiseModelling it is not clear how NoiseModelling is integrating all the assets in the 3D scene.
We already have google earth export but there is some issues with the height and the result is not the same between desktop or web rendering. The customisation of rendering is also very limited with this format.
Being able to export the post-processed input data into a 3D model would make easier to the user to debug input data.
This format GLTF is supporting also animation, so it could be used for animation of noisemaps with vehicles or any 3d objects.
The format is JSON based, so it is easy to generate without using any library.
ref:
https://github.com/KhronosGroup/glTF-Sample-Assets
https://github.khronos.org/glTF-Sample-Viewer-Release/
The text was updated successfully, but these errors were encountered: