This page serves as the primary resource for editors of Virginia. 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.
SR < 600 and VA > 600 is official now! Please see this section for more information.
- 1 Introduction
- 2 Mapping resources
- 3 Community
- 4 Update Requests
- 5 Cities and towns
- 6 Major roads
- 7 Special roads
- 8 Closures
- 9 Places
- 10 Cameras
- 11 To do list
- 12 Area Managers
- 13 Other states and territories
- 14 About this page
Virginia is a part of the Mid Atlantic region, which includes the states and/or territories of:
Before editing the maps in Virginia, 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 Virginia/Resources for guidance in Virginia that may not be universal to all other states and territories.
Tools and Scripts
A Virginia version of the WME Validator localization script has been created.
It can be downloaded Here.
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 Virginia.
- Virginia section of Waze forum
- The Mid Atlantic 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.
See Virginia/Community for guidance in Virginia that may not be universal to all other states and territories.
An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See update requests for more information.
In Virginia we have adopted at 1/4/8 system for response to Update Requests. 1/4/8 is the short way of explaining the following.
Within 24 hours (1 day) after an Update Request has been submitted, an editor needs to provide a response to the Update Request to get the process started.
If the reporter has not commented after 3 days (4 days since initial comment) a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue.
"If no further information is provided we will be unable to fix the issue you encountered and this report will be closed soon"
If the reporter still has not commented after 4 more days (8 days since initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified.
"This report is being closed due to lack of information, please submit another report if the issue continues. Happy Wazing!"
While we would like to have every inch of Virginia covered with a network of editors, we are not currently at that level of community involvement. The 1/4/8 rule has been set as the standard for areas with Area Managers, active editors and applies to all of Virginia. However, in many areas of Virginia there is not only spotty cellphone coverage but sometimes very little editor coverage. That being said, use good judgement in areas with with little or no editor coverage, as there may be Update Requests that are greater than 30 or even 60 days old. There is no penalty or negative perception to answering these, quite the opposite. Please, still take the time to send the reporter a message to see if they can remember the issue and allow them additional time to provide more information.
"Thank you for your report! I apologize for the late response, we are volunteer editors and in some areas there are not many of us. You reported a General Error near 5th street and Main street in Suffolk, VA way back on 8/15/2014. Do you remember what issue you encountered?"
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 are 38 independent cities and 95 counties in the state. The city layer in Virginia should be drawn from the 2010 Census Maps, adding only independent cities, towns and census designated places. Additionally, city layer names should only be added to segments inside of the city/town/CDP boundary. However, due to the highly urban nature of some areas, other names will be allowed to be added to the map as discussed in the forum topic What to put in city field, and how to determine?. This topic contains a list of names approved for the city layer; other names should not be added or removed without posting to the forum or asking a state manager.
- 2010 Virginia County Census Maps(PDFs)
- Lower Resolution 2010 Virginia County Census Maps (PDFs)
- Virginia 2010 Census Cities, Towns and CDPs (KML)
- Overlay the above boundary file(s) with the WME Geometries Plugin. After loading the file(s) in WME, turn on the Roads Layer and the cities layer to view which WME city boundaries may need to be adjusted.
In Virginia, outside cities and major towns (and a couple of urban counties), nearly every road and street is designated as a "state highway" and assigned a number for VDOT inventory purposes. However, for Waze routing, we only treat primary state highways as "numbered state highways" for purposes of applying the road type guidelines. Highways marked with primary route numbers must be designated as at least "Minor Highway" in Waze, unless the road's functional classification requires a higher designation. For Virginia secondary highways, rely on the road's functional classification only.
Primary state highways have numbers in the range of 2 to 599 (and, as exceptions, 785, 895), displayed in a route marker using a shield design. All other numbers from 600 up are secondary highways; if these roads have route markers (many do not), they use a circle design instead of a shield. See Virginia DOT Route Index Resources for more info.
Our naming convention is SR-### for primary routes (SR-2 - SR-599, SR-785 and SR-895) and VA-### for secondary routes (VA-600+). Since this update is fairly new (1/24/2015), your first priority should be making sure that ramps and roads with the route name as their primary name are correct. Correcting alt names is a secondary priority.
Actual locks used may be more or less than values in the table below, depending on area circumstance
Please consult RC, SM, or appropriate AM for guidance
|Highest rank of connected segment|
Virginia 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
- Dirt roads
- 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.
State specific special road guidelines
The following special roads are managed slightly uniquely in some states and territories.
Parking Lot Roads
Virginia uses the following national standard guidelines found in the Wiki for Parking Lot Roads.
Virginia uses the following guidelines for mapping alleys.
- 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 "Private"
- 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.
Be careful adding alleys which will be closer to the destination pins for house numbers, or from Google, as this can cause all navigation to all the addresses on that block to route onto the alley instead. It may be better not to map these alleys, or you may have to adjust all the address pins to be closer to the actual roads.
This state uses the following national standard guidelines found in the Wiki for Dirt Roads.
Generally, if a path can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Runway/Taxiway) then it not normally mapped, unless approved by a Virginia State Manager or the Mid-Atlantic Regional Coordinator. If it is mapped, it should not be connected to any roads, its elevation should be set to 9 and it should be locked at Level 5. This is due to the way the routing engine works, as Waze will route users to drive on these "Non-Drivable" road types.
The "Railroad" road type serves two purposes in Waze. First, it provides drivers with visual orientation relative to railroad and light-rail tracks. More importantly, in the common case where passenger-carrying tracks lie parallel with roads, mapping the tracks allows Waze to recognize spurious speed data from people Wazing on the train and prevent it from corrupting speed data for the adjacent road. Please see USA Road Types wiki page for more information on mapping railroads.
The Federal Highway Administration keeps a website indexing all states that can provide highway and construction project information. Go to the page, find your state, and check the links for the desired information.
Places (formerly called landmarks) in Virginia now follow the detailed guidance in the US standard for places, after having followed the guidance from the state of Connecticut while it was under development.
To prevent loss of data due to automatic acceptance of submissions from "trusted users, all area places should be locked to Level 2 at minimum. Additionally, area places for Hospital/Medical Care, Fire Department and Police Station should be locked at Level 3 at minimum and preferably Level 4 in urban areas.
|Place Type||Minimum Lock Level|
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.
Currently only the Waze client app can add cameras to the map. When adding a camera from the app, 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 Virginia.
Be sure to know your cameras before accepting new camera reports. Currently only the Waze client app can add cameras to the map. When adding a camera from the app, be sure to review the camera placement recommendations.
There are no speed enforcement cameras anywhere in the Commonwealth of Virginia as they are illegal.
Red light cameras
Red light cameras are legal, but the number of them is regulated by State law.
Other camera types
These are cameras or signs that either provide driver feedback or are used for traffic control such as VDOT monitor cameras and emergency vehicle detectors. These devices CAN NOT issue tickets and should not be mapped.
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.
This state does not currently have an active "to do" list at this time. Check in the Virginia section of the Waze forums to discuss creating one.
The table below identifies the editors also designated as Area Managers or higher who are editing in Virginia. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers Virginia, or a USA Country Manager that does a lot of work in Virginia, please add yourself to this list (alphabetical by username) in the correct rank section.
The editor who also serves as the Regional Coordinator for Virginia 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.
|Virginia — Area, State and Country Managers|
Regional Coordinator(s): CBenson ( ) and ply8808 ( )
| Country Managers (Mid Atlantic region)|
|ply8808(6) [ ]||Assisting With RC Duties|| |
|ct13(5) [ ]||Country Manager USA|| |
|MojaveCactusMonkey(5) [ ]||Country Manager USA|| |
NV, RI, CT
|TerryPurdue(5) [ ]||Country Manager USA|| |
|State Managers (Mid Atlantic region)|
|triage685(5) [ ]||VA State Manager|| |
| Area Managers |
|j2brown(5) [ ]||Northern Virginia||Sterling Area|
|russblau(5) [ ]||Northern Virginia|| |
|stephenr1966(5) [ ]||Statewide|| |
|HotFzz(4) [ ]||Northern Virginia|
|kwrigh01(4) [ ]||Virginia's Western Highlands||Alleghany, Bath, Craig & Highland Counties|
|Nimbus-(4) [ ]||Northern Virginia||Alexandria, Arlington, & Fairfax County|
|Poncewattle(4) [ ]||Northern Shenandoah Valley|| |
|subs5(4) [ ]||Northern Virginia||Alexandria, Arlington, & Fairfax County|
|eeschuler(3) [ ]||Southwest Virginia|
|Gadtica(3) [ ]||Southwest Virginia||Danville Area|
|SeZAKxing(3) [ ]||Central Virginia||Charlottesville to Fork Union|
|str33t_fir3(3) [ ]||Southwest Virginia||Blacksburg|
|subcritical71(3) [ ]||Central Virginia||South Chesterfield, Colonial Heights|
|SuperMedic(3) [ ]||Hampton Roads||Suffolk|
|TwoEightZero(3) [ ]||Eastern Shore||Accomack County|
|WahooG(3) [ ]||Central & Northern Virginia||Richmond & Fredericksburg|
Other states and territories
About this page