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
We've noticed that all GPX tracks are currently displayed in red, making it challenging to differentiate between multiple overlapping GPX data sources.
This becomes a problem when trying to drive a GPX route while recording a GPX track so we know where we've been.
Would it be possible to introduce color customization options for imported GPX tracks? Offering default color schemes, like blue for planned and green for recorded tracks, could improve readability. Additionally, allowing users to select colors for both track types manually would increase accessibility for some users.
Thank you for your time and consideration. I look forward to any feedback or suggestions you may have.
The text was updated successfully, but these errors were encountered:
Tracks in progress are red, while previously recorded (or imported) tracks are pink. If you want to import a route you can use the new Data Overlays feature to import it as a GeoJSON, and it is be in a third color (cyan).
My main concern with adding additional customization is complicating the UI. I’m open to suggestions.
We've noticed that all GPX tracks are currently displayed in red, making it challenging to differentiate between multiple overlapping GPX data sources.
This becomes a problem when trying to drive a GPX route while recording a GPX track so we know where we've been.
Would it be possible to introduce color customization options for imported GPX tracks? Offering default color schemes, like blue for planned and green for recorded tracks, could improve readability. Additionally, allowing users to select colors for both track types manually would increase accessibility for some users.
Thank you for your time and consideration. I look forward to any feedback or suggestions you may have.
The text was updated successfully, but these errors were encountered: