I think the new 15mph limit is a great idea. But I know I’ve been guilty of forgetting to stop my watch or phone (I double record for accuracy) and driving off. Most memorably around 40 miles at 70mph before I realised..
So my idea is: can we have either a filter on activities so I can find these and edit them to remove the driving bits in the gpx or can we sort activities via average speed?
Thanks for the updates @JamesChevalier - really appreciate the amount of work going in to make all the improvements happen
The implementation of this 15mph limit was kind of quick-and-dirty, because I needed to clean things up so city syncing could be operational again.
The existing flow/process is prone to confusing people … your activity won’t sync in … you’ll wonder why … maybe you’ll try a ‘sync now’ if you’re a Supporter … maybe you’ll try the single activity sync … maybe you’ll send me an email (hasn’t happened yet ) … at some point along the way, maybe you look at the activity at its source and notice the wild GPS track.
I’m not really interested in allowing this data into CityStrides at all - I’m already having a tough enough time managing all this good data - but some kind of in-site notification could be useful. Ideally, a notification with a title like “Skipped activity” with some details in there like why it was skipped (too long, too fast, etc), its date and distance, and a link back to the activity in the tracking service (if possible; some services don’t have this capability).
I’m also not super interested in activity edit capability within CityStrides, because that strays from the current ‘source of truth’ setup that’s in place now. It’s a bit like the OSM data situation, where I’m not looking to add a street editing feature in CityStrides - we should fix things in OSM and let those changes flow into CityStrides.
When i have seen erratic tracks in CityStrides i have gone back to Strava to trim the original (or delete if the whole event is messed up) - and then resynched. The thing that would be helpful (if its reasonable to implement) is a URL back to the source event, since Strava is not good at event searching…
But yes, having the means to identify it in the first place is important - or a notification that it wasn’t loaded because of a trigger like 15mph.
Love the speed limit implementation. Would like to see it even more aggressive eventually. I know a guy on here who will do what OP mentioned except it’s on purpose and doesn’t go back to crop off the portion tracked via vehicle. Unfortunately the new speed limiter doesn’t remove his activity because his overall average speed is still below threshold due to the 90 mins of jogging before the 1 to 5 miles of driving
The tracking service logo on every activity page (where possible; some services don’t provide this capability) links back to the activity in that service.
) … at some point along the way, maybe you look at the activity at its source and notice the wild GPS track.
- but some kind of in-site notification could be useful. Ideally, a notification with a title like “Skipped activity” with some details in there like why it was skipped (too long, too fast, etc), its date and distance, and a link back to the activity in the tracking service (if possible; some services don’t have this capability).