Before I made recent changes, there were a number of URs by people being unexpectedly directed off I-85 N at Exit 69B (to Old National Hwy) who anticipated taking Exit 68 (to I-285 E).
After the changes there were URs by those that wanted to take Exit 69B to I-285 E (it’s not signed that way) for whatever reason (traffic backup at Exit 68?). Although I seems about half were made through the Livemap (b/c the URs were too wordy to be done while driving), it is clear that neither the prior or current configuration are functioning as desired.
Allows routing from Exit 69B to I-285 E even though Exit 69B is only signed for Old Nat’l Hwy. This is a viable alternative if traffic heading to Exit 68 (I-285) is backed up…which it seems to be when I drive through there.
This may be a happy medium to cut down on the number of URs that pop up no matter which way it’s configured.
This will support future restriction of the collector ramp routing back onto i-285. That can be decided on a future date whether it is needed anymore. That is probably the last choice at this time. Making that change would only require a turn restriction, and a stub segment exiting the junction node to force prompting.
This collector ramp also goes back to I-85 N. The current setup also prevents a route to another highway interchange further up in the collector. There is another off-ramp to access the interchange from i-85 but this routing may be ideal in a backup.blocked ramp from initial exit sign
I also propose putting alt name “BDP I-285 E” on these segments. Add “BDP I-285 E”
This will turn big detour prevention for the signed ramp, preventing the other routing in all but traffic jam situations.
For the sake of further discussion, let’s try your proposal first, then give it a couple weeks to see what happens. Then we’ll try my proposal. There’s no critical urgency other than to get it right.
The problem with the previous alignment is that crossing over from the Nat’l Hwy Exit 269B to I-285E was restricted. That may have been an oversight or it may have been intentional, but either way URs continued to be generated.
I estimate at least 50 pct of the URs at this location in the past 3 weeks were added from Livemap, not actual drivers – with real GPS tracks – because of the very wordy write-ups, so I mostly ignored those. If that also turns out to be the case after your proposal has been in effect for a few days, then I’m going to ignore those, too. Without real GPS tracks, the issue gets too muddied.
In anticipation of sending this post and you being able to make changes, I’m the one that deleted the stub segment since it was locked at L6.
It seems as if users will be unhappy regardless of the configuration. Half will be upset they got put on the collector ramp during a backup/or no backup, the other half will be upset they didn’t get the collector when the main road was slightly backed up…
Why are you ignoring these? Do you think it’s one of us adding them? We would all be glad to post on the UR to prove it’s not, if that is what you are hinting at. People can type super fast on phones, some as fast as a keyboard. It is not anything to ignore because it is wordy and/or no GPS. I have reported stuff before and my GPS track not show up. Sometimes URs don’t even show up in the right spot. Drivers/passengers are taking the time to explain something, and you are ignoring it?
I read them, so “ignored” might not be accurate, but they’ve all been about the same problem of which we are well aware plus there was no accompanying GPS data. There’s plenty of others that do have useful data. No need to spend a lot of time on the ones that don’t.
I’ve applied my changes, its going to take more than just a few weeks for this to meddle through to the app though. I’ve seen these take as long as 6 months to update fully for everyone.
Note that if a UR is filed in the app and not “finished”, after a minute or so it will minimize to a small icon on the screen and can be completed once the destination is reached or some other opportunity when there is more time to type. This can explain wordy URs.
