|This map raid is over! Thank you for your help. Check back here for results.|
Start: September 17th (Sunday)
End: September 25th (Monday)
Registration FORM (Will be closed on: September 12th)
(You MUST be in Waze MapRaid Discord to be able to edit in this MR - No Discord...No Area....No exceptions)
GOALs: * Improve Basemap (Primary goal)
- Improving routing and navigation within the designated area quickly and efficiently.
- Solve / respond to User Reports.
- Updating pending “Places”.
|orbitc(6) [ ]||Regional Coordinator|
Map Raid Organizer
- 1 Mapraid Host
- 2 MapRaid Goals
- 3 Basemap
- 4 MR Area
- 5 Groups
- 6 About this map raid
- 7 Communication
- 8 Reference Links
- 9 Mapraid edit lists
- 10 Results
Our primary goal is to Improve Basemap
- Improve Routing and Navigation.
- Solve / Respond to User Reports.
- PURs (Places)
- General map verification, restricted turn verification (Shift + Z)
- Functional Classification.
About this map raid
Please read the entire MapRaid wiki. If you are still uncertain what to do about something you see on the map, please ask your group leader.
Beginning and junior editors -- find a senior editor and start asking questions. Take this raid as a learning opportunity. Everything new you learn -- do a little follow-up reading in the wiki to make sure you understand. The more you learn, and the more positive interaction you get with the senior editors, the better you can prepare yourself for a future rank upgrade or area expansion. There are always a few promotion announcements at the end of every map raid.
Thank You for your help with the map.
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. Do not close URs if the UR contains a tag such as [NOTE], [CLOSURE], or any other [MESSAGE] -- check with the editor who placed the tag.
Do Not Mass-Edit
DO NOT perform edits that affect large numbers of segments at once. We want to be able to see how URs and other problems got resolved. Mass edits can be done at the end of the map raid.
We use micro-doglegs to control turn- vs. stay/keep/exit instructions. Zoom in very close to see the closely-spaced geometry nodes. Preserve them.
Road Types, Names, and Functional Classification (FC)
In Pennsylvania , we follow general US standards for road types based on the hybrid rule of FC and Route Type. Special road names are
- Federal: I-195 E, US-9
- State: SR-35 S, SR-72
- If the state road appears on the sign that drivers see as PA-xxx, use that in the road name.
If a road has more than one name follow the standard for Concurrent names on US roads.
In Pennsylvania 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 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.
Trust the rules in the places browser.
How to order a Philly cheesesteak
If you go to Pat's or Geno's, don't ask for a cheese steak -- that's redundant. Say "One, provolone, with". Or, if you must, "One, wiz, with".
We will use Discord to communicate. There is a Pennsylvania Raid general channel and also a channel for each raid group. You must be in Discord to be able to edit in this MapRaid
WME chat can also be used. The WME Chat addon is recommended.
- 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. Tampermonkey / greasemonkey 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.
- 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
For more information, please see Pennsylvania/Resources
- City/County of Philadelphia (all groups) Street, address and FC
- Delaware County (groups A, B, C) Parcels and FC
- Montgomery County (groups B, C, D) Streets (PDF), County Roads and FC
- Bucks County(E and D) Parcels and FC
- Chester County (group 2 -- a tiny corner) Streets and Parcels and FC
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.
Great job for the first ever PA MR. Incredible improvements on the connectivity score.
HOF Image here
|Watch here for results of promotions during and after the raid.|