A driver reported a UR at this location: https://www.waze.com/editor/?zoom=8&lat=51.52227&lon=-0.16236&layers=1989&segments=148378601&env=row
At the point where Melcombe Place (eastbound) meets Melcombe Place (westbound) and Melcombe Place (bi-directional), the app gives a Turn Left instruction to continue onto Melcombe Place (bi-directional). Street View shows that in fact you need to continue straight, or at most, keep left, at this point, and a left turn would take you the wrong way up a nearby one way street.
I’ve probably worded this terribly, but if you have a look at the link, all should become clear. Ish.
My question is: What is the best way to remove the “Turn Left” instruction? Does the intersection angle need amending, or does the whole intersection need playing with?
TIA,
Dave (n00b)
The angle is currently 48 degrees at the split, and it would need to be less than 45 degrees to change the instruction. If you are not currently using the Junction Angles script, it is excellent for precision work like this.
In addition to the Junction Style Guide, if you have not yet seen it, here is a page from the wiki that goes into more detail on turn versus keep.
Thanks for this, David.
The scripting possibly goes over my head a little (fairly new here), but the provided links make for interesting reading. I shall research before attempting any changes.
Dave
No problem. You would just need to bring down the circled node a little to get the angle that you are seeking.

Ah, that wasn’t nearly as complicated as I feared! Have gone ahead and made that change.
Follow up question - is there a way to test this without physically navigating it - i.e. a virtual app?
Thanks,
Dave
Yes. You can test out the change on the Live Map once the map tiles have updated. Right now, you can see the “turn left” instruction, but just go to Navigate, drop your origin and destination points, click “Find routes”, and click on the route to see the turn-by-turn instructions.

Thanks, I feel like such an ignoramus! Enjoying learning these things though 
I wouldn’t say that, it looks like you are doing pretty well and asking the right questions. Like you I’m still on a steep learning curve.
In my opinion (and I’m very much a junior editor as only been here 3 months) I can’t help feeling that the problems here stem from the original roads being over complicated, that section of road has been made a dual carriageway when really a single road would suffice, it’s only about 50 yards long through the hotel / station forecourt, it’s a minor road with a long traffic island.
If you read the Waze Wiki for editing guidelines one of the points it makes is simplicity and I’d ask myself what difference it would make to navigation if it was a single road. I think the guidelines for making a dual carriageway is something like 5 metres between carriageways, at Marylebone you will be lucky if there is much more than 3 feet?
Personally, at that “junction” I wouldn’t expect to get any verbal directions, I see it as one road with a slight kink. I check in Street View from some way back and ask myself what directions I would need.
If you were in the green taxi below would you need any directions to drive towards the camera?

The last question I ask myself is what are the consequences if I really louse it up? It’s a minor road, you may get a few UR’s, but as long as you check back in a couple of days when the map updates and make sure it routes correctly in all directions then there shouldn’t be any major problems, but I wouldn’t start editing the Marylebone Road… 
Apologies, I probably waffled a bit above and didn’t answer your question.
If you make the angle shallow enough you won’t get any directions when the dual carriageway ends (which is possibly what you want here), would have to look up in the Wiki to find out how shallow but see this example where there are no directions making the transition from dual carriageway to single carriageway.
Don’t forget you can really zoom in with the editor to make just a really short section at the shallow angle, this will not then been seen on the client sat nav.