4 ms·
> If OsmAnd got a new rendering engine (no, not that "3D" sluggish thing it has for a couple years now), like streetcomplete has (or the Strava-built-in mapbox
by maelito 1y ago
> If OsmAnd got a new rendering engine (no, not that "3D" sluggish thing it has for a couple years now), like streetcomplete has (or the Strava-built-in mapbox renderer), it would be possibly the best.
What "3D sluggish thing" are talking about ? Streetcomplete, like most OSM vector 3D maps use MapLibre, for a few months now https://github.com/streetcomplete/StreetComplete/pull/5693 https://github.com/streetcomplete/StreetComplete/pull/5693
Edit : sorry, I read Organic. Indeed OSMand is sluggish for me as well. I don't know why they went for something other than MapLibre. It's probably in-house and entangled in their code :/
- kmarc 1y agoYes :-) Streetcomplete is amazing; I understand it provides less polygons to render but it does an absolutely amazing job at it, even when there are thousands of quests.
- palata 1y ago> I don't know why they went for something other than MapLibre. OSMAnd existed looong before MapLibre :-).
- maelito 1y agoSorry, what I wanted to say is I don't know why they stick with their stack, instead of doing like Streetcomplete.
- palata 1y agoIt most likely involves a lot more than "just swapping the maps engine". Everything is built on top of their stack. It would basically mean rewriting an app from scratch.