User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Kentucky/Closures/Main" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(580 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    ↓
Kentucky Transportation Cabinet posts road closures and road reports to the [http://511.ky.gov/kyhb/ Kentucky 511 page].
==============================
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/>


Louisville Public Works maintains their own [http://louisvilleky.gov/government/public-works/services/road-and-street-closures Road and Street Closures] page.
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.


=== Major Construction Projects ===


[http://www.kyinbridges.com/ The Louisville-Southern Indiana Ohio River Bridges Project]
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 (=).


[http://transportation.ky.gov/District-5/Pages/US-421-Milton-Madison-Bridge-Approach.aspx US 421 Milton-Madison Bridge Approach]
==Accepted parameters:==


[http://www.aaroads.com/forum/index.php?topic=3518.0 I-69 Forum discussion about current status in Kentucky]
*<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.




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


An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See [[Update_Requests_in_Waze_Map_Editor|update requests]] for more information.


=== Team UR Handling ===
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.
In Kentucky, we generally work as a team. URs are not owned by the first responder. If another editor has first hand knowledge of the issue and can make the necessary corrections to the map to solve the reported issue, they are free to do so.  Editors must comment on a UR when closing them, even if the editor is the original reporter.


When a UR does not contain enough information or the fix is not obvious, Kentucky has adopted at 1/4/8 system for response to Update Requests. 1/4/8 is the short way of explaining the following.
==== Day 1 ====
Within 24 hours (1 day) after an Update Request has been submitted, an editor should provide a response to the Update Request to get the process started. This starts a seven day clock.


==== Day 4 ====
For example an Event row should look like this;
If the reporter has not commented after 3 days (4 days since initial comment) a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue.


Example
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


"''Just a reminder: We have not received a response on your report. If we don't hear back from you soon we will infer everything is okay and close the report. Thanks!''"


'''Note''' - While the 4 day reminder is not required in the South Atlantic region, Kentucky editors have seen a large number of responses from them and encourage their use.
If there are multiple editors it should look like this


==== Day 8 ====
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
If the reporter still has not commented after 4 more days (8 days since initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed.  The Update Request then needs to be closed as Not Identified.


Example


"''The problem was unclear and volunteers didn't receive a response so we are closing this report. As you travel, please feel welcome to report any map issues you encounter. Thanks!''"


=== Old User Reports ===
'''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 1/4/8 rule has been very successful in our busy areas with editors maintaining them. There are some areas outside of our reach and occasionally as we venture off the beaten path, we come across a report that has been there for quite some time.  We feel these reports are as valid as the reports opened yesterday and they should be given the same courtesy of response as new reports. Give the reporter a chance to respond.  
————————————————————————————————————


Example:


"''I apologize for the late response, as volunteer editors that have to travel an area to unlock it for editing, there are sometimes areas that only have a few editors. I recently visited this area and would like to help. Do you recall the problem you had here?''"


If they let you know too much time has passed and they do not recall the issue, it can be closed if the problem can not be spotted. If the user does not respond, use the 1/4/8 rule.
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''


<br>
==TO EDIT THIS TABLE CLICK HERE >> ==
<br>
</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}}


=== Speed Limit Update Requests ===
{{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}}
<br>
1. The reporter reports the same SL that is already on the segment/road: <br>
"''Volunteer responding. Thank you for your report. Did you know You can set Waze to always display the speed limit? In Android tap speedometer > Settings > Show speed limit > Always show speed limit. In iOS tap the speedometer > Settings > toggle Show Speedometer to green/on.''"<br>
Close the report as solved. Rationale for "solving" is the Wazer is verifying the SL for us in real time and closing as "not identified" could confuse or anger the Reporter.
<br>
2. Reporter gives a speed limit that doesn't make sense but would otherwise be a valid report. Tell the reporter what they reported and ask for input. In the above the report is 55MPH for a street in a commercial area. 25 MPH would be the expected limit. Below is an example. Change your response accordingly.<br>
"''Volunteer responding. Thank you for your report. We received your 55mph Speed Limit report you submitted for Highland Point Dr. Please verify the missing or incorrect speed limit.''"<br>
Use normal UR process.
<br>
3. Speed Limit Update Request without enough info to process: <br>
"''Volunteer Responding. Thank you for your report. Waze did not send us enough information to fix your request. Would you please tell us as much as possible about the speed limit? Thanks!''" <br>
Use normal UR process.
<br>
4. Ramps:  <br>
"''Volunteer responding - We reviewed your Missing Speed Limit report. At this time our guidance is to only publish speed limits that are signed with a regulatory sign, so we will close the report at this time. Please always try to follow advisory limits for safety.''" <br>


<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
{{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}}
-------------------------------------------------------------------------------------
 
---- This page is only transcluded into (displayed on) the main page for this state.
{{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}}
---- 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
{{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}}
---- in that section.
 
---- If the original optional code from the main page for this section is still
{{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}}
---- desired, it can be restored by adding the following code to the first line
 
---- between the "DO NOT MODIFY" lines on this page:
{{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}}
----  {{:USA/CommonState/Closures|optional}}
 
----
{{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}}
-------------------------------------------------------------------------------------
 
---- If there will be a full page for this section, use code similar to the wording
{{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}}
---- 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
{{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}}
---- formatting the page. Don't just use the red link from this section once it is
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
---- saved.
=====                                =====
----
=====                                =====
See [[{{BasePage2}}/Closures]] for guidance in {{RootPage2}} that may not be universal to all other states.
----- DO NOT MODIFY BELOW THIS LINE ----->
----
</includeonly>
-------------------------------------------------------------------------------------
---- 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 >>