The GPS trace data should be regularly stored

[GoogleCodeExporter]

It seems that the trace data is only stored at the end, when clicking 
"stop/store tracking".
OSMTracker should however regularly (e.g. all n minutes) its data to SDcard in 
order to prevent complete loss in case of crashes, or power failure.

Original issue reported on code.google.com by calestyo@gmail.com on 14 Jul 2010 at 7:59

[GoogleCodeExporter]

In fact it is stored internally in a SQLite database but exported in a file 
only at the end. Ideally some screens should be added to manage multiple tracks 
and export or delete selected ones, instead of working only with a "current" 
track. That is a major change but could solve a lot of related issue and 
prevent data loss.

Original comment by nguillau...@gmail.com on 17 Jul 2010 at 5:13

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Even when the phone shuts down due to empty battery, the track is saved 
internally but not on the sd card. I presume there is no way to recover the 
track? When I reboot the phone and start up osmtracker again, I can still 
display the track and the waypoints, but I cannot save it. As soon as I start 
new tracking, the old track is gone.

Original comment by prollius@gmail.com on 20 Aug 2010 at 1:51

[GoogleCodeExporter]

Hi,

the current SVN revision contains the possibility for showing and handling all 
tracks that are stored internally in the database.
So nguillaumin is currently working on this and perhaps it will be available 
within the next release.

Best regards
Matthias

Original comment by matthias...@gmail.com on 21 Aug 2010 at 12:03

[GoogleCodeExporter]

Indeed I've started working on that, but as it impacts all the application it 
takes some time to do properly. But the idea is to be able to manage multiple 
tracks, and re-export previous ones.

Original comment by nguillau...@gmail.com on 21 Aug 2010 at 2:34

[GoogleCodeExporter]

Issue 62 has been merged into this issue.

Original comment by nguillau...@gmail.com on 14 Sep 2010 at 9:11

[GoogleCodeExporter]

I like the idea of being able to manage multiple tracks, but it is a bit 
different than the original bug report, which was about periodically saving the 
data to the .gpx file.

Will the new multiple-track management feature periodically save to a file? 
This is pretty important, not only because of empty batteries, but I've had at 
least twice have the app crash while in a long track, and all was lost. Now I 
force myself to manually stop the tracking and restart it after 10 minutes of 
logging, that way I would lose only a part of the tracks if the application 
crashed.

Original comment by emilien.klein on 23 Sep 2010 at 12:13

[GoogleCodeExporter]

The track will be stored in a internal database, and the "track manager" screen 
will allow you to list existing tracks, and (re-)export selected ones.

Once that will be done, it should be fairly easy to add a "pause/resume" 
function to continue tracking on a previous track.

Original comment by nguillau...@gmail.com on 24 Sep 2010 at 8:43

[GoogleCodeExporter]

I wonder if it would make sense to query the remaining battery percentage, 
every few minutes, and pause or stop tracking if it's too low.  We could notify 
the user, and they wouldn't lose their entire track.

Original comment by jdmo...@nand.net on 25 Sep 2010 at 5:07

[GoogleCodeExporter]

With multiple track you should never lost a track again because it's stored 
directly in a database as soon as a GPS location event or a tag is entered. So 
even if your phone shuts off for a battery shortage, you'll still be able to 
export the track.

However it could be a good idea to notify the user, but maybe it will double 
the already existing Android notification ?

Original comment by nguillau...@gmail.com on 25 Sep 2010 at 9:09

[GoogleCodeExporter]

I'll close this one since v0.5.x allows multiple track management and 
re-exporting of previous tracks, including those which ended in a crash (or a 
low-battery shutdown).

Concerning the battery notification Android does already notify the user that 
he have to plug the phone to its A/C unit, so I guess it should be enough. Feel 
free to open another issue for that if needed.

Original comment by nguillau...@gmail.com on 4 Oct 2010 at 5:01

• Changed state: Fixed