When running by power, the scheduled workout displays an estimated distance, which is a really useful feature for route planning. However, it seems the distance is currently calculated using the upper limit of the power range for each workout step, rather than a more realistic value.
For example, in the attached screenshot the estimate is based on 281W, which is the top of my target power range. In practice I ran closer to 250W (roughly the midpoint), which resulted in the actual distance being about 1 km shorter than estimated.
Would it be possible to base the distance calculation on the midpoint of the power range instead? This would give a much more accurate estimate and make it easier to plan an appropriate route ahead of time.
Hi Jordi, Thanks. For any other interval but Endurance, i.e. Tempo, Threshold, VO2Max we already do the midpoint but for Endurance it’s tricky. I think better to ‘conservatively’ estimate the distance via the upper bound because otherwise you might run more distance than we estimate.
Hi, thanks for the clarification, good to know the midpoint is already used for the other interval types.
I understand the reasoning, but in practice the conservative estimate actually works against me, because the estimated distance is longer than what I actually run, I plan a route based on that distance and end up having to walk the last kilometre home. So the upper bound doesn’t feel conservative from a user perspective, it overshoots the route planning. For a user that runs against the upper limit, it has less of an impact. Is one supossed to run close to the upper limit, then I can understand it but I always try to hit the middle of the power range.
Would it be worth showing a distance range instead, so users can see both the lower and upper bound and plan accordingly?
