Export GPX-failure

Export GPX/TCX Failure

I have the same error, erratic tracks when I export in TCX or GPX.

293654 km in 1h for this morning,

5350 km in 1h30 this afternoon

Yes I'm better in the morning !!!!

:(

Laurent LANG

Maybe the answer is in this thread?

https://forums.garmin.com/showthread.php?358557-downloaded-GPX-file-goes-to-lat-0-long-0

I will try this...
https://www.youtube.com/watch?v=5CuE0rNrjno

GPX and TCX export issues on iMac and Windows

I have the same issue (trying to import track to Quickroute).

If there is some lat/lon 0 issue, why track is ok in Garmin Connect?

I have exactly the same issue and am trying to export runs to GPX or TCX for Quickroute for orienteering. This started to happen about 4 weeks ago and all I can obtain on my iMAC are useless .wml" formats. It occurs differently with my two watches. My wife has the same problem on a different computer and with a different Garmin watch.

I have investigated further:

I normally download on an iMAC directly to Garmin Connect through Garmin Express. My watches are a 210 and a 225. Both are fully up to date with software.
When I then export the run from Garmin Connect to TCX or GPX then on opening the file in Quickroute I get a straight line that can be expanded to several points.

To experiment, I opened Garmin Connect on a Windows computer and Exported the runs to TCX and GPX. This worked and I then sent the exported TCX and GPX files to my iMAC, opened Quickroute using Parallels but still had a straight red line for the runs.
Then about a week or so ago, I repeated the process (using the Windows computer as the iMAC gave the original .wml files still) and with the runs using the Garmin 210 I had straight red lines but had a correct trace for the run with the 225 that I could then use in Quickroute.

I then used Sportstracks to download all the runs directly and had perfect tcx and gpx traces from both watches when I exported. These were useable in Quickroute.The watches are operating fine and clearly Garmin has made some change in the sofftware that is causing all these problems.
I hope that they correct it soon.

I have the same issue (trying to import track to Quickroute).

If there is some lat/lon 0 issue, why track is ok in Garmin Connect?

Try opening the activity file (the FIT file) in Garmin Basecamp and generating the GPX file from there. There is some conversion logic difference between Basecamp and Garmin Connect Online. I opened a case with Garmin support and provided sample files just yesterday.

If I were to guess, and this is purely a guess on my part, when the watch can't determine it's location to within a certain degree of accuracy, it probably records <null> in the FIT file for lat/lon. Basecamp knows to ignore <null> values, but Garmin Connect is probably converting the <null> to 0 when creating the GPX file (it does this for TCX exports as well). This is not an unheard of error to encounter when working with data conversion. MS Excel will even do this inconsistently. Some Excel formulas will treat <null> as <null> and some will return it as a 0 value.

If this is the cause of the issue, it should be a fairly simple bug to fix (but also one that probably should have been detected during testing).