This page serves as the primary resource for editors of Washington. Review all the sections to better understand how the guidelines for this state might deviate from the overall USA or worldwide guidelines. If you have any comments or questions about this page or state refer to the community links below.
Welcome to the Washington State wiki page.
Washington is a part of the Northwest region, which includes the states and/or territories of:
Before editing the maps in Washington, be sure to fully review and understand the editing manual.
The Waze user community follows the Waze etiquette guidelines discussed in the Wiki. Be sure to familiarize yourself with these guiding principals while editing the maps and this Wiki, as well as when communicating with other Waze users.
See Washington/Resources for GIS info and other specific WA info.
All of the state's roads are typed and set according to WSDOT functional classification. Washington follows the Functional Classification (FC) system for both state and non-state roads. This change from the previous road-typing guidance was changed in September 2014. Please cross reference using the functional classification table
- Washington State Department of Transportation (WSDOT) home page
- Washington State Highways PDF format
- WSDOT maps home page Maps & Geospatial Data
- List of All Washington State Routes
- WSDOT - Roadway Characteristics Special use lanes, access control, legal speed limits, number of lanes, surface type and roadway width along State Routes.
- State Highway Log
If you want to know more about the Federal Functional Classification check the Functional Classification article.
The Waze forum is a great place to find answers to previously asked questions and also a place to ask new ones. Below are links to the forums specific to Washington.
- Washington section of Waze forum
- The Northwest region forum
- The USA section of Waze Forum
- The USA segment unlock requests
New editors should consider checking into the formal mentoring program available at no charge.
Discord - Waze NWR Editors
Discord is a all in one voice text chat that's free for anyone to use. We are moving away from Google hangouts (GHO) and encourage editors to use the discord channel. Join NWR Discord
Discord - Waze NA
This is the North America waze channel we encourage editors to join but not required. Join Waze NA Discord
(CCP) Connected Citizens Program
Information to Help connect on what Government agencies have been contacted about the Connected Citizens Program
|Connected Citizens Program|
Cities and towns
One of the most common errors when editing the maps is when an editor creates a road and does not confirm the road by setting the city and road name (or stating it has none).
|There is an error in the Waze Map Editor (WME) which periodically sets the state to Idaho or Oregon when creating new segments in Washington areas that border those states. This has also been seen with base map roads that have never been touched. When adding new segments within 100 miles of border, please ensure that the state is correctly set to Washington. Existing roads that are edited with other than Washington as the state will throw an error when saving.|
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
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.
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.
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
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
Washington follows the standard USA guidelines for all of the following special road types.
- Divided highways and roadways
- Carpool, HOV, Transit lanes
- Roundabouts and traffic circles
- Toll roads
- Partial and scheduled restrictions
- Private installations and military bases
Review the Wiki guidelines for non-drivable roads to ensure compliance with the general guidelines.
- Alleys should always be mapped if they have a name.
- Alleys should always be mapped if they are the sole access to a home or business.
- Alleys should always be set to "Parking Lot Road"
- Some alleys mapped before these guidelines are mapped as "Private Road". It is okay to change these to "Parking Lot Road".
- Alleys are normally mapped if they are acknowledged by the municipality.
If an alley does not meet the above criteria, mapping is optional. Leave the name field blank. Always disable the straight turn restriction from one alley to another when it crosses another road to prevent alleys from being overly used in routing.
See the Driveways article for more details.
- Driveways are always marked as private road
- Driveways are mapped if they are 50m (164 feet or about half a football field) or longer Example
- Driveways are mapped if they are close but not connected to adjacent street Example
- Driveways are mapped if they are serving two or more addresses Example
- Driveways that have names can be added. These still need to be set to private road.Example
When mapping roundabouts in Washington state, it is important to know the difference between roundabouts and traffic circles. Traffic circles are small circles to help slow traffic at intersections.
In Washington, we usually only map roundabouts. We don't map traffic circles unless:
- Specific directions are needed to navigate the traffic circle (i.e. more instructions than just turn right or turn left)
- If the traffic circle is on a Primary Street with high traffic or higher road type(contact a SM for traffic circles on primary streets)
- The traffic circle is larger than 12m.
Dead end segments
Dead ends should all have nodes on the dead end side of the segment. It was possible in older versions of WME to add a road with a dead end and no node. As of July 2014, U-turns at dead ends or cul-de-sacs, no longer need to be adjusted in a particular way. WME no longer provides a link to adjust it. Please make sure U-Turns on the end of cul-de-sac with private driveways are Not Allowed. Example
See Non-driveable roads for guidance that may not be universal to all other states and territories.
Parking lot roads
Washington State uses the following standard guidelines found in the Wiki. Parking lot road Please follow them.
Forest service roads
Forest Service Roads should be built according to Forest Service Roads.
Based on the conditions and climate of Washington, Usually the main FSR is marked Primary Street. (Example: FS-2800) Usually the Spurs of the Main FSR is Street. (Example: FS-2875) Usually the Spurs of the Spurs are Dirt Road / 4x4 Trail (Example: FS-2875050, FS-2875053)
See To Do Washington for Washington FSR mapping updates.
This section contains details about long term or seasonal road closures currently in place in Waze, usually through disconnecting of segments to prevent Waze from routing along a certain stretch of road. If you perform a closure in Waze, please document it here so other area managers can ensure the roads are reconnected at the appropriate time.
|Road Name||Editor||Closed Date||Est Open Date||Links and comments|
GENERAL NOTE: If you need a closure the segment can not be edited since the last tile update. Do not update a segment then ask for a closure.
Washington has a lot unique guidelines for mapping Places. Please see Washington/Places for guidance in Washington that may not be universal to all other states and territories.
Washington follows the USA guidelines for Parking lot places (PLA's). Places/Parking_lot
Not every camera-looking device at an intersection is a speed or red light camera. Generally speaking:
Be sure to know your cameras before accepting new camera reports.
When adding a camera, be sure to review the camera placement recommendations.
Laws regarding speed and red light cameras vary between the states and territories, so be sure to understand the details of camera legality in Washington.
Please see for specific guide to mapping cameras in Washington: Washington/Cameras
Here is the current list of mapped cameras in Washington
To do list
Many states and territories keep an active list of pending or closed actions that need to be done in the state by the editors. All editors are welcome to contribute to the list of activities.
See Washington/To do for guidance in Washington that may not be universal to all other states and territories.
The table below identifies the editors also designated as Area Managers or higher who are editing in Washington. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers Washington, or a USA Country Manager that does a lot of work in Washington, please add yourself to this list (alphabetical by username) in the correct rank section.
The editor who also serves as the Regional Coordinator for Washington is automatically listed at the top of the table. That editor may not be highly active in this state and therefore may not be listed separately in the table.
|Washington — Area, State, Country Managers, and Regional Coordinators|
[RC] ply8808 ( )
[ARC1] FzNk ( )
[ARC2] TheChrisK ( )
| Country Managers (Northwest region)|
|ply8808(6) [ ]||Countrywide|| |
Northwest Regional Coordinator
Based in Arizona
|TheChrisK(6) [ ]||Countrywide|| |
Based in Omaha, NE
|AlanOfTheBerg(5) [ ]||Countrywide||Lifelong Pacific NW resident|
|State Managers (Northwest region)|
|dude463(5) [ ]||Northwest Region|| |
Resident of state
|SeveriorumPatrem(5) [ ]||Statewide and PDX Metro|| |
Resident of state
|State Managers - Emeritus|
| Area Managers |
|DCinSEA(5) [ ]||Washington|| |
|nhanway(5) [ ]||Greater Seattle Area AM|| |
Resident of Spokane
|nidnarb(5) [ ]||Northwest Region|| |
Resident of state
| ojlaw(5) [ ]
USA CM, WI State Manager
|jr1982jr(5) [ ]||Seattle/Tacoma area|| |
NWR & MAR Collaboration
|benandjerry(4) [ ]||Preston / Fall City / Snoqualmie / Carnation/|| |
|taylorcrossing(4) [ ]||Tri-Cities / Walla Walla / Pullman / Moscow / Lewiston||Longview Resident|
|tinfoilhattie(4) [ ]||Northwest Region|| |
NWR & PLN Collaboration
|AJSmoke(3) [ ]||Vancouver, WA / North Portland|| |
|helifino206(3) [ ]||Ellensburg / Yakima|| |
Seattle area Resident
|serega_12(3) [ ]||I-5 Corridor / Clark County / Lewis County / Kelso / St. Helens|| |
Greater PDX to Longview, WA / North Seattle / Everett / Marysville / Whidbey Island
|Skulllzzcode(3) [ ]||Pierce County|| |
NWR & SER Collaboration
The following editors are also editing in the state and may be working towards an Area Manager position. Feel free to contact them for assistance in their respective areas.
| Other Area Editors |
|Username||General Editing Area||Comments|
|NJMedic2535(4) [ ]||Everett Area|| |
NJ State Manager
|paul_2010(3) [ ]||Seattle, Olympic/Kitsap Area|
|MukYJ(2) [ ]||Everett / Seattle|
|TCHappy8(2) [ ]||Greater Seattle Area|
|Voltylicious(2) [ ]||Greater Seattle Area|
Other states and territories