I am still waiting for somebody to unlock this junction, so that I can add correct turn instructions.

https://www.waze.com/en-GB/editor?env=r ... ,121909480

Could you give us an idea of what you intend to add/change at this junction.

Lane Guidance is currently only designed to work with simple junctions or H/# layouts, complex junctions are not yet supported and adding LG can often cause more confusion than it solves. Adding LG to complex junction should therefore only be done with careful consideration.

If you are asking for the JB removal it seems as though you are planning to remap the junction to suit LG which shouldn't really be done at this time.

All unlocked and JB removed. We’re curious to see your changes.

Attempt number 2nd

Personally I'm not impressed with how you've mapped this.

You asked for the unlock to simplify the junction but have instead mapped 3 segments on the same section of road solely for Lane Guidance. LG doesn't support complex junctions and we should not be hacking the map to make LG work, instead we should be pressuring Waze to improve LG and make it work with all types of junctions.

We should not be adding fake stub segment just to make LG work. We should not be hacking the map solely for the purpose of adding LG. There was no original routing issues at this junction and we have already had complaints that LG has made this junction confusing.

I have reverted all changes and await an improvement in the LG tool.

You should maybe re-read the public and private messages I have sent you that I have repeatedly suggested that lane guidance doesn't support complex junction mapping. Clearly you don't bother listening to advice, and continue to map based on your own standards. I admit that I was wrong to attempt to keep some LG at this junction after removing all your false segments that simplified this junction. This junction didn't have a mass of URs about routing or LG before you thought you would improve it. It only started to generate URs after your simplification.

In future if you'd like us to publicly start listing editors bad editing and being offensive to each other then we can, however, you may wish to review your editing area first, compare your excessive use of TIOs, excessive LG, false segments, naming of segments, etc to the rest of how the country is mapped.

I will say again LG doesn't support complex junctions, and is only intended for basic layouts and H/# junctions. Again I suggest you petition Waze HQ to improve the LG tool to support more junction types and heuristics to support linking adjacent instructions, you can do so on the following resources;

• Waze UserVoice - https://waze.uservoice.com/
• Waze LG forum thread - https://www.waze.com/forum/viewtopic.php?f=8&t=301138
• Waze Centercode - https://waze.centercode.com/welcome/

As with all my editing on Waze, I will happily removed all LG from this junction when I have the spare time.

And finally, if you are unhappy with how I have treated you, or any of my advice, both publicly and privately, you can request I get banned via the UK Country Admin contact email.

Are these little stub segments that go no-where going to cause more problems in the future?
It seems an un-neccessary hack to show LG on segments with only one connection. Would it not be simpler to split the original segment at this point and use LG as intended?

If we ever do get LG on roundabouts, I think this shows a problem in how it might be implemented. Having LG on the approach to a big roundabout would be great, its often not clear where you need to be until its too late. But having LG on the actual roundabout? It might seem helpful when your're in WME world, but not sure about the reality on the ground.
On this example on the bottom "roundabout", a user travelling on A39(S) to London Rd is going to get three separate LG instructions over a very short travel time...if the traffic lights are in your favour, I'm not even sure that Waze could keep up with displaying the lanes.