OK, sorry about all the posts, I’m still trying to understand what causes various quirks in Waze’s routing.
This UR for example: Permalink
I think the user was heading south on Leonard St, and Waze tried to shunt him/her off into a one-way spur that probably ought to be tagged a parking lot road.
BTW the MBTA Fitchburg line is an elevated train track – Leonard street crosses under it in a tunnel. However since the Railroad segment on the map is at level -5, it is shown as underneath the road. Is that the way it is supposed to be?
If you manage to explain the strange zig-zag in the routing, perhaps you can also explain this wrong-way use of another parking lot road further down Concord Ave in the same UR. Permalink
Note: this report was from before the roll-out of the new construction re-routing feature (which I hope would have been indicated with an icon anyway).
Oh, I should say that I looked, but I wasn’t able to find any strange geometry nodes, disconnected segments or turn restrictions that might have explained either effect.
Are these still open? If so, please leave them open. I would like to show the Waze staff that this issue is happening all over & not just in Connecticut.
Has anyone else noticed a significant increase in this “around the block” routing problems? I’ve started to see more of them since the “Minimize Turns” option disappeared from the client…
I would also very much like to hear what waze staff would say about this route. It is much worse than around the block routing. The second screen shot is showing a route the wrong way over a one way parking lot road. I can still see the UR in the sandbox.
Here’s another example for your collection: permalink. I’m leaving this open for you, although there’s no guarantee that someone else won’t close it, so here’s a screenshot, too.
I checked, and there are no turn restrictions preventing the left turn that would avoid going around the block.
FWIW, this route may in fact be faster than waiting for the left-turn light. The only difficulty is that turning right from the Service Road onto Beauregard puts you in the right-turn-only lane, unless you cut across it to go straight through the intersection.
I’m very familiar with this intersection. While it may be true that the three-rights maneuver could sometimes be quicker than waiting for the left-turn arrow, there’s no way the Waze routing server could possibly know that. The route it gave uses all the same segments as the more direct left-turn route, plus four additional segments. The server only stores speed data on a per-segment basis, as far as I can tell; there isn’t any separate speed recorded for traffic turning left as opposed to traffic going straight. So there’s no way any possible comparison of the two routes could measure the longer route as being preferable.
The server stores transit times for each segment based on time of day, and also the amount of time each turn at each junction takes. So it does know that the left turn from Route 236 onto Beauregard introduces a considerable delay, whereas the additional segments and right-turn times are comparatively short.
