User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Idaho/Major roads/Main" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(209 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    ↓
==============================
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/>


==== Highway Status ====
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.
The status for all interstates, federal, and state highways running through Idaho [[Idaho/Major_roads|are documented here]]. This includes any project status pertaining to those highways, as well as any known changes coming down the pike from ITD and/or other cities as we find out about them.


==== State highway naming ====
[[File:ID-Highway-Blank.png|48px|left|frameless|Idaho Highway]]
State highways are to be named '''SH-###'''<br><br>


There is [[Glossary#TTS|TTS support]] to name state highways as '''ID-###''' but doing this will cause the state shields to go away in the app. Until this is implemented fully, we will stick with the '''SH-###''' format.
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 (=).


Exception: Ramp names can use the '''ID-###''' format since they do not carry shields.
==Accepted parameters:==


==== County road naming ====
*<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.


[[File:WY-County-Blank.png|48px|left|frameless|Wyoming County]]County roads with the name designation of "County Road ##" or "Co Rd ##" are to be named in Waze as '''CR-##'''. This shortened version takes up less space on the map screen and is announced correctly as "County Road ##" while navigating with the Waze app.<br><br>


==== 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 (=).


In Idaho, 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 US road type standards (FC and highway systems). Lock the roads based on type after they've been set to [[Road_types/USA#Public_roads|current US road type standards]].
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.


{| class="wikitable" style="text-align:center; margin: 1em auto 1em auto; width: 40%"
|+ Idaho Minimum Locking Ranks
! Segment Type !! Rank
|-
| {{Freeway}}||4
|-
| {{Ramp}}||4
|-
| {{Major Highway}} || 3
|-
| {{Minor Highway}} || 2
|-
| {{Primary Street}} || 2
|-
| {{Railroad}}|| 2
|-
| All Others || 1
|}


==== Roads named N, S, E or W ====
For example an Event row should look like this;


If you encounter any roads that are named N, S, E, or W, you must add a period (.) to the end of the letter. For example, West N Street is abbreviated as '''W N. St'''. County Road W is abbreviated as '''CR-W.''', and so on. This ensures the TTS system reads the road name as "County Road W" and not "County Road West."
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


==== U-turns ====


Page 2-10 of the [http://itd.idaho.gov/wp-content/uploads/2016/06/driver_manual.pdf Idaho Driver's Manual] says this about U-turns:
If there are multiple editors it should look like this
:U-turns are not legal everywhere, so first look for prohibiting signs. When making a U-turn near a hill or curve, the law requires that you be able to see 500 feet in either direction. U-turns are prohibited in no-passing zones. Stop and yield to all traffic before completing a U-turn.


For Waze routing, u-turns should only be enabled where they provide the potential for improved routing, which includes recovering from missed turns. A common example is a median-divided primary street that has homes/businesses with their driveways/entrances directly on it, where reaching them would otherwise require lengthy, multi-turn deviations through side roads in order to end up on the correct side of the median.
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}


==== Road Elevations ====


These are the general guidelines for elevation in Idaho:
* Drivable and non-drivable segments are handled the same way with elevation.
* Set elevation to ground in most cases.
** Segment(s) passing over other segment(s), rivers, major waterways, and ''all bridges'' shall have higher elevation, relative to ground.
** Only elevate/lower the actual bridge/tunnel section of the road.
** Elevation of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless a tunnel).
** Tunneled segments shall have lower elevation, relative to ground.
** Only segments that "cannot see the sky" should have negative elevation (i.e. tunnels).
** Only set elevation as low/high as necessary.
* If you use the Bridge tool to join segments, be aware that it raises the elevation of the joined segment. Lower the joined segment as appropriate.
* [[Elevation_-_bringing_the_Seagull_to_Australia|"Seagull"]] guidelines apply to elevation in Idaho.
** Bridges should be cut at the start/end of the bridge.
** Tunnels should be cut at least 15m/50ft '''before''' and '''after''' the tunnel, to allow time for the GPS to regain signal.
** Do not cut segments for elevation purposes if the bridge/tunnel starts/stops within 60m/200ft of an existing junction.


<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY 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.'''
-------------------------------------------------------------------------------------
————————————————————————————————————
---- 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
 
---- page is present (even if blanked), it displaces any optional code that might be
 
---- in that section.
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
---- 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
==TO EDIT THIS TABLE CLICK HERE >> ==
---- between the "DO NOT MODIFY" lines on this page:
</noinclude><includeonly><!--
----  {{:USA/CommonState/Major_roads|optional}}
------ DO NOT MODIFY ABOVE THIS LINE -----
----
======                              ======
-------------------------------------------------------------------------------------
======                              ======
---- If there will be a full page for this section, use code similar to the wording
======                              ======
---- below to provide a hyperlink to that page. When creating the full page, use the
====== DO NOT MODIFY ABOVE THIS LINE ====-->
---- link on the talk page to ensure the preload data is provided to help with
{{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}}
---- formatting the page. Don't just use the red link from this section once it is
 
---- saved.
{{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.
{{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}}
---- This section has three possible purposes:
 
---- 1. It is only providing a hyperlink to the full page for this section.
{{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}}
---- 2. It is only providing some unique guidance for this state that differs from
 
---- other states.
{{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}}
---- 3. It is intentionally wiping out the general optional content for this section
 
---- for this state.
{{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 >>