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 - Average Speed of Segments Based on Arbitrary Distance Values

The average speed of segments is not based on the original distance that was driven, but on a different value which diverts and therefore delivers wrong average speed values. Not clear why Garmin Connect even calculates a diverging distance value in the first place. This applies to ALL segments, the value increases with length of the segment.

  • Some example would be good.

    Usually too fast pace is calculated when a run doesn't cover whole segment, but it's close enough for a match. Then it takes time on a segment, but distance of whole segment.