Improper estimate calculations
Please evaluate the algorithm for estimating time to arrival. On longer trips, it is not possible to make the trip in the estimated time. For an example, in the last week, I've made two different trips, one 12 hour and one 13 hour. 90% of trip was on major highway or interstate. The only way to maintain "on time" was to drive 10-15 miles over speed limit. Obviously I made stops and those stops were timed and I adjusted the trip estimate for these stops.
It wouldn't be a big deal but calculate a 10-15 mph over a 13 hour trip; that is a significant underestimation. It does seem to be consistent in its underestimations.
Anonymous
shared this idea
-
Ert Dredge
commented
I've noticed that Waze consistenly estimates I'll arrive about 15% sooner than I actually arrive. On ~30 minute city trips it's not a big deal, although it's definitely far more often optimistic about my arrival time than times I beat the original estimate. But on 2-or-more hour trips it starts to really make a difference, to the point that I just mentally round up a bunch and don't actually trust the original esimate.
It makes a difference in who I'm willing to in-app share my trip with: If I'm visiting a relative on the other side of the state, and I know they'll take the estimate to the bank and then get stressed when I'm not there at the estimated time, I won't share it with them.