The BeanTown MapRaid will begin on 7 July, 2015. The raid will last for approximately 10 days.
| Please be sure to explore the Wiki page. Also, check back regularly in case of added materials.
You are only seeing modifications of this page made up until Mon, 14 Oct 2019 02:26:03 UTC,
make sure to log in to the wiki to see the latest updates.
|add image of raid area|
- 1 Welcome to Boston!
- 2 Mission
- 3 Local Hosts
- 4 Important!
- 5 Local Guidance
- 6 Mapping Resources
- 7 Communication
- 8 Reference Links
- 9 MapRaid edit lists
- 10 Results
- 11 MapRaid Promotions
- 12 Teams
Welcome to Boston!
Our mission are to handle the following (in order of priority):
- URs and PURs
- Places validation
- Road Classification Conversion
- General map verification
The MapRaid! is being divided up by teams.
Please do not alter any of the following road types without first consulting a Local Host: Freeway, Ramp, Major Highway, Minor Highway, Primary Street. You may edit these roads, but do not change the type of the segment.
Anything locked at 5 or 6? Please check with a local editor before making changes.
If you are a rank 5 or 6 editor - consider keeping highlights active for locks 5 and 6.
Close nodes We make 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.
In Massachusetts we have a set minimum standard for locking roads based on segment type. 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 (FC and highway systems). Lock the roads based on type after they've been set to current US road type standards.
|Highest rank of connected segments|
Note: Do Not Mass Edit just to update locks to these standards, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.
Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of BDP, U-turn prevention, or using micro-doglegs, or other complex intersection setups.
Functional Classification is partially complete within the state.
PUR should be reviewed for accuracy, once approved all relevant information pertaining to the place should be entered. Please use each company's website to gather all information you can.
All Places added to the map must contain the following entries:
- Proper Category
- Place Name
- Address (including address numbers)
- Placed in the correct location on the map
This is the minimum acceptable amount of information for inclusion on the map.
- All Places that have complete information (to include, at a minimum, address/city, hours of operation, phone number) are to be locked at Level 2. This is to prevent loss of data due to automatic acceptance of Place Update submissions from Trusted Users, or Place Update Request approvals from other editors without careful examination.
Once a place is complete please lock to Level 3. If your own editor rank is 1 or 2, let someone else know via Slack, since you can't lock to rank 3.
This practice will prevent app trusted users and most IGN editors from making incorrect changes to places we know are right. App trusted users and IGN editors are rarely rank 3.
Following are general standards for place locking in Massachusetts:
|PLACE TYPE||LOCK LEVEL|
|Military Installation / Airport||4|
|Hospitals / Urgent Care / Police & Fire Dept||4|
|National & State Parks and Monuments||4|
|Gas Stations / Charging Stations||3|
|Schools / Universities / Colleges||3|
|Government Buildings / Consulates||3|
Update Requests (URs)
For the purpose of the MapRaid we will be using a 5-day response time. Once initial contact is attempted you will be allowed to close the UR after 5 days. Reminder comments can be used within the five days. The clock used to close the UR will be from the initial MapRaid contact. Reminder comments do not reset the closure clock.
2014-12-05 UR is opened
2014-12-15 Local editor comment
2015-01-25 Initial MapRaid comment
2015-01-28 MapRaid reminder comment
2015-01-30 UR can be closed.
Before closing the UR, please make all attempts to solve the UR before closing it as 'Not Identified'. Even if there is no reporter response, use the report type, description, route and GPS traces, streetview and other resources to diagnose the problem.
Those found closing UR's before 5 days as "Not Identified" will be removed from the Raid.
The preferred method of communication for this Raid will be a web based program called "Slack". This program has many advantages over Google Hangouts.
If you aren't already a member of the Waze Map Raid Slack then please submit your information on this form: http://bit.ly/Slack_invite
You will receive an invitation in your email within 24 hours.
- 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 MapRaid
- UR Comments - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.
- 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.
* 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
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.
|Check back here after the raid is completed to see the results and achievements|
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.
|Watch here for results of promotions during and after the raid.|
|add teams here|