User:TheLastTaterTot/Elevation

From Wazeopedia

< User:TheLastTaterTot

Revision as of 18:42, 2 October 2015 by TheLastTaterTot (talk | contribs) (Created page with "{{anchor|Elevation}} The Road Elevation should be changed where one road passes over another. By default, the Elevation of a segment is '''Ground''' (zero). When two segments...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The Road Elevation should be changed where one road passes over another. By default, the Elevation of a segment is Ground (zero). When two segments overlap but do not actually connect in the real world, the value of Elevation for each segment must be different. This ensures that the Waze problem detection system doesn't flag the spot where two segments overlap as a location where a junction might be needed.

The visual representation of the relative Road Elevation is different when viewed in the Waze Map Editor (WME) and the Client application.

1. The Client App displays segment elevation based on the road type only, meaning Freeways are always on top, Major Highways are next, followed by Minor Highways, Ramps next, Primary Streets below all those, and finally Streets are at the bottom. This is the same order seen when setting the road type in the editor.

2. The WME uses the Road Elevation setting to display the relative elevation of the road. It displays the road with the highest "elevation" number at the top of the visual stack and works its way down as would be expected.

Although the client application does not benefit from the Road Elevation setting, it is recommended to set the Road Elevation relative to the physical mapping in the real world to enable possible future Client application updates to show the same visual representation as the WME.

3. Elevation -5 is used for non-drivable roads to help ensure that the routing engine does not try to connect or route drivers from roads onto non-roads by mistake. It acts to prevent false system reporting that the roads should be connected.