Confusing Concurrencies

[roadman65]

Hawkinsville, GA is got a bunch and the signing there is more confusing as the truck routes, plus GDOT's typical way of signing and implementing too many state routes does not help.

[Skye]

Any one where you are simultaneously going "North" and "South" or "East" and "West".  The first one that comes to mind is I-77/I-81 in Virginia.

[sbeaver44]

I think anything where a bannered and non-bannered route exist together, like US 220 Alt/US 460 in Roanoke, VA, can be confusing.

Nexus 6P

[sandwalk]

Or how about any wrong way multplex where you are traveling say north and for some reason a route heading south is multiplexed or east and west same thing. I've seen this before and it's probably confusing due to the fact that if it's dark out and you see both north and south you'd be confused on which direction you were really going.

It's even better when it's a N/S wrong-way concurrency but the road itself is E/W aligned.

Ah, yes. Fremont, Ohio: https://goo.gl/maps/FzPyn5rqrXN2

[US 89]

Or how about any wrong way multplex where you are traveling say north and for some reason a route heading south is multiplexed or east and west same thing. I've seen this before and it's probably confusing due to the fact that if it's dark out and you see both north and south you'd be confused on which direction you were really going.

It's even better when it's a N/S wrong-way concurrency but the road itself is E/W aligned.

Really? That seems like it'd be the easiest type of wrong way concurrency to understand.

As an example of where this is not the case, I-25 has a wrong-way concurrency with US 285 near Santa Fe, NM. You are traveling on I-25 towards Santa Fe. Your compass says North, and you are going North on US 285, but South on I-25! (To add to the confusion, you are also going west on US 84.)

[catsynth]

I-80 East / I-580 West in Emeryville/Berkeley/Albany/El Cerrito

I actually enjoy the dissonance, but it's confusing when I have to explain it to others...

[OrangeLantern]

California 88 and 89 have a short concurrency.

Also 101/1. Are they even concurrent? Doesn't 1 just have gaps?

[formulanone]

US 221, 321, and 421 in Boone, North Carolina.

[pdx-wanderer]

California 88 and 89 have a short concurrency.

Also 101/1. Are they even concurrent? Doesn't 1 just have gaps?

US-101 and CA-1 are concurrent for a stretch from Ventura to a little north of Santa Barbara (and just misses having one with I-10 too).

[NWI_Irish96]

Coming SE --> NW through Chicagoland, you start off with 80/90.  Then 80 leaves 90 and joins 94.  Then 94 leaves 80 and heads into the city where it joins 90, and at the same spot where 94 leaves 80, 294 joins 80 for a few miles, then they split.  90 and 94 also split apart north of downtown.

This is of course why the locals all call roads by names instead of numbers, but it can get confusing for people passing through or new to the area.

[Terry Shea]

How many concurrencies can you think of where the two (or more)  route numbers are confusing?

I cite as my example the I-69 / 96 concurrency in Lansing, Michigan.  I almost got lost through there one time because I wasn't paying strict attention to the route numbers.

Any more examples of similar situations?

This can really be problematic for dyslexic sex maniacs.

[SSOWorld]

How many concurrencies can you think of where the two (or more)  route numbers are confusing?

I cite as my example the I-69 / 96 concurrency in Lansing, Michigan.  I almost got lost through there one time because I wasn't paying strict attention to the route numbers.

Any more examples of similar situations?

This can really be problematic for dyslexic sex maniacs.

Dinner for 4

[OrangeLantern]

California 88 and 89 have a short concurrency.

Also 101/1. Are they even concurrent? Doesn't 1 just have gaps?

US-101 and CA-1 are concurrent for a stretch from Ventura to a little north of Santa Barbara (and just misses having one with I-10 too).

they're not signed though, I think

[bugo]

Or how about any wrong way multplex where you are traveling say north and for some reason a route heading south is multiplexed or east and west same thing. I've seen this before and it's probably confusing due to the fact that if it's dark out and you see both north and south you'd be confused on which direction you were really going.

It's even better when it's a N/S wrong-way concurrency but the road itself is E/W aligned.

Really? That seems like it'd be the easiest type of wrong way concurrency to understand.

As an example of where this is not the case, I-25 has a wrong-way concurrency with US 285 near Santa Fe, NM. You are traveling on I-25 towards Santa Fe. Your compass says North, and you are going North on US 285, but South on I-25! (To add to the confusion, you are also going west on US 84.)

It's also secret US 85.

[US 89]

Or how about any wrong way multplex where you are traveling say north and for some reason a route heading south is multiplexed or east and west same thing. I've seen this before and it's probably confusing due to the fact that if it's dark out and you see both north and south you'd be confused on which direction you were really going.

It's even better when it's a N/S wrong-way concurrency but the road itself is E/W aligned.

Really? That seems like it’d be the easiest type of wrong way concurrency to understand.

As an example of where this is not the case, I-25 has a wrong-way concurrency with US 285 near Santa Fe, NM. You are traveling on I-25 towards Santa Fe. Your compass says North, and you are going North on US 285, but South on I-25! (To add to the confusion, you are also going west on US 84.)

It's also secret US 85.

Imagine if that were actually signed: “North 85/South 285”. Throw in the I-25 and US 84 for good measure.  Now that would be confusing.

[fillup420]

US 221, 321, and 421 in Boone, North Carolina.

The three routes never actually run together, nor meet at the same intersection. However, there are concurrencies of 221/321, 321/421, and 221/421 (221 North/421 South). So it can still get confusing.

[Beeper1]

All of the surface routes in Pawtucket, RI.   Seriously, RI-114 here is the worst of a state that already has plenty of knuckleheaded routes. 

[webny99]

Any one where you are simultaneously going "North" and "South" or "East" and "West".  The first one that comes to mind is I-77/I-81 in Virginia.

Funny, when I saw the thread title, that was my first thought as well. It doesn't get much more complicated than going opposite directions at once 

I-87/I-287 was mentioned. It's not that confusing to me, but its just weird for a 3di and its parent to have such a long multiplex. Not a huge fan of that arrangement.

[kphoger]

All of the surface routes in Pawtucket, RI.   Seriously, RI-114 here is the worst of a state that already has plenty of knuckleheaded routes. 

What?

Which highway concurrencies are confusing in Pawtucket?
RI-114 has no concurrency in Pawtucket at all.

[hotdogPi]

All of the surface routes in Pawtucket, RI.   Seriously, RI-114 here is the worst of a state that already has plenty of knuckleheaded routes. 

What?

Which highway concurrencies are confusing in Pawtucket?
RI-114 has no concurrency in Pawtucket at all.

RI 114 has a wrong-way concurrency with itself.

[kphoger]

All of the surface routes in Pawtucket, RI.   Seriously, RI-114 here is the worst of a state that already has plenty of knuckleheaded routes. 

What?

Which highway concurrencies are confusing in Pawtucket?
RI-114 has no concurrency in Pawtucket at all.

RI 114 has a wrong-way concurrency with itself.

OK, I see it now.

[inkyatari]

All of the surface routes in Pawtucket, RI.   Seriously, RI-114 here is the worst of a state that already has plenty of knuckleheaded routes. 

What?

Which highway concurrencies are confusing in Pawtucket?
RI-114 has no concurrency in Pawtucket at all.

RI 114 has a wrong-way concurrency with itself.

OK, I see it now.

Help me here, I'm not seeing it...

[kphoger]

All of the surface routes in Pawtucket, RI.   Seriously, RI-114 here is the worst of a state that already has plenty of knuckleheaded routes. 

What?

Which highway concurrencies are confusing in Pawtucket?
RI-114 has no concurrency in Pawtucket at all.

RI 114 has a wrong-way concurrency with itself.

OK, I see it now.

Help me here, I'm not seeing it...

Google Maps doesn't show it and signage is severely lacking, which is probably why.  RI-114 has a crazily circuitous route through town, such that both directions of travel officially use the same short one-way segment of Broadway.

[froggie]

^ Not unlike US 60 in Newport News, VA.

[Flint1979]

Or how about any wrong way multplex where you are traveling say north and for some reason a route heading south is multiplexed or east and west same thing. I've seen this before and it's probably confusing due to the fact that if it's dark out and you see both north and south you'd be confused on which direction you were really going.

It's even better when it's a N/S wrong-way concurrency but the road itself is E/W aligned.

Really? That seems like it'd be the easiest type of wrong way concurrency to understand.

As an example of where this is not the case, I-25 has a wrong-way concurrency with US 285 near Santa Fe, NM. You are traveling on I-25 towards Santa Fe. Your compass says North, and you are going North on US 285, but South on I-25! (To add to the confusion, you are also going west on US 84.)

That's what I was thinking too. There is a wrong way multiplex in Bay City, Michigan. M-13 and M-84 multiplex as a wrong way and the road is running east and west.