Nodes missed due to GPS drift

This is weird. Based on the image, things seem to line up that the nodes should have been found. It must be that my code to find street points within X meters of the run points isn’t accurate enough. I’ll need to think this one through…

The way it’s currently configured, it iterates through your activity’s GPS records & marks any Node within 25 meters of it as ‘run’.

I think there might be some other factors, like if a street has 10 Nodes & you’ve run 1 & 2, 5-10 then you’ve probably run 3 & 4 as well… There are a lot of caveats to this, though - some of them are noted in this thread:

1 Like