michaelminhvo
commented
3 weeks ago I'd suggest loading a subset of the data. The use case I'm thinking of is I'm currently travelling, on spotty reception in the mountains, and I try to look at the closest crags nearby.
We could use a user's IP to only fetch the current country, and we could zoom into an area that is say 200kms in radius. That should prevent a lot of the redrawing of the bubbles and counts.
I think the World Map isn't particularly useful. It's rare that I want to see ALL the options, unless I'm researching for a trip.
One of the problems I experience on all devices is that the overview map loads quite slowly, especially while zooming and moving around. The underlying map is fairly fast, but the climbing areas layer seems to be a bottleneck. I saw a nice way of how this could be improved in the "Park4Night" App, whereby it doesn't load the layer with the location information while moving around and zooming, and only when you press "Search in this Area" it displays the location for the given map boundaries. This might be useful to reduce the server load and improve user experience, as currently the "Map:World" view starts from the global view, which means every user has to zoom in and move around quite a lot until the location his looking for is found.