The user indicates that a U-turn isn’t allowed. They were going east on Lakeshore, and were prompted to do a U-turn at Carlaw, to eventually go north on Morse.
Lakeshore is divided at this point, so it appears there a segment of road between the eastbound and westbound lanes. Such a segment doesn’t really exist.
I considered restricting turns from this “segment” onto Lakeshore, but that won’t work, as a regular turn is allowed for northbound and southbound traffic.
Note that the problem is there for both eastbound and westbound Lakeshore traffic.
Pondering this further… One solution would be to bring the divided roads together like an X at each intersection (removing the pretend segment). That way, the turns could be assigned correctly. It might make the roads look ugly in the map, though.
I just checked the the wiki: https://www.waze.com/wiki/Junction_Style_Guide. Search for “Bow tie intersections”. That appears to be what we need to do here. None of those segments is locked, so I’ll go ahead and do that now. I’ll also check other intersections in that area of Lakeshore.
With bowties we have to watch that the angles are not too sharp. Right now, eastbound traffic on Lakeshore going straight through will probably get a “turn right on Lakeshore” because the change of heading between these two segments is 49°. Try adjusting it so that it is less than 45°.
The other trick – make that joining segment (the one between the two directions of a split road) less than 15m long. That will apparently key the routing engine to not use it for a u-turn (and seems to work, as it has resolved any issue that is reported when I’ve used it).
With the bow-tie, be ready for URs like “the road doesn’t look like this” and “there’s no curve to the road here”. Ultimately, you could probably unsplit that road, if you wanted a really good solution.
Ok, I’ve changed it back to an H. I went to test it, but the Live map still shows the bow tie (of course). Curiously, it still routed it as a U-turn. I’ll wait until the recent H reintroduction is reflected on the map, and then test it again. If necessary, I’ll un-divide that section of Lakeshore.
Good point. In general you aren’t supposed to make a U-turn at a “controlled” intersection, although I’ve never been able to get a clear explanation of what constitutes “controlled”.
Generally, at an intersection with a median, if there are turn signals and no U-turn prohibited signs, then U-turns are generally permitted.
This 11m segment on Carlaw Ave is clearly not preventing the routing server to make a u-turn.
See the user error just east of the intersection.
There is no other option here and the intersection need to be a bow tie to prevent the u-turn.
Maybe Waze should implement sequential turn restrictions in the future (where it will prevent a sequence of turns), but in the meantime this intersection need to become a bow tie, even at the cost of not pleasing graphically some of the Wazers in the area.
No Problem.
I suggest you add a landmark on the editor, where the UR is, to ask editors not to handle it.
Let us know what the staff had to say about this.
I’ve added a comment to the UR – I hope that people are looking at the comments before closing them. I’ve also locked the segments in question to ‘6’ to avoid someone trying to “fix” it before we get something back from the staff.
FYI: my contact is away until the 15th, so it will probably be after then that we hear back.
I find people are following the ethics of the conversation and not closing open tickets for no reason.
I hope this will help.
I wish there was an option to lock a UR to a higher level so people can’t close it by accident.
Also, there should be a way to see closed URs. Maybe Waze staff has this kind of ability.
If you recall, I had changed it to a bow tie for a while. Strangely, it was still permitting the U-turn, even those the turn restrictions should have prevented it. It all seemed quite odd, but I didn’t worry about it much, as I was about to switch it back. Sounds like there’s a ghost at this intersection.
