NO SPOILERS 
get the exit right and stay to the left navigational instructions we need when we come to the end of this segment
maintain correct name continuity for 322 and 22 across all the ramp and highway segments in order to avoid the risk of weird BDP issues.
PM me. After everyone who wants to has had a chance to think this through, we can start posting solutions.
Whoops! Didnât think my UR would create a quiz for the whole class
It was you! Good one.
Ok sorry everyone. It looks like this all got fixed sometime after the last time I looked at it.
I jumped the gun.
Yeah looks like no1uknow went and fixed it yesterday. I saw a UR for it on Tuesday and employed DJNeubie on the first attempt at a fixâŚguess it wasnât 100% right 
How did it get fixed??? no1knows [emoji5]
I donât think it is QUITE fixed yet. Looks like thereâs a BC on the right.
I still hold that there should be a wayfinder that prompts âexit rightâ and âkeep leftâ at the first fork. Because âkeep leftâ at the second fork without an âexit rightâ first is very confusing. And I agree w/ qwaletee that there is a BC currently at the first fork on the right and the second fork on the left, leading to no prompt currently for the exit to I-81N, which just ads to the confusion.
Sure enough.
What did Qwaletee and DrNeubie see that I couldnât see because I was not zoomed in far enough on a small screen?
What is causing BC at that fork?
If a wazer is routed to I-81 S, what nav. instruction will they receive and where?
Is there any risk that they will wind up in the wrong lane and be unable to exit?
At the first split from 322, a driver will get no keep right or exit right instruction at all if they are heading to 81, which could be confusing. That segment after the split is FW, so even if an instruction was given, it would be âstay rightâ while the BGS both say âExitâ.
Then at the second split, a driver heading to 81 N would get no instruction, while 81 S would get an exit right, which is OK.
Seems to me the first split should be âexit rightâ (and keep left to stay on 22) and then the second split should be âstay rightâ and âstay leftâ.
PMâd you my solution.
One issue here is that SV makes it look like âto I-81 S Carlisleâ comes before the âI-81 N / etc / Hersheyâ , according to where the whte lines start â which is actually correct?
That you first exit for I-81, and then choose which direction?
Or, if you are headed for I-81 S, you get exit right
If you are headed for I-81 N you get an exit left a little later (and no further instructions)
If you are headed for 22, you get no instructions? or you are told to stay to the left? At the I-81S or at the I-81 N exit?
I believe there are 2 exits at the same location. The solid white lines indicate 2 lanes and 2 exits, each for a different direction on 81. Itâs odd that it isnât a more normal single exit that divides later, since there are 2 distinct exit signs.
Since Waze is incapable of lane guidance (and we do not put lane guidance into segment names), it is impossible to get good nav instructions from a three-way split. (Waze cannot say: Right lane to exit to X vs second-from-right to exit to Y vs left two lanes to continue into Z).
So we have to put something befor something else, even if it is not quite correct. Of all the bad choices available to us, is the current ramp configuration the least-bad choice? Or at least ânot much worseâ than the alternative?
Are the segment names / nav instructions now recognizable / useful to a driver looking at the BGS?
Voludu,
In exceptional cases, I have allowed lane guidance in seg names for three way splits.
We did one on 78 W in NJ that I havenât seen any more complaints on. Although I do think it was 1 person that kept reporting it.
Iâd like to share my mockup. May I?
Well sure why not show a mockup?
The first question is â is the current road configuration inadequate?
If that is the case, is this a truly exceptional case that merits âhard codingâ lane guidance into the segment name? This would be just one more âbad choiceâ option for this interchange.