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.