m (Copying text of wiki page for coparison with the "Wisconsin/Special roads/Main" page) |
m (Copying text of wiki page for coparison with the "Indiana/Closures/Main" page) |
||
| Line 2: | Line 2: | ||
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> | ------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> | ||
= | INDOT posts road closures and road reports to the [http://indot.carsprogram.org/#roadReports/layers=allReports,roadReports,winterDriving,weatherWarnings,trafficWise/ Indiana Traveler Information]. | ||
Indianapolis maintains their own [http://www.indy.gov/egov/city/dpw/rebuildindy/projects/pages/streetclosingalerts.aspx Road and Street Closures] page. | |||
=== | Indiana Department of Transportation (INDOT) maintains a listserv for their projects and closures: [http://public.govdelivery.com/accounts/INDOT/subscriber/new INDOT Projects and Closures Mail List] . | ||
=== Major Construction Projects === | |||
[http://www.kyinbridges.com/ The Louisville-Southern Indiana Ohio River Bridges Project] | |||
[http://www.in.gov/indot/projects/i69/ I-69 status for Indiana] | |||
[http://www.in.gov/indot/2371.htm A few more Major projects currently in Indiana] | |||
==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_in_Waze_Map_Editor|update requests]] for more information. | |||
=== Team UR Handling === | |||
== | |||
2015-06-06: The Great Lakes Region has standardized on a UR response system after extended discussion in the [https://www.waze.com/forum/viewtopic.php?f=943&t=137036 forum]. | |||
=== Overview === | === Overview === | ||
| Line 42: | Line 42: | ||
=== Process Chart === | === Process Chart === | ||
[[File:GLR_-_UR_Process_20150606.png| | [[File:GLR_-_UR_Process_20150606.png|800px]] | ||
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- | <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- | ||
| Line 53: | Line 53: | ||
---- desired, it can be restored by adding the following code to the first line | ---- desired, it can be restored by adding the following code to the first line | ||
---- between the "DO NOT MODIFY" lines on this page: | ---- between the "DO NOT MODIFY" lines on this page: | ||
---- {{:USA/CommonState/ | ---- {{:USA/CommonState/Closures|optional}} | ||
---- | ---- | ||
------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ||
| Line 62: | Line 62: | ||
---- saved. | ---- saved. | ||
---- | ---- | ||
See [[{{BasePage2}}/ | See [[{{BasePage2}}/Closures]] for guidance in {{RootPage2}} that may not be universal to all other states. | ||
---- | ---- | ||
------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ||
Revision as of 03:06, 16 February 2017
INDOT posts road closures and road reports to the Indiana Traveler Information.
Indianapolis maintains their own Road and Street Closures page.
Indiana Department of Transportation (INDOT) maintains a listserv for their projects and closures: INDOT Projects and Closures Mail List .
Major Construction Projects
The Louisville-Southern Indiana Ohio River Bridges Project
A few more Major projects currently in Indiana
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
2015-06-06: The Great Lakes Region has standardized on a UR response system after extended discussion in the forum.
Overview
NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter.
Response Timeline
- 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 request for information 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
Shared Ownership:
- All editors are considered to have equal ownership of and responsibility for all URs in the Great Lakes Region.
- All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere to the minimum time spacing guidance between responses.
- 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
Notes:
- 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.
Process Chart
