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
In its current implementation there seems to be a fixed number of trails simultaneously visible on the map.
While there might be performance implications, it would be very helpful to be able to manually adjust the number visible tracks on a client by client basis.
Feel free to ignore the following section
To remedy the performance problems, one could use an approach similar to Komoot mobile app, which when zoomed out simplifies the track by lowering the “resolution” of the track depending on zoom level. They seem to have a number x tied to the zoom level and only each x's point of the track is used for displaying the track.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. This has been on my roadmap indeed. I would like for it to group trails into a marker with a number on higher zoom levels and only show the actual trails once you zoom in more. Something like this:
Thanks for your quick answer. I can see how this would eliminate the potential performance issues. I like to use wanderer to store all my previously finished trails and then use it to find places I haven't been to. Especially for longer bike rides upwards of 100 kilometers, this implementation might make it harder to use wanderer for this since only their stating point would be visible.
In its current implementation there seems to be a fixed number of trails simultaneously visible on the map.
While there might be performance implications, it would be very helpful to be able to manually adjust the number visible tracks on a client by client basis.
Feel free to ignore the following section
To remedy the performance problems, one could use an approach similar to Komoot mobile app, which when zoomed out simplifies the track by lowering the “resolution” of the track depending on zoom level. They seem to have a number
x
tied to the zoom level and only eachx
's point of the track is used for displaying the track.The text was updated successfully, but these errors were encountered: