CBenson wrote:Its a routing algorithm issue.

The live map shows routing algorithm fastest route. But waze routes fine if the navigation type is set to shortest.

Bluebonnet.jpg

Thus, I do not believe that any correction the map is warranted. My understanding of the issue is that with the speed data that waze has, waze has calculated that on average it is faster to take the right/U than it is to wait at the light to make the left turn. Sometimes you can fix this by actually driving the U route so waze gets better data.

I'm not sure that this is considered a "problem" to be fixed, as based on the waze data it seems that it is the fastest route.

Hmmmm That makes sense until I take a look at the actual figures.

I would like to know how they compared the two routes and come out with faster for the longer. Something is seriously wrong with their algorithm!

Neglecting time lost making turns, here is what I calculate for time to get to the node where the left turn is made on the short route:

segment 1 (short route) Length: 15 meters

Average speed for segment*

B->A: 20km/h (12.4mph or 5.543 meters/second) = 2.7 seconds

total 2.7 seconds

segment 1 (longer route)Length: 178 meters

Average speed for segment*

A->B: 54km/h (33.6mph or 15.021 m/s) = 11.85 seconds

segment 2 (longer route) Length: 18 meters

Average speed for segment*

A->B: 6km/h (3.7mph) = 10.88 seconds

segment 3 (longer route) Length: 81 meters

Average speed for segment*

A->B: 11km/h (6.8mph) = 26.64 seconds

segment 4 (longer route) Length: 91 meters

Average speed for segment*

A->B: 9km/h (5.6mph) = 36.35 seconds

total 85.7 seconds

85.7 seconds seems quite a bit slower than 2.7 seconds!

I think another possible 'fix' is to make the 'crossover' on the long route a 'parking lot road'.

Any objections to this?