In Indianapolis a very busy section of interstate is going to be closed for 59 days. Is this something that can be indicated in the map somehow?
http://www.in.gov/indot/3154.htm
Normally I’d say leave, but since this is a major route, it’d probably be nice if Waze would route around it instead of waiting until someone hits a detour sign and ends up having to drive through downtown.
I think it would be a good idea to fix them for the 59 days. I drive through there 2-10 times a day as a courier, and the rerouting would be very helpful.
So this starts midnight on Tuesday and will be chaotic for the next 60 days. Who and How can Waze be updated to route around this mess?
I’ll help but someone will really need to get on here with reply when it opens back up so I can fix it back for you too.
Sent from my Nexus 7 using Tapatalk 4
I followed this closure map here: http://www.in.gov/indot/files/GF_SouthSplit_MainlineRampClosures.pdf
Looks great. Thanks!
I’ll try to post close to when the roads will reopen.
With the map tile update delay, it won’t show up on the client until then. Just figured would point that out.
Sent from my Nexus 7 using Tapatalk 4
I expected the map to be updated by now, but it looks like it’s not. If it takes this long, we’ll probably want the map fixed back at least a couple of weeks before they reopen.
They are experiencing map tile issues that required a rollback to Aug 25, per their post at status.waze.com which right now we can only hope can be fixed as soon as possible so that they can restore daily updates. I think by then we just update about a few days before the 59th day.
It looks like the updates have taken effect. Thanks for all the work. It definitely helps in routing through the mess. I’ll let you know if I see any issues with it.
There is one issue I’ve seen now that I think about it:
The access road connecting Virginia to Calvary labelled, “to I-65 N / I-70 E, Indianapolis, Indiana” is open, although you have it closed.
Ok, I fixed that, I was doing that based on how the INDOT reported the closure as being closed from there, at least how I read it, anyways, fixed that.
Time to reopen it. They opened all lanes last night. I haven’t driven past, yet, but I believe it is fully operational from this morning’s report in the paper.
Yep, it’s open!
http://www.indystar.com/article/20131016/NEWS/310160075/South-split-Downtown-Indy-reopens-after-more-than-month-construction
I didn’t have to sit through 3 red lights on Illinois at South St. So happy. 
(And I don’t have to complain about my commute being 3 minutes longer… while those coming from the north had ~30 minutes added to their commute.)
Thanks for the PM to bring to my attention faster. I have edited the ramps and freeway segments, please review. I added pathfinder segments to the North and South where the freeway is technically continuous, but it is probably best so add those there. Let me know how those work out. I have them working like that here in KC.
Thanks the1who! It looks like everything’s hooked back up. Now we’ll just watch for any user reports. They were quick to report the roads being back open.
Out of curiosity, what type of edits did you make to close the roads? Did you simply disallow all the turns? I’m just wondering how this type of change is made in WME.
Sorry for long delay in reply. I have been on hiatus for move for new job. At the time, because of the long closures that took place and because of a feature, the temp closure feature, was still in beta, they were just disconnected to prevent routing. Even if the turn was disabled, it could have still potentially routed through the junction, but suffered a large penalty in the routing engine to do so. So to answer your question plainly and simply, they were disconnected. However, the new feature with closures is supposed to circumvent us from having to disconnect. I have been out of the loop for some reading on the technicals lately, but using the time based turn restriction feature was explained to me by the Country Manager as being the preferred way when all is working.