Treadmill calibrated distance not sent to Strava

As explained earlier in this thread, the calibrated distance is being sent to Strava, but Strava does not use it. Please contact Strava and ask them to use the data in Garmin's FIT files properly.

Thanks for the explanation. Calibrated Garmin treadmill files are posted correctly when uploaded automatically to Training Peaks, which leads me to think Strava should just copy whatever TPs does. 

SOLVED: I built a free tool that allows you to download your treadmill run from Garmin and sync it to Strava with the correct distance info while maintaining HR and other data!

Give it a try here: https://www.stravatreadmillfixer.com/

9563292

- Is there any cost to your product since your page is behind a sign-up required?

Thank you for the additional information. Your post will be fine then. We appreciate the update.

Thanks for doing this, I'll give it a try. I've been doing manual edits/uploads up to now, all data is maintained but it takes maybe 10 minutes each time so anything that makes things easier is a win. 

It's just a shame that seemingly both Garmin and Strava see this as a problem for the other to fix. The root cause being the watches don't carry out a recalibration of the raw data on-board prior to upload, they just add a single data entry which the Garmin site knows what to do with... whereas Strava doesn't manipulate any raw data. That's also why some makes of watches work fine, as they apply the recalibration and effectively learn from that calibration each time, and consecutively became more accurate. e.g. my old TomTom, uploading only after the calibration has taken place.

I guess Garmin aren't really motivated to have people use a competitor's website over their own. Strava on the other hand should have been more motivated. It will be a consideration though when choosing my next watch.

Well, I don't want to be accused of having no sense of humour but 6 years without a fix and Garmin fans saying Garmin don't need to do anything... leaving it to users to try and mediate between the two companies... and cobble together their own fixes, leaves me a little jaded.

I'll ask on the Strava forum which watches don't have this issue as I can see that question probably wouldn't go down well here.