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

Toggle State Changes

Activity


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
Bulk Close.

Realistically, project isn't going to see any further development so closing as Won't Fix
btasker changed status from 'Reopened' to 'Closed'
btasker added 'Won't Fix' to resolution