The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "User:RussPA/Elevations"

From waze
Jump to: navigation, search
(100% bullet points)
Line 1: Line 1:
So how should a street Elevation be mapped?
+
Elevations should be mapped more-or-less realistically, with elevation numbers showing where the higher-elevation segments above lower-elevation segments.
 
+
 
* If a seagull can fly right under it, it’s a bridge (level greather than 0).
 
* If a seagull can fly right under it, it’s a bridge (level greather than 0).
 +
* A road is only level = +2 if there’s another bridge (+1) running underneath it.
 
* If it is underground, it’s a tunnel (level lower than 0)
 
* If it is underground, it’s a tunnel (level lower than 0)
 
* For every other case the road is ground level (level = Ground), even if it’s artificially elevated or dug under street level.
 
* For every other case the road is ground level (level = Ground), even if it’s artificially elevated or dug under street level.
 
+
*[[File:Tight_Marking.jpeg|thumbnail|right|Tight Marking]] Roads that have poor or no GPS reception should have the tunnel checkbox set. The road segment must begin at least 50 feet before GPS signal is lost, and continue at least 50 feet after GPS signal is recovered.y.
 
+
*'''Tight Marking'''. We mark bridges with level = +1.  In some cases we will need to split segments into two or more segments to mark only the right parts of the road as a bridge or a tunnel. This is Tight Marking.
We mark bridges with level = +1.  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. An example of this "tight marking": 
+
* At interchanges, where there is already a nearby junction, it will not be necessary to use "tight" marking for an elevation change on the overpass.  Use the existing junctions if at all reasonable.
[[File:Tight_Marking.jpeg|thumbnail|none|Tight Marking]]
+
 
+
<br> We only mark a road as level = +2 if there’s another bridge (+1) running underneath it.
+
 
+
<br> Regarding tunnels: It is important that a tunnel segment has GPS lock before and after the tunnel. As we all know, this is impossible once you're in the tunnel so keep the "tight marking" at least 50ft BEFORE and AFTER the tunnel and don't forget to tick the Tunnel checkbox for the segment going through the tunnel.
+

Revision as of 16:23, 22 February 2016

Elevations should be mapped more-or-less realistically, with elevation numbers showing where the higher-elevation segments above lower-elevation segments.

  • If a seagull can fly right under it, it’s a bridge (level greather than 0).
  • A road is only level = +2 if there’s another bridge (+1) running underneath it.
  • If it is underground, it’s a tunnel (level lower than 0)
  • For every other case the road is ground level (level = Ground), even if it’s artificially elevated or dug under street level.
  • Tight Marking
    Roads that have poor or no GPS reception should have the tunnel checkbox set. The road segment must begin at least 50 feet before GPS signal is lost, and continue at least 50 feet after GPS signal is recovered.y.
  • Tight Marking. We mark bridges with level = +1. In some cases we will need to split segments into two or more segments to mark only the right parts of the road as a bridge or a tunnel. This is Tight Marking.
  • At interchanges, where there is already a nearby junction, it will not be necessary to use "tight" marking for an elevation change on the overpass. Use the existing junctions if at all reasonable.