User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Illinois/Special roads/Main" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(199 intermediate revisions by 4 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    ↓
<!-----
==============================
{{AddCode|Replace this template message with specific information unique to the state.  If the information is more than a screen full, consider moving it to a full subpage. Minimally the following link is required to reach the full subpage from the main page. Exclude this link if all the relevant information is already displayed in this section.}}
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/>


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.


<!-- === Non-Drivable Roads === -->
The {{Walking Trail|Walking Trails}} and {{Pedestrian Boardwalk|Pedestrian Boardwalks}} ''road types'' are not added to the map in Illinois. In general, these road types do not add to the routing function of the application.


Special exceptions may be made with the approval by State Managers. For example, a {{Pedestrian Boardwalk|Boardwalk}} may be used to support house numbers in situations where they are not assigned to drivable road types. This use must be approved by a State Manager (refer to [[#Illinois#Area_managers|Area Managers]] table).
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 (=).


Please consult with a State Manager before adding or removing these road types.
==Accepted parameters:==


=== Unpaved and Unmaintained Roads ===
*<code>name=</code> The name of the event.
Illinois follows this specific guidance on the use of {{Dirt|Off-road / Not maintained }} road types and unpaved roads in the state. This supplements the guidance for [[Road_Types_(USA)|road types]].
*<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.


Unpaved roads may or may not be classified on IDOT Functional Classification maps. Maintained, but unpaved, roads should have the ''unpaved'' attribute checked. Unpaved [[driveways]] should be mapped using the Private Road type, regardless of their condition. Similarly, [[Illinois#Alleys|alleys]] and [[Road_Types_(USA)#Parking_Lot_Road|parking lot roads]] should use the appropriate road type. Unpaved roads classified in one of the arterial classes will be mapped as specified in [[Road_Types_(USA)|road types]] guidance. Collector, local and unclassified roads will be mapped as shown in the table below.
<br />
<br />


<div style="font-size:smaller">
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 (=).  
{| border="1" align=center style="border-collapse:collapse; text-align:center;"
! scope="row" rowspan="2" colspan="2"|
! colspan="5"| Highway System & Road Surface
|-
!County<br>Highway{{ref label|a|a}}{{ref label|c|c}}
!Paved<br>Street
!Gravel<br>Street{{ref label|c|c}}
!Narrow<br>Gravel Street{{ref label|b|b}}
!Soil<br>Street
|-
|examples
|
|CH-14
|Main St
|Side St
|Farm Dr
|Farm Ln
|-
! rowspan="4" | Functional<br>Classification
|| Major Collector||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Dirt|N/M}}||{{Dirt|N/M}}
|-
|| Minor Collector||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Dirt|N/M}}||{{Dirt|N/M}}
|-
|| Local||{{Primary Street|PS}}||{{Street}}||{{Street}}||{{Dirt|N/M}}||{{Dirt|N/M}}
|-
|| Unclassified||{{Primary Street|PS}}||{{Street}}||{{Dirt|N/M}}||{{Dirt|N/M}}||{{Dirt|N/M}}
|}
{{note|a|a}} A road in a county highway system is always mapped as a primary street, adding the '''unpaved''' attribute if the county highway is gravel rather than a paved surface.
<br />
{{note|b|b}} A narrow gravel road is defined as one less than 14.5 feet from edge to edge. This is less than the minimum width of two lanes as defined by the [[wikipedia:Federal Highway Administration|Federal Highway Administration]] (FHWA). Vehicles approaching from opposite directions would likely need to leave the roadway to pass.<br />
{{note|c|c}} Gravel surfaces on '''maintained''' roads should be mapped with the '''unpaved''' attribute checked.<br />
<br />


{| border="1" align=center style="border-collapse:collapse; text-align:center;"
| colspan="2" | Legend
|-
|{{Primary Street|PS}}||{{Primary Street}}
|-
|{{Street}}||{{Street}}
|-
|{{Dirt|N/M}}||{{Dirt|Off-road / Not maintained}}
|}
</div>
<br />


To determine if a road falls into the "narrow" category, measure the distance from edge to edge using by creating a temporary, un-saved, segment (using zoom level 9). Create the segment perpendicular to the roadway with end-points at the road edge at each side. The edge being a solid line of grass or other material not part of the road surface. Use the [[Scripts/WME Toolbox/Measurement Tool|WME Meausurement Tool]] in [[Scripts/WME Toolbox|WME Toolbox]], or the WME True Segment Length script, to measure the length of the segment without saving the temporary segment.
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.


=== Alleys ===
Alleys are driveable roads passing between or behind buildings and are not intended for thru-traffic. They can be an important component in routing when primary access is not on a local street or drivers start a route from an alley.


Generally speaking, only residential alleys should be mapped. An alley should only be mapped if it is a locally accepted parking destination near a residence. It should function only as the starting point or destination of a route.
For example an Event row should look like this;


Within District 1 (LAMD1), including the Chicagoland, alleys are mapped as the likely starting point for many routes. Do not delete any alleys mapped within this district. Outside LAMD1, alleys may be mapped or removed after careful consideration of the above guidance and their routing benefit. Please consult with a [[Illinois#Area_Managers|LAM or SM]] before adding alleys.
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


If an alley is to be mapped or updated, be sure to review nearby house numbers and ''nudge'' them if needed.


All alleys should have their road type set to {{Parking Lot Road|Parking Lot Road}} and should be named "Alley".
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}}


== Update Requests ==


Illinois encourages cooperation between editors in resolving issues. Clear status notes in URs are strongly suggested. While keeping a reporter apprised on a timely basis, detailed inter-editor conversations are often best kept in private messages or in hangout conversation to avoid involving a reporter in editing minutia or protracted discussions. Remember: Courtesy counts.


Illinois uses the [[USA/Great Lakes/Test#Update Requests | Great Lakes Region Update Requests Response System]] outlined below.
'''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.'''
————————————————————————————————————


=== Overview ===


NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter.


'''Response Timeline'''<ul>
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
* '''Day 0''': The first editor who is able to respond to UR should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it closed. 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.
* '''Day 4+''': Polite reminders should be sent to reporters who have not responded to the initial at any time, provided at least four full days have elapsed since the initial response was sent.
* '''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.
</ul><br />


'''Shared Ownership'''<ul>
==TO EDIT THIS TABLE CLICK HERE >> ==
* All editors are considered to have equal ownership of and responsibility for all URs in the Great Lakes Region. All editors, regardless of whether they have worked the UR previously, may send any of the responses describe above, provided they adhere the minimum time spacing guidance between responses.
</noinclude><includeonly><!--
* All editors are explicitly encouraged to attempt resolving URs at any point during their lifecycle, even if others happen to be actively working it at the same time.</ul><br />
------ 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}}


'''Notes'''<ul>
{{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}}
* The ideal timeline for UR response is when responses are sent as early as the minimum required time spacing between messages permits. Experience has reliably shown that UR response rates are much higher when editors are able to send responses promptly.
 
* While strongly recommended, it is not required to send the followup message.</ul>
{{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}}
<!-- See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.
 
-->
{{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/Special 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>
----
See [[{{BasePage2}}/Special 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 >>