User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Virginia/Major roads/Main" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(564 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
<!-- ========================
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
:''For further information, see [[Road names/USA]], [[Road types/USA]] and [[Virginia/Resources]].''
==============================
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/>


:''The following is intended for Virginia Specific roadways. For further information about Interstates and US Highways and other non-Virginia roadways, see [[Road names/USA]], [[Road types/USA]] and [[Virginia/Resources]].''
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.
<gallery>
File:Virginia 28.png|Primary route marker
File:VA_613.PNG|Secondary route marker
</gallery>
===Naming===
Virginia folows the [[Road Names (USA) | road naming guidelines of the USA]]. The local name of a road should always be set as the primary name and the route number should be set as an alternate name; there are very few state routes in Virginia that do not have a local name.


'''Primary state routes''' have numbers in the range of 2 to 599 (and, as exceptions, [http://en.wikipedia.org/wiki/Interstate_785 785], [http://en.wikipedia.org/wiki/Virginia_State_Route_895 895]), displayed in a route marker using a shield design.  Using the example above, the road should be named '''SR-28'''.


'''Secondary state routes''' are those with route numbers 600 or greater; if these roads have route markers (many do not), they use a circle design or a small rectangle instead of a shield. Using the example above, the road should be named '''VA-613'''.
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 (=).


'''Frontage roads''' are roads run parallel to a higher-speed, limited-access road. A frontage road is often used to provide access to private driveways, industries, farms, etc.. A list of these roads can be found [http://www.vahighways.com/route-log/fseries.htm here.] They should be named '''F-###'''
==Accepted parameters:==


'''Town Roads''' or T-Roads are roads that are maintained by incorporated towns on an optional basis. They should be named '''T-###'''
*<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.


===Road typing===
Virginia follows the [[Road Types (USA) | national guidelines for road types]].
VDOT Functional Classification
The VDOT Functional Classification Maps have been approved for setting road type in WME based on the quick reference chart and other considerations listed below.The functional classifications are available via an interactive map that can be found [http://www.arcgis.com/home/webmap/viewer.html?webmap=3eca6c9adb6649c988d98734f85baddb here]. Alternatively, [http://arcg.is/1FxkS9x maps] have been made to match WME colors.


'''NEW Script''' to help for '''Functional Classification''' -  This should be considered as a tool to help in functional classification.   There are some problems with incorrect FC; some are caused by bad VDOT data, some are by conflicting rules.  Please make sure to use other resources including street signs in recent SV shots (cross streets may be more current) and other FC resources.  This script is currently available for R3+ editors who have Area Manager roles.  (If interested in an AM position please contact one of your State Managers).  Link to script is [https://greasyfork.org/en/scripts/21944-wme-fc-layer-beta here]. Thanks to MapoMagic for developing this script.  
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 (=).  


[[File:VA_FC.png|center]]


For purposes of applying the US road type guidelines, we treat only primary state routes as "numbered state highways." Primary state routes must be designated as at least [[Road Types (USA) #Minor_Highway|{{Minor Highway}}]] in Waze, unless the road's functional classification requires a higher designation. (For example, primary routes '''785''' and '''895''' are road typed to reflect their future designation as freeway.)
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.


'''Exception''': Primary routes that solely access state facilities (parks, educational/correctional institutions, etc.) should be given a road type that matches the FC maps published by VDOT, even if that is less than Minor Highway. Many, but not all of the routes that service state institutions are '''SR-3##'''; a non-exhaustive list can be found [http://en.wikipedia.org/wiki/State_highways_serving_Virginia_state_institutions here.]


Secondary state routes, frontage roads, and town roads are always typed based solely on the FC maps
For example an Event row should look like this;


Consult the [[Road Types (USA)]] page for further guidance on how to type based on functional class and road signage.
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


===Locking===
In Virginia 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.
A great time to implement these locks is while bringing the road types of an area into compliance with the current [[Road Types (USA) | US road type standards.]] Lock the roads based on type after they've been set to current US road type standards and connecting roads are set up correctly and all other edits are complete for the segment.


;Minimum Locking Standard
If there are multiple editors it should look like this


Actual locks used may be more than the table below, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}


{| border="1" style="border-collapse:collapse;margin: 1em auto 1em auto; text-align:center"
 
|+ '''Locking Levels'''
 
|-
'''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.'''
| {{Freeway}}||5
————————————————————————————————————
|-
 
| {{Ramp}}||4
 
|-
 
| {{Major Highway}}||4
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
|-  
 
| {{Minor Highway}}||3
==TO EDIT THIS TABLE CLICK HERE >> ==
|-
</noinclude><includeonly><!--
| {{Primary Street}}||2 (3 for one way PS)
------ DO NOT MODIFY ABOVE THIS LINE -----
|-
======                              ======
| {{Street}}||1 (2 for one way S)
======                              ======
|-
======                              ======
| {{Railroad}}||2
====== 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}}
| {{Ferry}}||5
 
|}
{{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}}
<!--
 
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.
{{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}}
If a different locking standard for the midatlantic region is desired, please develop it at {{:USA/Mid Atlantic/Locking standard}}. If state-specific guidance for {{BasePage2}} is desired, please develop it at [[{{BasePage2}}/Locking standard]].
 
-->
{{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}}
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
 
-------------------------------------------------------------------------------------
{{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}}
---- This page is only transcluded into (displayed on) the main page for this state.
 
---- It directly follows the common guidelines applicable to all states. When this
{{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}}
---- page is present (even if blanked), it displaces any optional code that might be
 
---- in that section.
{{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}}
---- If the original optional code from the main page for this section is still
 
---- desired, it can be restored by adding the following code to the first line
{{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}}
---- between the "DO NOT MODIFY" lines on this page:
 
----  {{:USA/CommonState/Major_roads|optional}}
{{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}}
---- If there will be a full page for this section, use code similar to the wording
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
---- below to provide a hyperlink to that page. When creating the full page, use the
=====                                =====
---- link on the talk page to ensure the preload data is provided to help with
=====                                =====
---- formatting the page. Don't just use the red link from this section once it is
----- DO NOT MODIFY BELOW THIS LINE ----->
---- saved.
</includeonly>
----
<!--  this is a comment  --><!--
    If this section grows too long, move most of it to the following page
    and uncomment the paragraph:
--><!--
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
-->
<!--
----
-------------------------------------------------------------------------------------
---- This section has three possible purposes:
---- 1. It is only providing a hyperlink to the full page for this section.
---- 2. It is only providing some unique guidance for this state that differs from
---- other states.
---- 3. It is intentionally wiping out the general optional content for this section
---- for this state.
------------------------------------------------------------------------------------>

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