|
| ? re: moving time on Garmin vs. MB -- which is correct? (Read 302 times) |
| view log Frustrating Project |
posted: 4/10/2008 at 5:29 PM |
| Quote from sparky1 on 4/10/2008 at 5:25 PM: I've used my Garmin in a HM and Marathon now, and for both races I found it measured the courses as apx. 0.2-0.3 miles longer than the race is. Since we're on the topic of Garmin accuracy, has anyone else experienced this? I know not taking proper tangents around corners adds distance... but 0.2-0.3 miles worth of distance?
This is a common result. Being 0.3 miles long is only 1.1% off for a marathon, so that's not much. And over the course of a long race, not taking the tangents and corners properly really can add up, especially on a course with a lot of curves. |
20th Century: 800m: 2:04 |1600m: 4:37 |3200m: 10:06 |5k: 16:23 |10k: 35:38 |15k: 54:20
25k: 1:35:59
21st Century: 5k: 19:42 |10k: 43:00
What are you doing?
"Do not allow children to mix drinks. It is unseemly, and they use too much vermouth."
Steve Allen |
|
|
| view log |
posted: 4/10/2008 at 5:31 PM |
| Quote from sparky1 on 4/10/2008 at 5:25 PM: I've used my Garmin in a HM and Marathon now, and for both races I found it measured the courses as apx. 0.2-0.3 miles longer than the race is. Since we're on the topic of Garmin accuracy, has anyone else experienced this? I know not taking proper tangents around corners adds distance... but 0.2-0.3 miles worth of distance?
Trent and I ran the same route 4 times last week. It is exactly 11.8 miles. We both wore Garmins.
I think we ranged from 11.7 to 11.9. Never got the same reading.
I routinely find it off by 0.01-0.05 miles per mile on a hilly course with a lot of turns. Over the course of 20 miles that can add up. |
E-mail: JakeKnight2002@aol.com
-----------------------------
|
|
|
| view log Soon to be Dad (Apr. 30) |
posted: 4/10/2008 at 5:40 PM
modified: 4/10/2008 at 5:40 PM |
| Quote from jEfFgObLuE on 4/10/2008 at 5:29 PM: 0.3 miles long is only 1.1% off for a marathon, so that's not much.
Ah statistics. Gotta love them. Thats a very good point you raise when you think of it in those terms. A 1.1% error is not that much (be it the runner or the device)
Hills, crowd weaving, and inefficient tangents make for extra distance/computing errors.
I guess I'll stop sending hate mail to race directors now (kidding)
A good thing to be aware of too, especially when going for a time goal... don't be too confident in the readings of one's Garmin. It is nothing but a (close) approximation of what you have actually done.
|
Goals for 2009:
Find the perfect jogging stroller
Sub-3hr Marathon
Contemplate an ultra |
|
|
|
|
