Moderators: support, Unholy, krankyd, The Fej
AlanOfTheBerg wrote:Unfortunately, they were the useless kind where it changed the ETA to later and earlier by the same amount within seconds. Once, the popup for the reverse-ETA change came immediately after I dismissed the first.
CBenson wrote:2) I also get annoyed when I'm rerouted to a different turn at an intersection when I'm already so close to the intersection that I have had to commit to the previous route. I just can't think of nice things when waze essentially tells me "if you were in the right lane you could take this exit and save some time, but you're not as I was telling you to turn left in another block."
gettingthere wrote:Great point. It is useless to get rerouted to avoid traffic unless there is sufficient advance notice. On a highway, likely Waze should not try to reroute you to an exit that is 100 feet way - 4 lanes over. I know that Waze has not concept of what lane you are in or how many lanes there are. So likely they should not try to send you off of an exit or to another highway if it any less than say 1/2 of a mile away.
gettingthere wrote:Another issue I have noticed in regard to this is that Waze will tell you it has rerouted you to save time, and THEN actually calculate the new route vs. prior to the notice. So if you happen to lose data connection, the routing server times out, etc - you don't actually get a new route!
gettingthere wrote:guri211 wrote:I hope Ori will explain that soon, so we will know if we could start testing the fix right now or have to wait.
Likely we won't get another response until next week. I am 99% sure the fix is not yet installed on the routing servers.
foxitrot wrote:gettingthere wrote:guri211 wrote:I hope Ori will explain that soon, so we will know if we could start testing the fix right now or have to wait.
Likely we won't get another response until next week. I am 99% sure the fix is not yet installed on the routing servers.
A hour ago I've checked our usual "Friday evening city-wide traffic jam" (INTL servers) - apparently no fix applied yet.
gettingthere wrote:I am 99% sure the fix is not yet installed on the routing servers.
gettingthere wrote:Until Waze resolves this issue with the traffic not being properly factored into the routing, the usability of Waze is highly compromised. Traffic avoidance is the primary function of Waze.

gettingthere wrote:The is no possible way that traffic can build 4 minutes, ease up 3 minutes, build 4 minutes, ease up 3 minutes in a matter of 30 seconds...
Return to Navigation & Routing
Users browsing this forum: No registered users