User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Kentucky/Area Managers/Main" page)
m (Copying text of wiki page for coparison with the "Kentucky/Closures/Main" page)
Line 1: Line 1:
<!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------
<!-- 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 ------>
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--
Kentucky Transportation Cabinet posts road closures and road reports to the [http://511.ky.gov/kyhb/ Kentucky 511 page].
------------------------------------------------------------------------------------
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----
---- Other Area Editors: Cancel edit and use link on table next to "Other Area
----    Editors". If does not exist, that section can be added from talk page.
---- Country/State Managers: Continue.
------------------------------------------------------------------------------------
---- This page is only transcluded into (displayed on) the main page for this
---- state. When first setting up this page, remove the example users for Country
---- and State managers. Area Managers are changed in a different section as noted
---- above. When adding a new user, use the following template:
{{AM/Editor|Username|Area Managed|Other Comment|badge1=x|badge2=x|badge3=x}}
---- If any fields are skipped, ensure the first three pipe "|" characters are
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"
---- is replaced only by what is defined under: {{AM/Badge}}
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or
---- search the Wiki for: "Template:AM/Badge"


----
Louisville Public Works maintains their own [http://louisvilleky.gov/government/public-works/services/road-and-street-closures Road and Street Closures] page.
---- When adding a new user, place the new template based on Rank (highest first)
 
---- and then alphabetical order in that rank.
=== Major Construction Projects ===
------------------------------------------------------------------------------------
 
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------
[http://www.kyinbridges.com/ The Louisville-Southern Indiana Ohio River Bridges Project]
---------------------------- EDIT BELOW LINE ---------------------------------------
 
----------------------------------------------------------------------------------->
[http://transportation.ky.gov/District-5/Pages/US-421-Milton-Madison-Bridge-Approach.aspx US 421 Milton-Madison Bridge Approach]
{{AM/Top}}<!-- Top of the table -->
 
{{AM/Country}}<!-- Defines the start of the country manager section -->
[http://www.aaroads.com/forum/index.php?topic=3518.0 I-69 Forum discussion about current status in Kentucky]
{{AM/Editor|crazycaveman|5|Statewide|Resident of SC<br />Covers SAT region|badge1=cm|badge2=sm}}
 
{{AM/Editor|ialangford|5|Statewide|Resident of SC<br />Covers SAT region|badge1=cm|badge2=sm|gho=Ian|pic=File:Avatar ialangford.jpg}}
 
{{AM/Editor|Khaytsus|5|Statewide|Resident of state|badge1=cm|badge2=bt}}
==Update Requests==
{{AM/State}}<!-- Defines the start of the state manager section -->
 
{{AM/Editor|xanderb|6|Statewide|Working in state<br />Covers SAT region|gho=Xander|pic=File:Avatar_xanderb.jpg|badge1=mlc|badge2=cm|badge3=sm|badge4=mr}}
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.
{{AM/Editor|ttninja55|5|Statewide|Resident of state|badge1=sm|badge2=mr|gho=Tom|pic=File:Ttninja55avatar.jpg}}
 
{{AM/Editor|jbayes|4|Statewide|Resident of state|badge1=sm|badge2=m|badge3=mr|gho=John|pic=File:Jbayes-Avatar.jpg}}
=== Team UR Handling ===
{{AM/AreaLink}}<!-- Defines the start of the area manager section -->
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.
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--
 
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.-->
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.
}}<!-- End ifexist -->
==== Day 1 ====
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------
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 ====
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
 
"''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.
 
==== Day 8 ====
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 ===
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.
 
<br>
<br>


====KY Area Manager Coverage Map====
=== Speed Limit Update Requests ===
Please feel free to reach out to the Area Manager for the area you are working in. If there is not an Area Manager assigned, contact the State Manager.
<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>


{{#widget:Iframe
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
|url=https://www.google.com/maps/d/embed?mid=z8qhZRM2p_BI.k84e6rG7-oF4
-------------------------------------------------------------------------------------
|border=0
---- This page is only transcluded into (displayed on) the main page for this state.
|width=712
---- It directly follows the common guidelines applicable to all states. When this
|height=534
---- page is present (even if blanked), it displaces any optional code that might be
}}
---- in that section.
====Other Area Editors====
---- If the original optional code from the main page for this section is still
{{#ifexist: {{BasePage2}}/AM/Editor/Area2 <!-- If other table exists -->
---- desired, it can be restored by adding the following code to the first line
| {{AM/Area2Link}}<!--then display Other Table, or skip -->
---- between the "DO NOT MODIFY" lines on this page:
}}<!-- End ifexist --></includeonly>
----  {{:USA/CommonState/Closures|optional}}
<!----------------------------------------------------------------------------------->
----
<!------------------------ DO NOT ADD CODE BELOW THE TABLE -------------------------->
-------------------------------------------------------------------------------------
---- 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
---- 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
---- saved.
----
See [[{{BasePage2}}/Closures]] 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.
------------------------------------------------------------------------------------>

Revision as of 04:05, 2 September 2016

Update Requests

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 for more information.

Team UR Handling

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

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

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

Day 8

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

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.



Speed Limit Update Requests


1. The reporter reports the same SL that is already on the segment/road:
"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."
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.
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.
"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."
Use normal UR process.
3. Speed Limit Update Request without enough info to process:
"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!"
Use normal UR process.
4. Ramps:
"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."