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

Extreme smoothing of climb data in imported generic GPX files

In the process of importing around 800 activities over many years sitting in SportTracks. As I'm working my way through these, I noticed that Garmin Connect seems to perform an EXTREME amount of smoothing on the climb data.

As an example (but this is basically for all activities): A MTB drive in ST has 463hm of climb. Upon import into GC, it's coming out as 260hm... To validate the data itself, same GPX file imported into GPSSee shows 480hm and into Garmins own Basecamp show 488hm. And to even validate the data in GC itself, exporting the data from there back into GPX and then validating in GPSSee give 480hm (exactly same as before) and in BaseCamp 489hm (practically the same). Altitude correction is DISABLED in GC, so that is not the reason, it's how it evaluates the data on on import.

Because it's coming across as a generic GPX file, Garmin Connect doesn't know it's recorded using an Edge 705. If same exercise is performed where GC gets the data directly from the Edge 705 device and not from a generic GPX file, there's no issue - then climb data matches quite closely across SportTracks, Garmin Connect, GPSSee and BaseCamp, it's only when GC imports generic GPX data it does something with analysis of the data, that none of the other programs does.

I also noticed that the effect is most extreme, sometimes lowering climb data up to 40%, when the actual dride is many very small knolls/hills, whereas if the ride is long monotone climbs, the effect is much smaller, sometimes taking away less than 10% of climb data.

Anyone knows what's going on with this importing and ideally have a way to fix it. I hate loosing 30% of my historic climb data just because I'm moving to Garmin Connect.

No issue by the way is seen to the distance or time tracking, it's only on the climb data.

  • For those in the future seeing same issue. My conclusion is, that if the GPX / TCX data being imported is not stamped with a Garmin device as recording it, Garmin Connect applies very aggressive averaging on elevation data, resulting in 30-40% of total climb disappearing when doing MTB riding.

    To work around this with 1000+ activities over 15 years I have amassed in SportTracks, I deleted all the already imported activities in Garmin Connect (yes > 1000..., each is two clicks to delete, there's also no bulk delete). I then found an old copy of the Export2TCX plugin to SportTracks 3.1, then I went ahead and exported all activities again to TCX instead of GPX, which also brought over heart rate, kadence and power (where I had this) as part of the data - so much better data. This resulted in about 30 files, as Garmin Connect will also not reliably import data files over 25MB in size.

    Importing this data still gives the same smoothing issue. So to solve that, I used a text/replace tool that can replace blocks of text in ASCII/ANSI files (TCX files are just ASCII XML files), and in the right places between each "</lap> </activity>" pair, I inserted the right XML text to signify which Garmin device (530 or 705) was used to record the data, to not have Garmin Connect smooth out data. And the modified TCX files were then imported. To get all data tagged to the right bicycle equipment, the files imported were grouped by bicycle, and before each run I modified the bicycle to be used as default for new data, to get all this correctly tagged also.

    After importing all data, I had to go through all the 1000 activities to retag them also to either Mountainbike or Biking on Road as right type of activity - there was no way to trigger this during import (e.g. default activity type) or as bulk edit. So another few thousand clicks.

    Finally all data is as needed - however Garmin has not made it easy in any way to move over your life history of training activities, there's so many simple things that could be done to ease this, like bulk edits, better filters and ability to set defaults.

    If you haven't noticed, Garmin Connect is also a lock-in on the data, they go through all possible steps to prevent you to migrate off again... Now when connecting to other services, they only allow to sync over the last month of data, and there's no bulk export function at all. Wonder what the various trials and rulings at EU level of Right to Your Own Data would think about that. I'm saving my TCX exports that I've already done to cover that future scenario, but as new data comes in from the Garmin devices (actually I already have 2 years of that), I can only get it off the Garmin platform again by exporting each activity individually and manually.

  • Those can be done by script, and there is the Export Your Data option. Below threads have more info.

     

    deleted all the already imported activities in Garmin Connect (yes > 1000..., each is two clicks to delete, there's also no bulk delete

    Loaded rides by mistake

     

    exporting each activity individually and manually

    Is there a way to export bulk data to TCX or GPX files? Seems like I can only bulk export to .csv and individual activities to GPX