User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "West Virginia/WV MapRaid" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(283 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<!-----{{mbox|text='''West Virginia MapRaid''', 16 days: 03/08/2017 - 04/02/2017. USA editors (at all ranks!) are invited to join an effort to improve the WV map and interact with other editors, experienced editors, and Waze Champs.}}----->
<!-- ========================
{{mbox|text=The WV MapRaid Wiki is a work in progress; subject to change as necessary due to changes in Waze guidance or Raid Goals}}
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
==============================
This page is only viewed directly in the Major Events table on the Closures subpage.--><noinclude>[[Category:{{RootPage2}}]]
[{{fullurl:{{BasePage2}}/Closures|action{{=}}purge}} {{u|Click here to return to the {{RootPage2}}/Closures Subpage}}]<br/>


=== Welcome to Wild, Wonderful West Virginia ===
These rows fill the major Event table, and are modified using the template {{tl|Event/Item}}. If you are working on a Major Event in {{RootPage2}}, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the <code>updated=</code> parameter.
[[File:USA West Virginia.png|300px|thumbnail|right]]
<!-----Insert Text about WV to give a back story----------->
Despite its relatively small size (24,000 square miles), the Mountain State is home to over 3,000 communities; approximately 450 of those are incorporated cities and towns. To link them (and to provide an important part of the transportation of the state’s abundant natural resources), there are some 39,000 miles of public roads, of which the State of WV maintains 35,000 miles (90%) of those roads. Included amongst these roads are 468 miles of Interstate Routes, 88 miles of the WV Turnpike, 835 miles of Federal Roadways, and 7,000 bridges (most less than 100 feet in length).


===Sign Up===
If you would like to participate in the WV Map Raid, review the goals and resources below. Then, please [http://docs.google.com/forms/d/e/1FAIpQLSc_jkVtSxUfBiQRcLNgiwdjYT-782t3C99eF8zVEq_nzs6OpA/viewform '''CLICK HERE'''] to go to the Signup Page and get an invitation to the WV MAP RAID. Sign up will be open until Friday 03/03/2017


=== Map Raid Goals ===
This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically  the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).


The primary goal of the '''WV Map Raid''' is to review and connect basemap roads as well as update and review existing confirmed roads. Secondary goals are to review and edit all places and to resolve URs/PURs/MPs. If you are unsure if the items are completed, please contact a [[#WV Leadership | WV State Manager]] or your [[#Raid Groups | Group Leader]].
==Accepted parameters:==


We would like to perform these goals in the following order:
*<code>name=</code> The name of the event.
*<code>area=</code> The county or are the event takes place in.
*<code>date=</code> The estimated date(s) this event happens on.
*<code>road=</code> The main road(s) affected by this event.
*<code>pl=</code> A [[permalink]] to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
*<code>source=</code> A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
*<code>status=</code> Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
**<code>not submitted</code> produces a red background
**<code>submitted</code> produces a light green background
**<code>in progress</code> produces an orange background.
*Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
*<code>updated=</code> the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


# Base Map / Connectivity
#*Please review the [[Basemap|Basemap Wiki]] for steps to, and a guide for, editing basemap
#*#In addition to the steps in the Basemap wiki, please pay special attention to the following:
#*#*Look for and correct other state names on segments (OH/VA/KY/PA/MD)
#*#*Add Speed Limits (SL)
# Remove names and adjust Railroad (RR) segments (elevation/junctions/etc). Leave the name on "Cass Scenic Railroad" and "WVU PRT".
<!-----* Remove/Add/Update PLR or PR (and driveways) per [[Road_types/USA#Other_drivable_roads|National Wiki Guidance]] as necessary for routing----->
# Use the [http://w-tools.org/PlaceBrowser?group=MapRaidWestVirginia WV Place Browser] to review and fix all places.
#*If/when you Add/Update any Fire Stations, [http://docs.google.com/spreadsheets/d/1CAKvxB3J8-P9W7Ru3FEj6jP9iO75mhwnrkbMEzFOynY/edit?ts=582f3dc8#gid=0 Add your Editor Name/Permalink/Any Comments here]
# Resolve User Reports (UR), Place Update Requests (PUR) and Map Problems (MP)


=== Raid Areas ===
The updated parameter (<code>|updated=YY/MM(/DD)|</code>) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).
{{mbox
| type      = speculation
| text      = Once sign up is complete Areas will be released.
}}
<!-----Insert raid area pictures/definitions here---------->


=== Raid Groups ===
{{mbox
| type      = speculation
| text      = Once sign up is complete Groups will be released.
}}
<!-----Insert raid groups here----------------------------->


=== WV Leadership ===
The <code>|date=|</code>, and <code>|updated=|</code> parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.
<!-----Insert Leadership info here------------------------->


{{username|stephenr1966}} - [http://plus.google.com/+StephenRimbey/about GHO: Stephen] - Local Champ, USA CM, WV SM


{{username|roadtechie}} - [http://plus.google.com/+ToddRoadtechie/about GHO: Todd-roadtechie] - USA CM, WV SM
For example an Event row should look like this;


{{username|markr4468}} - [http://plus.google.com/u/0/107083213002975349432 GHO: Mark] - WV SM, OH LAM
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


=== Important! ===
'''Please do not alter any of the following road ''types'' without first consulting a [[#WV Leadership | WV State Manager]] or your [[#Raid Groups | Group Leader]]''': Freeways, Ramps, Major Highways, Minor Highways or Primary Streets.


'''Please do not mass-edit''' Do not perform edits which will affect large numbers of segments at once. The edit history of segments is highly valuable in the process of solving URs. Mass editing effectively mass erases this history, permanently. We ask that all necessary processes which might affect large portions of the map, or long stretches of roads, be reserved until near the end of the MapRaid. This includes the “Select entire street” function.
If there are multiple editors it should look like this


'''Anything locked at 5?''' Please check with a [[#WV Leadership | WV State Manager]] or your [[#Raid Groups | Group Leader]] before making changes. Rank 5 and 6 editors - consider keeping highlights active for locks.
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}


'''West Virginia uses the concept of True Elevation on segments within the State.''' The use of True Elevation (TE) is to better represent segments in relationship with its surroundings/ground level. For more information please review the [[West_Virginia#True_Elevation|WV True Elevation Guidance]] page.


<!-----'''[[Junction Style Guide/Intersections|Micro Dogleg/Close nodes]]''' We make extensive use of the "micro-dogleg" technique, where a geometry node is carefully placed, at full zoom, directly next to a junction node, in order to set the angle to create a desired Turn/Stay/Exit prompt. Please watch for these if you move any junction node, and be sure to recreate the same angle at the new location.----->
'''Please refer to the [[Turn Instruction Overrides/USA|Turn Instruction Overrides]] National Guidance''' if you believe that a turn instruction override is warranted. Let us be clear we do not want anyone to go out and look for Micro-Doglegs to change into TIO's. BUT we do not want to create any NEW Micro-Doglegs. If you have any questions please contact your [[#Raid Groups | Group Leader]].


==Local Guidance==
'''Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box.'''
————————————————————————————————————


=== WV Route Naming ===
West Virginia uses the WV-XXX format for all State Routes. For County Routes, CR-XX or CR-XX/YY is used. There are no Township Roads (TR-XXX) in West Virginia. In a few limited cases, there are special road names in use; if you see one, please do not delete it or ask a question first prior to deleting it. More detail and examples can be found here:  [[West_Virginia/Major_roads|WV Route Naming]].




=== Functional Classification ===
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''


'''Functional Classification Will Not Be Part Of This Raid.'''
==TO EDIT THIS TABLE CLICK HERE >> ==
</noinclude><includeonly><!--
------ DO NOT MODIFY ABOVE THIS LINE -----
======                              ======
======                              ======
======                              ======
====== DO NOT MODIFY ABOVE THIS LINE ====-->
{{Event/Item|name=New Years Celebration|area=NYC|road=Times Sq/Coney Island|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1716991474|date=12/31-01/01 annual|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}


{{Event/Item|name=NYC 1/2 Marathon & St. Patricks' Day Parade|date=03 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=339510355|area=NYC|road=5 Boroughs|status=submitted|updated=2017/02/09|Rfrsw101|jdelosa|johnsninja58|PesachZ}}


=== MAR Minimum Road Lock Standard ===
{{Event/Item|name=July 4th Celebration|area=NYC|status=submitted|updated=2017/02/12|Rfrsw101|jdelosa|johnsninja58|PesachZ|road=FDR Dr|date=07/04 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1864894199|source=http://www.nyc.gov/html/dot/html/motorist/wkndtraf.shtml}}
{| class="wikitable" style="text-align:center"
!colspan="3" style="background-color:#6699cc"|Minimum Road Lock Standard
|-
|style="font-weight:bold; background-color:#ccffcc"|Segment Type
|style="font-weight:bold; background-color:#ccffcc"|Direction
|style="font-weight:bold; background-color:#ccffcc"|Lock
|-
|{{Freeway|Freeway}}
|
|5
|-
|{{Ramp|Ramp}}
|
|4
|-
|{{Major Highway|Major Highway}}
|
|4
|-
|{{Minor Highway|Minor Highway}}
|
|3
|-
|rowspan="2"|{{Primary Street|Primary Street}}
|One-way
|3
|-
|Two-way
|2
|-
|rowspan="2"|{{Street|Street}}<br>{{Private Road|Private Road}}
|One-way
|2
|-
|Two-way
|1
|-
|{{Railroad|Railroad}}
|
|2
|-
|{{Ferry|Ferry}}
|
|3
|-
|{{Runway|Runway}}
|
|4
|-
|Other Named Types
|
|5
|}


{{Event/Item|name=Summer Streets|road=Park Ave|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1984749524|source=http://www.nyc.gov/html/dot/summerstreets/html/home/home.shtml|date=08 First 3 Sundays|area=NYC|status=submitted|updated=2017/02/10|Rfrsw101|jdelosa|johnsninja58|PesachZ}}


Note that these are minimums and, for protection, certain segments may be at higher lock levels. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.
{{Event/Item|name=West Indian Day Parade|date=09 Labor Day annual|area=Kings|road=Eastern Pkwy, Classon-Rochester St Johns-Empire|source=http://maps.nyc.gov/streetclosure/|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1605830763|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/10}}


=== West Virginia User Report Management ===
{{Event/Item|name=TD 5 Boro Bike Tour|area=NYC|date=05 First Sunday annual|road=5 Boroughs|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=790135118|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}


West Virginia has a very good grasp on User Reports/Map Problems throughout the state. This will not be a "''primary focus''" of the raid, but please feel free to work any UR/PUR/MP's in your editable area. Remember to follow the Response Timeline guidelines below.  
{{Event/Item|name=NYC TCS Marathon|area=NYC|date=11 First Weekend annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=0|road=5 Boroughs|source=http://www.tcsnycmarathon.org/race-day/course|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/07}}


====Response Timeline====
{{Event/Item|name=UN General Assembly|area=NYC|road=East Midtown|date=09 Last Two Weeks Annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1895099030|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
''(NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter)''


'''Day 0'''
{{Event/Item|name=Macy's Thanksgiving Day Parade|area=NYC|road=Herald Square|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1774745119|date=11 Last Thursday Annual|source=http://social.macys.com/parade/#route|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}


The first editor who is able to respond to a User Report (UR) should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it '''"Solved'''". If more information from the reporter is required to make progress towards closure, a response should be sent to the reporter containing the information needed for resolution.
{{Event/Item|name=Chinese New Year Parades|date=01 or 02 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1190958434|area=NYC|road=Chinatown/8th Avenue/Flushing|status=submitted|updated=2017/02/08|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
 
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
'''Day 4+'''
=====                               =====
 
=====                               =====
Polite reminders should be sent to reporters who have not responded to the initial request for information at any time, '''provided at least four full days have elapsed''' since the initial response was sent
----- DO NOT MODIFY BELOW THIS LINE ----->
 
</includeonly>
'''Day 8+'''
 
URs may be noted as closed due to lack of reporter response at any time, '''provided at least four full days have elapsed''' since the followup message was sent. These need to be marked as '''"Not Identified"''' and a brief comment sent.
 
'''Shared Ownership'''
 
All editors are considered to have equal ownership of and responsibility for all URs in West Virginia. All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere to the minimum time spacing guidance between responses. All editors are explicitly encouraged to attempt to resolve URs at any point during their lifecycle, even if others happen to be actively working it at the same time.
 
'''Notes'''
 
The script [[Scripts#URComments|URComments]] streamlines the process of responding to a UR and provides comments based on the UR type and can be edited prior to sending to fit your needs. Highly recommend you install this script if you will be responding to URs.
 
=== Cameras ===
'''Cameras will not be mapped'''
 
[http://www.legis.state.wv.us/WVCODE/ChapterEntire.cfm?chap=17c&art=6&section=7A#06 §17C-6-7a] of the West Virginia Code prohibits use of cameras to detect or prove traffic law violations. You can remove all Red Light or Speed Cameras in WV. 
 
=== Place Editing ===
West Virginia follows the national [[Places]] guidance.
 
For specific WV naming standards please review the [[West_Virginia#Naming_Standards|WV Naming Standards]]
 
To prevent loss of data due to automatic acceptance of submissions from "trusted users", all area places and points with complete data should be locked to Level 2 at a minimum.
Additionally, please consult the following table for minimum lock level for completed places.
 
{| border="1" cellpadding="2" style="text-align:center;"
!|Place Type
!|Minimum Lock Level
|-
||Area/Point Places ||2
|-
||Gas Stations ||3
|-
||Hospital/Medical Care ||4
|-
||Fire Department ||4
|-
||Police Station ||4
|-
||Airports ||4
|-
||Parking Lot Area (PLA) ||3
|}
<br />
 
<!-----What are we putting here? Do we need it
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/1dIU3dOUsyUoo6OievX58i01GV02ttcT9YWHbY45joEE/pubhtml?gid=206688714&single=true&amp;single=true&amp;widget=true&amp;headers=false
|width=100%
|height=500
|border=0
}}
----->
 
== Mapping Resources ==
 
=== West Virginia Maps ===
 
<!-----Only need this link:------->
 
[http://www.transportation.wv.gov/highways/programplanning/gti/GIS/MAPS/Pages/WVMapGISSelect.aspx WVDOT County Maps]
 
=== West Virginia GIS Resources ===
<!-----Insert GIS resources here----->
We highly recommend that you install the [http://greasyfork.org/en/scripts/21228-wme-gis WME GIS script]. This script will make it a lot easier to access the multiple GIS websites.
 
If you do not wish to install this script please visit the [[West_Virginia/Cities_and_towns|West Virginia Cities and Towns]] page for all GIS links. '''NOTE''':Not all WV counties have GIS links. Only hyperlinked county names are linked to the County GIS. City/Town names are hyperlinked to the WME Permalink. If you get confused digging through all of the different GIS sites, which will probably happen (it has to all of us), please contact your [[#Raid Groups | Group Leader]] or a [[#WV Leadership | WV State Manager]] for guidance
 
== Reference Links ==
 
=== West Virginia Wiki Page ===
If you have any questions regarding WV standards during editing and you cannot find the answer on this page, please visit the [[West_Virginia|West Virginia Wiki Page]].
 
=== West Virginia Map Raid Forum ===
<!-----Create Forum and add link here----->
 
=== New Editors ===
If you are new or relatively new to map editing, please [[West_Virginia/Resources|CLICK HERE]] for some tips to get started; including settings, options, scripts, Wiki References, and instructions on lock requests and how to create a Permalink (PL). You do not need to join the WV GHO, you will be given an invitation to map raid specific GHOs.
 
=== Basic US Wiki Links ===
*[[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]]
*[[Community Plugins, Extensions and Tools]].
 
=== Recommended Tools for MR West Virginia ===
<!-----What do we want in here?----->
New editors should be aware there are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct.  The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.
 
 
'''Toolbox'''
 
* [http://chrome.google.com/webstore/detail/wme-toolbox/ihebciailciabdiknfomleeccodkdejn?hl=en For Chrome]
* [http://gitlab.com/doctorkb/wme-toolbox-public/raw/master/Dist/Firefox/wmetoolbox.xpi For Firefox]
 
After Toolbox is installed it will add several things to the WME editor.  At the top next to the Places Icon will be a picture of a toolbox.
If you hover your mouse over it, a menu should open.  Select the following options:
 
[[File:Ron-Toolbox-settings.jpg]]
 
 
'''TamperMonkey / GreaseMonkey'''
 
The most common and supported browser is Chrome with Firefox a close second. Install the appropriate one for your browser. This is needed to install other scripts.
 
* [http://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo?hl=en TamperMonkey (Chrome)]
* [http://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ GreaseMonkey (Firefox)]
 
 
'''Other Recommended Scripts'''
 
# If you are working on User Reports (UR), install [http://www.waze.com/forum/viewtopic.php?f=819&t=122776 UrComments] . UR Comments is a script designed to streamline the process of responding to Update Requests. It can autofill the comment box based on UR type, or you can manually choose from the list of responses, depending on your preference.
# If you are working on places, install [http://www.waze.com/forum/viewtopic.php?f=819&t=133650&start=60#p1548089 WME Closest Segment] . It helps you determine the closest segment to the navigation stop point of a place. A line is drawn from a selected place (for point places) or its navigation point (for area places) to the nearest segment.
# [http://www.waze.com/forum/viewtopic.php?f=819&t=61926&start=50#p735439 WME Junction Angle Info] . This script helps with junction maintenance. If two connected segments are selected, it shows the turn angle, and estimates navigation instructions. Otherwise it shows the the angle between each segment.
# [http://greasyfork.org/en/scripts/18089-wme-simple-permalink-from-wme-keepmylayers WME Simple Permalink]. Shortens WME permalinks by removing any layer and filter specifications.
# [http://github.com/WazeUSA/WME-Place-Harmonizer/raw/master/WME-Place-Harmonizer.user.js Place Harmonizer (WMEPH)]. Harmonizes, formats and locks a selected place. Also for Chains, please Submit New Chain Data for any that are not in the database. '''NOTE: Now Available for all editors, including R1!'''
# [http://greasyfork.org/en/scripts/25631-wme-us-government-boundaries WME US Government Boundaries] is a script by '''MapOMatic''' that will display USPS Zip Code Boundaries on the map.
# [http://greasyfork.org/en/scripts/26683-wme-wv-scripts WV Scripts] Allows you to toggle the  County, City, Town, and Census Designated Place (CDP) in the Waze Map Editor (WME) (original script by Rickzabel). Also the WV Validator Localization File (original script by XanderB). And links to WV Forum, MAR Forum and WV Wiki Pages. Script by '''JustinS83''' with many thanks!
# When working with House Numbers (HN), please use this script by '''JustinS83'''. It highlights un-nudged house numbers. [http://greasyfork.org/en/scripts/21779-wme-hn-tool-justins83-fork WME HN Tool (JustinS83 fork)]
# [http://greasyfork.org/en/scripts/19941-waze-edit-count-monitor Edit Count Monitor] will add a counter to the top "blue" bar. This script will show you how many edits you have and will also turn Yellow for a warning, and Red to alert you if you are being throttled.
 
== Results ==
 
{{mbox
| type      = speculation
| text      = Watch here for results of the Raid.
}}
 
== 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.
}}

Latest revision as of 05:15, 19 February 2017

Click here to return to the PesachZ/Closures Subpage

These rows fill the major Event table, and are modified using the template {{Event/Item}}. If you are working on a Major Event in PesachZ, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the updated= parameter.


This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).

Accepted parameters:

  • name= The name of the event.
  • area= The county or are the event takes place in.
  • date= The estimated date(s) this event happens on.
  • road= The main road(s) affected by this event.
  • pl= A permalink to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
  • source= A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
  • status= Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
    • not submitted produces a red background
    • submitted produces a light green background
    • in progress produces an orange background.
  • Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
  • updated= the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


The updated parameter (|updated=YY/MM(/DD)|) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


The |date=|, and |updated=| parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


For example an Event row should look like this;

{{Event/Item|date=14/10|in progress|username|updated=14/08}}


If there are multiple editors it should look like this

{{Event/Item|date=14/10|in progress|username1|username2|updated=14/08}}


Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box. ————————————————————————————————————


The actual contents of this page will only be visible in the Major Events table, or when editing this page.

TO EDIT THIS TABLE CLICK HERE >>