• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 72 replies
  • Answers 2 answers
  • Subscribers 12 subscribers
  • Views 22941 views
  • Users 0 members are here
Options
Related

Treadmill calibrated distance not sent to Strava

digpix
over 6 years ago
Did a treadmill run and did a calibration of the distance (Fenix 5X) according to the treadmill distance. Saved the data and Mobile Connect shows the new, calibrated distance but Strava show the distance before calibration?
  • 0 over 2 years ago

    And still Garmin offers no valuable input or solution.
    Hugely disappointed!!!!

    I honestly cannot fathom why Garmin are unable to get their heads around this  

  • 0 over 2 years ago

    ...and after 5 years, still an issue. Just started using a 255 from my trusted TomTom, same as jkny said.

    Surely this can be sorted out??? if it means adjusting the 'thousands' of data points, not just the distance... then adjust them! it can't be that difficult, the TomTom did it from day one and the resultant FIT file was perfect.

    Guess I'll be going back to the TomTom for treadmill runs.

  • 0 over 2 years ago in reply to 5609075

    The watch saves both - the originally estimated, and the calibrated distance into the activity FIT file that is being transmitted to Strava. Strava chose to use the uncalibrated value, although Garmin places the calibrated value into the main total_distance field designed for that purpose.

    I just verified it again - did a 4km treadmill run (the watch reported 4.01 km before calibration), and then calibrated it to 4.12 km. The activity FIT file shows correctly the calibrated value of 4120 m (4.12 km) in the standard total_distance field:

    The original distance of 4.01 km is not available anywhere else than at the distance of the last track point - 4007.44 m (rounded to 4.01 km on the watch).

    It means from the side of Garmin there is nothing to do. The ball is on Strava's side of the court. You have to contact them, and ask them to change the way they process the data from Garmin. They have all the needed data, and in the field exactly designed for it.

  • 0 over 2 years ago in reply to trux

    I'm not sure it's as simple as saying there's nothing for Garmon to do and it's just down to Stave. It seems to me that either body can solve the problem.

    What is the need to save 2 values when just the calibrated value is the one that's of use?  How does Strava know which value it should use?

    TomTom presumably doesn't have this issue because it doesn't save or upload dual stats. Is there any communication between Garmin and Strava? Is it up to us to pester both companies until one decide to solve it? 5 years is a long time. I'll post this on the Strava forum and try to push it forward although I have a feeling it's already been raised, same as here.

    Unfortunately my uncalibrated value is 20% out. It'll no doubt learn and improve quickly but these things tend to drift off again as soon as you change your pace.

  • 0 over 2 years ago in reply to 5609075
    5609075 said:
    I'm not sure it's as simple as saying there's nothing for Garmon to do and it's just down to Stave.

    I am sure Slight smile

    5609075 said:
    What is the need to save 2 values when just the calibrated value is the one that's of use?

    There is only one total distance. Strava, for some incomprehensible reason does not use the total distance but the last track point that was written to, before the calibration happened.

    5609075 said:
    How does Strata know which value it should use?

    They only need to use the total_distance

    5609075 said:
    TomTom presumably doesn't have this issue because it doesn't save or upload dual stats.

    I know nothing about TomTom, but probably Strava handles imports from TomTom better.

    5609075 said:
    Unfortunately my uncalibrated value is 20% out.

    You have to complain at Strava. Garmin cannot do more for you. The data is in the file.

  • 0 over 2 years ago in reply to trux

    Wow, you are quite dismissive aren't you?

    Yes, clearly Strava handles TomTom imports better. If you're saying that there's nothing Garmin can do to get the Garmin imports handled better then it's difficult to argue with you.

    Simply put, both watches upload their files, one format works one does not, if you're saying Garmin can do nothing more, I'm beginning to understand why this has gone on so long.

    Anyway I'll leave it there as clearly I don't know what I'm talking about.

    Cheers.

  • 0 over 2 years ago in reply to 5609075

    BTW, I am not from Garmin. But if you want to have your treadmill runs correctly imported to Strava, you really have to speak to Strava, and have them fix it.

  • 0 over 2 years ago in reply to trux

    Thank you for a very technical response that we technically can do nothing with. Given that the connection between Strava and garmin is offered it is good UX to ensure it works. It is not up to clients to connect 2 companies, this is seriously not a customer centred answer! 

  • 0 over 2 years ago in reply to 8417615
    8417615 said:
    Given that the connection between Strava and garmin is offered it is good UX to ensure it works.

    There is no need to connect the companies. As far as I know, the calibrating works all right in Garmin Connect. The problem is at Strava, and I do not understand why you think that Garmin should spend time and money on fixing mistakes in the interface of a company that is not their business. Strava gains enough money with using data from providers like Garmin, to be able fixing their problems alone. And if they do not know how to do it, they can ask Garmin (or read the documentation).