Changing the map engine (and supporting 3D maps) #2503
Replies: 1 comment 1 reply
-
I would push back on this, for three reasons:
In an extreme case of all 3, a boat may be sent down a mountain river, in which case it could be valuable to visualise its sensor readings localised to the full position (altitude included), not just horizontally I would note that 3D-capable maps may come with a performance penalty to use, and aren't necessary for every use-case. Ideally we will continue supporting 2D as a standard option, but I do think we also want to empower users to enable 3D if and when they would benefit from the functionalities it provides. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Today we are using Leaflet as our map engine. It is probably the most used lib for map displaying in the world, has a lot of documentation and is relatively easy to work with, but it has some caveats, with the most relevant one being the fact that it doesn't support 3D maps (terrain elevation).
Supporting 3D maps is not something that is holding us today, as our focus is on the ROV and the Boat. For the Boat, elevation doesn't change things, as it is always in a plain body of water, and for the ROV it would be interesting if we had underwater 3D maps, which are not that common, but if we plan to attract aerial users, this is a must.
There are different alternatives out there that support 3D, like Cesium, Mapbox and MapLibre.
Opening the discussion so we can have more info in advance when starting that work.
Beta Was this translation helpful? Give feedback.
All reactions