Ohio/minimapraid

MapRaid Ohio will begin on May 24, 2015. The raid will last for roughly 2 weeks.

---

Welcome to the Ohio Mini-MapRaid

Mission

This raid has two primary goals:

1. Introduce newer editors to the fundamental skills required to (eventually) become an Area_Manager
2. Improve the map in a historically-neglected portion of Ohio

Logistics

Raid Areas

The MapRaid! is being divided up by teams.

Raid Groups

Local Hosts

• GizmoGuy411 (PM) - Regional Coordinator (Great Lakes Region), R6 Global Champ
• SkiDooGuy (PM) - R6 Local Champ (US), Country Manager (US, Canada, Palau), State Manager (MI, ME)
• TerryPurdue (PM) - R5 State Manager (OH)
• ohiostmusicman (PM) - R5 State Manager (OH)

Important!

Local Guidance

Functional Classification

Unlike some of the previous raids, almost NONE of the map in this raid will have been properly classified.

1. Follow ODOT FC map for minimum classification for road
   • Local (Black_: Street
   • Collector (Yellow/Pink): Primary Street
   • Minor Arterial (Green): Minor Highway
   • Principal Arterial (Red): Major Highway
   • Other Freeway and Expressway (Brown):
     • Fully controlled-access: Freeway (may require dividing road -- Contact Raid Mentor before attempting!)
     • Otherwise: Major Highway
   • Interstate (Blue): Freeway
2. Follow Waze rules for upgrading above ODOT guidelines
   • Primary Street: frontage roads, county roads
   • Minor Highway: signed, numbered state routes; BUS/LOOP/SPUR sections of US Highways
   • Major Highway: US Routes, partially-limited-access roads
3. Local expertise/editor judgement: if you feel that a road/highway is still underclassified after applying the previous rules, please contact a Raid mentor and make a case for further upgrades

Lock Levels

Ohio is using a version of the still-developing Great Lakes regional standard for locks

• "Standard" segments
  • Freeways: L5
  • Ramps: Highest Connected Segment (HCS)
  • Major Highway (MH): L3
  • Minor Highway (mH): L3
  • Primary Street (PS): L2
  • Street/PLR/private: L1
• Special cases
  • 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)

Place Editing

Grading

Each editor will have a specific area that the Raid organizers will be "grading." This will be used as part of the decision about which participants are selected to participate in the subsequent raids in the series.

Areas

• Area 1W
• Area 1E
• Area 2W
• Area 2E
• Area 3W
• Area 3E
• Area 4W
• Area 3E
• Area 5W
• Area 5E
• Area 6W
• Area 6E
• Area 7

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."

1. Make sure all edits are in accordance with current best practices
2. WME Validator clean through R6
   • Mentors will be available to downlock as needed
   • Remove check for "Exclude non-editable segments"
   • Make sure to fix all issues flagged by the Ohio Localizations plugin as part of this task!
   • Make sure all extraneous junction nodes are removed
   • Unknown direction roads, unconfirmed roads, etc. fixed
3. User Reports (URs) and Place Update Reports (PURs) either closed or actively being worked
4. Fix any junctions with unconfirmed turns
5. Check for any improper turn restrictions0
   • Shift-Z will display all disabled turns visible on screen
6. Junctions with U-turns enabled
7. Excessive geometry points removed
   • Can hover and press D or (with Toolbox installed) press 1 to clear all geometry points from a segment
8. Road segments named properly
   • Make sure all naming follows national guidance
   • Proper abbreviations and acronyms
   • Ohio name normalization
9. Proper elevation settings on segments
10. 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
11. 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.
12. At-Grade Connectors (AGCs)
    • Make sure they're only used when needed/justified!
    • Proper naming, geometry for turn guidance, etc.
13. 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
    • Note that all editors are expected to fix all freeway segments in their area
    • Ramps are named correctly
14. Place objects set with correct type (area vs point), categories, and addresses (including street/street number!)
15. House numbers added (within reason, not every single structure needs a house number!)
16. All segments should be set to their MINIMUM lock level (higher if justified, check with mentors)
17. Functional Classification: make sure all rules from the Functional Classification section have been correctly applied
18. Rest areas drawn correctly (segment types, place objects, etc.)
19. Private areas identified, marked with private roads
    • Things to look for: gates, non-standard speed limit signs in Street View
20. All gas stations identified and mapped correctly -- including street address!
21. Only those driveways that meet the criteria are mapped
22. Special care is spent identifying and correctly mapping hospitals/urgent care facilities

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 script - Shows boundaries for each of the thirteen Raid areas inside WME editor
• 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