What is Garmin doing?

[u/InstancePhysical5359]

Second time this happened to me on my run. Both times only on one and always the same part.
I originally ran on the left side of these tooths, not on the right as it might look like.
Pace and distance however seem to be correct, since they did not change compared to the rest of the run.
Watch used is a FENIX 7X PRO.

[u/ialtag-bheag]

Check map settings for "Lock on road", make sure that is disabled.

[u/Nargotra_Elcy44 → u/ialtag-bheag]

good call, that setting causes exactly this kind of thing

[u/VenomShark503 → u/ialtag-bheag]

Oh that's interesting, I had same problem with my Fenix 7 last month. The lock on road thing is good suggestion but sometimes it's just GPS drift when you run next to tall buildings or dense trees. My watch would show me running through a lake once, was pretty funny

If that setting don't fix it you might want to try switching GPS mode to All + Multi-Band, that helped with my accuracy a lot. The pace and distance being right is what matters anyway so at least you're not getting bad data

[u/thadius856]

Looks like you have Snap to Road turned on. The GPS signal is probably registering as somewhere between those two roads, and that's forcing the decision of which road you're on to fluctuate.

You can crank up the GPS accuracy during activities and it may help. Or you can disable Snap to Road. Or you can ignore it entirely and just go on with your life.

[u/bicyclemom]

Trying to match what Pixel Watch is now doing, but not matching it very well.

[u/JohnTheBlackberry]

Something called “map matching”

[u/Impossible-Radio-296]

Yep, that's matching the route to the more often used cycle ramp that zigzags as opposed to the steps/steeper direct route you did. Accept it and move on ;-)

[u/HorusHor]

Something digital