[SUPPORT] Traffic Avoidance Failure

[islupepa]

It looks like there are multiple routing servers answering our requests and some of them do not have information about traffic. This could cause such problems.

Today morning, same alternative routes, same minute, 2 results rotating:

07:26:10 UTC: 20 / 21 / 23 minutes
07:26:17 UTC: 23 / 24 / 27 minutes
07:26:27 UTC: 20 / 21 / 23 minutes
07:26:35 UTC: 23 / 24 / 27 minutes

http://dl.dropbox.com/u/10259654/SC20120306-082610.png
http://dl.dropbox.com/u/10259654/SC20120306-082617.png
http://dl.dropbox.com/u/10259654/SC20120306-082627.png
http://dl.dropbox.com/u/10259654/SC20120306-082635.png

It´s strange that the third route suggestion varies in time since there is no automatic traffic jam identified.

[gettingthere]

That could explain the issue with the rotating messages, traffic buildup - traffic freed up. If the routing servers don't have their data in sync the client could be getting different data for each server.

Waze, is this a possible problem?

[foxitrot]

It´s strange that the third route suggestion varies in time since there is no automatic traffic jam identified.

How can you be sure there was no traffic jam marked at the third street

If you remember, this and few other threads are full of screenshots, where the manual report pins were displayed on the routes' overview, but the red jam markings were missing. This might eventually be the same case.

BTW, at the times (08:30 at workdays) the Rožňavská street is usually full as well.

[islupepa]

How can you be sure there was no traffic jam marked at the third street

If you remember, this and few other threads are full of screenshots, where the manual report pins were displayed on the routes' overview, but the red jam markings were missing. This might eventually be the same case.

You are right

[CBenson]

I just wanted to mention that there was another accident on New York Ave this morning similiar to the one I discussed above. The routes waze provided clearly took the traffic into account and tried to use roads with less traffic. (The routes didn't work out so well due to map problems, time based turn restrictions, waze's inability to handle closed roads and some other issues completely beyond waze's control, but the issues didn't appear to be not taking the traffic into account.)

[gettingthere]

I just wanted to mention that there was another accident on New York Ave this morning similiar to the one I discussed above. The routes waze provided clearly took the traffic into account and tried to use roads with less traffic. (The routes didn't work out so well due to map problems, time based turn restrictions, waze's inability to handle closed roads and some other issues completely beyond waze's control, but the issues didn't appear to be not taking the traffic into account.)

So maybe Waze now has the fix they described several posts above deployed to the routing servers? Or maybe there are additional issues with routing servers not having the same traffic info across all of the relevant routing servers and our Waze applications get inconsistent routing and traffic data due to the discrepancy? Or maybe that is the issue that Waze has identified and is going to patch?

We know that Waze added additional routing servers in sometime after August 2011 to make the routing infrastructure redundant to help avoid the route timed out errors. Maybe these traffic avoidance, ETA, and route recalculation issues started to occur after the redundant routing servers were deployed?

[osbumlets]

So maybe Waze now has the fix they described several posts above deployed to the routing servers? Or maybe there are additional issues with routing servers not having the same traffic info across all of the relevant routing servers and our Waze applications get inconsistent routing and traffic data due to the discrepancy? Or maybe that is the issue that Waze has identified and is going to patch?

We know that Waze added additional routing servers in sometime after August 2011 to make the routing infrastructure redundant to help avoid the route timed out errors. Maybe these traffic avoidance, ETA, and route recalculation issues started to occur after the redundant routing servers were deployed?

Sadly, we'll probably never know the answer to any of those questions.

[krankyd]

Not so sadly, I'm happy to say we found the issue and deployed a fix.

The fix should solve two of the three problems mentioned here:
1. ETA is not realistic / changes while you drive
2. Traffic avoidance is not working (and takes you smack to traffic)

There's one more problem still being worked on:
3. Route graphic preview does not show all events on the route

====

Please let us know if there's any feedback on issues #1,2.
If you can post examples - like the ones you posted here before - of cases where waze's ETA is still off, or fails to avoid traffic, please let us know.

[islupepa]

Not so sadly, I'm happy to say we found the issue and deployed a fix.

That's great news:)!
There's another issue though, maybe unrelated, with the ETA:s.
If you plan a route in São Paulo, for example the following one http://world.waze.com/livemap/?zoom=6&l ... g=61767782

you will get almost the same estimated time for the route in the middle of the night and during rush hour if there isn't any automatic traffic information on the route (black, red, orange lines on the route). Seems like it is not considering the time of day/night when it gives me the ETA.

[guri211]

Please let us know if there's any feedback on issues #1,2.
If you can post examples - like the ones you posted here before - of cases where waze's ETA is still off, or fails to avoid traffic, please let us know.

Hi Dror,

Still the same problem:

Racianska, Bratislava, Slovakia (Permalink); 2012-03-12, 06:22 UTC, guri211, World server

Route to traffic jam start point: 7 min / 4.5 km
http://dl.dropbox.com/u/10259654/SC20120312-072137.png
Full route incl. traffic jam: 12 min / 6.4 km
http://dl.dropbox.com/u/10259654/SC20120312-072207.png

Traffic jam distance: 1.9 km; speed: 7 km/h; confirmed by 2 wazers incl. 1 manual report
Traffic jam duration should be 16.3 minutes. Full route duration should be 23.3 minutes (instead of 12 minutes)

D1, Bratislava, Slovakia (Permalink); 2012-03-12, 07:16 UTC, guri211, World server

Route to traffic jam start point: 4 min / 2.1 km
http://dl.dropbox.com/u/10259654/SC20120312-081650.png
Full route incl. traffic jam: 12 min / 9.7 km
http://dl.dropbox.com/u/10259654/SC20120312-081628.png

Traffic jam distance: 7.6 km; speed: 29 km/h; confirmed by 4+ wazers incl. 2 manual reports
http://dl.dropbox.com/u/10259654/SC20120312-081704.png
Traffic jam duration should be 15.7 minutes. Full route duration should be 19.7 minutes (instead of 12 minutes)