More intelligent "Estimated Moving Time"

[HM]

I love trying new cycling routes but need to understand what I am getting myself into. The current "Estimated Moving Time" based on my average speed for the last 4 weeks isn't useful at all. It treats a mostly flat ride the same as a hill climb and can be wildly off. I would like more intelligent "estimated moving time" for routes that takes into account the nature of the terrain when calculating the time. Strava knows my speed on a 7% uphill grade versus when I am cruising on a flat. Bonus points if you can also look at ride duration and incorporate how my performance tails off on long rides vs short ones, known times on known segments, etc. This shouldn't be a hard problem for modern predictive AI algorithms.

[Soren]

Thanks for submitting your idea on improving our estimated time calculations for Routes. It has been reviewed by our moderation team and is now open to voting.

[VikK]

I agree the estimation for routes should take account of terrain data, that would improve its accuracy.

[BikeSaviour]

As a potentially easier fix, might it be possible to perform the "Estimated Moving Time" calculation based on discipline? I create and ride Road, Gravel and MTB routes, and it's obvious that my average time for each one is going to be fairly different. That would be a lot easier than trying to create an estimate based on surface type and elevation, I suspect. The current estimate for routes is pretty useless if you do more than one type of riding.

[BikeSaviour]

Or at least allow the user to manually fix the estimated moving time  based on their personal knowledge - at the moment it can't be edited.