Kentucky/Closures/Main: Difference between revisions View history

(*/Closures/Main*/)
m (synced to wiki matching history up to 2016-09-02T04:05:54Z)
 
(9 intermediate revisions by 2 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><!--
<!-- 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 ------>  
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
Kentucky Transportation Cabinet posts road closures and road reports to the [http://511.ky.gov/kyhb/ Kentucky 511 page].


<big>Major Construction Projects</big>
Louisville Public Works maintains their own [http://louisvilleky.gov/government/public-works/services/road-and-street-closures Road and Street Closures] page.
 
=== Major Construction Projects ===


[http://www.kyinbridges.com/ The Louisville-Southern Indiana Ohio River Bridges Project]
[http://www.kyinbridges.com/ The Louisville-Southern Indiana Ohio River Bridges Project]
Line 9: Line 12:


[http://www.aaroads.com/forum/index.php?topic=3518.0 I-69 Forum discussion about current status in Kentucky]
[http://www.aaroads.com/forum/index.php?topic=3518.0 I-69 Forum discussion about current status in Kentucky]


==Update Requests==
==Update Requests==
Line 17: Line 21:
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.
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.


For unclear issues, Kentucky has adopted at 1/4/8 system for response to Update Requests. 1/4/8 is the short way of explaining the following.
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 ====
==== 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.
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.
Line 27: Line 31:


"''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!''"
"''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 ====
==== Day 8 ====
Line 40: Line 46:
Example:
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 have that only a few editors. I recently visted this area and would like to help. Do you recall the problem you had here?''"
"''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.
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>
=== Speed Limit Update Requests ===
<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 ----
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----

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