URGENT L5 fix - Maidenhead

Oh crappity crappity crap… trying to fix a badly reconstructed roundabout here and hadn’t noticed that one of the roads joining onto it was locked at L5 until I’d already deleted the old roundabout in readiness to draw in the new one :oops:

Can a L5+ please stick a new, properly constructed, roundabout in here ASAP so that we don’t end up with even more routing problems than were already being caused by the previous iteration of the roundabout.

As an aside to this (and coupled to the L5 renaming request I’ve just posted), can someone remind me what the point of having all of these segments locked to L5 is anyway? I vaguely recall it had something to do with them being considered “sensitive” segments due to them crossing over/under motorway segments, but since all the latter are locked to L5 now I fail to see what benefit there may still be in keeping these non-motorway segments also locked at L5, particularly not when it leads to problems like this one…

Red-faced thanks all round,
Chris

Done. I don’t recall being told that all segments crossing motorways should be locked to 5. I may have missed it, but I can’t see any logic in the idea, so I’ve downlocked it to Auto(4).

Thanks John!

The thing about locking segments crossing motorways was from a few years ago, IIRC it was to prevent any unexpected junctions being created between the motorway segment and the crossing segment, but I can’t recall if the lock was to prevent other editors from creating the junction or if it was to prevent a glitchy WME (or possibly even Cartouche) from doing it all by itself. I just remember that it was a real issue at some point in the history of Waze map editing…