I can’t see anything wrong with this junction, I think it should already be avoiding u-turns. 90deg, 9m no-name, 90deg
My first opinion is that your permalink is for a closed UR in Kemsing. :lol:
gah! updated 
My second opinion is that HQ are pissing around with the routing engine and lying about it and this is going to be a major topic at the UK Meetup in 2 weeks. :twisted:
I have always understood that the u-turn prevention depended on the short segment being un-named. This very junction was an example of that. Something like a year ago, it was giving u-turns. An inexperienced editor wanted to complicate the junction to prevent u-turns. Instead, I removed the name from the segment in the middle - and Waze stopped routing u-turns through here.
Recently, there has been talk on the forums that the naming of the short segment is irrelevant. This information does not appear in the Wiki: whether it ever did, I’m not sure. I’ve learned the rule by “word of mouth”. Waze staff are also saying that the naming of the segment has never had an effect. I do not believe this at all. I have personally named/un-named hundreds, if not thousands of connector segments to control u-turns. I am totally convinced that, until recently, it worked. Indeed, if it doesn’t the only way to control u-turns would be bowties. I don’t mind them, but I know others do.
OK. Rant over. :lol:
Back to this specific example: it should not route a u-turn, no matter what the rules may have been or are. Indeed, the brand-new development version of JAI, which indicates forbidden u-turns, shows these as forbidden.
It’s got to the point where it’s beyond me to remember which is the current channel we’re supposed to use to report routing errors to HQ. If you can’t find anything you can access, come back to me and I’ll conduct a similar search in the Champs’ forums.
For reference: screen grab showing yellow circles from JAI, indicating forbidden u-turns
Another u-turn UR raised yesterday. Same junction, but approaching it from the north this time.