*<p style="color: blue;">Lock: Level 3</p>
<p style="color: red;">Note: this Road type's usage conditions are still under revision. Please contact your State Manager or Country Manager for more information and guidance on how to use it.</p>
== <span class="mw-headline" id="Other_Situations">Other Situations</span> ==
=== <span class="mw-headline" id="Roads_Not_Matching_Aerials">Roads Not Matching Aerials</span> ===
With the change to Google aerial imagery there will probably be some situations where the current road layout doesn't match the images. It is advisable that these are locked at L3+, to prevent well-meaning editors "correcting" them.
=== <span class="mw-headline" id=".22Unexpected.22_Situations">"Unexpected" Situations</span> ===
These are odd situations that occur sometimes. For example: a no-right-turn where you wouldn't expect one; a short one-way segment at the end of a two-way road; a deliberate no-name segment joining double-mini roundabouts. If you think that a feature is likely to be reverted by someone who doesn't know what was intended, it is acceptable to lock it.
=== <span class="mw-headline" id="Vandalism">Vandalism</span> ===
If an area is subject to repeated bad edits, it may be locked up. '''This should only be done after discussion with the Australian Community team and the approval of the Country Managers''' (who may want to take further action).
=== <span class="mw-headline" id="Toll_Segments">Toll Segments</span> ===
These should be locked to L5 to prevent interference.
=== <span class="mw-headline" id="Level_6_Locks">Level 6 Locks</span> ===
So far we have not identified any occasions where we really need to use L6 locks. We don't have so many L5 editors that we can't all keep track of what's going on, so we hope not to need it. But, if you have a situation that you feel needs a L6 lock, please post on the forum for discussion.