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

TCX export problem: elevation gain way too high

Former Member
Former Member
I have been having a problem with TCX files exported and then imported to Strava giving way too high elevation gain numbers. For example, a ride on GC showing 300m gain, when exported to TCX and imported to Strava resulted in 432m elevation gain. If I upload the .FIT file from the device, I get a number matching GC: 300m.

I contacted Strava support, and they showed me the how same TCX file imported to Garmin Connect resulted in 430m elevation gain, almost 50% too much.

So I did an experiment: I changed all the dates in the TCX file and re-imported the file to Garmin Connect. And Strava Support was correct. Garmin Connect now shows 430m elevation gain for the exact same ride that previously was 300m (except the date change).

The error is not always 50% but the numbers are always way too high with the TCX export/import method. CopyMySports transfers from GC to Strava result in the same errors. TrainingPeaks auto-transferred rides, however, have the correct elevation data.

I really prefer Bluetooth upload to GC, then TCX or CopyMySports to avoid connecting my device for every Strava upload.

Any advice? My device is an Edge 510.
  • Subscribed. I also notice this.
  • Former Member
    0 Former Member over 11 years ago
    To show the error I uploaded two screenshots. The original data, and the same ride exported to TCX, dates changed +1, and re-imported. The elevation gain shows 430m instead of 300m, while the elevation curve and max min elevations are the same. Unfortunately, this bug makes TCX exports and CopyMySports relatively useless for moving Garmin ride data, unless one wants the up to 50% incorrect elevation gain forever listed in your achievements.

    " />">

    " />">
  • Tapiriik seems to have figured something critical out. My last activity sync between GC and Strava using Tapiriik maintained all data and Strava's elevation correction was not applied. Woohoo!
  • Former Member
    0 Former Member over 11 years ago
    That's great news! Will try it out. He never replied to my suggestion to include the device tag, but perhaps he received enough suggestions to make that change... I just went over my last two weeks on Strava, deleted .tcx imported rides, and re-uploaded .fit files: net loss of incorrectly added elevation: 1500m or so!