EDIT (Nov. 28th 2011) - this change has now gone live on both US and WORLD editors. See details below the dashed line.
Thanks to Shorty-CM and other wazers who sent us great feedback, we discovered a bug in the way our nodes and turn restrictions behave.
Basically, today you can have a situation where there's no connectivity (in cartouche) / you see a red arrow (in papyrus), but the routing will still route you through the turn.
This is happening because the turn was never set as 'restricted' (though it was never set as 'allowed' either). If it was never set as 'restricted', and waze routing server has no other information that indicates it is not allowed, it might choose to go through this turn, even though it isn't marked as allowed (in papyrus / cartouche).
As more and more people ignore this turn, waze will eventually learn that it is indeed not allowed. But in the meantime, wazers might get a wrong turn maneuver - and this is where this fix comes in handy.
To fix such a situation, we are tweaking the lock mechanism, as follows (all information relevant for Papyrus only, see below for cartouche):
* When you edit allowed / restricted turns for a specific segment, you are locking the turns for that intersection.
* If no turns are edited, the system will treat it as described above. That means, a user who makes the turn will open the turn to be 'allowed'. Once you edit at least one turn restriction on the node, it means all turns for that segment on that node will be locked.
* When you lock a segment, you are locking the turns on both ends of the segment. This is a bit tricky - especially for long segments - as you have to make sure you checked the turns on both ends of the segment.
* Permissions-wise, locking will still lock the segment from being edited by another user who has a lower rank than yours. At this time, we're not going to lock the editing of turns (as we do with the segment), so even if the segment is locked, other users can change the turn restrictions.
* Driving direction of the segment is also locked (as before) from being changed by the analysis of drives.
* The segment's geometry is protected from being changed by the analysis of drives.
So, to sum up:
When you edit (even w/o locking) a driving direction or a turn restriction in the Papyrus you guarantee two things:
1. The routes analyzer (merger) will treat this driving direction as the true direction, and will not open it again (even if a person with a scooter, for example, drove the wrong way in a one-way street).
2. Our routing will treat this driving direction as the true one, i.e. will give a higher penalty for driving against the direction [28/11/2011 -This is still being developed, and will be implemented soon]
In the cartouche:
* We are more limited on the cartouche. When you edit a restricted turn, you are actually locking the entire node. We realize usually you work on all turns in a junction, but this is something you should be aware of if you're still working with the cartouche and not papyrus.
Note - Nov. 7th - the fix is not uploaded yet to the Papyrus. On the cartouche, it is already working as described above.
We will update you once uploaded and operational - should be in the next couple of days.
Finally, a short note about locking your segments as 'protection'.
Locking your segment guarantees that a user with a lower rank will not be able to edit your segment based on his 'drive-by' permissions. However, a user who's an area manager, will be able to edit any segment within his area, even if it is locked.
wazing like a hurricane