From 08a231c64ff4f71177922f29c55ad3a408595a50 Mon Sep 17 00:00:00 2001 From: Dennis Guse Date: Thu, 13 Mar 2025 06:42:23 +0100 Subject: [PATCH] README: added information for backups. Fixes #2072. --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 67269c42f..2eff7f335 100644 --- a/README.md +++ b/README.md @@ -153,6 +153,19 @@ slow and does not provide updates while recording. The developer documentation is in [README_API.md](README_API.md). +## Backup + +OpenTracks stores the data in the app-internal space: +`/data/data/de.dennisguse.opentracks[|.playstore]` + +There is a SQLite database `database.db` that contains the tracks as well as the markers. +Pictures attached to markers are stored as separate files. + +For backup and recovery, the best approach is to export as one KMZ file. +This will contain all the tracks, pictures and the data as similar as possible as stored internally. +In difference to backing up the database directly, a KMZ allows to be imported into a different ( +e.g., newer) version of OpenTracks. + ## Project history _OpenTracks_ is based upon Google _My Tracks app_ ([code](https://code.google.com/archive/p/mytracks/)).