AARoads Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

New rules to ensure post quality. See this thread for details.

Author Topic: Confusing Concurrencies  (Read 15592 times)

roadman65

  • *
  • Offline Offline

  • Posts: 14287
  • Location: Lakeland, Florida
  • Last Login: Today at 08:34:53 PM
Re: Confusing Concurrencies
« Reply #50 on: December 15, 2017, 03:24:23 PM »

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.
Logged
Every day is a winding road, you just got to get used to it.

Sheryl Crowe

Skye

  • *
  • Offline Offline

  • Posts: 190
  • Age: 40
  • Location: Cincinnati
  • Last Login: Today at 09:36:59 PM
Re: Confusing Concurrencies
« Reply #51 on: January 05, 2018, 08:18:33 PM »

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.
Logged

sbeaver44

  • *
  • Offline Offline

  • Posts: 572
  • Accountant/Roadgeek

  • Age: 35
  • Location: Lewisberry, Pennsylvania
  • Last Login: Today at 03:12:58 PM
    • Flickr - WestPA31
Re: Confusing Concurrencies
« Reply #52 on: January 06, 2018, 07:13:06 PM »

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

Logged

sandwalk

  • *
  • Offline Offline

  • Posts: 221
  • Age: 38
  • Location: Ohio
  • Last Login: March 05, 2023, 08:25:10 PM
Re: Confusing Concurrencies
« Reply #53 on: January 07, 2018, 10:04:51 PM »

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
Logged

US 89

  • *
  • Offline Offline

  • Posts: 5793
  • 189 to Evanston

  • Location: Tallahassee, FL
  • Last Login: March 25, 2023, 09:17:39 AM
    • Utah Highways
Re: Confusing Concurrencies
« Reply #54 on: January 08, 2018, 12:30:21 AM »

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 itd 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

  • *
  • Offline Offline

  • Posts: 124
  • Location: San Francisco, CA
  • Last Login: January 27, 2023, 08:09:40 PM
    • CatSynth
Re: Confusing Concurrencies
« Reply #55 on: January 08, 2018, 12:56:19 AM »

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...
Logged
http://www.catsynth.com
Highway☆ App for iOS
Highway☆ App for Android

Completed 2di: I-80, I-87 (NY), I-84 (E), I-86 (E), I-97, I-44

OrangeLantern

  • *
  • Offline Offline

  • Posts: 12
  • Location: California
  • Last Login: April 12, 2018, 12:52:06 AM
Re: Confusing Concurrencies
« Reply #56 on: January 09, 2018, 07:54:27 PM »

California 88 and 89 have a short concurrency.

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

formulanone

  • *
  • Offline Offline

  • Posts: 11831
  • Age: 49
  • Location: HSV
  • Last Login: Today at 09:07:05 PM
Re: Confusing Concurrencies
« Reply #57 on: January 09, 2018, 08:39:00 PM »

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

pdx-wanderer

  • *
  • Offline Offline

  • Posts: 125
  • Age: 26
  • Location: Portland, OR / Los Angeles, CA
  • Last Login: March 22, 2023, 09:44:12 PM
Re: Confusing Concurrencies
« Reply #58 on: January 09, 2018, 10:36:34 PM »

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).
Logged

NWI_Irish96

  • *
  • Offline Offline

  • Posts: 6836
  • Formerly cabiness42

  • Age: 49
  • Location: Munster, IN
  • Last Login: March 25, 2023, 07:47:18 PM
Re: Confusing Concurrencies
« Reply #59 on: January 10, 2018, 09:30:40 AM »

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.
Logged

Terry Shea

  • *
  • Offline Offline

  • Posts: 691
  • Last Login: Today at 10:05:01 PM
Re: Confusing Concurrencies
« Reply #60 on: January 10, 2018, 05:31:37 PM »

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.
Logged

SSOWorld

  • 'Sconsin
  • *
  • *
  • Offline Offline

  • Posts: 4049
  • Interstate <Make up your mind!>

  • Age: 49
  • Location: MAH House!
  • Last Login: Today at 09:47:28 PM
Re: Confusing Concurrencies
« Reply #61 on: January 10, 2018, 07:05:36 PM »

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
Logged
Scott O.

Not all who wander are lost...
Ah, the open skies, wind at my back, warm sun on my... wait, where the hell am I?!
As a matter of fact, I do own the road.
Raise your what?

Wisconsin - out-multiplexing your state since 1918.

OrangeLantern

  • *
  • Offline Offline

  • Posts: 12
  • Location: California
  • Last Login: April 12, 2018, 12:52:06 AM
Re: Confusing Concurrencies
« Reply #62 on: January 10, 2018, 08:46:59 PM »

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
Logged

bugo

  • *
  • Offline Offline

  • Posts: 6514
  • Age: 49
  • Location: Tulsa
  • Last Login: Today at 05:08:14 PM
    • No Frills Blog
Re: Confusing Concurrencies
« Reply #63 on: January 10, 2018, 09:04:47 PM »

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 itd 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.
Logged

US 89

  • *
  • Offline Offline

  • Posts: 5793
  • 189 to Evanston

  • Location: Tallahassee, FL
  • Last Login: March 25, 2023, 09:17:39 AM
    • Utah Highways
Re: Confusing Concurrencies
« Reply #64 on: January 10, 2018, 09:26:38 PM »

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

  • *
  • Offline Offline

  • Posts: 488
  • Business route advocate

  • Location: NC 147
  • Last Login: Today at 07:01:29 PM
Re: Confusing Concurrencies
« Reply #65 on: January 11, 2018, 04:46:57 PM »

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.
Logged

Beeper1

  • *
  • Offline Offline

  • Posts: 409
  • Location: Western MA
  • Last Login: Today at 08:59:16 PM
Re: Confusing Concurrencies
« Reply #66 on: January 11, 2018, 09:27:41 PM »

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. 
Logged

webny99

  • *
  • Offline Offline

  • Posts: 12280
  • Left lane is for passing, not camping!

  • Age: 23
  • Location: Monroe County, NY
  • Last Login: Today at 06:37:05 PM
Re: Confusing Concurrencies
« Reply #67 on: January 11, 2018, 09:53:27 PM »

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  :D

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.
Logged
On April 25, 2022, I became the 20th user in forum history to Like the Forum Way, Way Too Much. And then I found that there's another way..
__ _______ ___ __ _______ _____

kphoger

  • *
  • Offline Offline

  • Posts: 25827
  • My 2 Achilles' heels: sarcasm & snark

  • Location: Wichita, KS
  • Last Login: March 24, 2023, 06:21:24 PM
Re: Confusing Concurrencies
« Reply #68 on: January 12, 2018, 01:01:57 PM »

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.
Logged
Keep right except to pass.  Yes.  You.
Visit scenic Orleans County, NY!
Male pronouns, please.

Quote from: Philip K. Dick
If you can control the meaning of words, you can control the people who must use them.

1

  • *
  • Offline Offline

  • Posts: 13352
  • Age: 24
  • Location: MA/NH border
  • Last Login: Today at 09:38:00 PM
    • Flickr account
Re: Confusing Concurrencies
« Reply #69 on: January 12, 2018, 01:03:59 PM »

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.
Logged
Clinched

Traveled, plus several state routes

kphoger

  • *
  • Offline Offline

  • Posts: 25827
  • My 2 Achilles' heels: sarcasm & snark

  • Location: Wichita, KS
  • Last Login: March 24, 2023, 06:21:24 PM
Re: Confusing Concurrencies
« Reply #70 on: January 12, 2018, 02:12:35 PM »

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.
Logged
Keep right except to pass.  Yes.  You.
Visit scenic Orleans County, NY!
Male pronouns, please.

Quote from: Philip K. Dick
If you can control the meaning of words, you can control the people who must use them.

inkyatari

  • *
  • Offline Offline

  • Posts: 1480
  • Widen I-80 through all of Illinois!

  • Age: 54
  • Location: Morris, IL
  • Last Login: April 02, 2022, 10:41:13 PM
    • Pie Factory Podcast - Classic Arcade gaming talk
Re: Confusing Concurrencies
« Reply #71 on: January 12, 2018, 02:29:25 PM »

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...
Logged
I'm never wrong, just wildly inaccurate.

kphoger

  • *
  • Offline Offline

  • Posts: 25827
  • My 2 Achilles' heels: sarcasm & snark

  • Location: Wichita, KS
  • Last Login: March 24, 2023, 06:21:24 PM
Re: Confusing Concurrencies
« Reply #72 on: January 12, 2018, 02:38:16 PM »

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.
Logged
Keep right except to pass.  Yes.  You.
Visit scenic Orleans County, NY!
Male pronouns, please.

Quote from: Philip K. Dick
If you can control the meaning of words, you can control the people who must use them.

froggie

  • *
  • Online Online

  • Posts: 12618
  • Location: Greensboro, VT
  • Last Login: Today at 11:14:36 PM
    • Froggie's Place
Re: Confusing Concurrencies
« Reply #73 on: January 12, 2018, 08:16:52 PM »

^ Not unlike US 60 in Newport News, VA.
Logged

Flint1979

  • *
  • Offline Offline

  • Posts: 8198
  • Age: 43
  • Location: Michigan
  • Last Login: Today at 07:41:17 PM
Re: Confusing Concurrencies
« Reply #74 on: January 12, 2018, 10:46:03 PM »

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 itd 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.
Logged

 


Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.