< VEHPI-22: Create Test Scripts
VEHPI-24: time.strptime is not threadsafe >
VEHPI-23: Implement Journey/Track/Segment logic
: 2013-12-21 20:58:11
Time Spent Working
: Implement GPS Support
Need to implement logic to decide when to create a new journey, track or segment
GPX export contains trailing 0 mph trackpoints
Toggle State Changes
btasker changed status from 'Open' to 'In Progress'
btasker changed status from 'In Progress' to 'Resolved'
btasker added 'Done' to resolution
Re-opening issue. When running as a service, new Journeys are not being created
btasker removed 'Done' from resolution
btasker changed status from 'Resolved' to 'Reopened'
Commit 993ce6e implements a minor logic change. Before a new track is automatically started, the Journey ID will be refreshed. So tracks can overlap days if needed (such as driving overnight) but when a new track starts, a new journey will begin (if appropriate)
A new journey ID doesn't appear to have been generated overnight. Not looked further into why as yet