(3 intermediate revisions by one other user not shown) | |||
Line 19: | Line 19: | ||
=== Locking Standard === | === Locking Standard === | ||
{{Lock Standard State|WA}} | |||
=== Road Elevations === | |||
These are the general guidelines for elevation in Washington: | |||
* Drivable and non-drivable segments are handled the same way with elevation. | |||
* Set elevation to ground in most cases. | |||
** Segment(s) passing over other segment(s), rivers, major waterways, and ''all bridges'' shall have higher elevation, relative to ground. | |||
** Only elevate/lower the actual bridge/tunnel section of the road. | |||
** Elevation of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless a tunnel). | |||
** Tunneled segments shall have lower elevation, relative to ground. | |||
** Only segments that "cannot see the sky" should have negative elevation (i.e. tunnels). | |||
** Only set elevation as low/high as necessary. | |||
* If you use the Bridge tool to join segments, be aware that it raises the elevation of the joined segment. Lower the joined segment as appropriate. | |||
* [https://wiki.waze.com/wiki/Elevation_-_bringing_the_Seagull_to_Australia "True Elevation"] guidelines apply to elevation in Washington. | |||
** Bridges should be cut at the start/end of the bridge. | |||
** Tunnels should be cut at least 15m/50ft '''before''' and '''after''' the tunnel, to allow time for the GPS to regain signal. | |||
** Do not cut segments for elevation purposes if the bridge/tunnel starts/stops within 60m/200ft of an existing junction. | |||
===Junction Style Guide=== | |||
When editing roads please note that you do not need to perfectly match the street view. Simple is better. | |||
Local guide is as follows. | |||
*Local streets do not need u turns unless a sign is posted. Waze will automatically reroute without a u-turn via dead end segment. Adding these will only make routing more complicated. | |||
*Local streets that have small courts on the side of the road do not need to be mapped unless its over 50ft. In that case a single node without a making a loop or u turn will help route correctly to those houses. [https://www.waze.com/en-US/editor/?env=usa&lon=-122.31688&lat=47.82989&zoom=8&segments=53881000 Example] | |||
*Here is small court were a node is not needed. [https://www.waze.com/en-US/editor/?env=usa&lon=-122.34047&lat=47.83118&zoom=8&nodes=44445191 Example] | |||
*Washington follows USA guidance with Turn instruction override(TIO's) [[Turn_instruction_override | Turn_instruction_override]] Any TIO edit of a freeway/ramp/major highway must be approved by the SM's or CHAMPS. | |||
Washington follows the US wiki [[Junction_Style_Guide | USA/Junction_Style_Guide]] | |||
=== Speed Limits === | === Speed Limits === | ||
Latest revision as of 03:03, 27 September 2017
State Highway Naming
State highways are to be named SR-###
Washington State highways should be current to our wiki standard,
if you see one that doesn't seem right contact one of the SM's.
County Road Naming
County roads with the name designation of "County Road ##" or "Co Rd ##" are to be named in Waze as CR-##. This shortened version takes up less space on the map screen and is announced correctly as "County Road ##" while navigating with the Waze app.
Locking Standard
In Washington we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current US road type standards.
Segment Type | Statewide |
---|---|
Freeway | 5 |
Ramp | 5 |
Major Highway | 3 |
Minor Highway | 3 |
Primary Street | 2 |
Street | 1 |
• • • • Ferry • • • • | 5 |
|-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-| | 2 |
Note: Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of Washington.
Road Elevations
These are the general guidelines for elevation in Washington:
- Drivable and non-drivable segments are handled the same way with elevation.
- Set elevation to ground in most cases.
- Segment(s) passing over other segment(s), rivers, major waterways, and all bridges shall have higher elevation, relative to ground.
- Only elevate/lower the actual bridge/tunnel section of the road.
- Elevation of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless a tunnel).
- Tunneled segments shall have lower elevation, relative to ground.
- Only segments that "cannot see the sky" should have negative elevation (i.e. tunnels).
- Only set elevation as low/high as necessary.
- If you use the Bridge tool to join segments, be aware that it raises the elevation of the joined segment. Lower the joined segment as appropriate.
- "True Elevation" guidelines apply to elevation in Washington.
- Bridges should be cut at the start/end of the bridge.
- Tunnels should be cut at least 15m/50ft before and after the tunnel, to allow time for the GPS to regain signal.
- Do not cut segments for elevation purposes if the bridge/tunnel starts/stops within 60m/200ft of an existing junction.
Junction Style Guide
When editing roads please note that you do not need to perfectly match the street view. Simple is better. Local guide is as follows.
- Local streets do not need u turns unless a sign is posted. Waze will automatically reroute without a u-turn via dead end segment. Adding these will only make routing more complicated.
- Local streets that have small courts on the side of the road do not need to be mapped unless its over 50ft. In that case a single node without a making a loop or u turn will help route correctly to those houses. Example
- Here is small court were a node is not needed. Example
- Washington follows USA guidance with Turn instruction override(TIO's) Turn_instruction_override Any TIO edit of a freeway/ramp/major highway must be approved by the SM's or CHAMPS.
Washington follows the US wiki USA/Junction_Style_Guide
Speed Limits
Washington follows the US wiki Speed_limits/USA for adding speed limits to the map.
Local guidance will be listed on the Washington speed limit page Washington/Speed limits