Allow for track segmenting via track recording suspend/resume

[GoogleCodeExporter]

Tracks are now recorded as a single sequence of trackpoints. When a track is 
exported the GPX file will contain a single track element (<trk>) with one 
single track segment element (<trkseg>). While this satisfies many cases for 
example where a track is used for OSM import, there are use cases where tracks 
with multiple segments (GPX <trkseg>) within a single track are very useful, 
for example within applications where tracks are visualized, e.g. drawn on a 
screen. Withour track segments, a straight line would be drawn if points are 
very far apart, e.g. since tracking was stopped. Also all kinds of statistics 
like average speed while moving can be more accurate. 

Usually track segmenting appears to the user as a "suspend and resume" option 
instead of the current "stop & save". Also when the app is closed and at a 
later time reopened, possibly at a different location this would imply a new 
segment. Segmenting is a common feature in most GPS trackers. For example in a 
Garmin like a Etrex Legend, daytrack GPX files are recorded with GPX segments 
for each reset and when the unit is switched off/on.

While this is a refinement it would make osmtracker even more useful than it is 
already. 

A possible implementation could be to add a segment id column to the trackpoint 
table. This id is incremented each time a track is resumed. A more normalized 
option is to have a tracksegment table but this has more upgrade implications. 

Original issue reported on code.google.com by jus...@gmail.com on 1 Oct 2011 at 1:04

[GoogleCodeExporter]

Offcourse this issue is meant as an enhancement not a defect...

Original comment by jus...@gmail.com on 1 Oct 2011 at 1:05

[GoogleCodeExporter]

Original comment by nicolas@guillaumin.me on 2 Oct 2011 at 5:48

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

+1 to this. I recently did a track where I hit 3 cities but wasn't running 
OsmTracker in between the cities because I knew I had already mapped those 
roads. When I opened the resulting GPX file in JOSM it had long straight 
segments that confused the processing a bit. I ended up opening up the file in 
vim and adding <trkseg> elements manually.

Original comment by toby.mur...@gmail.com on 25 Jan 2013 at 5:56

[GoogleCodeExporter]

Nice idea, I'll take a patch :)

Original comment by nicolas@guillaumin.me on 28 Jan 2013 at 1:29