Yes, that is a good way of correcting erronous gpx tracks. I stopped using runkeeper, since the snap to road feature was not working really well. Each zoomchange of the map, or each repositioning of the track takes AGES to refresh.
So now i am using similar approach to change the wildy wrong gps from the gamrin 2021 error from last months first run of the year. But instead of runkeeper i use the freeware app from viking. works quite good also.
Thanks for posting that workflow!
It’s interesting to see so many positive reactions to that, and not see much interest in having this feature built into CityStrides directly.
I think the lack of interest for this to be built in to Citystrides is because the vast majority of traces are OK. In my 100 runs so far in Citystrides only 1 is way off and that’s the first one I’ve had like that in over 10 years fo using GPS watches. So for me the Runkeeper edit routine was the solution, never likely to use it again for another 10 years
Not sure if this is the same issue, but I get implausible points when I go into a shop or other building. This messes up the trace. I don’t know if citystrides.com import the timestamp for each lat/long point, but if so it would be pretty easy to identify suspect points as the speed will be implausible. Stepping through the trace in sequence and deleting implausible points ‘should’ be reasonably easy. I’ve done this in the past for vehicle data loggers and it works nicely.