mNo edit summary |
|||
| Line 8: | Line 8: | ||
}} | }} | ||
---- | ---- | ||
==Welcome to the DC Metro Area== | ==Welcome to the DC Metro Area== | ||
| Line 20: | Line 20: | ||
====Raid Groups==== | ====Raid Groups==== | ||
====PUR Areas==== | ====PUR Areas==== | ||
== Mission == | == Mission == | ||
| Line 134: | Line 134: | ||
===GIS=== | ===GIS=== | ||
== Communication == | == Communication == | ||
| Line 173: | Line 154: | ||
*[[Community Plugins, Extensions and Tools]] where you'll links and descriptions to most of the editing scripts being used. Some of these are essential to good editing, and others make the editing process much easier. WME Validator, URO+, and WME Toolbox are highly recommended. | *[[Community Plugins, Extensions and Tools]] where you'll links and descriptions to most of the editing scripts being used. Some of these are essential to good editing, and others make the editing process much easier. WME Validator, URO+, and WME Toolbox are highly recommended. | ||
=== Recommended Tools for | === Recommended Tools for MegaMapRaid DC=== | ||
* | * <!---- add greasyfork script for DC layer if available ----> | ||
* [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. | ||
| Line 200: | Line 181: | ||
===Scheduled Edits=== | ===Scheduled Edits=== | ||
=== Boots on the ground === | === Boots on the ground === | ||
== Results == | == Results == | ||
== MapRaid Promotions == | == MapRaid Promotions == | ||
| Line 243: | Line 197: | ||
== Teams == | == Teams == | ||
[[Category:Mapraid]] | [[Category:Mapraid]] | ||
Revision as of 02:42, 4 March 2015
MegaMapRaid! will run from Sunday, March 7, 2015 thru Wednesday, March 11, 2015. The raid will last 4 days.
 |
Please be sure to explore the Wiki page. Also, check back regularly in case of added materials. |
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.
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.
Raid Areas
The MapRaid! is being divided up by teams. You can see the interactive map with all the teams, and PUR areas drawn out here.
Raid Groups
PUR Areas
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 you feel is not classified correctly or set to the right type, please contact a local champ or State Manager (SM) before making changes. |
Local Hosts
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.
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
| 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.
Place Editing
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 | 3 |
| 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.
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 Host before making changes.
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 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.
Construction
There are a number of major construction projects in process within the overall MapRaid area. These construction projects can cause frequent intermittent road closures. Many closures change daily and cause great numbers of URs to appear. When handling URs in one of these areas, be aware that reports of "Turn not allowed", "Missing road", "Wrong driving direction" are common, but may not indicate a map problem that can be fixed, because the physical road situation will change before our edits can take effect.
""NOT SURE IF THIS SECTION IS NEEDED. NO MAJOR CONSTRUCTIONS PROJECTS JUMP TO MIND, BUT THERE IS A DC THREAD ABOUT CONSTRUCTION""
U-turns
Note: Important Change
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 the Wiki) on residential streets, but please avoid confirming them on major streets. ""CHECK DC UTURN RULES""
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. Alleys should not be named, unless they are signed.
"" CHECK ON DC ALLEY POLICY""
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.
Cameras
Speed Cameras are illegal in Virginia."" ""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.""
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
Communication
Communication will be handled mainly in Slack and WME chat. WME Chat addon will be required (which can be found here). Chat rooms will be split up and named by group.
In addition, there is a Waze Forum dedicated to the MapRaid here, where questions can be asked, and specific issues may be identified as the Raid progresses.
Reference Links
The Basics
- New editor welcome page
- Waze Map Editor
- Best Map Editing Practice
- Editing manual
- Common editing mistakes
- How to make a Permalink
- All about using the WME Chat
- Community Plugins, Extensions and Tools where you'll links and descriptions to most of the editing scripts being used. Some of these are essential to good editing, and others make the editing process much easier. WME Validator, URO+, and WME Toolbox are highly recommended.
Recommended Tools for MegaMapRaid DC
- 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:
* For Chrome browser please download the script at Chrome Web Store * For Firefox browser please download the script at GreasyFork.org
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.
Tapermonkey/Greasmonkey is required to use this script
 |
Click here to view the MapRaid! LA 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
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.