|
|
| (27 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| '''MapRaid <!-- location name -->''' will begin on May 24, 2015<!--start date -->. The raid will last for roughly 2 weeks.
| | <!-- |
| ---- | | #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- |
| {{mbox |text = add image of raid area}}
| | #### This page has been curated #### |
| | | #### to be included in the new #### |
| == Welcome to the Ohio Mini-MapRaid==
| | #### Wazeopedia - GLOBAL Wiki. #### |
| | | #### Please do not make any #### |
| <!-- add a link to the local map raid thread here -->
| | #### edits on this page without #### |
| | | #### PRIOR CONSENSUS in the Wiki #### |
| == Mission ==
| | #### Updates and Discussions #### |
| | | #### forum thread for this page. #### |
| Our primary mission will be to handle the URs, and PURs, followed by Place validation, and general map verification.
| | #### If a specific forum thread #### |
| | | #### for this page doesn't exist #### |
| === Raid Areas ===
| | #### please start one. #### |
| The MapRaid! is being divided up by teams. <!-- add Google Interactive Maps link here ----->
| | #### www.waze.com/forum/ #### |
| [https://greasyfork.org/en/scripts/9729-wme-ohio-mini-mapraid-may-june-2015-overlay Mini-MapRaid Overlay]
| | #### viewforum.php?f=276 #### |
| ====Raid Groups====
| | #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> |
| <!---- add map image of raid groups ---->
| | 5 m (16 feet)<noinclude>{{documentation}}</noinclude> |
| | |
| ====PUR Areas====
| |
| <!---- add image of PUR areas if applicable ---->
| |
| | |
| ==Local Hosts==
| |
| | |
| <!-- add list of local hosts here -->
| |
| | |
| ==Important!==
| |
| <!-- add any important information pertaining to the raid here -->
| |
| | |
| ==Local Guidance==
| |
| | |
| ===Functional Classification===
| |
| | |
| <!-- status of FC implementation, if applicable -->
| |
| | |
| ===Place Editing===
| |
| | |
| <!-- describe how places will be handled during the raid -->
| |
| | |
| === 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 [[Best_map_editing_practice | current best practices]] | |
| # Validator clean through R6 | |
| #* in [[Community_Plugins,_Extensions_and_Tools#WME_Validator | 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 | |
| #* <code>Shift-Z</code> will display all disabled turns visible on screen | |
| # Junctions with U-turns enabled | |
| # Excessive geometry points removed | |
| #* Can hover and press <code>D</code> or (with Toolbox installed) press <code>1</code> to clear ''all'' geometry points from a segment | |
| # Road segments named properly | |
| #* Make sure all naming follows [[Road_names/USA | national guidance]] | |
| #* Proper [[Abbreviations_and_acronyms | abbreviations and acronyms]] | |
| #* Ohio [https://www.waze.com/forum/viewtopic.php?f=261&t=115836 name normalization] | |
| # Proper [[Creating_and_editing_road_segments#Road_elevation | elevation settings]] on segments | |
| # Junctions | |
| #* Follow all guidance in the [[Junction Style Guide]] (JSG), including [[Junction_Style_Guide/Intersections | Intersections]] and [[Junction_Style_Guide/Interchanges | Interchanges]] | |
| #* Simplify as much as possible | |
| #* Ensure geometry will provide correct turn guidance | |
| # Divided roads | |
| #* Make sure all intersections are done with [[Junction_Style_Guide/Intersections#Box_and_partial_box_intersections | box/partial box]] intersections. | |
| #* Do not use any [[Junction Style Guide/Intersections#Bow_tie | bowtie intersections]]. Replace any bowties you may find with box/partial-box. | |
| # [[At-grade_connectors | At-Grade Connectors]] (AGCs) | |
| #* Make sure they're only used when [[At-grade_connectors#Should_the_connector_be_mapped.3F | 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 [[Junction_Style_Guide/Interchanges#Ramp_geometry_and_complexity | JSG guidance]] | |
| #* 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!) | |
| # 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) | |
| # Functional Classification | |
| #* Follow [http://gis.dot.state.oh.us/tims/map ODOT] FC map for ''minimum'' classification for road | |
| #* Follow [Road_types/USA#Quick_reference_chart | Waze rules] for upgrading ''above'' ODOT guidelines | |
| #** [[Road_types/USA#Primary_Street | PS]]: frontage roads, county roads | |
| #** [[Road_types/USA#Minor_Highway | mH]]: signed, numbered state routes; BUS/LOOP/SPUR sections of US Highways | |
| #** [[Road_types/USA#Major_Highway | MH]]: US Routes, partially-limited-access roads | |
| | |
| ==Mapping Resources==
| |
| | |
| <!-- include any mapping resource links if available -->
| |
| | |
| == Communication ==
| |
| | |
| <!-- add the prefered method of communication -->
| |
| | |
| == Reference Links ==
| |
| | |
| === The Basics ===
| |
| *[[Waze Map Editor/Welcome|New editor welcome page]]
| |
| *[[Waze Map Editor]]
| |
| *[[Best Map Editing Practice]]
| |
| *[[Editing manual]]
| |
| *[[Common editing mistakes]]
| |
| *[[Permalink|How to make a Permalink]]
| |
| *[[WME Chat|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
| |
| | |
| * [http://www.google.com/url?q=http%3A%2F%2Fwiki.waze.com%2Fwiki%2FUser%3ARickzabel%2FUrComments%2F&sa=D&sntz=1&usg=AFQjCNF3YdPXqECiZuPNd9F3MqtR2xgSiQ UR Comments] - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.
| |
| | |
| | |
| * The [http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
| |
| | |
| * [http://www.waze.com/forum/viewtopic.php?t=76488 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.<br>
| |
| Download links:
| |
| * For Chrome browser please download the script at [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih Chrome Web Store]
| |
| * For Firefox browser please download the script at [http://greasyfork.org/scripts/1571-wme-validator GreasyFork.org]
| |
| ''Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.''
| |
| | |
| * [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] is a script that improves the WME chat GUI. For a list of all the features check the thread [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 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 ==
| |
| | |
| {{Mbox
| |
| | type = speculation
| |
| | text = 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.
| |
| | |
| {{mbox | |
| | type = speculation
| |
| | text = Watch here for results of promotions during and after the raid.
| |
| }} | |
| | |
| == Teams ==
| |
| | |
| {{mbox |text = add teams here}}
| |
| | |
| [[Category:Mapraid]]
| |
