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
The backend we've selected may not be performant with large datasets. Will we need to support multiple back-ends, each with trade-offs? I feel that the current state of mapping backends in JS is that none will do everything we want. E.g. Openlayers has great support for projections. Lonboard excels at performantly visualizing large vector datasets. MapLibre is working on delivering a 3D user experience soon.
The user experience of having to judge the tradeoffs of different mapping backends seems likely to be frustrating.
Does this analysis align with others' experience? What can we do to improve the situation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The backend we've selected may not be performant with large datasets. Will we need to support multiple back-ends, each with trade-offs? I feel that the current state of mapping backends in JS is that none will do everything we want. E.g. Openlayers has great support for projections. Lonboard excels at performantly visualizing large vector datasets. MapLibre is working on delivering a 3D user experience soon.
The user experience of having to judge the tradeoffs of different mapping backends seems likely to be frustrating.
Does this analysis align with others' experience? What can we do to improve the situation?
Beta Was this translation helpful? Give feedback.
All reactions