User:PesachZ/SyncScratch View history

PesachZ
VisualWikitext
m (Copying text of wiki page for coparison with the "Template:Lock Standard State" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(27 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<noinclude>
<!-- ========================
{{Documentation}}
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
</noinclude>
==============================
<includeonly>{{#switch: {{uc:{{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}
This page is only viewed directly in the Major Events table on the Closures subpage.--><noinclude>[[Category:{{RootPage2}}]]
| NH
[{{fullurl:{{BasePage2}}/Closures|action{{=}}purge}} {{u|Click here to return to the {{RootPage2}}/Closures Subpage}}]<br/>
| VT
| MA
| RI
| CT
| ME
| NEW ENGLAND<!-- per Regional SM HO discussion with OrbitC on 2/11/16 https://www.waze.com/forum/viewtopic.php?f=945&t=177664&p=1328584#p1328582 -->
| NJ
| DE
| PA
| NORTHEAST = {{Locking Standard<!-- per Regional SM Hangout discussion with OrbitC https://www.waze.com/forum/viewtopic.php?f=569&t=177663 -->
    |title=Statewide
    |Fwy=5
    |Ramp=Highest rank of connected segments
    |MH=3
    |mH=3
    |PS=1 (Auto)
    |Street=1 (Auto)
    |Private=1 (Auto)
    |note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.


Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of [[Detour Prevention Mechanisms/USA|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}
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.
| NY = {{Locking Standard <!-- https://www.waze.com/forum/viewtopic.php?f=569&t=177663 -->
    |title=NYC Only
    |Fwy=5|Ramp=Highest rank of connected segment|MH=5|mH=4|PS=3|Street=1 (Auto)
    |title2=Everywhere Else
    |MH2=3|mH2=3|PS2=1 (Auto)|Street=1 (Auto)|Private=1 (Auto)
    |note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.


Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of [[Detour Prevention Mechanisms/USA|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}<!--A/p wiki-->
| TX = {{Locking Standard
  |lede=In Texas we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked '''at least''' to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower. 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.
  |title=Lock Level
  |Fwy=5
  |Ramp=4
  |MH=4
  |mH=3
  |PS=2
  |Private=2
  |Street=Automatic (1)}}


| CA = {{Locking Standard
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 (=).
  |title=Metro Areas
  |title2=Rural
  |Fwy=5
  |Ramp=5
  |MH=3
  |MH2=2
  |mH=2
  |PS=2
  |Street=1}}
| UT = {{Locking Standard <!-- Per Jemay, 2015-11-19. Temporary lowering from 54-4/3-3/2-2 to 4H322 per herrchin/AoTB/Bretmcvey 2016-06-01-->
  |caption=Utah locking standard
  |title=Statewide
  |Fwy=4
  |Ramp=Highest rank of connected segments
  |MH=3
  |mH=2
  |PS=2
  |Street=1
  |lede=In {{RootPage2}} we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked '''at least''' to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
  }}
| NV = {{Locking Standard <!-- As per State Forum discussions, SuperDave1426, 2015-01-28 -->
  |title=Urban Areas
  |title2=Rural Areas
  |Fwy=5|Fwy2=4
  |Ramp=5|Ramp2=4
  |MH=3
  |mH=2
  |PS=2
  |Street=Automatic (1)
  |Private=Automatic (1)
  |PLR=Automatic (1)
  }}
| CO = {{Locking Standard <!-- per Random sample from the map - 2015-11-25 -->
  |Fwy=5|Ramp=Highest Rank of Connected Segment|MH=3|mH=2|PS=2|Street=1}}
| NM
| SOUTHWEST = {{Locking Standard <!-- per Jemay - 2015-11-25 -->
  |Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1
  |lede=Actual locks used may be more or less than values in the table, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance.
}}
| AZ = {{Locking Standard <!-- per nnote - 2017-01-25 -->
  |Fwy=4|Ramp=4|MH=4|mH=3|PS=2|Street=1}}


==Accepted parameters:==


| MO = {{Locking Standard <!-- a/p BlueTiger68 MO SM -->
*<code>name=</code> The name of the event.
  |title=Statewide|Fwy=4|Ramp=4|MH=3|mH=3|PS=2|Street=1}}
*<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.


| KS = {{Locking Standard <!-- KC-guardrail KS SM -->
  |title=Statewide|Fwy=4|Ramp=4|MH=3|mH=3|PS=2|Street=1}}


| MN = {{Locking Standard
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 (=).  
    |title=Urban<ref>This includes any city over [http://www.city-data.com/city/Minnesota.html 6,000 people]</ref>|Fwy=5|Ramp=Highest rank of connected segments|MH=4|mH=3|PS=2<ref>Increase lock level to 3 if [[House_numbers|House Numbering]] is correct</ref>|Street=1<ref>Increase lock level to 2 if [[House_numbers|House Numbering]] is correct</ref>
    |title2=Rural<ref>This includes any area considered a township or a small town</ref>|Fwy2=5|Ramp2=Highest rank of connected segments|MH2=3|mH2=2|PS2=2|Street2=1<ref>Increase lock level to 2 if [[House_numbers|House Numbering]] is correct</ref>
|lede=In {{RootPage2}} we have a set minimum standard for [[Best_map_editing_practice#Locking_Segments|locking roads]] based on the segment type. Any road of a certain segment type must be locked to '''at least''' the [[Your_Rank_and_Points#Map_Editing_Rank|rank (level)]] in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.


A great time to implement these locks is while performing the [[Functional_Classification|FC Upgrade]] of an area. Lock the roads based on the type after they've been set to [[Road_types/USA#Quick_reference_chart|FC standards]].
}}


| WV = {{Locking Standard  <!-- 2015-07-06, stephenr1966, as discussed within state -->
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.
  |caption=West Virginia Locking Rank Standard Guideline
  |Fwy=5|Ramp=4|MH=3|mH=2|PS=1
  |lede=Actual locks used may be more or less than values in the table below, depending on area circumstance
    Please consult RC, SM, or appropriate AM for guidance
    }}
| VA = {{Locking Standard
  |caption=Virginia Locking Rank Standard Guideline
  |title=Urban|Fwy=5|MH=4|mH=3|PS=2
  |title2=Rural|MH2=3|mH2=2|PS2=1
  |lede=Actual locks used may be more or less than values in the table below, depending on area circumstance
    Please consult RC, SM, or appropriate AM for guidance
    }}
| WASHDC = {{Locking Standard
  |caption=Washington, DC Locking Rank Standard Guideline
  |Fwy=5|MH=4|mH=3|PS=2
  |lede=Actual locks used may be more or less than values in the table below, depending on area circumstance
    Please consult RC, SM, or appropriate AM for guidance
    }}
| SOUTHERN = {{Locking Standard
  |caption=Standard for locking roads in the southeast region:
  |Fwy=5|Ramp=5|MH=5|mH=4|PS=3
  |lede=
    There are some cases that do not adhere to this standard, such as military base gates (6), and any theme park type areas in Orlando (5/6).
  }}
| PR
| VI
| AS
| GUAM
| NMI
| TERRITORIES = {{Locking Standard|title=Statewide|Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1}}<!-- Per nnote, RC-->
| OK = {{Locking Standard|title=Statewide|Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=2|Street=1}}
| MD = {{Locking Standard <!-- a/p Kodi, nzahn1 SMs -->
  |title=Urban
  |title2=Rural
  |Fwy=5|Fwy2=4
  |Ramp=5|Ramp2=4
  |MH=3|MH2=2
  |mH=2
  |PS=2
  }}
| MIDATLANTIC = {{Locking Standard
  |title=Two-Way
  |Fwy=5
  |Ramp=4
  |MH=4
  |mH=3
  |PS=2
  |Street=1
  |title2=One-Way
  |PS2=3
  |Street2=2}}


| MI = {{Locking Standard
  |caption=Michigan locking standard
  |title=Urban
  |title2=Rural
  |Fwy=5
  |Ramp=Highest rank of connected segment
  |MH=3
  |mH=2|mH2=3
  |PS=2
  }}


| WI = {{Locking Standard
For example an Event row should look like this;
  |title=Statewide
  |Fwy=5|Ramp=Highest rank of connected segment|MH=3|mH=2|PS=2|Street=1
  |note=These are minimums and, for protection, certain segments may be set at higher lock levels.  In these cases, please contact the last editor or a {{RootPage2}} SM before editing the segments.  Once changes have been made and verified, the locks should be returned to their elevated levels, unless standard levels are approved by a {{RootPage2}} SM}}<!-- per GHO KB_Steveo, 2015-12-26 -->
| KY = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2
    |note=These are minimums and, for protection, certain segments may be at higher lock levels. Locks should be applied after the segments are correct. Remember you are putting your name on it, make sure it is correct.}}
| NC = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2
    |note=Certain areas may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}}
| SC = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2
    |note=Certain areas may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}} <!-- a/p crazycaveman SC SM -->
| TN = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2}}
| ND = {{Locking Standard <!-- As per bretmcvey 2016-04-26 -->
    |title=Statewide
    |Fwy=4
    |Ramp=4
    |MH=3
    |mH=3
    |PS=2
    |Street=1}}
| WY = {{Locking Standard <!-- Preliminary proposal subject to discussion and approval - TheChrisK, 2015-12-18 -->
  |title=Statewide
  |Fwy=4
  |Ramp=4
  |MH=3
  |mH=2
  |PS=2
  |Street=1
  |note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}}
| AK = {{Locking Standard
<!--per HO discussion with AlanOfTheBerg and AK state manager-->
|title=Statewide|Fwy=4|Ramp=4|MH=3|mH=2|PS=2|Street=1|PLR=2{{ref|PLR}}|append={{note|PLR|1}}This rule should primarily apply to LARGE parking lots such as shopping malls/centers/plazas, tourist attractions/sports/music venues, large office buildings and schools/colleges.}}
| OR = {{Locking Standard <!--As confirmed by AlanOfTheBerg-->
  |title=Statewide
    |Fwy=4
    |Ramp=4
    |MH=3
    |mH=2
    |PS=2
    |Street=1}}
|lede=In {{RootPage2}} we have a set minimum standard for [[Best_map_editing_practice#Locking_Segments|locking roads]] based on the segment type. Any road of a certain segment type must be locked to '''at least''' the [[Your_Rank_and_Points#Map_Editing_Rank|rank (level)]] in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.


A great time to implement these locks is while performing the [[Functional_Classification|FC Upgrade]] of an area. Lock the roads based on the type after they've been set to [[Road_types/USA#Quick_reference_chart|FC standards]].<!--A/p wiki-->
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}
| = {{Mbox|type=critical|text={{Red|Error: The Lock Standard State template requires a state/province abbreviation or other equivalent; none was supplied, so no locking scheme can be generated}}}}
 
| {{Mbox|type=critical|text={{Red|The Lock Standard State template cannot display the locking scheme because it does not recognize the state/province/region specified: {{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}}}
 
}}</includeonly>
If there are multiple editors it should look like this
 
{{Tlx|Event/Item|name=''EVENT NAME''|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 [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
 
==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}}
 
{{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}}
 
{{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}}
 
{{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}}
 
{{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}}
 
{{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}}
 
{{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}}
 
{{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}}
 
{{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 ------=====                                =====
=====                                =====
=====                                =====
----- DO NOT MODIFY BELOW THIS LINE ----->
</includeonly>

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

Retrieved from "https://beta.waze.com/wiki/Mauritius/index.php?title=User:PesachZ/SyncScratch&oldid=151586"