https://www.waze.com/editor/?zoom=5&lat=40.0677&lon=-86.49504&layers=TBFTFFTTTTFTTFTTTTTFTTTTTTT&env=usa
I’d like to discuss the exit from I-65N to US-52W. It is incorrectly mapped at the moment. I have reported the issue but it looks like a level 5 will need to step in.
The exit comes off I-65N and merges with the on ramp from Lafayette Ave, then they split left to I-65N and right US-52W.
As it stands, the exit instruction is delayed until the last exit, when in fact there should be one exit instruction, and then a keep right instruction to continue on US-52W. This is very clear in aerial images.
Is there a reason why the map should be kept the way it is?
My guess, it was done to stop routing off and back on to I-65. If the off ramp is moved to where the exit really is, the city of Lebanon will need to be added on this segment so the waze routing mechanism won’t do that anymore, or change all of the I-65 segments to “no city”.
I see what you mean though, the exit instruction is late, and can be a problem with the barrier wall separating the ramps on and off.
I’m pretty sure it’s to keep mainline traffic on the mainline, and exiting/entering traffic on the auxiliary lanes. This section of I-65 often bottlenecks when crashes North of there happen. Traffic exits and gets back onto I-65 North or they get off onto US 52 W.
bigbear, what does the city on segments have to do with routing?
Waze added a routing logarithm that will avoid off and back on if the highway segments are named the same and if the cities are set the same.
I’ll look later tonight at it and see what we can do there.
Sent from my iPhone using Tapatalk
Ok, think I got it. Keep an eye on this for any other problems. I’ll wait a couple days for the tiles to update and try routing to see what happens.
Just checked routing and didn’t get the off and back on routing here anymore. That fixed it.