Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Garmin Megathread-Ask your questions here-See post 1 on how to search thread
Options
Comments
-
Krusty_Clown wrote: »No, unfortunately you need to edit it in a text editor.
I've done it for you (you owe me a pint.
)
I had to:
1. Export it from Garmin Connect
2. Open it in a text editor (preferably something that understands XML tags).
3. Remove all of the erroneous data. In your case, all <trackpoints> after the time: <Time>2010-09-11T11:00:08Z</Time>
4. Finally, I had to edit the overall lap time, which was showing 647 seconds, or something. So I edited it to show 321 seconds (start of your lap to the last trackpoint).
I tried it in GTC and it's showing correctly. You need to download the attached and remove the .txt part of the filename. Then try and import it into your Garmin Connect.
That's perfect now KC, you are a genius, The next couple of rounds are on me
http://connect.garmin.com/activity/485130120 -
Oops. your average pace for the last lap is showing 17:22. Ah well. We fixed most of it!That's perfect now KC, you are a genius, The next couple of rounds are on me
http://connect.garmin.com/activity/485130120 -
-
-
-
Advertisement
-
-
-
-
-
-
Advertisement
-
-
-
-
Krusty_Clown wrote: »If you want to run slightly faster in your training runs then do so, but don't adjust your race expectations based on what the watch recorded.
yup, im not talking about race expectations...but a tempo pace recorded on garmin is prob faster that a tempo pace were it in a 10m or half marathon race(if you know what i mean).....so in training, should a tempo pace be based by what is recorded from a garmin.
Eg 2, Krusty(hope you dont mind me using you as a example) you ran at a pace of 6:35m/m in barcelona, even though you prob finished with 6:4Xm/m(?) by race finish time.
is there any merit in basing your tempo pace on a 6:35m/m marathon instead of a 6:4xm/m marathon?*
* post barcelona marathon that is and a long time before you did a 60:02min 10m race! 0 -
Yeah, I know what you mean. But if you think of it, if I didn't own a Garmin watch, my pace in Barcelona would be 6:42/mile, without question. So suddenly ownership of a GPS watch makes you 7 seconds per mile faster.yup, im not talking about race expectations...but a tempo pace recorded on garmin is prob faster that my tempo pace were it in a 10m or half marathon race(if you know what i mean).....so in training, should a tempo pace be based by what is recorded from a garmin.
Eg 2, Krusty(hope you dont mind me using you as a example) you ran at a pace of 6:35m/m in barcelona, even though you prob finished with 6:4Xm/m(?) by race finish time.
is there any merit in basing your tempo pace on a 6:35m/m marathon instead of a 6:4xm/m marathon?
The problem is, it's quite misleading. If you train at 6 min/mile as a PMP (according to the watch), you'll find that that pace translates to 6:05 in a race environment (don't forget some of this gain comes from GPS inaccuracy). So if you want to hit sub-3 in a marathon, Mcmillan will tell you you need to run it at 6:53 (for 2:59:59). The reality is that if you plan on hitting that time and running according to the Garmin's average pace, then you should realistically be aiming for an average pace of approximately 6:48/mile.
For the sake of consistency, I'd suggest that when you're calculating training/tempo paces, you stick with the officially recorded pace/achievement (except where the course is found to be short or long). Remember: there is nothing to stop you from doing those tempo sessions a little bit faster (and in fact the difference between the two devices will typically only be a couple of seconds per mile).0 -
Related to the previous post and it often gets asked, here are the fields that I would recommend people have displayed on a Garmin watch during a race. Remember, these are just my views/suggestions, so others will have their own preferences and views on what works best, so please post alternative points of view (I'm not the greatest authority on Garmin watches, just the most willing to reply to people's questions!):
1) Time: This isn't the time of day, but actually the time since the race started (race time). Use this in conjunction with a pace band, so you get an accurate reflection of your pace on a mile by mile basis.
2) Distance: This is an approximation of the distance you have covered since the race began, but will likely read long due to GPS inaccuracy, poor racing line, water stops, etc.
3) Average Pace: This is an approximation of your average pace over the course of the race so far, but may read either too fast or too slow, depending on GPS accuracy, racing line, etc. Handy as a backup in case your pace-band strategy doesn't work out (e.g. no distance markers), but values should be taken with a pinch of salt.
4) If you have a 4th data field (Forerunner 205/305/310): Then maybe something like Heart rate (though some find having this information available to be counter-productive), pace (if you want to see your pace at a specific point in time), or sun-rise (if you are racing the 50 mile in Dingle).
Like I said above, these just represent my opinions and are not a definitive guide. Others will likely have alternative (better) approaches.0 -
Join Date:Posts: 23659
Krusty_Clown wrote: »...or sun-rise (if you are racing the 50 mile in Dingle).
Does it actually calculate the sun-rise times? Do they run east in Dingle as different people will get different times depending on what part of the course they are on, and what about if your the wrong side of a mountain at the time?0 -
I think it downloads that info from the almanac, based on your approximate position. Sunrise is still sunrise, even if you can't see it.Does it actually calculate the sun-rise times? Do they run east in Dingle as different people will get different times depending on what part of the course they are on, and what about if your the wrong side of a mountain at the time? 0 -
Krusty_Clown wrote: »Related to the previous post and it often gets asked, here are the fields that I would recommend people have displayed on a Garmin watch during a race. Remember, these are just my views/suggestions, so others will have their own preferences and views on what works best, so please post alternative points of view (I'm not the greatest authority on Garmin watches, just the most willing to reply to people's questions!):
1) Time: This isn't the time of day, but actually the time since the race started (race time). Use this in conjunction with a pace band, so you get an accurate reflection of your pace on a mile by mile basis.
2) Distance: This is an approximation of the distance you have covered since the race began, but will likely read long due to GPS inaccuracy, poor racing line, water stops, etc.
3) Average Pace: This is an approximation of your average pace over the course of the race so far, but may read either too fast or too slow, depending on GPS accuracy, racing line, etc. Handy as a backup in case your pace-band strategy doesn't work out (e.g. no distance markers), but values should be taken with a pinch of salt.
4) If you have a 4th data field (Forerunner 205/305/310): Then maybe something like Heart rate (though some find having this information available to be counter-productive), pace (if you want to see your pace at a specific point in time), or sun-rise (if you are racing the 50 mile in Dingle).
Like I said above, these just represent my opinions and are not a definitive guide. Others will likely have alternative (better) approaches.
fair play to ya Krusty, 2 very good, informative posts....
with regards training pace, your right in my case its only a couple of sec for tempo pace...was just a idea though.
thanks for the replies...0 -
-
Advertisement
-
Krusty_Clown wrote: »Related to the previous post and it often gets asked, here are the fields that I would recommend people have displayed on a Garmin watch during a race. Remember, these are just my views/suggestions, so others will have their own preferences and views on what works best, so please post alternative points of view (I'm not the greatest authority on Garmin watches, just the most willing to reply to people's questions!):
1) Time: This isn't the time of day, but actually the time since the race started (race time). Use this in conjunction with a pace band, so you get an accurate reflection of your pace on a mile by mile basis.
2) Distance: This is an approximation of the distance you have covered since the race began, but will likely read long due to GPS inaccuracy, poor racing line, water stops, etc.
3) Average Pace: This is an approximation of your average pace over the course of the race so far, but may read either too fast or too slow, depending on GPS accuracy, racing line, etc. Handy as a backup in case your pace-band strategy doesn't work out (e.g. no distance markers), but values should be taken with a pinch of salt.
4) If you have a 4th data field (Forerunner 205/305/310): Then maybe something like Heart rate (though some find having this information available to be counter-productive), pace (if you want to see your pace at a specific point in time), or sun-rise (if you are racing the 50 mile in Dingle).
Like I said above, these just represent my opinions and are not a definitive guide. Others will likely have alternative (better) approaches.
This covers perfectly a question I was going to ask myself. As Krusty said would love to hear other peoples options too.
Neil0 -
-
-
-
-
-
Just an update on my banjaxed watch from earlier posts.
I managed to get a screwdriver set that fits the garmin forerunner. Using a hair dryer I have cleared all condensation from the display and sorted out the buttons also. Some oxidation had occurred so I removed this with some gentle scraping. Water seal was fecked anyway so will have to be mindful of this.
Krusty can look after software problems and I'll now handle all hardware problems 0 -
-
-
Advertisement
-
Advertisement