Road Attributes: Difference between revisions View history

(Moved Other Situations)
Line 23: Line 23:


These bridges should be marked relatively tightly. This also applies to railroad segment types.
These bridges should be marked relatively tightly. This also applies to railroad segment types.
==<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.&nbsp;'''This should only be done after discussion with the Australian Community team and the approval of the Country Managers'''&nbsp;(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.

Revision as of 15:02, 25 March 2019

Road Names

Speed Limits

Each direction of travel on a road can have a speed limit set on it. Waze uses the speed limit to (optionally) warn the driver when they're exceeding the limit. Editors should map the speed limits on roads with the following considerations:

  • Map the legal speed limit, not the opinion of the editor e.g. speed limits in car parks.
  • Avoid mapping speed limits on roundabouts, as they have no use.
  • Do not map advisory speeds, only speed limits.
  • Where variable speed limits are in use (such as digital signs, alternate speed when raining, school zones), editors should always map at the higher speed limit.

Elevations

The "Seagull Rule" represents Waze's policy for setting elevation levels. The reason for it is related to the representation of roads, tunnels and bridges in the live map and the app.

  • If a seagull can fly right under it, it’s a bridge (Level 1+).
  • Seagulls don't fly underground, these are tunnels (Level -1 and lower)
  • For every other case the road is ground level (Level 0), even if it’s artificially elevated or dug under street level.

For example:

  • We mark bridges with level = 1.
  • We only mark a road as level 2 if there’s another bridge (1) running underneath it.
  • Same logic applies for tunnels (in opposite direction), and further (3,4 & -3,-4).

Note:

Typical Elevation setup at a Bridge

In many cases we will need to split segments into two or more segments to correctly mark only the right parts of the road as a bridge or a tunnel. (This is important for the map’s fidelity and as cues for drivers, see image on the right)

These bridges should be marked relatively tightly. This also applies to railroad segment types.

Other Situations

Roads Not Matching Aerials

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.

"Unexpected" Situations

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.

Vandalism

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).

Toll Segments

These should be locked to L5 to prevent interference.

Level 6 Locks

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.