Scenic wildly over-estimates duration of rides
For every route I plan on Scenic, the expected duration gets wildly over-estimated. I've attached a screenshot of a route I do regularly. The total distance is 81 km, 95% of the entire route is along a straight 4-lane road, and Scenic estimates the duration to be 1h and 47m (which is an average speed of around 46km/h...). I've done that route dozens of times, and each time I can easily ride it in 60 to 70 minutes (depending on traffic lights) at a leisurely pace without breaking any speed limits.
And that's on a straight route on a fast 4-lane road. It gets it almost ridiculously wrong if I plan a route with curvy roads: the time estimated by Scenic is often more than double compared to what it takes in reality, and I am absolutely not a fast rider.
I understand that duration estimates are not an exact science and highly dependent on circumstances, but the estimates are so far off that they are essentially completely useless, which is a real nuisance mainly when planning routes. I suspect that this may have to do with the fact that I live (and thus ride) in Thailand, and that average speeds and traffic density info for the roads here may be less accurate or even totally missing. In general, the map of Thailand is quite sparse and a lot of info is missing or outdated. Is there anything that can be done about this?
Quote from oz_djh on 20.01.2025, 02:00I appreciate it's been a big rewrite but the basic functionality we rely upon has taken a big step backwards.
After doing a test, I can say this has nothing to do with speed limit data with the new map provider. On a recent ride, the estimate was just totally wrong, as per the attached. A 51km ride was going to take 69 minutes apparently. How is that even possible? That's just over 40 kmph. It actually took 44 minutes so the estimate was over 50% out. During the ride I kept an eye on the speed limit and if anything it was over-stated as it didn't know that the speed limit had been reduced in some places.
