AlanOfTheBerg wrote:How often have you driven route A, purposely getting caught in the slower traffic so that Waze learns that this route is slower? Just because it might know how fast Route B is doesn't mean it has the data about route A in order to make the right choice.
bgodette wrote:I'd like to know what route B is because every single destination I've set inside the 470/nwp loop and into central Boulder has been accurate to +/- 2 minutes even during rush. The only times I've had it be inaccurate is when an accident has just happened or there's something that doesn't happen at the same time on the same day of week (sports, presidential debates, stolen tanks, etc).
It's all my phone's fault for using Tapatalk.
chrysrobyn wrote:sublimese wrote:For those that really want to know....
I live in North Arvada CO. I drive to the North end of the Tech Center
Route A == Kipling south -> I70 East -> I25 South -> Belleview (50-70 minutes)
Route B == Kipling south -> I70 West -> C470 South -> 285 East -> Happy Canyon South (45-50 minutes)
Waze only gives me the choice of Route A (or a few variations on it) and tells that that Route A will only take 35 minutes. You try driving route A during rush hour and tell me that it only takes 35 minutes.......
Having never spent a minute in Denver, I wanted to see what I could about your problem. I think you're saying you drive this instead of this. Is that right?
(I wish Waze had a helpful way of permalinking a route, including waypoints.)
CBenson wrote:I've had basically the same problem for last couple of days. I'm 99% convinced that my issue is not a map problem, but a routing server problem where the current/historic traffic info is not correctly taken into account. Interestingly, waze has been rerouting for me, so it is only the initial route calculation that seems to not take into account the traffic. Haven't really been able to verify that traffic is not taken into account in the initial evening route I receive, but it seems clear to me in the morning that the initial route is not taking into account the traffic data.
AlanOfTheBerg wrote:chrysrobyn wrote:(I wish Waze had a helpful way of permalinking a route, including waypoints.)
You can in Livemap. Well, you can permalink the origin/destination, but not the route itself. That may be future functionality in the app, though, having Waze actually remember your preferred route.
http://www.waze.com/livemap/?q=denver,% ... &to_seg=-1
AlanOfTheBerg wrote:Has it been asked yet (and answered) whether your Route B shows as an alternate route in the app? I've seen odd behavior sometimes where, for whatever reason, the route Waze chooses isn't actually the fastest. (You do have "fastest" selected in the app settings, right?)
Users browsing this forum: Google [Bot]