VEHPI-23: Implement Journey/Track/Segment logic

Issue Information

Issue Type: Sub-task
 
Priority: Major
Status: Closed

Reported By:
Ben Tasker
Assigned To:
Ben Tasker
Project: VehManPi (VEHPI)
Resolution: Won't Fix (2019-09-09 16:24:38)
Target version: 1.0,
Components: GPS , Core Classes ,

Created: 2013-12-21 20:58:11
Time Spent Working
Child of: VEHPI-7: Implement GPS Support


Description
Need to implement logic to decide when to create a new journey, track or segment


Issue Links

Causes VEHPI-34: GPX export contains trailing 0 mph trackpoints
Toggle State Changes

Activity


2013-12-22 23:22:50
btasker changed status from 'Open' to 'In Progress'

2013-12-26 23:50:26
btasker changed status from 'In Progress' to 'Resolved'

2013-12-26 23:50:26
btasker added 'Done' to resolution

2013-12-27 01:48:29
Re-opening issue. When running as a service, new Journeys are not being created

2013-12-27 01:48:29
btasker removed 'Done' from resolution

2013-12-27 01:48:29
btasker changed status from 'Resolved' to 'Reopened'

2013-12-27 01:51:35
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)

2013-12-29 07:29:30
A new journey ID doesn't appear to have been generated overnight. Not looked further into why as yet

2019-09-09 16:24:38
Bulk Close.

Realistically, project isn't going to see any further development so closing as Won't Fix

2019-09-09 16:24:38
btasker changed status from 'Reopened' to 'Closed'

2019-09-09 16:24:38
btasker added 'Won't Fix' to resolution