Treadmill calibrated distance not sent to Strava

Hey thanks for your effort and letting us know, my next step was going to be contacting support, often they read threads in other forums but depends on how busy things are I guess. If we don't hear anything, I'll look at seeing what can be done with converting the FIT to maybe a CSV and doing a group adjustment to the relevant values in excel and converting back. I doubt it's a simple as I'm thinking so it would be great if Garmin can sort it out.

It actually is quite simple, but tedious. You should just be able to adjust the incorrect distance values by multiplying them by the factor of (modified distance/ original distance). This will be inaccurate, of course, but it is a better form of inaccurate than the current state.

Yeah, it depends how strict the formatting is with these FITs and whether anything gets messed up during the conversion to a file we can edit and during the conversions back... or if Strava can import CSVs then just one conversion necessary. I'm away from home right now so no access to my PC, but I'll have a play at the weekend.

OK if you have 10 minutes to edit the FIT files and you have a PC and MS excel then you can correct the files and manually upload them to Strava.

Basically, you need to convert the FIT to a CSV (copy the file from the watch, don't download them from Connect), apply a multiplier to the whole distance column (this can be done in a single step), convert the CSV to a TCX and upload the activity to Strava.

There are 2 conversion sites on the GOTOES Strava org site, one for each conversion.

I tried to post step-by-step instructions, including hyperlinks to the converters, but it looks like this forum has a strict character limit on each post.

Interestingly the file, when converted to a CSV doesn't include the corrected final distance field at all, so I'm guessing that's just the way that Garmin decided to deal with calibration, other sites don't know what to do with that field, they just use the raw distance fields. TomTom must apply the multiplier to all of the distance fields, then upload.

Also, unfortunately, the 255 seems to fall down on the calibration process as it is. My first treadmill run was 2k over the actual distance and the second run was 2k under, with the same pace set on the treadmill. The watch seems to have over corrected by 100%

5609075 said:

Interestingly the file, when converted to a CSV doesn't include the corrected final distance field at all

As shown in my first post, the FIT file does include the corrected final distance in the field total_distance:

I didn't say the FIT file didn't contain the total distance. I said the CSV file that was created from the FIT file didn't contain the corrected total distance.

I used the converter that was mentioned in my post and it gave 3217 entries corresponding to each of the data points (one per second), in a format that seems consistent with treadmill CSV files.

6 populated columns corresponding to timestamp, heart_rate, cadance, distance, speed, power. Plus 11 more columns for various data not used for treadmill runs such as altitude, GPS position etc.

No additional calibration fields.

If you've used a CSV converter that shows something different, then great but I suspect it's not an industry standard.

5609075 said:

I didn't say the FIT file didn't contain the total distance. I said the CSV file that was created from the FIT file didn't contain the corrected total distance.

5609075 said:

If you've used a CSV converter that shows something different, then great but I suspect it's not an industry standard.

My screenshot is from a CSV file converted from the FIT file, using Garmin's FitCSVTool - and since the FIT file format was developed by Garmin, it is the most official Industry standard.