TerryPurdue (talk | contribs) |
TerryPurdue (talk | contribs) |
||
Line 72: | Line 72: | ||
#* Ramps are [[Road_names/USA#Exit_ramps_and_Entrance_ramps_.28on-ramps.29 | named correctly]] | #* Ramps are [[Road_names/USA#Exit_ramps_and_Entrance_ramps_.28on-ramps.29 | named correctly]] | ||
# [[Places | Place objects]] set with correct type (area vs point), categories, and addresses (including street/street number!) | # [[Places | Place objects]] set with correct type (area vs point), categories, and addresses (including street/street number!) | ||
# [[House_Numbers_in_WME | House numbers]] added (within reason, not every single structure needs a house number!) | |||
# All segments should be set to their MINIMUM lock level (higher if justified, check with mentors) | # All segments should be set to their MINIMUM lock level (higher if justified, check with mentors) | ||
#* Street/PLR/private: L1 | #* Street/PLR/private: L1 |
Revision as of 16:31, 16 May 2015
MapRaid will begin on May 24, 2015. The raid will last for roughly 2 weeks.
add image of raid area |
Welcome to the Ohio Mini-MapRaid
Mission
Our primary mission will be to handle the URs, and PURs, followed by Place validation, and general map verification.
Raid Areas
The MapRaid! is being divided up by teams. Mini-MapRaid Overlay
Raid Groups
PUR Areas
Local Hosts
Important!
Local Guidance
Functional Classification
Place Editing
Grading Criteria
The following is a list of improvements that all editors should attempt to make across the entire Raid area, but especially at the "Grading PL."
- Make sure all edits are in accordance with current best practices
- Validator clean through R6
- in WME Validator, remove check for "Exclude non-editable segments"
- Mentors will be available to downlock as needed
- User Reports (URs) and Place Update Reports (PURs) either closed or actively being worked
- Fix any junctions with unconfirmed turns
- Check for any improper turn restrictions
Shift-Z
will display all disabled turns visible on screen
- Junctions with U-turns enabled
- Excessive geometry points removed
- Can hover and press
D
or (with Toolbox installed) press1
to clear all geometry points from a segment
- Can hover and press
- Road segments named properly
- Make sure all naming follows national guidance
- Proper abbreviations and acronyms
- Ohio name normalization
- Proper elevation settings on segments
- Junctions
- Follow all guidance in the Junction Style Guide (JSG), including Intersections and Interchanges
- Simplify as much as possible
- Ensure geometry will provide correct turn guidance
- Divided roads
- Make sure all intersections are done with box/partial box intersections.
- Do not use any bowtie intersections. Replace any bowties you may find with box/partial-box.
- At-Grade Connectors (AGCs)
- Make sure they're only used when needed/justified!
- Proper naming, geometry for turn guidance, etc.
- Freeways
- In Ohio only, freeway segments (and all ramps that connect to freeways) should always be set to "No City" (check with Mentors for explanation)
- Ramps meet JSG guidance
- Ramps are named correctly
- Place objects set with correct type (area vs point), categories, and addresses (including street/street number!)
- House numbers added (within reason, not every single structure needs a house number!)
- All segments should be set to their MINIMUM lock level (higher if justified, check with mentors)
- Street/PLR/private: L1
- Primary Street (PS): L2
- Minor Highway (mH): L3
- Major Highway (MH): L3
- Freeways: L5
- Ramps: Highest Connected Segment (HCS)
- At-Grade Connectors: Highest Connected Segment (HCS)
- One-way segments: increase lock minimum by one (e.g., one-way PS should be locked to L3)
- Functional Classification
- Follow ODOT FC map for minimum classification for road
- Follow Waze rules for upgrading above ODOT guidelines
- Rest areas drawn correctly (segment types, place objects, etc.)
- Private areas identified, marked with private roads
- Things to look for: gates, non-standard speed limit signs in Street View
- All gas stations identified and mapped correctly -- including street address!
Mapping Resources
Communication
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.
- 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
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 |