MegaMapRaid/Washington DC MMR: Difference between revisions Discussion View history

Mega map raid
VisualWikitext
 
(52 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{MMR Subpage heading}}
{{MMR Subpage heading}}
'''MegaMapRaid!''' will run from Sunday, March 7, 2015 15:00 UTC thru Wednesday, March 11, 2015. The raid will last 4 days.
'''MegaMapRaid!''' will run from Sunday, March 8, 2015 19:00 UTC thru Thursday, March 12, 2015. The raid will last 4 days.
----
----




==Welcome to the DC Metro Area==
==Welcome to the DC Metro Area==
The group will be divided into XXXXXX teams, one for each section, and two exclusive teams; one to handle PURs, the other for the Waze provided problem sheet. Each team will have their own assigned senior editor (rank 6, or 5) who will be able to edit anywhere in the Raid area, but will focus on their assigned section.
[[File:DC-MMR.png|200px|right]]The group will be divided into multiple teams, one for each section, and possibly other exclusive teams; for PURs or to handle the Waze provided problem sheet. Each team will have their own assigned senior editor (rank 6, or 5) who will be able to edit anywhere in the Raid area, but will focus on their assigned section.  
 
This wiki page is an attempt to highlight a majority of the local differences, but does not cover all local differences. Please see the [[DC|Washington DC]], [[Virginia]] or [[Maryland]] wiki pages for complete information.


This wiki page is an attempt to highlight a majority of the local differences, but does not cover all local differences. Please see the [[DC|Washington DC]], [[Virginia]] or [[Maryland]] wiki pages for complete information. Additionally, parts of the DC Metro area that are actually in Maryland will follow the local guidance found in the [[MegaMapRaid/Baltimore|Mega Map Raid Baltimore wiki page]] as this page is primarily for D.C. and Virginia.


=== Raid Areas ===
=== Raid Areas ===
The MapRaid! is being divided up by teams. You can see the [http://mapsengine.google.com/map/u/0/edit?mid=zIoPO0KHtaWo.khISn97ChBmQ interactive map] with all the teams, and PUR areas drawn out [http://mapsengine.google.com/map/u/0/edit?mid=zIoPO0KHtaWo.khISn97ChBmQ here].
The MapRaid! is being divided up by teams. Team assignments have been posted on the [http://www.waze.com/forum/viewtopic.php?t=131741 Waze Forum].
 
====Raid Groups====
 
 
====PUR Areas====


[[File:Dc mmr 360.png]]


== Mission ==
== Mission ==
 
{{MapRaid Mission|area=the DC Metro area|DOT=state DOTs}}
Our primary mission will be to handle the URs, and PURs, followed by Place validation, and general map verification.
{{mbox
| type      = critical
| small      = left
| textstyle  = color: red; font-weight: bold; font-style: italic;
| text      = Functional Classification (FC) has been fully implemented for the DC Metro area. Some road types deviate intentionally from the state DOTs classifications. If you find a road which you feel is not classified correctly or set to the right type, please contact a local champ or State Manager (SM) before making changes.
| smalltext  = Text for the top of article sections.
}}


==Local hosts==
==Local hosts==
Line 34: Line 21:


* {{Username|CBenson}} - Mid Atlantic Regional Coordinator and primary local host
* {{Username|CBenson}} - Mid Atlantic Regional Coordinator and primary local host
* {{Username|russblau}} - Washington DC State Manager
* {{Username|russblau}} - Washington D.C. State Manager
* {{Username|Mike-1323}} - Virginia State Manager (and US Country Manager)
* {{Username|ct13}} - Virginia State Manager
* {{Username|ct13}} - Virginia State Manager
* {{Username|stephenr1966}} - Virginia Editor
* {{Username|subs5}} - D.C. and Virginia editor


Note that Metropolitan Washington DC includes areas outside the city in the states of Virginia and Maryland. Washington DC is not considered to be in any US state, but is treated as a quasi-state.
Note that Metropolitan Washington DC includes areas outside the city in the states of Virginia and Maryland. Washington DC is not considered to be in any US state, but is treated as a quasi-state.
Line 58: Line 48:
In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our [http://wiki.waze.com/wiki/Road_types/USA#Functional_classification Road Type Wiki]
In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our [http://wiki.waze.com/wiki/Road_types/USA#Functional_classification Road Type Wiki]


The Functional Classification has been completed in the DC Metro Area. Occasionally, we find short segments that were missed in the selection process for conversion, and it is important that these be corrected for routing continuity. In general, however, we ask that Road Types not be changed without consulting one of the [[#Local Hosts | Local Hosts]]. In isolated cases, we have chosen to deviate from official classifications, due to errors or outdated information in the VDOT or DCDOT FC maps, or to better accommodate real-life situations and Waze quirks. It is important that these remain intact. If you find an area that doesn't seem to be complete please bring it to the attention of a Local Host for review.  
The Functional Classification has been completed in the DC Metro Area. Occasionally, we find short segments that were missed in the selection process for conversion, and it is important that these be corrected for routing continuity. In general, however, we ask that Road Types not be changed without consulting one of the [[#Local Hosts | Local Hosts]]. In isolated cases, we have chosen to deviate from official classifications, due to errors or outdated information in the VDOT or DCDOT FC maps, or to better accommodate real-life situations and Waze quirks. It is important that these remain intact. If you find an area that doesn't seem to be complete please bring it to the attention of a Local Host for review.
{{mbox
| type      = critical
| small      = left
| textstyle  = color: red; font-weight: bold; font-style: italic;
| text      = The Functional Classification (FC) map for Virginia is currently broken. Please do NOT make any road type changes to any segment typed Primary Street or above without first contacting a Virginia State Manager.
| smalltext  = Text for the top of article sections.
}}


===Place Editing===
===Place Editing===
Line 75: Line 72:
||Gas Stations ||3
||Gas Stations ||3
|-
|-
||Hospital/Medical Care ||3
||Hospital/Medical Care ||4
|-
|-
||Fire Department ||3
||Fire Department ||3
Line 81: Line 78:
||Police Station ||3
||Police Station ||3
|}
|}


'''Gas Stations'''<br>
'''Gas Stations'''<br>
Gas Stations should be locked to level 3 but, only after all data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a hosting local if you need help identifying gas station information.
Gas Stations should be locked to level 3 but, only after all data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a hosting local if you need help identifying gas station information.


For editors below rank 3, once you have completely filled out a gas station with the min required information, please ask for a lock request.
For editors below rank 3, once you have completely filled out a gas station with the min required information, please ask for a lock request.
===Complex Intersections===
There are many complicated intersections in Los Angeles which should not be edited without consulting a local senior editor, even if the presence of URs seems to indicate problems. Some of these intersections have been carefully refined to achieve the best Waze performance, which can involve years of testing, adjustment, and experimentation. Others are locations which are currently under construction, and daily changes to the physical roads cause Wazers to report problems which will no longer exist by the time our edits could take effect. We have done our best to lock the most important of these intersections to Rank 6. When dealing with URs at these locations, please keep in mind that few, if any additional road changes are required. Again, please consult with a [[#Local Hosts | Local Host]] before making changes.


===Toll Roads / HOV / HOT / Truck Lanes===
===Toll Roads / HOV / HOT / Truck Lanes===


It is our custom to mark the Toll checkbox ''only on the entrance segments'' to Toll Roads. HOV and HOT road types have already been set correctly according to our local practices. Many toll road in the DC Metro area require the use of an EZ-Pass Toll transponder and the exits should be marked as such. If you have a question about one of these lanes, please contact a [[#Local Hosts | Local Host]]. There are multiple URs a day about people being directed onto the Express or HOT lanes but staying on the regular lanes. Please explain to them how Waze will not recalculate until it is sure that you are no longer following the suggested route.
It is our custom to mark the Toll checkbox ''only on the entrance segments'' to Toll Roads. (Exception: the Dulles Toll Road, or Virginia Route 267. Please check with a local host before changing the toll/non-toll status of any segments along this road.) HOV and HOT road types have already been set correctly according to our local practices. Many toll road in the DC Metro area require the use of an EZ-Pass Toll transponder and the exits should be marked as such. If you have a question about one of these lanes, please contact a [[#Local Hosts | Local Host]]. There are multiple URs a day about people being directed onto the Express or HOT lanes but staying on the regular lanes. Please explain to them how Waze will not recalculate until it is sure that you are no longer following the suggested route.


===U-turns===
===U-turns===
Line 99: Line 94:
'''Note: Important Change'''
'''Note: Important Change'''


In the District of Columbia, U-turns are prohibited at intersections
controlled by traffic lights or police officer, or on a crosswalk adjacent to such an
intersection.


In Virginia, U-turns are generally allowed unless unsafe, or specifically denied by signage. That being said,in Virginia, a U-turn is defined as two left turns and as such, is prohibited when a left hand turn is as well. In general we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see [[Turn_restrictions#Turn_restrictions|the Wiki]]) on residential streets, but please avoid confirming them on major streets. ""CHECK DC UTURN RULES""
In Virginia, U-turns are generally allowed unless unsafe, or specifically denied by signage. That being said,in Virginia, a U-turn is defined as two left turns and as such, is prohibited when a left hand turn is as well.  
 
Generally we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see [[Turn_restrictions#Turn_restrictions|the Wiki]]) on residential streets, but please avoid confirming them on major streets.


===Alleys===
===Alleys===


In Virginia, we have many access/service roads which run behind businesses and between houses on residential streets. We mark these alleys as Private Roads, to prevent routing through them.
Often, Google address points are closer to these alleys than to the street they belong to, and Waze routing suffers. The correct response is to "nudge" the House Numbers on the streets along (either side of) the alley, so they will become trusted. See the UR page below for a suggested response to these issues. All alleys should not be named, unless they are signed.
Often, Google address points are closer to these alleys than to the street they belong to, and Waze routing suffers. The correct response is to "nudge" the House Numbers on the streets along (either side of) the alley, so they will become trusted. See the UR page below for a suggested response to these issues.
 
Alleys should not be named, unless they are signed.
'''D.C.-''' Alleys should not be mapped unless they are named, and/or necessary for routing to a destination that should be accessed from the alley. If they are mapped they should be set as parking lot roads.


"" CHECK ON DC ALLEY POLICY""
'''Virginia-'''  There are many access/service roads which run behind businesses and between houses on residential streets. Alleys are not always used but if they are they should be set as Private Roads, to prevent routing through them.


===UR Guidance===
===UR Guidance===
Due to the short nature of this map raid normal UR protocol will be suspended. All URs will be commented on, before the map raid begins. A reminder notice should be sent 2 days after initial contact and a then a closure notice to all URs without responses on the final day of the raid.
Due to the short nature of this map raid normal UR protocol will be suspended. All URs will be commented on, before the map raid begins. A reminder notice should be sent either 3 days after initial contact or on Tuesday morning. Finally a closure notice to all URs without responses on the final day of the raid.


===Cameras===
===Cameras===


'''Speed Cameras''' are illegal in Virginia.""
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. Reference the [http://mpdc.dc.gov/page/dc-streetsafe-automated-traffic-enforcement DC MPD Automated Traffic Enforcement page] to verify camera locations.
""INSERT DC CAMERA GUIDANCE. NOTE- THERE ARE MOBILE SPEED CAMERAS THAT SHOULD BE MARKED AS POLICE RATHER THAN CAMERAS. THEY ROTATE OFTEN AND SHOULD NOT BE APPROVED.""
 
{| border="1" cellpadding="2"
|- align="center"
! scope="col" width="100pt" bgcolor="skyblue" | Camera Type
! scope="col" width="200pt" bgcolor="skyblue" | Icon Used
|- align="center" bgcolor="white"
| Traditional Speed Cameras
| Speed Camera
|- align="center" bgcolor="white"
| Speed Cameras at Intersections
| Speed Camera
|- align="center" bgcolor="white"
| Traditional Red Light Cameras
| Red Light Camera
|- align="center" bgcolor="white"
| Gridlock Cameras
| Red Light Camera
|- align="center" bgcolor="white"
| Stop Sign Cameras
| Red Light Camera
|- align="center" bgcolor="white"
| Pedestrian Right of Way Cameras
| Red Light Camera
|- align="center" bgcolor="white"
| Oversized Vehicle Cameras
| Not Mapped
|}
 
 
'''Red Light Cameras''' are legal in Virginia, but are used at a very few locations in certain jurisdictions, all of which are already mapped. In particular, there are ''no'' red light cameras in Fairfax County.
 
'''Speed Cameras''' are illegal in Virginia.
 
===Roundabouts===
 
Many of the larger roundabouts in D.C. are named and should be left named. Please do not attempt to "fix" any roundabouts without first consulting a local host.


==Mapping Resources==
==Mapping Resources==


Our local GIS maps are almost always more up-to-date and correct than the Caltrans information. Please use them instead of any Caltrans documentation.


===GIS===
===GIS===
[http://dcgis.maps.arcgis.com/home/ Washington D.C. GIS ]
[http://gis.alexandriava.gov/parcelviewernet/viewer.htm City of Alexandria GIS]
[http://gis.arlingtonva.us/GIS/gis_acmap.asp Arlington County GIS]


[http://cofgis.fairfaxva.gov/fairfax/ City of Fairfax GIS]


== Communication ==
[http://www.fairfaxcounty.gov/gis/DMV/Default.aspx Fairfax County GIS]
Communication will be handled mainly in [http://www.mapraid.slack.com Slack] and WME chat. WME Chat addon will be required (which can be found [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here]).
Chat rooms will be split up and named by group.


In addition, there is a Waze Forum dedicated to the MapRaid [https://www.waze.com/forum/viewforum.php?f=1392 here], where questions can be asked, and specific issues may be identified as the Raid progresses.
[http://logis.loudoun.gov/weblogis/ Loudoun County GIS]


== Reference Links ==
== Reference Links ==
Line 144: Line 182:


=== Recommended Tools for MegaMapRaid DC===
=== Recommended Tools for MegaMapRaid DC===
* <!---- add greasyfork script for DC layer if available ---->
* [https://greasyfork.org/en/scripts/8443-wme-mega-mapraid-overlay MegaMapRaid Overlay Script]
 
* [http://www.google.com/url?q=http%3A%2F%2Fwiki.waze.com%2Fwiki%2FUser%3ARickzabel%2FUrComments%2F&sa=D&sntz=1&usg=AFQjCNF3YdPXqECiZuPNd9F3MqtR2xgSiQ UR Comments] - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.  
* [http://www.google.com/url?q=http%3A%2F%2Fwiki.waze.com%2Fwiki%2FUser%3ARickzabel%2FUrComments%2F&sa=D&sntz=1&usg=AFQjCNF3YdPXqECiZuPNd9F3MqtR2xgSiQ UR Comments] - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.  
 
* [https://w-tools.org/PlaceBrowser?group=MegaMapRaidWashingtonDC Place Browser] - In combination with the Place Name Harmonization list, this is an invaluable tool for working on existing places. Be sure to click the About tab to get an overview of the tool.
* [http://joyriding-001-site1.myasp.net/?group=MapRaidLA Place Browser] - In combination with the Place Name Harmonization list, this is an invaluable tool for working on existing places. Be sure to click the About tab to get an overview of the tool.
 
* The [http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
* The [http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
 
* [https://www.waze.com/forum/viewtopic.php?t=76488 Validator] is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.<br>Download links:
* [https://www.waze.com/forum/viewtopic.php?t=76488 Validator] is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.<br>
** For Chrome browser please download the script at [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih Chrome Web Store]
Download links:
** For Firefox browser please download the script at [https://greasyfork.org/scripts/1571-wme-validator GreasyFork.org]
* For Chrome browser please download the script at [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih Chrome Web Store]
*:''Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.''
* For Firefox browser please download the script at [https://greasyfork.org/scripts/1571-wme-validator GreasyFork.org]
* [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] is a script that  improves the WME chat GUI. For a list of all the features check the thread [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here].
''Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.''
*:''Note'': Tampermonkey/Greasmonkey is required to use this script
 
* [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] is a script that  improves the WME chat GUI. For a list of all the features check the thread [https://www.waze.com/forum/viewtopic.php?f=819&t=95038 here].
  Tapermonkey/Greasmonkey is required to use this script
----
----


{{Mbox|type=forum|text=Click [http://www.waze.com/forum/viewtopic.php?f=3&t=120113 here to view the MapRaid! LA forum] thread}}
{{Mbox|type=forum|text=Click [http://www.waze.com/forum/viewforum.php?f=1392 here to view the MapRaid forum] thread}}


== Mapraid edit lists ==
== Mapraid edit lists ==
Line 173: Line 205:
=== Boots on the ground ===
=== Boots on the ground ===


We sometimes need local information not available online -- local editors can help discover this needed infoboots on the ground to check things. Please add requests for locals to go and scout things in person, as in on the road.
Some examples when this would be used include to verify if:
* The street view is accurate,
* A road is really closed,
* A turn really allowed/prohibited, etc.


First, try the local slack channel for your area: [http://wazemapraid.slack.com/messages/mmr-md-va-dc/ #mmr-md-va-dc]
If you don't have success there, you can post a more enduring request to the '''Boots on the Ground''' sheet, to be explored by local editors. To place a new request, or respond to an existing request, please use  [//docs.google.com/forms/d/1EX8T5ZKHNUAiFVzejkgDSFM5UAlK2isUc9igREDiFKA/viewform this form].
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/1N8ZYFkew8bcVjJAMygd87BN38Rwze-3XN9GZJ6HXbss/pubhtml?gid=1833776804&amp;single=true&amp;widget=true&amp;headers=false
|width=700
|height=300
|border=0
}}
[//docs.google.com/spreadsheets/d/1N8ZYFkew8bcVjJAMygd87BN38Rwze-3XN9GZJ6HXbss/pubhtml?gid=1833776804 View this list full-screen in Google Sheets]
'''''New feature:''''' Boots responders can click the '''Navigation Link''' on a Waze-enabled device, or copy and send/save it for later use. It will open Waze and navigate to the coordinates at the center of the permalink.


== Results ==
== Results ==
Line 184: Line 234:
When the Champs see someone consistently editing well, interacting well with the community, and knowledgeable of the various details from the Wiki, they can issue promotions. This can be anything from the size of a managed area, to a rank increase, or even a new role.
When the Champs see someone consistently editing well, interacting well with the community, and knowledgeable of the various details from the Wiki, they can issue promotions. This can be anything from the size of a managed area, to a rank increase, or even a new role.


== Teams ==
== Groups ==
 
{{Anchor|Team assignments|Teams}}
{{MapRaid teams/MMR Washington}}


[[Category:Mapraid]]
[[Category:Mega map raid]]

Latest revision as of 12:17, 30 June 2015

 This wiki page is complete. Editing Group assignments are complete, and the MapRaid is in full swing! Check this page and the MegaMapRaid page for changes at least once per day, as we will post updates regularly. Stay in touch in your assigned slack channel (not the general channel if you can avoid it)

MegaMapRaid! will run from Sunday, March 8, 2015 19:00 UTC thru Thursday, March 12, 2015. The raid will last 4 days.


Welcome to the DC Metro Area

The group will be divided into multiple teams, one for each section, and possibly other exclusive teams; for PURs or to handle the Waze provided problem sheet. Each team will have their own assigned senior editor (rank 6, or 5) who will be able to edit anywhere in the Raid area, but will focus on their assigned section.

This wiki page is an attempt to highlight a majority of the local differences, but does not cover all local differences. Please see the Washington DC, Virginia or Maryland wiki pages for complete information. Additionally, parts of the DC Metro area that are actually in Maryland will follow the local guidance found in the Mega Map Raid Baltimore wiki page as this page is primarily for D.C. and Virginia.

Raid Areas

The MapRaid! is being divided up by teams. Team assignments have been posted on the Waze Forum.

Mission

Our primary mission will be to handle the URs, and PURs, followed by Place validation, and general map verification.

Functional Classification (FC) has been fully implemented for the DC Metro area.
Some road types deviate intentionally from the state DOTs classifications. If you find a road which is set to a type that is too low, upgrade it. Conversely, if you find a road which you feel is set to a type that is too high, or you need to talk about deviating from FC, please contact a local champ or State Manager before making changes.

Local hosts


Note that Metropolitan Washington DC includes areas outside the city in the states of Virginia and Maryland. Washington DC is not considered to be in any US state, but is treated as a quasi-state.

Important!

Please do not alter any of the following road types without first consulting a Local Host: Freeway, Ramp, Major Highway, minor Highway, Primary Street. It is OK to change segments of the above types, but do not change the segment's type without local guidance.

Please do not mass-edit Do not perform edits which will affect large numbers of segments at once. The edit history of segments is highly valuable in the process of solving URs. Mass editing effectively mass erases this history, permanently. We ask that all necessary processes which might affect large portions of the map, or long stretches of roads, be reserved until near the end of the MapRaid. This includes the “Select entire street” function.

Anything locked at 5 or 6? Please check with a local editor before making changes. Rank 5 and 6 editors - consider keeping highlights active for locks 5 and 6.

Close nodes We make extensive use of the "micro-dogleg" technique, where a geometry node is carefully placed, at full zoom, directly next to a junction node, in order to set the angle to create a desired Turn/Stay/Exit prompt. Please watch for these if you move any junction node, and be sure to recreate the same angle at the new location.


Actual locks used may be more or less than values in the table below, depending on area circumstance 

   Please consult the RC, SM, or appropriate AM for guidance
Washington, DC Locking Rank Standard Guideline
Segment Type Default locks
 Freeway  5
 Ramp  Highest rank of connected segment
 Major Highway  4
 Minor Highway  3
 Primary Street  2
 Street  1
 • • • • Ferry • • • •   5
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2

Note that these are minimums and, for protection, certain segments may be at higher lock levels. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.

Local Guidance

Functional Classification

In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our Road Type Wiki

The Functional Classification has been completed in the DC Metro Area. Occasionally, we find short segments that were missed in the selection process for conversion, and it is important that these be corrected for routing continuity. In general, however, we ask that Road Types not be changed without consulting one of the Local Hosts. In isolated cases, we have chosen to deviate from official classifications, due to errors or outdated information in the VDOT or DCDOT FC maps, or to better accommodate real-life situations and Waze quirks. It is important that these remain intact. If you find an area that doesn't seem to be complete please bring it to the attention of a Local Host for review.

The Functional Classification (FC) map for Virginia is currently broken. Please do NOT make any road type changes to any segment typed Primary Street or above without first contacting a Virginia State Manager.

Place Editing

Please show some national pride and update your country's embassy!

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 minimum. Places (formerly called landmarks) in Virginia now follow the detailed guidance in the US standard for places. Additionally, please consult the following table for minimum lock level for completed places.

Place Type Minimum Lock Level
Area Places 2
Gas Stations 3
Hospital/Medical Care 4
Fire Department 3
Police Station 3


Gas Stations

Gas Stations should be locked to level 3 but, only after all data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a hosting local if you need help identifying gas station information.

For editors below rank 3, once you have completely filled out a gas station with the min required information, please ask for a lock request.

Toll Roads / HOV / HOT / Truck Lanes

It is our custom to mark the Toll checkbox only on the entrance segments to Toll Roads. (Exception: the Dulles Toll Road, or Virginia Route 267. Please check with a local host before changing the toll/non-toll status of any segments along this road.) HOV and HOT road types have already been set correctly according to our local practices. Many toll road in the DC Metro area require the use of an EZ-Pass Toll transponder and the exits should be marked as such. If you have a question about one of these lanes, please contact a Local Host. There are multiple URs a day about people being directed onto the Express or HOT lanes but staying on the regular lanes. Please explain to them how Waze will not recalculate until it is sure that you are no longer following the suggested route.

U-turns

Note: Important Change

In the District of Columbia, U-turns are prohibited at intersections controlled by traffic lights or police officer, or on a crosswalk adjacent to such an intersection.

In Virginia, U-turns are generally allowed unless unsafe, or specifically denied by signage. That being said,in Virginia, a U-turn is defined as two left turns and as such, is prohibited when a left hand turn is as well.

Generally we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see the Wiki) on residential streets, but please avoid confirming them on major streets.

Alleys

Often, Google address points are closer to these alleys than to the street they belong to, and Waze routing suffers. The correct response is to "nudge" the House Numbers on the streets along (either side of) the alley, so they will become trusted. See the UR page below for a suggested response to these issues. All alleys should not be named, unless they are signed.

D.C.- Alleys should not be mapped unless they are named, and/or necessary for routing to a destination that should be accessed from the alley. If they are mapped they should be set as parking lot roads.

Virginia- There are many access/service roads which run behind businesses and between houses on residential streets. Alleys are not always used but if they are they should be set as Private Roads, to prevent routing through them.

UR Guidance

Due to the short nature of this map raid normal UR protocol will be suspended. All URs will be commented on, before the map raid begins. A reminder notice should be sent either 3 days after initial contact or on Tuesday morning. Finally a closure notice to all URs without responses on the final day of the raid.

Cameras

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. Reference the DC MPD Automated Traffic Enforcement page to verify camera locations.

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


Red Light Cameras are legal in Virginia, but are used at a very few locations in certain jurisdictions, all of which are already mapped. In particular, there are no red light cameras in Fairfax County.

Speed Cameras are illegal in Virginia.

Roundabouts

Many of the larger roundabouts in D.C. are named and should be left named. Please do not attempt to "fix" any roundabouts without first consulting a local host.

Mapping Resources

GIS

Washington D.C. GIS

City of Alexandria GIS

Arlington County GIS

City of Fairfax GIS

Fairfax County GIS

Loudoun County GIS

Reference Links

The Basics

Recommended Tools for MegaMapRaid DC

  • MegaMapRaid Overlay Script
  • UR Comments - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.
  • Place Browser - In combination with the Place Name Harmonization list, this is an invaluable tool for working on existing places. Be sure to click the About tab to get an overview of the tool.
  • The WME Reference Sheet[PDF] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
  • Validator is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.
    Download links:
    Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.
  • WME Chat Addon is a script that improves the WME chat GUI. For a list of all the features check the thread here.
    Note: Tampermonkey/Greasmonkey is required to use this script
 Click here to view the MapRaid forum thread

Mapraid edit lists

Spreadsheets and forms are being used to streamline management of various group efforts and track important edits. Below you can find links to use these these forms, sheets, and see the lists.

Scheduled Edits

Boots on the ground

We sometimes need local information not available online -- local editors can help discover this needed infoboots on the ground to check things. Please add requests for locals to go and scout things in person, as in on the road. Some examples when this would be used include to verify if:

  • The street view is accurate,
  • A road is really closed,
  • A turn really allowed/prohibited, etc.

First, try the local slack channel for your area: #mmr-md-va-dc

If you don't have success there, you can post a more enduring request to the Boots on the Ground sheet, to be explored by local editors. To place a new request, or respond to an existing request, please use this form.

View this list full-screen in Google Sheets

New feature: Boots responders can click the Navigation Link on a Waze-enabled device, or copy and send/save it for later use. It will open Waze and navigate to the coordinates at the center of the permalink.

Results

MapRaid Promotions

Some editors really let their bright side out, and let their community skills shine. This is even more evident in a concerted group effort with high-density editing like a MapRaid!. Editors of all ranks working closely with each other and the Champs, really lets us everyone get to know each other, and allows certain editors to be recognized for their skills and effort.

When the Champs see someone consistently editing well, interacting well with the community, and knowledgeable of the various details from the Wiki, they can issue promotions. This can be anything from the size of a managed area, to a rank increase, or even a new role.

Groups

MegaMapRaid!
Regional Coordinator: Silvio (PM [Help])  , Enhket (PM [Help])  , caradellino (PM [Help])  , orbitc (PM [Help])  , Jemay (PM [Help])  , sketch (PM [Help])  
Username (rank) Team Assigned Comments Team Area
Amarock85(6) [PM [Help]]  21 - Washington 21
vectorspace(6) [PM [Help]]  21 - Washington 21
gaetanaga(5) [PM [Help]]  21 - Washington 21
PhantomSoul(5) [PM [Help]]  21 - Washington 21
iamrioo(4) [PM [Help]]  21 - Washington 21
rst193(4) [PM [Help]]  21 - Washington 21
BenMimix(3) [PM [Help]]  21 - Washington 21
gimow(3) [PM [Help]]  21 - Washington 21
juanfelipep(3) [PM [Help]]  21 - Washington 21
kgatit(3) [PM [Help]]  21 - Washington 21
TR-11(3) [PM [Help]]  21 - Washington 21
ekapan(2) [PM [Help]]  21 - Washington 21
eletrimark(2) [PM [Help]]  21 - Washington 21
jumantilla(2) [PM [Help]]  21 - Washington 21
marianox94(2) [PM [Help]]  21 - Washington 21
sabrikadir(2) [PM [Help]]  21 - Washington 21
Trotskyist(2) [PM [Help]]  21 - Washington 21
Durango48(6) [PM [Help]]  22 - Washington 22
HEPST(6) [PM [Help]]  22 - Washington 22
alexnet1983(5) [PM [Help]]  22 - Washington 22
qwaletee(5) [PM [Help]]  22 - Washington 22
elcitia(4) [PM [Help]]  22 - Washington 22
maxoTNS(4) [PM [Help]]  22 - Washington 22
amiga6(3) [PM [Help]]  22 - Washington 22
DelleTenebre(3) [PM [Help]]  22 - Washington 22
nirvuad(3) [PM [Help]]  22 - Washington 22
RIMAJUES(3) [PM [Help]]  22 - Washington 22
theups(3) [PM [Help]]  22 - Washington 22
brujofav(2) [PM [Help]]  22 - Washington 22
haziqruzaini(2) [PM [Help]]  22 - Washington 22
hkubilayk(2) [PM [Help]]  22 - Washington 22
jhcifue(2) [PM [Help]]  22 - Washington 22
mkovnick(2) [PM [Help]]  22 - Washington 22
rfergomes(2) [PM [Help]]  22 - Washington 22
BellHouse(6) [PM [Help]]  23 - Washington 23
frankino36(5) [PM [Help]]  23 - Washington 23
perezgustavo(5) [PM [Help]]  23 - Washington 23
TerryPurdue(5) [PM [Help]]  23 - Washington 23
JaRoY(4) [PM [Help]]  23 - Washington 23
NalaKarokaro(4) [PM [Help]]  23 - Washington 23
Bluediemond(3) [PM [Help]]  23 - Washington 23
curantes(3) [PM [Help]]  23 - Washington 23
diegopineros(3) [PM [Help]]  23 - Washington 23
foxrpg(3) [PM [Help]]  23 - Washington 23
skydras(3) [PM [Help]]  23 - Washington 23
billt42(2) [PM [Help]]  23 - Washington 23
ermidel(2) [PM [Help]]  23 - Washington 23
ferchomon(2) [PM [Help]]  23 - Washington 23
HeladoCaliente(2) [PM [Help]]  23 - Washington 23
ivancarlos81(2) [PM [Help]]  23 - Washington 23
kadirardic(2) [PM [Help]]  23 - Washington 23
top_gun_de(6) [PM [Help]]  24 - Washington 24
jab_au(5) [PM [Help]]  24 - Washington 24
ohiostmusicman(5) [PM [Help]]  24 - Washington 24
Olestas(5) [PM [Help]]  24 - Washington 24
GerritW74(4) [PM [Help]]  24 - Washington 24
kakmade(4) [PM [Help]]  24 - Washington 24
Andris30(3) [PM [Help]]  24 - Washington 24
eaglejm7(3) [PM [Help]]  24 - Washington 24
hurja(3) [PM [Help]]  24 - Washington 24
Ralphius(3) [PM [Help]]  24 - Washington 24
sammyke007(3) [PM [Help]]  24 - Washington 24
Cp820(2) [PM [Help]]  24 - Washington 24
dalejandro7(2) [PM [Help]]  24 - Washington 24
DustinHetzel(2) [PM [Help]]  24 - Washington 24
f1tzy1(2) [PM [Help]]  24 - Washington 24
MetallicAsh(2) [PM [Help]]  24 - Washington 24
PetryLuz(2) [PM [Help]]  24 - Washington 24
Mynios(6) [PM [Help]]  25 - Washington 25
DavidChanTW(5) [PM [Help]]  25 - Washington 25
Helgramite(5) [PM [Help]]  25 - Washington 25
ituajr(5) [PM [Help]]  25 - Washington 25
juliansgm(4) [PM [Help]]  25 - Washington 25
mapdevil(4) [PM [Help]]  25 - Washington 25
grevco(3) [PM [Help]]  25 - Washington 25
hawkeygoal(3) [PM [Help]]  25 - Washington 25
MAL123MAL(3) [PM [Help]]  25 - Washington 25
MattKo(3) [PM [Help]]  25 - Washington 25
Zm0gis(3) [PM [Help]]  25 - Washington 25
AmySolen(2) [PM [Help]]  25 - Washington 25
bylipe(2) [PM [Help]]  25 - Washington 25
D3RPY(2) [PM [Help]]  25 - Washington 25
maknu_2(2) [PM [Help]]  25 - Washington 25
mlo1088(2) [PM [Help]]  25 - Washington 25
HugoGTM(6) [PM [Help]]  26 - Washington 26
dark_lobito(5) [PM [Help]]  26 - Washington 26
Dogshrink(5) [PM [Help]]  26 - Washington 26
fuchserl(5) [PM [Help]]  26 - Washington 26
SerzhM1(4) [PM [Help]]  26 - Washington 26
stefanogeol(4) [PM [Help]]  26 - Washington 26
AdamB1995(3) [PM [Help]]  26 - Washington 26
aler13(3) [PM [Help]]  26 - Washington 26
anjim(3) [PM [Help]]  26 - Washington 26
xanderb(3) [PM [Help]]  26 - Washington 26
yywilk(3) [PM [Help]]  26 - Washington 26
BERMOX(2) [PM [Help]]  26 - Washington 26
Luismedina85(2) [PM [Help]]  26 - Washington 26
M4n0t4z(2) [PM [Help]]  26 - Washington 26
Redman822(2) [PM [Help]]  26 - Washington 26
sandrormc(2) [PM [Help]]  26 - Washington 26
roencaco(6) [PM [Help]]  27 - Washington 27
arielorellana(5) [PM [Help]]  27 - Washington 27
ghost012(5) [PM [Help]]  27 - Washington 27
karlcr9911(5) [PM [Help]]  27 - Washington 27
ulle2(4) [PM [Help]]  27 - Washington 27
jayleongwk(3) [PM [Help]]  27 - Washington 27
ricardozanan(3) [PM [Help]]  27 - Washington 27
SanzClew(3) [PM [Help]]  27 - Washington 27
sonert(3) [PM [Help]]  27 - Washington 27
tomyk(3) [PM [Help]]  27 - Washington 27
ArmandoBro(2) [PM [Help]]  27 - Washington 27
bundlegut(2) [PM [Help]]  27 - Washington 27
FernandoBDutra(2) [PM [Help]]  27 - Washington 27
gio_ge(2) [PM [Help]]  27 - Washington 27
HEFEROCE(2) [PM [Help]]  27 - Washington 27
cherianchris(6) [PM [Help]]  28 - Washington 28
akkingjason(5) [PM [Help]]  28 - Washington 28
Ctpoole(5) [PM [Help]]  28 - Washington 28
netogrimald(5) [PM [Help]]  28 - Washington 28
ruspicioni(4) [PM [Help]]  28 - Washington 28
swm(4) [PM [Help]]  28 - Washington 28
aleonnet(3) [PM [Help]]  28 - Washington 28
boranbora(3) [PM [Help]]  28 - Washington 28
CoolCityCat(3) [PM [Help]]  28 - Washington 28
jaywazin(3) [PM [Help]]  28 - Washington 28
Pleswi(3) [PM [Help]]  28 - Washington 28
Davisnado(2) [PM [Help]]  28 - Washington 28
JackPoliceDepartment(2) [PM [Help]]  28 - Washington 28
lavmagno(2) [PM [Help]]  28 - Washington 28
Santii432(2) [PM [Help]]  28 - Washington 28
SeekingSerenity(2) [PM [Help]]  28 - Washington 28
ci2212(6) [PM [Help]]  29 - Washington 29
Arnoniem(5) [PM [Help]]  29 - Washington 29
ct13(5) [PM [Help]]  29 - Washington 29
stebur71(4) [PM [Help]]  29 - Washington 29
sweus(4) [PM [Help]]  29 - Washington 29
advent149(3) [PM [Help]]  29 - Washington 29
AgentW4C(3) [PM [Help]]  29 - Washington 29
asher399(3) [PM [Help]]  29 - Washington 29
netoathayde(3) [PM [Help]]  29 - Washington 29
tckma(3) [PM [Help]]  29 - Washington 29
GeorgiaBreeze(2) [PM [Help]]  29 - Washington 29
nightshadeNOLA(2) [PM [Help]]  29 - Washington 29
Peagah(2) [PM [Help]]  29 - Washington 29
spiderveprik(2) [PM [Help]]  29 - Washington 29
tonybt(2) [PM [Help]]  29 - Washington 29
neo777(6) [PM [Help]]  30 - Washington 30
apolo16(5) [PM [Help]]  30 - Washington 30
lipegam(5) [PM [Help]]  30 - Washington 30
nhanway(5) [PM [Help]]  30 - Washington 30
mapzade(4) [PM [Help]]  30 - Washington 30
xFrancesca(4) [PM [Help]]  30 - Washington 30
james890526(3) [PM [Help]]  30 - Washington 30
JasonN899(3) [PM [Help]]  30 - Washington 30
Longlay(3) [PM [Help]]  30 - Washington 30
rodrigojusti(3) [PM [Help]]  30 - Washington 30
stausholm(3) [PM [Help]]  30 - Washington 30
AntonioLuizCC(2) [PM [Help]]  30 - Washington 30
cheaspee(2) [PM [Help]]  30 - Washington 30
DjjDcz(2) [PM [Help]]  30 - Washington 30
mudge42(2) [PM [Help]]  30 - Washington 30
Rand-o-licious(2) [PM [Help]]  30 - Washington 30
Retrieved from "https://beta.waze.com/wiki/USA/index.php?title=MegaMapRaid/Washington_DC_MMR&oldid=111706"