User:Subs5 View history

VisualWikitext
No edit summary
mNo edit summary
(27 intermediate revisions by the same user not shown)
Line 39: Line 39:
[[User:subs5/HOV revision Allowable Restrictions|HOV revision Allowable restrictions]]
[[User:subs5/HOV revision Allowable Restrictions|HOV revision Allowable restrictions]]


Elevation Proposal
[[User:subs5/Junction Box 2.0|Junction Box 2.0]]


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.
[[User:subs5/Junction Box turn restrictions|Junction Box turn restrictions]]


The visual representation of the relative Road Elevation is different when viewed in the Waze Map Editor (WME) and the Client application.
[[User:subs5/Bus or taxi only lanes|Bus or taxi only lanes]]


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.
[[User:subs5/Routing preference|Routing preference]]


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.
[[User:subs5/Partial restrictions new turns|Partial restrictions new turns]]


Although the client application does not currently 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.
[[User:subs5/Editing restrictions|Editing restrictions]]


3. Please refer to your local (State/Country/Provence/Regional/etc.) Wiki page for local guidance since there are some occasional variations. The main guidance is: Lowest Road that sees the sky is "ground" and then raise the elevation for the subsequent road segments up as required. Roads that go under buildings or a body of water would be tunnels and have negative elevation (and marked as tunnel appropriately). This is sometimes called the seagull approach.
[[User:subs5/Segment speed tracking|Segment speed tracking]]


4. '''Bridges''' - Mark a bridge at the start and the end as tight as possible on the actual start and stop of the bridge. Don't worry about excessive nodes to mark a bridge.  If there are two (or more bridges) then mark the start and stop of each one.  The road segment(s) in the middle should be one elevation less than the bridge.
[[User:subs5/Timed difficult turns|Timed difficult turns]]


5.  '''Tunnels''' - Mark a tunnel tight but not as tight as a bridge.  Leave at least 15 m (49.21 ft) '''BEFORE and AFTER''' the tunnel and don't forget to tick the Tunnel checkbox for the segment going through the tunnel.  The reason for the 15 m (49.21 ft) is to allow that each tunnel segment has GPS lock before and after the tunnel.
[[User:subs5/JB resources|JB resources]]


6. '''Non-drivable roads''' - Please follow the road segment elevation guidance for non-driveable roads.    Previous guidance called for elevations of -5 or +9 on non-drivable roads. This is no longer required.  As of the end of 2015 guidance changed to treat elevations on non-drivable segments the same as elevations on any other segment.
[[User:subs5/Hospitals|Hospitals]]
 
[[User:subs5/TIO update for TR UI|TIO update for TR UI]]
 
[[User:subs5/House Numbers June 2018|House Numbers]]
 
[[User:subs5/Virginia 2025|Virginia 2025]]
 
[[User:subs5/Transponder lanes at toll plaze|Transponder lanes at toll plaza]]
 
[[User:subs5/Service road HN update|Service road HN update]]
 
[[User:subs5/RPP Changes|RPP Changes]]
 
[[User:subs5/Camera lock level|Camera lock level]]
 
[[User:subs5/Iowa dirt roads|Iowa dirt roads]]
 
[[User:subs5/Diffences between Waze app and Waze integrated car system|Diffences between Waze app and Waze integrated car system]]
 
[[User:subs5/PLR inheritence|PLR inheritence]]
 
[[User:subs5/PLR inheritence 2|PLR inheritence2]]
 
[[User:subs5/Place2|Places2]]
 
[[User:subs5/DC SpotHero Parking Project|DC SpotHero Parking Project]]
 
[[User:subs5/Parking Lot Area Naming|Parking Lot Area Naming]]
 
[[User:subs5/MAR Continue TIO|MAR Continue TIO]]

Revision as of 13:27, 12 July 2019

Welcome to my Waze wiki page

Elevation Proposal

HNs on Service Road

Verbal Commands for Turns

MAR RAT Guidance

DDI exit left TIO

closed refurb new const table

Closed place for remodel

Road type update unpaved

Metro Guidance

Roads to nowhere

HOV

Toll road

Gas station parking lot roads

Expand Template Suggestion

MAR LAM Guidance

Restrictions

Partial restrictions

HOV revision

HOV revision Allowable restrictions

Junction Box 2.0

Junction Box turn restrictions

Bus or taxi only lanes

Routing preference

Partial restrictions new turns

Editing restrictions

Segment speed tracking

Timed difficult turns

JB resources

Hospitals

TIO update for TR UI

House Numbers

Virginia 2025

Transponder lanes at toll plaza

Service road HN update

RPP Changes

Camera lock level

Iowa dirt roads

Diffences between Waze app and Waze integrated car system

PLR inheritence

PLR inheritence2

Places2

DC SpotHero Parking Project

Parking Lot Area Naming

MAR Continue TIO

Retrieved from "https://www.waze.com/wiki/USA/index.php?title=User:Subs5&oldid=169173"