kiwis wrote:
moorest wrote:
Agreed--current Garmin algorithms for loops yield distances that are too long or, conversely, times that are too short. My 16:54 5k on the track was a 15:43 on Garmin (plus another ~300 meters of running).
What mechanism would cause the watch to overestimate distance on the track? My garmin 220 always measured distances on the track at ~80% of the true distance. This makes sense since if the watch is updating position every few seconds and assuming you ran straight then it would always cut off parts of the curve and never assume you ran farther.
I have never seen a garmin under report distance on a track. Every one I have ever owned has over reported on a track. The same is true for the kids that I coach as well. Not saying that yours didn't under report but it is more common for the watch to over report on a track.