Cute intro like We're heading down to the shore early this season. MapRaid New Jersey May 2015 will be 27 May 2015 through 3 June 2015. Intro with some clues about population/road density This map raid region is affectionately known as "The Shore" in New Jersey, New York, and Pennsylvania. Salt air, cool summer breezes and endless boardwalk amusements for young and old bring visitors from the northeastern United States and Canada. Wintertime population is a little over a million, but summertime population is eight to ten times that. Fun exhortation: Let's raid the map to help Wazers find their favorite places and find better ways to get to them this summer and every summer!
Post Card/Meme
[[File:Mapraid JerseyShore meme2.png|frameless|350px|left]]
Mission
Our primary mission will be to handle the URs, and PURs, followed by Place validation, and general map verification.
Local Hosts
Your local hosts are the experts on how the guidance you see on this page applies to the MapRaid area. If the guidelines are not clear, please check with them or with anyone else they might designate during the raid.
Important!
Road Types
Please do not change the types of roads without getting appropriate guidance:
- Freeways
- Ramps
- Major Highways
- Minor Highways
- Primary Streets
Some changes to road types could mess up continuity and distort routing. See the section below on road names, types, and FC for more information
Mapraid UR Rules
We will follow the usual US UR etiquette with one exception: During the Map raid, the wait time is reduced to 4 days.
Some URs are meant to stay open for a while. Please contact the editor working on them before closing. Some examples are:
- The UR contains a tag such as [NOTE], [CLOSURE], or any other [xxx]. Unless -- it is a [CLOSURE] that has already passed. The URO+ extension makes it easy to spot these
- Very old [CLOSURE] URs might be ripe for closure -- check carefully.
- The UR contains a request from the editor not to close it.
- There is clearly communication going on between the reporter and one or more editors.
Please Do Not Mass-Edit
Do not perform edits that affect large numbers of segments at once. Specifically, avoid the Select Entire Street button completely. Doing so makes it difficult to tell who fixed what parts of the map to solve different URs. While we recognize that sometimes a solution might involve fixing a road name over an entire section of road or dividing/undividing it, for example, we ask that you defer these updates toward the end of the raid.
Level 5,6 Locks
Level 5 and 6 locks usually indicate that an unorthodox treatment to the map for those segments was necessary. They are also used for Freeway segments that we believe are accurate and up-to-date with the best information available at the current time. Please check with local editors before making any changes to these segments. Consider use WME Color Highlights or WME Toolbox extensions to highlight L5- and L6-locked segments.
Micro-Doglegs
We utilize these extensively throughout the state to engineer turn- vs. stay/keep/exit instructions based on the driving experience approaching many junctions, regardless of the angle any road might depart at. Be sure to zoom in really close at each junction where there might be a question about its geometry or routing to check for a micro-dogleg.
Local Guidance
Road Types, Names, and Functional Classification (FC)
We follow the general US standards for road types based on the hybrid rule of FC and Route Type. FC-based upgrades have been completed xxx. In xxx, all yyy and zzz are set correctly but some roads that should be www might not be set correctly. If you find roads that seem to need to be reclassified, please work with one of the raid hosts.
There are xxx diferent types of numbered routes in yyy
- Federal: I-195 E, US-9
- State: SR-35 S, SR-72
- County: CR-537, CR-4
When a segment has more than one name and/or more than one route designation, name it in a way that will be most useful to the wazer listening to navigational instructions. This means using the name that appears on the most frequently encountered signs. If the name on the signs changes very frequently, keep it consistant by using the most consistantly-used name. If both the name and the route designation consistantly appear on the same sign, use the name.All other names/route designations should be entered as alternate names. You can read more about this in Concurrent names on US roads.
For more information on correct names and road types, please see Mapping resources below.
Locking Standards
In Voludu2 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.
| Segment Type | Statewide |
|---|---|
| Freeway | 5 |
| Ramp | Highest rank of connected segments |
| Major Highway | 3 |
| Minor Highway | 3 |
| Primary Street | 1 (Auto) |
| Street | 1 (Auto) |
| Private Road | 1 (Auto) |
| • • • • Ferry • • • • | 5 |
| |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-| | 2 |
Note: Do Not Mass Edit just to update locks to these standards, these can be adjusted as you find them 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.
These are the minimum lock level guidelines. Higher level locks can be used in exceptional circumstances. Before locking a road, be sure its information is complete and up to date, including house numbers, if available. If the road should be locked above your editing level, be sure to request an appropriate lock. For more information, please see
Places
- Complex, intricate, or otherwise critical Places, such as airports, hospitals, police/fire departments, or many urban parks should be locked at least to Level X.
- Gas stations and other types of places fundamental to the functionality of the Waze app should also be locked at least to Level X, but only after at least all the Brand, Name, and Address have been filled in. Remember to ask locals for help if needed.
- If you can't lock it to the correct level, lock it as high as you can and ask for help with the locks.
For more information on Places editing in xxx, please read .
Mapping Resources
Communication
Communication will be handled primarily in #Slack Channels and WME chat can also be used. The WME Chat addon is recommended. Special Slack channels will be set up and named by raid location and group. Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to.
Click here to get your Slack invitation. Be sure to choose WazeMapRaid to the MapRaid question.
If you have an issue getting into the slack team and channels, please reach out to one of the MapRaid organizers.
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 MapRaid
- overlay link
- Places browser link
- UR Comments - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation. Tamper monkey required
- 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.
- Chrome browser: please download the script at Chrome Web Store
- Firefox browser: please download the script at GreasyFork.org -- tamper monkey or grease monkey required
- 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 required
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.
Results
 |
Check back here after the raid is completed to see the results and achievements |
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.
|
Watch here for results of promotions during and after the raid. |
Teams
 |
add teams here |