District of Columbia
(Redirected from DC)
This page serves as the primary resource for editors of the District of Columbia region. Review all the sections to better understand how the guidelines for this district might deviate from the overall USA or worldwide guidelines. If you have any comments or questions about this page or district refer to the community links below.
- 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
District of Columbia is a part of the Mid Atlantic region, which includes the states and/or territories of:
Before editing the maps in the District of Columbia 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.
These are official sources of information that can be used in the editor, in the form of downloadable PDFs or interactive GIS maps.
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 District of Columbia region.
- District of Columbia 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.
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. DC 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 DC 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.
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).
Washington is the only city in the District of Columbia and it spans the entire area. All street segments in the District should have "Washington" as the city name, without exception.
The primary reference for road types is the District's Functional Classification Map.
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. Lock the roads based on type after they've been set to current US road type standards and connecting roads are set up correctly and all other edits are complete for the segment.
- 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)|
The speed limit on all streets in the District of Columbia, unless otherwise posted, is 25 mph. Relatively few streets are otherwise posted, and most of those are main arterials that are classified as Major Highway or Minor Highway for Waze purposes.
The District of Columbia 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.
- 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 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.
Washington, D.C. has a large number of traffic circles. Most of the circles are named, and (unlike most roundabouts and rotaries in other jurisdictions) these names typically appear on street signs at the intersections between the circle and the connecting streets/avenues. Some circles even have assigned street addresses. Also, some circles have non-standard configurations that include overpasses, underpasses, and/or streets passing through the center of the circle. Because of these situations, D.C. deviates from the usual Waze editing rules for roundabouts in the following respects:
- If the circle has posted street signs, then the road segments of the circle should be assigned this name in WME, and not left un-named. If there are no street signs, check the "No name" box. If there are street signs but they name the connecting streets rather than the circle, name the segments so that turn instructions given to drivers will match what is on the street signs.
- If the circle has any interior intersections (that is, a street or avenue that crosses through the circle and intersects at ground level with the circle), then do not use the Waze roundabout type for the road segments; these circles should be converted to ordinary street/highway segments. You should still follow the guidance at Roundabouts/USA#Road type in deciding what type of segments to use, even for this kind of circle.
Many road closures in the District are posted on the "Advisories" tab on the DDOT website at http://www.dc.gov/ddot
However, there are numerous agencies with jurisdiction over various roads and streets in the District. Accordingly, not all road closures are announced through a common information source.
Places (formerly called landmarks) in DC now follow the detailed guidance in the US standard for places.
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 4 at 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.
|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.
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 District of Columbia region.
Based on information researched at the time this page was created, red light and speed cameras are legal districtwide in the District of Columbia region.
No other camera types should be mapped in Waze.
In the District of Columbia, their 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|
|Fake Cameras||Dummy Camera|
|Oversized Vehicle Cameras||Not Mapped|
Reference the DC MPD Automated Traffic Enforcement page to verify camera locations.
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 district does not currently have an active "to do" list at this time. Check in the District of Columbia 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 District of Columbia region. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers the District of Columbia region, or a USA Country Manager that does a lot of work in the District of Columbia 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 District of Columbia region is automatically listed at the top of the table. That editor may not be highly active in this district and therefore may not be listed separately in the table.
|District of Columbia — Area, State, Country Managers, and Regional Coordinators|
[RC] stephenr1966 ( )
[ARC1] ply8808 ( )
[ARC2] nzahn1 ( )
[ARC3] ct13 ( )
| Country Managers (Mid Atlantic region)|
|stephenr1966(6) [ ]||Regional Coordinator|| |
|ply8808(6) [ ]||Assistant Regional Coordinator|| |
|ct13(6) [ ]||Assistant Regional Coordinator|| |
|nzahn1(6) [ ]||Assistant Regional Coordinator|| |
|Kodi75(5) [ ]||MD State Manager|| |
|roadtechie(6) [ ]||WV State Manager|| |
|subs5(5) [ ]||VA State Manager|| |
|District Managers (Mid Atlantic region)|
|russblau(5) [ ]||Districtwide||Also Area Manager for Arlington, Alexandria, Fairfax|
|Nimbus-(5) [ ]||Districtwide||Also Area Manager for Northern Virginia|
| Area Managers |
|jr1982jr(5) [ ]||Northeast Washington DC||SM MD|
|LennyNRPD(5) [ ]||Statewide MSM||VA SM, PLN MSM, NJ AM|
|SirGadwall(5) [ ]||Statewide MSM||VA SM|
Other states and territories
About this page