This segment must have been accidentally locked, as the other segments near it are not locked at all.
What’s wrong with the segment?
I’m with txemt.
There are plenty of reasons to lock just one segment like that.
Have you pm’d AlanoftheBerg? (The editor who last worked on it)
He could have locked it because he didn’t want someone to come along and make a turn that’s not allowed, allowed, or something to that effect. Since AofB locked it yesterday, I’m assuming he has a very good reason. If it was something from 2 years ago, or maybe even this time last year, I may be inclined to unlock it, or look at it, but since the edit was done yesterday, you’ll have to ask him about it.
If I recall correctly, Alan was helping an editor here and needed to lock it to stop others messing. This is a bit tricky area. Hence, it should stay locked.
I was the one he was helping. I can no longer work on the area because that section is locked, now.
We still need a reason to unlock it. We’re not going to unlock it just because it’s locked. Alan locked it for a reason and until you explain your reasoning for needing it unlocked, we’re not going to unlock it.
I see a problem at that intersection.
It looks like EITHER this segment
https://www.waze.com/editor/?zoom=8&lat=39.79962&lon=-74.93627&layers=BFTFFTTTFTTFTTTTFTTTTFT&segments=64749053
should be one-way east bound
OR
west bound traffic needs access to it.
https://www.waze.com/editor/?zoom=8&lat=39.79966&lon=-74.93635&layers=BFTFFTTTFTTFTTTTFTTTTFT&segments=71818861
Traffic west bound has no way to go that way.
and south west bound traffic from this segment has no permission to go that way either.
It looks to me like the highway designers wanted to make everyone that wants to go west on Clementon from W White Horse to go this way,
https://www.waze.com/editor/?zoom=7&lat=39.79956&lon=-74.936&layers=BFTFFTTTFTTFTTTTFTTTTFT&segments=71833723,71833722,64749050,64749054
but the street view of that area doesn’t show any signs forbidding the left turn from WWH.
Perhaps drivers there ‘know’ that you gotta turn right to go left???
Looks to me like your first option is the right one: mark that Clementon segment one-way, and let traffic going to Clementon take the other segment. I would also move that junction with W White Horse Pike slightly southeast from where it is, so access is balanced from all three directions using it.
There is a sign right about here.
THANKS for that information. Great way to show it!
Then the intersection would make more sense (and get rid of a couple of red arrows) by making
https://www.waze.com/editor/?zoom=8&lat=39.79962&lon=-74.93627&layers=BFTFFTTTFTTFTTTTFTTTTFT&segments=64749053
one way east bound.
As for what ncc1701v said, if this is the junction he suggests moving South East, then that might break WAZE following people east bound turning right at that point.
I wonder what jreed wants to do.
Yes that was the one. I recant. Leaving it as it is is fine.
Also a “No Turns” sign here, though its hard to read
That section of Clementon rd needs to be two way to allow for Left turns from Park Dr onto Clementon. That was the original problem with this intersection, with how it was set up previously, that was impossible to allow on the map. The soltuion was to make one node for this intersection and add that one way section of Clementon.
I see. So what is it that you wish to do with the locked segment?
That’s too bad :-). If Park Dr is turning left on that segment, should W Whitehorse Pike use it also?
There are No Turns allowed from Whitehorse westbound. All turns are allowed eastbound.
I think Clementon isn’t allowed to go onto Whitehorse Westbound, but is allowed onto Park and EB Whitehorse. (In fact, Google Maps will route you like the Westbound turn is not allowed)
Park is clearly marked as all lefts and all rights allowed.
That locked segment could be angled more so it is a single straight line from the ramp onto Clementon.
I asked for it to be unlocked because I believed it was locked as an error when it was recently created.
There are sever reasons to lock something see http://www.waze.com/wiki/index.php/Automatic_map_updates_and_the_locking_of_roads
Many editors lock everything they edit along major roads,
- to remind themselves that they have finished checking the segment.
- to keep others from changing things without double checking to make sure that the changes are needed.
I usually leave locks as they were EXCEPT when I make extensive changes or when I repeatedly find someone has ‘messed up’ an intersection that I built and have tested.
BE warned: if you make ANY changes to a node or segment that is locked, it becomes locked AT YOUR LEVEL forever until someone of higher rank comes along and unlocks it.
segments I locked when I was level 1 are now locked at level 5 because the locks inherit the CURRENT level of the locker.
EDIT: even though it ‘breaks a couple of Best Practice guidelines’, I think I would do something like THIS:
And, I would ‘lock everything’ around there to make sure that only the allowed turns are really allowed.
I would add the westbound from park to Clementon (at level -1) and join it to the ‘locked’ segment just shy of where the ‘locked segment’ joins Clementon. This allows me to make the Clementon to Park etc., one way east bound and gets rid of some red arrows. I might also make the ‘locked segment’ a bit more like the traffic that would take it.
What do you think of a solution like this for that intersection???
I thought the current situation appears to work and look the best.
Then there is no need to unlock the segment you requested unlocked. Right?