Related
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

Bug when Garmin Connect rounds-up the total distance

Former Member
Former Member
Hello,
I just ran a marathon, and my Garmin watch measured 42.067km.
I uploaded the activity to Garmin Connect, and I can see a bug: Garmin Connect displays 42.7km.

From what I understand, Garmin Connect rounded-up 42.067 to 42.07 (which is fine), but then 42.07 became 42.7.
Weirdly, the split by segment is correct, I can see the last segment worthes 0.07km (cf. attached image), or 0.067km depending on the platform.
This bug is present on the three platforms: Connect online, Android app, iOS app.
Consequence is that average speed is erroneous, which is not nice when we want to compare similar runs.
Thank you
  • 0
    Mentioned the same here.
    But I didn´t thought it was a rounding issue. I´ll make a run this afternoon and we will see :)
  • Former Member
    0 Former Member
    Thanks for your reply.
    So it means it existed almost 1 year ago already, and still has not been fixed :(
    I don't think it is technically a rounding issue, I think it's a bug that happens when the first digit after dot is 0.
    The developer forgot to shift to the right, should be easy to fix :)
  • 0
    It is not happening all the time.
    I got a run last week with .07 and everything seems fine. Also last month another correct one with .08.
    Found a third one 14.05 km where the last KM is 0.03. I´d say some rounding is happening in the past too, but not messed up!

    It is a new "feature" ;)
  • 0
    I just reported the same thing in the "Garmin Connect forgot how to do arithmetic thread." I've noticed twice this week, but not every run.
  • 0
    Seeing same error

    I have seen this bug twice. Both times, my last 0.02m became 0.2m when added to the total.
  • 0
    Work Around

    Here is a work around to fix the distance on the activity. If go to the activity and "export original", you'll get the .fit file. Next, delete the activity, then import the .fit file. The activity will be back with the correct distance. I've done it twice now without issue. I don't know why this works, but it does.

    On a side note, this distance issue also affects the pace values for the run. Doing the above work around fixes the pace values too.