This page serves as the primary resource for editors of the Mid Atlantic region. Review all the sections to better understand how the guidelines for this region might deviate from the overall USA or worldwide guidelines. If you have any comments or questions about this page or region refer to the community links below.
No general message at this time.
- 1 Introduction
- 2 Mapping resources
- 3 Update Requests
- 4 Community
- 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
The Mid Atlantic region includes the states and/or territories of:
The items on this page should be used as the standard for the region unless specified in a state-level sub-page to ensure regional unity and consistency. See the Mid Atlantic Forum for more information. Questions should be addressed to the Mid Atlantic Regional Coordinator or the State Managers. We are always looking for editors, and have fun learning in the process.
This page is maintained by triage685. Please coordinate any changes in advance.
Mid-Atlantic Region Large Area Managers
Mid-Atlantic Region Large Area Managers (MAR-LAM) help manage large sections of a state working with the local Area Managers. You can also reach out to them for assistance.
A map of the MAR-LAM regions is below.
- MAR-LAMs are simplified areas. This may cause coverage into surrounding states. MAR-LAM's are expected to get permission from that other state's SM if they wish to edit in an area outside of their MAR-LAM state.
- As a rough rule of thumb, it is typical to grant MAR-LAM areas measured in thousands of square miles.
- There can be more than one MAR-LAM for each region.
- Abbreviation: MAR-LAM
- Responsibilities: As the name suggests, MAR-LAMs manage a much larger portion of the map than AMs.
- Establish Baseline
- Update segments with unknown direction/clearly-incorrect names (segments from initial basemap import are very common in rural portions of the region even to this day)
- Implement proper Road type selection for all updated segments based on national guidance
- Ensure all updated segments are locked to minimum lock level appropriate for their segment type
- Regular Upkeep
- UR/MP Management: perform frequent, regular User Report/Map Problem passes over their entire area in accordance with the MAR UR Policy
- Unlock/Update forum response: monitor Unlock/Update requests for any requests in their MAR-LAM that are posted in the forum, Discord, GHO, WME Chat, or PM; service directly or escalate if needed
- Construction/Closures: responsible for staying current on all major construction projects, ensuring realtime closures are entered into the system as needed.
- Mentoring/outreach: proactively seek out new editors and encourage them to join the community, stay in regular contact with existing editors who work within their zone and work to help them improve/expand skillsets and knowledge bases
- Rapid Reponse: lead the response coordination effort for traffic disruptions in their zones (examples, freeway closure due to major accident, weather events (major snow storm or hurricane), planned events (marathons or parades)
- MAR-LAM should maintain activity on the map and in the community on a weekly basis, and preferably a daily basis
- Establish Baseline
It is requested that a MAR-LAM who will be away from map editing activities for more than two (2) weeks please notify the State Managers by private message (PM). This is simply to ensure, if needed, that any adjustments can be made for handling update requests or other activities.
MAR LAM Application Process
- Editor must be an active MAR Area Manager for a polygon larger than PL at Zoom=0 for a minimum of 45 days
- Editor must be an experienced Rank 3 or higher
- Editor should be an active and effective communicator to other editors via forums, Discord, GHO, and/or Private Messages.
If you're already a MAR Area Manager and you're interested in becoming a MAR-LAM, please contact your State Managers and discuss possibilities and MAR-LAM areas.
Before editing the maps in the Mid Atlantic region, 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.
Use only state DOT level FC maps when determine how to type (classify) a segment (Major Hwy, Minor Hwy, etc.). Some counties and cities have their own FC system, but only the state level system is to be used as a reference as these have been through a federal and state level approval process.
Before changing the type of any road past the bounds of the rules, please post the situation to the Maryland Forum to receive feedback.
These are official sources of information that can be used in the editor, in the form of downloadable PDFs or interactive GIS maps. See Using External Sources for acceptable sources of information.
State highways that are primarily signed at entering intersections with a State Route number rather than a road name should be named WV-### ("WV-2"). County roads that are primarily signed at entering intersections with County Road numbers rather than a road name should be named CR-## or CR-##/## ("CR-65" or "CR-91/1").
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. 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.
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. MAR (DC, MD, VA, and WV) has a policy of shared UR management. This means that URs are open to all editors and that there is no "ownership" implied when posting the initial comment. However, it is courteous to allow new editors or editors you don't have an informal agreement with an extra day or two to respond to reporter comments and/or post reminders. Effective UR conversations are usually achieved with a single point of contact for the reporter, but other editors can step in if a UR with reporter comments begins to sit idle or if they think another editor needs help. Please be respectful to other editors and reporters while working URs; it is usually best to send a message to the editor rather than chatting with them through a UR. (Most reporters don't care about the chat, they just want it fixed and not be bothered with multiple responses). Typically, an editor should be given some time to respond to the reporter's comments (since real life has a way to occasionally get in the way to prevent editing time on some days).
In MAR, we have adopted at 0/4/4 system for response to Update Requests. 0/4/4 is the short way of explaining the following.
The first editor who is able to respond to UR should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it closed. If more information from the reporter is required to make progress towards closure, a query should be sent to the reporter requesting the information needed for resolution
Polite reminders should be sent to a reporter who has never responded to a query, provided at least three full days have elapsed since the initial response was sent. (You can send reminder at 00:01 Eastern Standard (or Daylight when applicable) Time on the fourth day).
"If no further information is provided we will be unable to fix the issue you encountered and this report will be closed soon"
Second Day 4+
URs may be noted as closed due to lack of reporter response, provided at least three full days have elapsed since the followup message was sent (You can close at 00:01 Eastern Standard (or Daylight when applicable) Time on the fourth day since the reminder was sent)
"This report is being closed due to lack of information, please submit another report if the issue continues. Happy Wazing!"
If you use URComments then the settings should be 4 for reminder and 4 for closure.
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 the Mid Atlantic region.
New editors should consider checking into the formal mentoring program available at no charge.
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).
Do not use the names associated with ZIP codes or the name of a neighborhood, community, or subdivision not included on the census map. Be sure to also set the city name of any alternate names correctly.
- Maryland: There are 157 incorporated places in Maryland. When assigning the city name to a road segment or landmark, use the name of the incorporated place or CDP (census-designated place). If it is outside the boundaries of either of those, set the city name as None. If the road type is Freeway, set the city as None (except in Baltimore City), regardless of the location, as this helps with routing.
- West Virginia: Despite its relatively small size, the Mountain State is home to approximately 3,100 cities, towns and small communities. To link them (and to provide an important part of the transport of the state’s abundant natural resources), there are some 36,000 miles of state-maintained highways that include 6,636 bridges (this figure does not include 238 railroad bridges, 117 city and county bridges, 99 West Virginia Turnpike bridges, 20 state park bridges, two private toll bridges and 132 other non-highway bridges).
- Washington DC: Washington is the only city in the District of Columbia and it spans the entire area.
- Virginia: There are 38 independent cities and 95 counties in the state. Proper naming information is still under discussion due to the highly urban nature of parts of northern Virginia
Determining road types in the Mid Atlantic region aligns with the Waze USA Standard for freeway, major highway, minor highways, and primary streets. The Waze USA standard is a hybrid system based on a national standard called "functional classification" with a few modifications.
Functional classification maps are available for most states. Compliance across state borders is important to insure better route selections between states; however, editors in some states have deferred adoption of the USA Standard due to in-state concerns.
- Minimum Locking Standard
Actual locks used may be more than the table below, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance
|2 (3 for one way PS)|
|1 (2 for one way S)|
Road Segment Naming
Often when US Hwys, State Roads, and County Roads pass through municipalities, they have a local name (e.g, "Main St"). Please see Road names for instructions on how to name these segments. Check here for other states.
The Mid Atlantic 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 "PLR"
- 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.
- Private Road/Dirt Road
Rural farm and logging roads that are never open to the public should be marked as Private Road type to prevent routing. Most should be left off the map unless they serve multiple residences or are longer than 50 meters and has its own street name. Do not create driveways based on other mapping sources and do not delete driveways without consulting the creator first. The Dirt Road/4x4 Trail designation should be reserved for public (state/locality maintained) dirt roads and Forest Service roads, etc, that a user may actually traverse freely during at least part of the year.
The Mid Atlantic region 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.
Generally, if a path can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Runway/Taxiway) then it is not mapped.
- Emergency Vehicle and DOT Service Roads
We do not map Emergency Vehicle and DOT Service Roads.
For areas where residents are dependent upon ferries, see the Ferries Editing Manual. Please contact your RC for any questions deciding if a ferry should be mapped.
Railroads can be mapped, but they are not a priority at this time.
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.
The Mid Atlantic follows the national Places guidance.
To prevent loss of data due to automatic acceptance of submissions from "trusted users, all area places and points with complete data should be locked to Level 2 at a minimum.
Metro stations in DC, MD, and VA The major public transportation system within the Washington DC metropolitan is METRO. It consists of both buses and rail. The above ground train/bus stations shall be mapped as area places and locked at L3. The below ground train stations shall be mapped as point places and locked at L3.
Additionally, please consult the following table for minimum lock level for completed places.
|Place Type||Minimum Lock Level|
Oddball Place Categories
Most categories in Waze are self-evident, however, occasionally questions arise as to what category should be used to maintain consistency in search results across the region. Use the chart below when working with a place that is not part of a chain and you are unsure of the category.
|Type of Place||Point/Area||Category 1||Category 2||Notes|
|Funeral Homes||Point||Shopping and Services|
|Liquor Stores||Point||Shopping and Services|
|Pawn Shops||Point||Shopping and Services|
|Storage Centers||Point||Shopping and Services|
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 the Mid Atlantic region.
In West Virginia, code section §17C-6-7a prohibits use of cameras to detect or prove traffic law violations.
In Virginia speed enforcement cameras are illegal. Red light cameras are legal, but the number of them is regulated by VA Code §15.2-968.1
In Washington DC there are seven different types of traffic enforcement cameras. Below is a table containing each type of camera and how it should be mapped.
|Camera Type||Icon Used|
|Traditional Speed Cameras||Speed Camera|
|Speed Cameras at Intersections||Speed Camera|
|Traditional Red Light Cameras||Red Light Camera|
|Gridlock Cameras||Red Light Camera|
|Stop Sign Cameras||Red Light Camera|
|Pedestrian Right of Way Cameras||Red Light Camera|
|Oversized Vehicle Cameras||Not Mapped|
Reference the DC MPD Automated Traffic Enforcement page to verify camera locations.
In Maryland speed cameras are authorized for use in the following areas: school zones throughout the state, work zones on freeways and major highways, and on streets in Montgomery County. Speed cameras can be mounted to a pole, concealed in a metal cabinet on the ground, or mounted on a trailer or vehicle parked on the shoulder, such as ones used in work zones. Most speed cameras in Maryland will not issue a ticket unless the vehicle is exceeding the speed limit by at least 12 mph; however, when setting the speed of a camera in the editor, use the speed limit of the road. Many speed cameras in school zones are portable and moved on a regular basis, in some cases weekly. This is usually indicated on the website and may include a rotation schedule. These reported camera locations should not be on the map. Red light cameras are also authorized for use throughout the state. Some red light cameras also include radar, and enforce speed limits. This is especially true in Baltimore City.
Other camera types
These are cameras or signs that either provide driver feedback or are used for traffic control such as DOT 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 region does not currently have an active "to do" list at this time. Check in the Mid Atlantic 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 the Mid Atlantic region. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers the Mid Atlantic region, or a USA Country Manager that does a lot of work in the Mid Atlantic region, please add yourself to this list (alphabetical by username) in the correct rank section.
The editor who also serves as the Regional Coordinator for the Mid Atlantic region is automatically listed at the top of the table. That editor may not be highly active in this region and therefore may not be listed separately in the table.
|Mid Atlantic — Area, State, Country Managers, and Regional Coordinators|
[RC] stephenr1966 ( )
[ARC1] ply8808 ( )
| Country Managers (Mid Atlantic region)|
|stephenr1966(6) [ ]||Regional Coordinator|| |
|ply8808(6) [ ]||Assistant Regional Coordinator|| |
|ct13(6) [ ]||VA State Manager|| |
|nzahn1(6) [ ]||MD State Manager|| |
|Roadtechie(6) [ ]||WV State Manager|| |
|Kodi75(5) [ ]||MD State Manager|| |
|ldriveskier(5) [ ]||WV State Manager|| |
|subs5(5) [ ]||VA State Manager|| |
|Region Managers (Mid Atlantic region)|
|jr1982jr(5) [ ]||MD State Manager|| |
|LennyNRPD(5) [ ]||VA State Manager|| |
|MrNicGuy(5) [ ]||VA State Manager|| |
|Nimbus-(5) [ ]||DC State Manager|| |
|russblau(5) [ ]||DC State Manager|| |
|SirGadwall(5) [ ]||VA State Manager|| |
|kwrigh01(4) [ ]||WV State Manager|| |
| Area Managers |
|j2brown(5) [ ]||Virginia||NOVA|
|Poncewattle(5) [ ]||Virginia||Northern Shenandoah Valley|
|DCLemur(4) [ ]||Virginia||Roanoke & Richmond LAM|
|hippocampusLol(4) [ ]||WV-VA-MD|| |
|kwrigh01(4) [ ]||West Virginia||Virginia|
|mtb2314(4) [ ]||Maryland|
|SeZAKxing(4) [ ]||Virginia||Charlottesville Area|
|SpencerFG(4) [ ]||Virginia||Central VA, NVA|
|ArthurUSCG(3) [ ]||Maryland||St. Mary's County|
|Gadtica(3) [ ]||Virginia||Danville|
|mdswbkq(3) [ ]||Maryland||Frederick, Washington Counties|
|TwoEightZero(3) [ ]||Virginia||Eastern Shore|
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|
|Example(2) [ ]||State||Am Area|
Other states and territories
About this page