Wrong average pace

Hello!

The incorrect average pace in timed activities arises from apps treating the final, partial segment as a full kilometer/mile. To fix this, manually calculate the average by dividing total time by total distance, use third-party apps for better analysis, or submit feature requests to app developers. Exporting data for external analysis or stopping tracking at a full segment are also options. 

Ok, but the apps can't do that ? Seing the correct average pace at a glance would be nice. However how can I submit featuer requests to app developpers ? Thank you.

9612063 said:

For timed activities, the calculated average pace for the whole activity is wrong because it includes the last line as a whole kilometer, whereas it's often much less. How can I fix this ?

I never saw anything like that. My average pace is always correct. Which device do yo use, and could you post a screenshot demonstrating the issue? A link to the concerned activity would be even better.

when you divided 1 hour 10 minutes 31 secondes  by 12.07 Km the veritable average is 5:80 and not 5:51 as displau in the app

Thanks for your response but I don't completly understand.

If we think 5 min 51 s as correct, then the time for 12km will be  5.51*12 = approximatily 66 min (1h 6min ) and not 1h10 min.

9612063 said:

time for 12km will be  5.51*12 = approximatily 66 min (1h 6min )

You still do not understand the difference between a decimal dot, and the minutes:seconds separator. A minute has only 60, not 100 seconds, hence the pace of 5:51 min/km is not equal to 5.51 min/km, and you cannot multiply 5.51 * 12.07. You have to convert it to seconds, multiply and then convert back to minutes:seconds:

5:51 * 12.07 = (5*60 + 51) * 12.07 = 351 * 12.07 = 4236.57 s = 70.6095 min = 1h 10.61 min = 1:10:37

There is just a small rounding error of 6 seconds, because the unrounded pace is in fact not 5:51, but 5:50.5799

.