Best ways to backup OpenTracks #1277
-
Hi everyone ! Recently I had to make a fresh new install of my phone. Before that, I exported all my tracks in GPX files (thanks to the auto-export feature !). Once I imported them back into my freshly installed OpenTracks, I noticed that all the tracks where tagged as cycling although, some where hiking, some ski and most of them cycling. I'm trying to figure out which tracks belongs to which activity. I have a question : is this a bug or is this due to the GPX file format I used for export ? I'm not familiar with KMZ file, but if this could resolve this issue, I can use that. As a side note, I noticed that there is no feature to export OpenTracks settings. Setting-up OpenTracks is quite quick and easy but it would be great to have an export feature, especially for the customized recording dashboards. Is this already implemented and I have missed it ? Thanks for your help ! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
Welcome back to the party 🥳
|
Beta Was this translation helpful? Give feedback.
-
Hi, how would I restore a file written by Opentracks in Opentracks? I have written all my tracks to a single file by choosing "Export all (one file for all tracks)" and moved that file to the new phone by using nearby share. It now sits in the Download folder. Opentracks "import all" says it cannot use this folder. I have copied the file to a new "opentracks" folder, pointed Opentracks to that, folder and clicked "use this folder". Opewntracks says "importing from opentracks, completed with one error", and show errors says "Parser error, cannot import track without any locations". How do I proceed? |
Beta Was this translation helpful? Give feedback.
Welcome back to the party 🥳
Use either KMZ or KML, because GPX cannot contain all the information.
Regarding the actual activity: it is exported as a localized string (in your language) if you import on another device with a different language, everything will be imported as unknown.
There is no documentation for this; definitely a point to improve.
It is only in code.
PS/ I have been writing this just from my memory.
Relevant code is in GPXTrackImporter and KMLTrackImporter.
So, you didn't miss anything.
Also a nice feature...