Technically legal, but ill-advised U-Turns

MN law is subjective on U-turns. Basically, except for curves and hills, U-turns are legal everywhere… until their not. Essentially, your U-turn is legal if it can be made safely and without interfering with other traffic.

This presents a problem from a waze perspective. I have seen numerous URs for Turn Not Allowed when Waze directs them to make a U-turn somewhere that might not be great. For example, this segment is double-left-turn allowed, but the intersections left-turn lane is actually for the next intersection: https://www.waze.com/editor/?env=usa&lon=-93.24739&lat=44.88353&layers=773&zoom=7&segments=78789735

Likewise, this segment allows the double-left-turn, but there is no lane for slowing down and turning: https://www.waze.com/editor/?env=usa&lon=-93.14912&lat=44.86060&layers=1957&zoom=7&segments=67107576

Thoughts?

I don’t see why the cross segments need to be two way here. That would suppress your unneeded u-turn instructions. Just make the ramp cross segments one way.

Unlike the first suggestion, you are going to need routing out from the Egandale segment, so making the segment shorter with modifying the geometry a bit to not catch a unknowing editor’s attention, to say maybe about 10 meters might help with suppressing the u-turn instruction as it is a hack of sorts we have been doing without creating a bow-tie intersection. Hope that helps, let me know if you need more guidance or help. I adjusted it just now since I was noting some other issues in the area that kept me busy too… just to let you know.