Originally Posted by
wphamilton
You're talking about 2 different things. He means (multipath) errors due to the different paths a GPS signal might take from satellites. There are various smoothing algorithms to deal with those kinds of outliers, but the result is always an approximation of course. You're talking about errors in the track of the bike's path. Your observation is more important than his, to the question of measuring the path length of the bike's travel btw.
Where multipath causes problems is (mainly) in cities, where you'll also get some signals blocked by the buildings in addition to buildings reflecting the signal. Say you've got 7 satellites visible, three pretty close to the direction of 7th St. (where you're riding), two to the north, and two to the south. The block-long tall building on the north side blocks the signals from the satellites to the north, and a shorter building blocks line of sight to the southern satellites. The three in your LOS let your GPS know you're between Walnut and Maple Streets. They can't triangulate well from north to south. But signals from the southern satellites bounce off the building on the north side of the street before getting to your GPS (multipath), indicating you're farther away from the satellites, and therefore farther north. It's possible your GPS will conclude you crossed Walnut, went up an alley to 6th or even to 5th St., and then sprinted back to 7th when you get to the end of the block. You speed demon cyclist, you just rode three blocks while your wheel sensor went one block!