Okay so yesterday I did 5X4 mins averaging 3:12 according to the garmin, I couldn’t accurately think about my distance and time as we had jog rest so didn’t start at a clear marking so not using gps wasn’t an option. Is there a way I can convert this accurately or is this accurate?
On a track my Garmin invariably records a shorter distance than I really ran, but it's within 1%-2%.
none of this post makes any sense
here's what I get wrote:
On a track my Garmin invariably records a shorter distance than I really ran, but it's within 1%-2%.
That is not normal. A gps will almost always read longer than the true track distance.
Thurl Ravenscroft wrote:That is not normal. A gps will almost always read longer than the true track distance.
Na. My garmin is usually .24 per lap and .97ish per mile. Cuts off the turns slightly.
Trackgps wrote:
Okay so yesterday I did 5X4 mins averaging 3:12 according to the garmin
That’s really impressive. I don’t think I could run 4 minutes in anywhere close to 3:12.
Thurl Ravenscroft wrote:
here's what I get wrote:
On a track my Garmin invariably records a shorter distance than I really ran, but it's within 1%-2%.
That is not normal. A gps will almost always read longer than the true track distance.
This is true. Did a 3x1 mile a few weeks back and the final distance was 3.26. That's a whole extra lap tacked on to my workout. WTF.
ummwut wrote:
Trackgps wrote:
Okay so yesterday I did 5X4 mins averaging 3:12 according to the garmin
That’s really impressive. I don’t think I could run 4 minutes in anywhere close to 3:12.
Aha cheers mate just hope the real value is around that.
Thurl Ravenscroft wrote:
here's what I get wrote:
On a track my Garmin invariably records a shorter distance than I really ran, but it's within 1%-2%.
That is not normal. A gps will almost always read longer than the true track distance.
I personally don’t think I went quicker than a 3:12 so I’m sure it read longer than is accurate. I was just wondering if there’s any way of converting this to accurate units or whether it’s just one of those things
Trackgps wrote:
I personally don’t think I went quicker than a 3:12 so I’m sure it read longer than is accurate. I was just wondering if there’s any way of converting this to accurate units or whether it’s just one of those things
The best way to do this is add up the time in took you to run each of your 4 min repeats, divide this by the total time that your watch read for each interval. This will give you the error between your workout and your watch. Divide the error by the number of repeats and add this to each of times recorded by your watch. This should correct for any errors you observed. Alternatively, upload your workout to Garmin Connect or Strava, which accounts for stop time, and you can pull the correct repeat duration from there. I glad so see someone using the full capacity of their Garmin product. It may be time for you to upgrade to the 735XT.
Thurl Ravenscroft wrote:
here's what I get wrote:
On a track my Garmin invariably records a shorter distance than I really ran, but it's within 1%-2%.
That is not normal. A gps will almost always read longer than the true track distance.
Wrong. It will read longer on a measured course but it will almost always read shorter on a track. This is because the sampling rate chops the corners off as mentioned previously.
OP - I don’t think there’s anything you can do to accurately convert it.
Like Really Bro wrote:
Thurl Ravenscroft wrote:That is not normal. A gps will almost always read longer than the true track distance.
Na. My garmin is usually .24 per lap and .97ish per mile. Cuts off the turns slightly.
A few thoughts:
1. Your Garmin is probably measuring in miles, not meters. 4 laps on a track is not a mile. That will account for some difference.
2. Tracks are measured from the inside line or rail, usually 8-12 inches in. So, if you wear your watch on your left arm, most likely that arm is directly over the white line, or even inside of it, therefore not a full 400m. This will account for some differences.
The best way to use a Garmin for track workouts is to just override the volume when you upload it. I did 6x800 last week with walking/jogging rest and my watch read 3.47 miles. I just left the raw data as is and listed the workout as 3 miles. That's what is used for weekly and monthly totals.
Coffee Grind wrote:
Like Really Bro wrote:
Na. My garmin is usually .24 per lap and .97ish per mile. Cuts off the turns slightly.
A few thoughts:
1. Your Garmin is probably measuring in miles, not meters. 4 laps on a track is not a mile. That will account for some difference.
2. Tracks are measured from the inside line or rail, usually 8-12 inches in. So, if you wear your watch on your left arm, most likely that arm is directly over the white line, or even inside of it, therefore not a full 400m. This will account for some differences.
The best way to use a Garmin for track workouts is to just override the volume when you upload it. I did 6x800 last week with walking/jogging rest and my watch read 3.47 miles. I just left the raw data as is and listed the workout as 3 miles. That's what is used for weekly and monthly totals.
once i started running on the outside of the inside lane, my garmin became correct.
yeah what he said wrote:
Coffee Grind wrote:
A few thoughts:
1. Your Garmin is probably measuring in miles, not meters. 4 laps on a track is not a mile. That will account for some difference.
2. Tracks are measured from the inside line or rail, usually 8-12 inches in. So, if you wear your watch on your left arm, most likely that arm is directly over the white line, or even inside of it, therefore not a full 400m. This will account for some differences.
The best way to use a Garmin for track workouts is to just override the volume when you upload it. I did 6x800 last week with walking/jogging rest and my watch read 3.47 miles. I just left the raw data as is and listed the workout as 3 miles. That's what is used for weekly and monthly totals.
once i started running on the outside of the inside lane, my garmin became correct.
Yet another issue! I had my watch on my right wrist, so if anything it could’ve been close to the outside of lane 1, which may explain that I could’ve actually ran that distance
Yeah, if you're on a track, GPS won't cut it. If your running pace is less than 5m/s (18kph, ~11.2mph), then your're effectively overlapping errors on 1-second GPS readings.
If you want to correct the distance, you can use software to adjust it. Or just manually create the workout based on your splits.
Priceiswrong wrote:
Thurl Ravenscroft wrote:
That is not normal. A gps will almost always read longer than the true track distance.
Wrong. It will read longer on a measured course but it will almost always read shorter on a track. This is because the sampling rate chops the corners off as mentioned previously.
OP - I don’t think there’s anything you can do to accurately convert it.
I have worn various garmins for around 15 years and they have always reported a longer distance when running on a track.
It has nothing to do with which arm it is on as I happen to wear mine on my left wrist which positions it at the inside of the track.
All of the kids on our team that wear garmins also have distances that are longer than what they actually ran on the track.
And this is true no matter what track we are running on. So it has nothing to do with our particular track.
I've noticed my Garmin usually measures each track lap longer than it is. Also, it measures a certified mile between 1.01 and 1.02 miles. This seems counterintuitive. Maybe the thing is just calibrated poorly. I used to have a Timex Marathon GPS and that thing was dead nuts accurate.
4/5 or 6:24/10
ummwut wrote:
Trackgps wrote:
Okay so yesterday I did 5X4 mins averaging 3:12 according to the garmin
That’s really impressive. I don’t think I could run 4 minutes in anywhere close to 3:12.
Your 3:12 is 4 minutes to an observer moving fast enough
Get a stryd.
400m track = 400m lap.
Run on the outside get 410m or so.
Run on one of those stupid tracks that's actually like 367m well then you know.