CBenson wrote:Waze staff has stated that they are addressing the circumstance when historic data creates unreasonable routes to cut time. It is acknowledged that many times, Waze prefers to continue straight, make a u-turn and turn right instead of just turning left in the junction just to save a few seconds. Very often this is perceived as a mistake and not as a time saving.
Waze is testing changes to the routing that will prevent such detours if there is under a 30 sec difference between the routes.
Thanks for taking the time to contact them about the problem.
Here is 'yet another example' of erroneous routing through a U turn rather than simply making a left turn.'https://www.waze.com/editor/?zoom=5&lat=30.44363&lon=-91.09093&env=usa&layers=TBFTFFTTTTFTTFTTTTTTTTTTTTTT
The 'faster' explanation often given makes no sense from the data we have available. Segment speeds for the avoided segment 15 m @ 36 kph vs the speeds for the 'recommended segments'
East Bound 33 m @ 22 kph, North Bound 10 m @ 32 kph, West Bound 31 m @ 3 kph. Clearly, the 'avoided path' should have been 'faster', based on total average segment travel times.
Perhaps the 'hidden data' on "wait time" would make it clear. It would be nice if the map editor displayed the wait time at the nodes involved at the time the UR was submitted.
Perhaps the User App could capture that information and pass it along so that it could be displayed along with the Problem Report.