Ohio/Training Raids/Summer 2015

Ohio Training MapRaid #2 runs from Sunday, August 16th, 2015 at 06:00 a.m. ET (10:00 UTC) and ends on Sunday, August 30th, 2015, at 06:00 p.m. (18:00) ET (22:00 UTC).

The Ohio Training MapRaid #2 Workshops run all day on Saturday, August 15th.

---

Welcome to the Ohio Training MapRaid #2

The Ohio Training MapRaid #2 is an event to give the opportunity for newer Waze editors to train and gain experience with editing while being mentored by more experienced editors. In addition, its intent is to significantly improve an area of the Waze map.

The editors participating in the Raid are divided into non-overlapping zones, meaning each editor gets their own uncontested editing zone.

Senior editors who have volunteered to serve as mentors -- their only responsibilities are answering questions from the participants and perhaps guiding or suggesting possible edits; they will not be doing any editing in this raid.

In addition to the individual editing areas for participants in the MapRaid, there is another general area set aside for workshops, demonstrations and examples. This geographic area is outside all the individual editing areas, but adjacent to them all at the north side.

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 (I-70 corridor from Buckeye Lake in the west to just west of Norwich in the east.)

Logistics

Dates

The MapRaid will run from Sunday, 2015-08-16 until Sunday, 2015-08-30, with Training Workshops on Saturday, 2015-08-15. See above for exact times for the MapRaid.

Raid Zones

NOTES:

• Clicking on the map redirects to an interactive Google MyMaps display which helps show where the Raid ZONES are inside Ohio
• Each zone is about 123 mi²/318 km², +/- 2 mi²/5 km²

Zone Assignments

Each participant is assigned their zone.

Ohio Training MapRaid #2
Username (rank)	Assigned Zone	Comments	Zone Link
cookswim(3) [PM [Help]]	1		WME
enembee(3) [PM [Help]]	2		WME
ChieF0x(3) [PM [Help]]	3		WME
andrewohio(2) [PM [Help]]	4		WME
Solsmac(2) [PM [Help]]	5		WME
Bill473(2) [PM [Help]]	6		WME
TsuDoNihm(2) [PM [Help]]	7		WME
TNT1001(2) [PM [Help]]	8		WME
UnassumingLocalGuy(2) [PM [Help]]	9		WME
sman28(2) [PM [Help]]	10		WME

Supporting Editors

The following editors are helping organize the event and/or answer questions for the participants, but are NOT editing as part of this Raid.

Local Hosts + Mentors
Username (rank)	Comments	Roles
GizmoGuy411(6) [PM [Help]]	Regional Coordinator (Great Lakes), Global Champ Mentor, CM (Multiple)
SkiDooGuy(6) [PM [Help]]	Local Champ Mentor (US), CM (US, Canada, Palau), SM (MI, ME)
TerryPurdue(5) [PM [Help]]	SM (OH), Mentor
ohiostmusicman(5) [PM [Help]]	SM (OH), Mentor
Helgramite(5) [PM [Help]]	SM (OH), Mentor
DaveKS14(4) [PM [Help]]	AM (OH), Large-Area Manager - Host
EdFromOhio(4) [PM [Help]]	AM (OH), Large-Area Manager
gunnargsd(4) [PM [Help]]	AM (OH), Large-Area Manager
JustinS83(4) [PM [Help]]	AM (OH), Large-Area Manager
Bruce1224(4) [PM [Help]]	AM (OH)
tango259(3) [PM [Help]]	AM (OH)
Even More Mentors
Username (rank)	Comments	Roles
orbitc(6) [PM [Help]]	Regional Coordinator (New England, Northeast), Global Champ Mentor, CM (Multiple)
xanderb(5) [PM [Help]]	SM (KY)
roadtechie(4) [PM [Help]]	SM (WV)
stephenr1966(4) [PM [Help]]	SM (WV)

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 R5+ Advisor 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 zone 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.

Zones

Zones may be located and identified from the Zone Assignments table, above.

Editing Criteria

The following is a list of improvements that all editors should attempt to make across the entire Raid zone, 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 restrictions
   • 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 zone
    • 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 installations 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
23. County Roads identified, marked (CR-xxx, "CH-" is not correct for any counties included in this Raid!) and classified (minimum Primary Street) appropriately leveraging ODOT Local Road Inventory

Communication

All communication for the Raid will take place in Google Hangouts that were created specifically for this effort.

Mapping Resources

• Directory of all county Auditors Offices

Counties

• Map of all Ohio counties
• Belmont
  • Auditor
  • GIS (needs site added to Java Exception List, and installation of other plugins -- did not get it working, but with more time may be possible)
• Carroll
  • Auditor
  • GIS
• Coshocton
  • Auditor
  • GIS
• Guernsey
  • Auditor
  • GIS
• Harrison
  • Auditor
  • GIS
• Holmes
  • Auditor
  • GIS (Requires MSIE + MS Silverlight)
• Monroe
  • Auditor
  • GIS
  • JPG Maps
  • Tax Map Dept
• Morgan
  • Auditor
  • GIS
• Muskingum
  • Auditor
  • GIS
• Noble
  • Auditor
  • GIS
• Stark
  • Auditor
  • GIS
• Tuscarawas
  • Auditor
  • County
  • GIS
• Washington
  • Auditor
  • GIS

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

• Raid Overlay - Shows boundaries for each of the Raid zones inside WME editor (requires Tampermonkey/Greasemonkey)
• 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.
  
  • Chrome: please download Validator at Chrome Web Store
  • Firefox: please download Validator at GreasyFork.org
    • Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.

• Ohio localizations for Validator (requires Greasemonkey/TamperMonkey)
  • Note that issues highlighted by this script are a core component of the grading criteria!

• Ohio Counties Overlay (requires Greasemonkey/TamperMonkey)

• WME Color Highlights (WMECH) - colors segments as indicated by user selections
• Junction Angle Info (JAI) -- shows you the number of degrees between segments, crucial for ensuring correct turn guidance
• WME Toolbox (WMETB or TB) - allows users to do more repetitive edit tasks with the click of a button

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.

Workshops

The organizers are putting together workshops before the raid to focus on specific issues that participants will need to understand to successfully complete all grading criteria.

Some previously-offered workshops are available in Google HangOut archives:

1. County Roads
2. Freeways
3. Functional Classification
4. Wayfinders

PM TerryPurdue for access to these workshops archived in Google HangOuts.

Suggestions

The team is very interested in suggestions of things to consider doing differently in future raids. Feel free to add (not remove!) any ideas/constructive criticism to the Suggestion Box, or PM/direct GHO entries to TerryPurdue who will add them for you.