There seems to be some errors with this junction.
unlocked :mrgreen:
please give us a shout when you finish. we need to re-locked the main roads
I have fixed the error on the turn, it was also system generated report.
Kingsway is now relocked, let us know if there was something I missed.
I think Neil wanted to have a go at fixing it. 
I am almost certain that I had put a 2nd road under the visible one here and used restricted turns on the two roads to stop it constantly generating URs from people saying U-Turns are not allowed.
Did you find a 2nd road and delete it?
That probably would cause an automatic error to be reported, but it was IMO a good solution, and probably needs to be put back.
I did a similar one here : https://world.waze.com/editor/?lon=-2.22649&lat=53.39199&zoom=8&layers=BFTFTTTTTTFTTTTTTTTTFT&segments=150038564 This so you can see what I mean. Do not change this or hundreds of people will get directed to come off at J3 and do a U turn to get into South Manchester.
I see what you did, as this U turn error has caused numerous problems elsewhere. I think he will probably do the same thing as I did. I will reinsert the hidden road now, but I think it will only continue to cause the same issues of the turn not being allowed, which is what I think he is trying to repair.
FYI, There are two other methods for preventing U-Turns:
- an unnamed segment that is less than 15m (or 10m?) will not generate a U-Turn [ref]
- the ‘mapcat bowtie’ junction, where all segments meet at a single node. [example]
I’ve not seen this double-segment approach, but it looks like it could work rather well.
Tim, have you seen this ‘mapcat bowtie’ in action? How does it perform? I have not seen one (yet) and was wondering how does it affect (if at all) client app when driving through one of those. I can think of several places which could use one of these! 
I’m pretty sure many editors will remove a bow-tie if they receive a UR at a junction containing one. They will take one look at it and think “that must be the problem”. Of course, if the junction is locked down to a higher level that’s not so much an issue.
I haven’t seen one myself, but I know that these are widely used in the US to fix exact this issue. The bowtie will not be discernible on the client, because it is so small, and navigation will be exactly as you would expect.
I feel that the bowtie approach is both simple, and obvious. The other two methods may look neater on the map, but are less obvious to the inexperienced editor, and users won’t noticed any difference.
Side note: If you’re getting URs about U-Turns, then this is indicative of problems with roads else where. Try to guess where the user is driving to, and look for common map issues in that direction.
I was going to suggest the bow-tie solution, similar to how it has been fixed now. I have not used Waze for that long but I think this is the best way to avoid U-turns.
… On that matter, I tried to fixed this junction in a similar way:
https://world.waze.com/editor/?lon=-2.25355&lat=53.48677&zoom=8&layers=BFTFTTTFTTTTTTTTTTTTFT
I deleted the small road in the middle that caused the U-turn, saved it to update my screen and then noticed one segment of Trinity Way is locked. I cant change it back now as it wont accept any changes.
Could somebody either unlock it or do a quick fix?
:oops:
Unlocked
Thanks. I fixed that one.
Good work indeed, Neil.
Just few things I found:
- I think it’ll be good to add the ‘At-Grade Connectors’. Wiki here.
- Some streets around do not have end-note. Two of them have not even been collected.
If you like, please fix them :mrgreen: (note: not your fault anyway :mrgreen: ) Wiki here.
I notice that one section of Trinity Way, just off the “Bow-tie” junction presently has no name nor city, not sure if that will impact on routing?
Regards,
Will.