Replies: 1 comment
-
If you changes the style of a track in the App, it stores the values in its own gpx database, but you can style them by modifying the gpx itself by inserting an extensions tag inside each tag: (AArrggbb):
Or with the well documented osmand style extension just inside the gpx tag:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When importing a GPX file containing multiple tracks you will be given the option to have OSMAnd break the gpx file up into individual track files. This will happen if the track count is between 2-50 tracks in the original gpx file.
These new track files contain tags describing the track's line width and color.
Strangely, theses tags are in two places in the gpx file. One is within the tag and the other is outside of the tag, within the tag. Doing some hand editing of the files it appears that OSMAnd uses the values within the tag for the initial display of the track.
You can use the OSMAnd edit appearance option to change the line width and color. However, these new width and color values are not written to the gpx file.
Shutting down and restarting OSMAnd retains these modified width/color values.
If I use the OSMAnd My places delete track option to remove the tracks and then reimport them then the track's original width/color values are restored.
If however I delete the track with a file utility and then reimport it the values modified before the delete are retained.
This indicates that OSMAnd storing these values modified width/color values in some other location and not the track gpx file. Does anyone know where this information is being stored and why the values modified using edit appearance are not written to the gpx file?
Beta Was this translation helpful? Give feedback.
All reactions