VEH-76: Map of Journey Origins/Destinations

Issue Information

Issue Type: New Feature
 
Priority: Minor
Status: Closed

Reported By:
Ben Tasker
Assigned To:
Ben Tasker
Project: VehMan (VEH)
Resolution: Won't Fix (2019-09-09 16:22:06)
Affects Version: 1.0.2,
Target version: 1.0.2,
Components: Charts ,
Labels: Map,

Created: 2016-03-27 12:09:15
Time Spent Working
Estimated:
 
240 minutes
Remaining:
 
240 minutes
Logged:
 
0 minutes


Description
A while back I was tinkering with a Map that displayed all recorded journeys on one map. Unfortunately most browsers couldn't handle displaying that many trackpoints in one go.

What may be more feasible, though, would be to extract all track start points and end points, normalise them a little (to account for small differences in lat/lon) and then display a flag to show each start point / destination.

Ideally, there should be a means to specify whether you want to show just start points, end points of both


Toggle State Changes

Activity


2016-03-27 12:46:29
Have a fairly basic mock up of what I've in mind, the start points (ignoring the fact we'll want to limit by vehicle) can be extracted with 
select JourneyID, lat, lon FROM JourneyTrackPoints GROUP BY JourneyID ORDER BY JourneyID, time ASC
INTO OUTFILE '/tmp/start_points.csv'
FIELDS TERMINATED BY ','
ENCLOSED BY '"'
LINES TERMINATED BY '\n';


and the end points 
select JourneyID, lat, lon FROM JourneyTrackPoints GROUP BY JourneyID ORDER BY JourneyID, time DESC
INTO OUTFILE '/tmp/end_points.csv'
FIELDS TERMINATED BY ','
ENCLOSED BY '"'
LINES TERMINATED BY '\n';


The POC just pulls in the two resulting CSVs, and draws red markers for start points, and blue markers for end points.

It should actually be relatively easy to embed as a chart, the POC already contains the logic needed to generate the chart itself, so it's just tidying up the extraction and updating handlers (and documentation) to allow access to the new method.

2019-09-09 16:22:06
Bulk Close.

Realistically, this project's not going to see any further development (other than possibly some bug fixes for anything new that's found).

Closing any outstanding issues as Won't Fix

2019-09-09 16:22:06
btasker changed status from 'Open' to 'Closed'

2019-09-09 16:22:06
btasker added 'Won't Fix' to resolution