Commute merger #3
Description
Add functionality to ID one-way 'commute' tracks on Strava; apply an optional, user-specified privacy zone; merge; upload to Strava with custom title; delete original rides from Strava.
A pair of rides should be considered a 'commute' if
- End of ride 2 is within 24 hr of the start of ride 1
- Ride 1 starts close to home and ends close to work (addresses and max distancees provided by user in parameter file); inverse for ride 2
The 'delete' part, of course, is dangerous. Do we need any safeguards in place to prevent the tool from deleting rides it shouldn't? Obviously, tools need to check that merged ride is produced (and longer than zero), and that it is uploaded to Strava successfully before proceeding to delete original rides. Also, at least in my workflow, I'll download original files from Strava and save them locally before running the merger script.
Could use the 'private' checkbox as a proxy here. At least in my setup, individual rides will be uploaded as 'private', merged rides should be set as visible to followers (incidentally: should users be allowed to change this? Probably). Forbid tool from deleting anything that isn't 'private' on Strava?