(→Road Types, Names, and Functional Classification (FC): simpler PA-XXX) |
(→About this map raid: opportunities for learning and advancement.) |
||
| Line 72: | Line 72: | ||
<!-- add any important information important to the raid here --> | <!-- add any important information important to the raid here --> | ||
<!-- keep this list short. link to other pages where possible.--> | <!-- keep this list short. link to other pages where possible.--> | ||
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 | '''Thank You for your help with the map.''' | ||
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. | |||
===Mapraid UR Rules=== | ===Mapraid UR Rules=== | ||
| Line 78: | Line 81: | ||
During the Map raid, the wait time is reduced to | During the Map raid, the wait time is reduced to | ||
4 | 4 | ||
days. | days. | ||
Do not close URs if the UR contains a tag such as [NOTE], [CLOSURE], or any other [MESSAGE]. | Do not close URs if the UR contains a tag such as [NOTE], [CLOSURE], or any other [MESSAGE]. | ||
=== Do Not Mass-Edit === | === Do Not Mass-Edit === | ||
DO NOT perform edits that affect large numbers of segments at once. We want to | 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. | ||
=== Micro-Doglegs === | === Micro-Doglegs === | ||
| Line 103: | Line 105: | ||
===Places=== | ===Places=== | ||
Pennsylvania follows the US standards for [[Places]] | Pennsylvania follows the US standards for [[Places]]. | ||
<!-- ===Left Turns=== | <!-- ===Left Turns=== | ||
? | ? | ||
| Line 118: | Line 120: | ||
===How to order a cheesesteak=== | ===How to order a 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 "One, wiz, with" | 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". | ||
==Mapping Resources== | ==Mapping Resources== | ||
Revision as of 17:56, 4 June 2015
 |
MapRaid participants: please do not edit in the area of the mapraid until the time of the official announcement in the mapraid slack general channel. This will allow us to get good mapraid statistics. This mapraid page is still under construction. Please be patient as we get it ready for the upcoming raid. |
MapRaid Philadelphia June 2015 will be 7 June at 19:00 UTC (3:00 PM EDT) through 14 June 2015. The group will be divided into 5 groups, one for each section. Each group will have both local and senior editors, one of which will be the "Group leader" - listed in blue below. Please direct all questions to your group leaders. The raid hosts will be available across all areas for added support.
Mission
Our primary mission is to handle
- URs -- On day 1, please respond to all URs which do not have enough information.
- MPs
- PURs (Places)
- General map verification and
- Functional Classification.
Local Hosts
Groups
About this map raid
Thank You for your help with the map. 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.
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].
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.
Micro-Doglegs
We use micro-doglegs (very short geometry sections of segments) to engineer turn- vs. stay/keep/exit instructions. Zoom in very close to see these micro-doglegs. 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.
Road Locks
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.
| 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.
Places
Pennsylvania follows the US standards for Places.
How to order a 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".
Mapping Resources
Communication
We will use #Slack Channels. There is a [http://wazemapraid.slack.com/messages/ xxx yyy Raid general channel] and also a channel for each raid group. Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to. If you are not already part of the WazeMapRaid slack team, Click here to get your Slack invitation. Be sure to choose WazeMapRaid to the MapRaid question. If you have trouble getting into the slack team and channels, please reach out to one of the MapRaid organizers.
WME chat can also be used. The WME Chat addon is recommended.
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
- Map Raid Place Browser tampermonkey/greasemonkey required
- 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.
- Chrome browser: please download the script at Chrome Web Store
- Firefox browser: please download the script at GreasyFork.org -- tampermonkey or greasemonkey 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. |