This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't export 1 ride as tcx from GC

Former Member over 15 years ago

I have a ride that I'd like to export from Garmin Connect, but when I try to export it as a tcx file, I.E. gives me an error message telling me that it can't download the file. I can successfully export other rides as tcx, but not this one. All the data seems OK when I view it through Garmin Connect, but I'm wondering if it's corrupted in some way.

Any ideas/similar experiences?

0 kansaiben over 15 years ago

Care to post a link to the activity for us to look at? If I can download it I'd be happy to post the tcx. file for you. Or you might try another browser to see if there's an IE problem. Also, what device recorded this activity (might be other ways to get the tcx file)? I've had a couple activities with sketchy HR have difficulties with GC.

0 Former Member over 15 years ago

Care to post a link to the activity for us to look at? If I can download it I'd be happy to post the tcx. file for you. Or you might try another browser to see if there's an IE problem. Also, what device recorded this activity (might be other ways to get the tcx file)? I've had a couple activities with sketchy HR have difficulties with GC.

Here's the link, it's for a hill climb

http://connect.garmin.com/activity/21460287

I recorded this on an Edge 305 and have downloaded the same ride into SportTracks and Ascent FWIW, but couldn't sync this ride from my unit (I'm trying out a couple of other web based GPS analysis tools).

0 saeedi over 15 years ago

There seems to be an internal error with GC on the file. Ascent does allow you to export the file as TCX, so there is a workaround and you can get your San Bruno Hill climb one way or another.

0 DW152 over 15 years ago

I've found GC and GTC to be fussy about the some of the tcx files, and will report errors because of some minor thing. The same file will import just fine into another program, such as Ascent.

0 Former Member over 15 years ago

There seems to be an internal error with GC on the file. Ascent does allow you to export the file as TCX, so there is a workaround and you can get your San Bruno Hill climb one way or another.

Thanks SAEEDI - any idea what that means? I was trying to upload the file to Strava.com for grins. When I got it out of Ascent, Strava.com didn't recognise it as coming from a Garmin so wouldn't upload it. Long story short, I emailed the file to them and they did it behind the scenes.

I'm still curious as to what went wrong in GC though? I think this has happened once or twice to me and it's pretty frustrating. Is it something to do with my 305, the particular ride, or is it something random with GC?

0 kansaiben over 15 years ago

When I looked over your activity there does seem to be two instances that I believe may be tripping up the tcx export (the GPX file exports just fine). There are two sections of your ride where there is a pause of sorts registered: once in the parking lot early on in your ride and another near the summit. If you view your activity graphed by time vs. distance you'll see these sections represented as flatlines of sorts. I suspect that these instances are lacking some data points to successfully render the xml/tcx file (missing cadence/HR). I've had problems working with files in the past that have had irregular HR data. Question is, how are you registering these pauses on your unit? are you manually stopping and restarting the activity? auto-pause? That's my theory anyhow, and may be resolved by examining how you register these pauses (restart closer to the stopping point so a true stop is registered and/or use auto-pause). Thoughts?

0 Former Member over 15 years ago

When I looked over your activity there does seem to be two instances that I believe may be tripping up the tcx export (the GPX file exports just fine). There are two sections of your ride where there is a pause of sorts registered: once in the parking lot early on in your ride and another near the summit. If you view your activity graphed by time vs. distance you'll see these sections represented as flatlines of sorts. I suspect that these instances are lacking some data points to successfully render the xml/tcx file (missing cadence/HR). I've had problems working with files in the past that have had irregular HR data. Question is, how are you registering these pauses on your unit? are you manually stopping and restarting the activity? auto-pause? That's my theory anyhow, and may be resolved by examining how you register these pauses (restart closer to the stopping point so a true stop is registered and/or use auto-pause). Thoughts?

Those are auto-pause points before and after the race. What's your suggestion? I'm intrigued, as this isn't the first ride that has misbehaved when I try to export it