The UR at this location is similar to many I’ve seen, usually I just shorten the u-turn segment under 15 meters so Waze doesn’t use it. Any idea how to really fix these? If UR isn’t present, screenshot below.
http://i.imgur.com/1ATy4Tl.jpg
But it is legal to make U-turns on Rte. 28 at this intersection. There’s nothing wrong with the map, it’s a routing engine error.
Yes, you are correct, but I was just wondering if there was any way we could fix such problems. It doesn’t seem there is. Pretty much have to rely on the user to see the error and turn anyway. And hopefully do it fast enough that the routing server thinks it’s the new, fastest way.
I should note that their intended turn was a left on Machen. So the issue being it routed them down to a U-Turn, then right-turn, instead of just turning left earlier.
The theory is that if anyone is ever determined enough to actually proceed south, make the U-Turn at New Braddock, and then go back to Machen, and this happens some unspecified number of times, Waze will learn that this route isn’t really so good after all. But if no one ever actually does this, because there is no good reason to do it, I don’t know how Waze can ever learn. 
Nonetheless, my philosophy has evolved to the point that if the user has tapped the “Map Issue” button even though there is nothing wrong with the map, I close it as “Not Identified” without a second thought. It may be an issue, but it is not a map issue.