AARoads Forum

National Boards => General Highway Talk => Topic started by: ColossalBlocks on April 19, 2017, 11:16:29 AM

Title: Clusterfucked interchanges
Post by: ColossalBlocks on April 19, 2017, 11:16:29 AM
What are some interchanges in your state/city that always seem to be completely clusterfucked?

Also, I mean interchanges with so many ramps leading in too many different directions. Or say an outdated interchange in an area seeing traffic increases every day.
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on April 19, 2017, 11:21:02 AM
The 69 465 interchange in Indianapolis. Should have been upgraded literally 25 years ago. Causes the daily backup from 4-7pm. It's being partially fixed next year finally.

Nexus 6P

Title: Re: Clusterfucked interchanges
Post by: epzik8 on April 19, 2017, 12:42:27 PM
I-95/695, Exit 33/64 in Rosedale, Maryland (just northeast of Baltimore) might be one, to some extent. I think both highways lose a lane within that interchange. It's sort of difficult for traffic to merge from the ramps onto each highway.
Title: Re: Clusterfucked interchanges
Post by: michravera on April 19, 2017, 01:02:49 PM
Quote from: ColossalBlocks on April 19, 2017, 11:16:29 AM
What are some interchanges in your state/city that always seem to be completely clusterfucked?

The I-880 and US-101 junction (especially I-880 southbound) displays the phenomenon that "everyone is always in the wrong lane".  This means that, until such a time, if ever, that the interchange is completely reconfigured, no number of extra lanes will fix the problem.

The counter-intuitve, but often necessary, US-101 northbound to I-880 southbound merge is less than 100 m from the normal I-880 southbound to US-101 southbound exit. The HOV lane (which often moves close to the speed limit)  is on the far left and ends roughly at the centerline of US-101. So, southbound HOVs that want to exit to US-101 southbound have to cut across 3, no 4, no 5, lanes in order to do so. The US-101NB-to-I-880SB mergers have to cut across 2, no 3, no 4 lanes in order to get into the flow of traffic. This is the NORMAL course of events. If there is an accident on anyone of the three roadways, well, I just look for an alternate route. Traffic often moves better when one of the movements is blocked (preferably the ramp from US-101NB to I-880SB) sufficiently early on US-101. That ought to tell you everything that you need to know about the configuration!
Title: Re: Clusterfucked interchanges
Post by: Brandon on April 19, 2017, 01:19:04 PM
Around Chicago, The Circle (https://goo.gl/maps/PtjNxBiF4rq).  This one has the power to fuck up not just the Ryan, Kennedy, and Ike expressways, but also the Stevenson (with the interchange near it), the Edens, the Bishop Ford, and I-57.
Title: Re: Clusterfucked interchanges
Post by: kphoger on April 19, 2017, 02:00:50 PM
I-135/I-235/K-254 (https://goo.gl/maps/xhpLTheM2xs)

Afternoon rush hour traffic is heavy going from NB 135 to SB 235.  On that movement which probably carries half of the NB 135 traffic...
1. There is no dedicated exit lane,
2. There is a 25-mph loop ramp,
3. Traffic has to merge onto a 60-mph highway,
4. Said highway immediately narrows to one lane over a bridge.

Traffic frequently backs up for a mile due to the choke point.  I am fortunate enough to have an opposite-direction commute, to where I'm traveling southbound at the time.
Title: Re: Clusterfucked interchanges
Post by: intelati49 on April 19, 2017, 02:11:59 PM
Quote from: kphoger on April 19, 2017, 02:00:50 PM
I-135/I-235/K-254 (https://goo.gl/maps/xhpLTheM2xs)

Afternoon rush hour traffic is heavy going from NB 135 to SB 235.  On that movement which probably carries half of the NB 135 traffic...
1. There is no dedicated exit lane,
2. There is a 25-mph loop ramp,
3. Traffic has to merge onto a 60-mph highway,
4. Said highway immediately narrows to one lane over a bridge.

Traffic frequently backs up for a mile due to the choke point.  I am fortunate enough to have an opposite-direction commute, to where I'm traveling southbound at the time.

Jeez. I never realized it drops to one lane there. the short left hand exits would be bad enough.
Title: Re: Clusterfucked interchanges
Post by: kkt on April 19, 2017, 02:25:29 PM
I-90 to I-5.
Title: Re: Clusterfucked interchanges
Post by: oscar on April 19, 2017, 02:37:44 PM
Quote from: ColossalBlocks on April 19, 2017, 11:16:29 AM
What are some interchanges in your state/city that always seem to be completely clusterfucked?

ColossalBlocks, what are your your examples?
Title: Re: Clusterfucked interchanges
Post by: Max Rockatansky on April 19, 2017, 03:25:12 PM
I-10/AZ 202/AZ 51 was always a disaster when I lived in Phoenix.  All three freeways were usually running smoothly until a mile or two of that interchange...but I guess that's what happens when all that traffic converges into a single point.  Florida's Turnpike and FL 528 was probably the strangest design that I've ever countered.  From FL 528 westbound you literally have to do a 360 degree turn almost onto OBT (US 17/92/441) followed by a couple 180 degree turns to get to the southbound Turnpike.  Worse yet is that if you aren't paying attention and don't get into the left lane at this booth there is no way to get back to the Southbound Turnpike for several miles:

https://www.google.com/maps/@28.4299322,-81.4011139,3a,75y,151.17h,79.52t/data=!3m6!1e1!3m4!1serbw-yIGo9U_imqQRLGD-A!2e0!7i13312!8i6656!6m1!1e1?hl=en
Title: Re: Clusterfucked interchanges
Post by: Joe The Dragon on April 19, 2017, 04:54:05 PM
I-290 / I-294 / I-88 + local roads is a mess.

I-294 / I-55 needs work.
Title: Re: Clusterfucked interchanges
Post by: jakeroot on April 19, 2017, 05:14:48 PM
Quote from: kkt on April 19, 2017, 02:25:29 PM
I-90 to I-5.

Washington's official cluster fuck is the 167/18 interchange (https://goo.gl/So2CIR)...

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F2xMnRpH.png&hash=7bc23b437038f74a43fb09e91bb0a294ea63161d)
Title: Re: Clusterfucked interchanges
Post by: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

PS: For those wondering why I travel 60+ miles for a primary doctor, the healthcare in Danville fucking sucks (like most everything else in this godforsaken town) and the local hospital is one of the worst hospitals in Virginia. I'm definitely not the only one that drives miles for decent healthcare.
Title: Re: Clusterfucked interchanges
Post by: Mr_Northside on April 19, 2017, 05:47:16 PM
Here in the Pittsburgh area, almost all of the interchanges on I-376 between Monroeville and I-79.

Some function much better than others (depending on traffic volume), but almost all look a little CF'd to look at.
Title: Re: Clusterfucked interchanges
Post by: Brandon on April 19, 2017, 05:58:54 PM
Quote from: oscar on April 19, 2017, 02:37:44 PM
Quote from: ColossalBlocks on April 19, 2017, 11:16:29 AM
What are some interchanges in your state/city that always seem to be completely clusterfucked?

ColossalBlocks, what are your your examples?

Why do that when you can start a thread and watch it grow?
Title: Re: Clusterfucked interchanges
Post by: kkt on April 19, 2017, 06:21:34 PM
Quote from: jakeroot on April 19, 2017, 05:14:48 PM
Quote from: kkt on April 19, 2017, 02:25:29 PM
I-90 to I-5.
Washington's official cluster fuck is the 167/18 interchange (https://goo.gl/So2CIR)...

18-167 is annoying, but not as bad for sheer person-hours of delay, I think...
Title: Re: Clusterfucked interchanges
Post by: Buffaboy on April 19, 2017, 06:36:39 PM
I-90 @ NY-33, it too should've been upgraded a while ago
Title: Re: Clusterfucked interchanges
Post by: jakeroot on April 19, 2017, 06:40:08 PM
Quote from: kkt on April 19, 2017, 06:21:34 PM
Quote from: jakeroot on April 19, 2017, 05:14:48 PM
Quote from: kkt on April 19, 2017, 02:25:29 PM
I-90 to I-5.

Washington's official cluster fuck is the 167/18 interchange (https://goo.gl/So2CIR)...

18-167 is annoying, but not as bad for sheer person-hours of delay, I think...

I suspect you may be right. But the 90/5 junction isn't much of a "clusterfuck". It provides ramps for all movements, the ramps are all well-designed and are capable of supporting high speeds and lots of volume. Just turns out that today's volume is too much for it.

I think of the 167/18 junction as a true clusterfuck because the whole thing, from start to finish, was very poorly executed. It takes up a titanic amount of land, yet it provides low capacity movements in limited directions.

ColossalBlocks, please define clusterfuck. There seems to be too many ideas of what it could mean.
Title: Re: Clusterfucked interchanges
Post by: 1995hoo on April 19, 2017, 07:04:38 PM
Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

....

That entire area was always a pain in the arse. I lived on Erwin Road just east of Anderson Street from 1995 to 1998 and getting from I-85 to my apartment was a perpetual nuisance, with the portion south of Durham (heading to or from Charlotte) being the worst because NC-147 ended at 15/501 back then and everything else right around there required going through too many traffic lights. I know it's better now.
Title: Re: Clusterfucked interchanges
Post by: sparker on April 19, 2017, 07:13:29 PM
Sacramento -- and Caltrans' penchant for in-city turbines and quasi-turbines (something they've not repeated elsewhere) mixed in with local-service exits & entrances has resulted in an almost perpetual state of congestion at the Oak Park (50/99/Biz80) interchange as well as the 5/50/Biz80 interchange a couple of miles to the west (the latter complicated by the location of the Pioneer Bridge on 50/B80).  I can understand the desire to consume as little acreage as possible, but to actually place through-route movement (old I-80, current CA 99) onto low-speed turbine ramps is probably one of the least efficient and effective practices that can be deployed.  Fortunately, the 5/50 etc. interchange has a bit more room with which to work, so some ramps are less troublesome than with Oak Park; but both facilities see almost daily mainline backups as drivers toggling between the freeways slow down to make the necessary moves.  Add to that lane changes which require competing with local off/on traffic, and a recipe for daily grief comes together!  I'm up in the Sacramento area at least once a month to handle a client/subcontractor -- and I avoid that section of freeway assiduously (I tend to use Grant Line and Sunrise (E2) to get out to the Folsom area where the client is located). 

At least IDOT had the good sense back in the '70's to reroute I-90 as a through route through Chicago's Circle interchange rather than turning it 90 degrees onto the Ike at that location!         
Title: Re: Clusterfucked interchanges
Post by: formulanone on April 19, 2017, 07:28:35 PM
Quote from: oscar on April 19, 2017, 02:37:44 PM
Quote from: ColossalBlocks on April 19, 2017, 11:16:29 AM
What are some interchanges in your state/city that always seem to be completely clusterfucked?

ColossalBlocks, what are your your examples?

Thanks, now I know it's not just me that finds the daily "post-thread-and-runaway" tactic a bit annoying.
Title: Re: Clusterfucked interchanges
Post by: ColossalBlocks on April 19, 2017, 07:31:02 PM
Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

PS: For those wondering why I travel 60+ miles for a primary doctor, the healthcare in Danville fucking sucks (like most everything else in this godforsaken town) and the local hospital is one of the worst hospitals in Virginia. I'm definitely not the only one that drives miles for decent healthcare.

Speaking of Danville, why did you move there if the town is a shithole?
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on April 19, 2017, 07:31:31 PM
Quote from: epzik8 on April 19, 2017, 12:42:27 PM
I-95/695, Exit 33/64 in Rosedale, Maryland (just northeast of Baltimore) might be one, to some extent. I think both highways lose a lane within that interchange. It's sort of difficult for traffic to merge from the ramps onto each highway.
:confused: Wasn't that interchange reconfigured not too long ago?  One of the biggest changes was longer ramps.
Title: Re: Clusterfucked interchanges
Post by: jp the roadgeek on April 19, 2017, 07:52:19 PM
I-91 North to CT 15 North (and eventually, I-84 East), and CT 15 South (from I-84 West) to I-91 South.  At least the latter has an alternate if the direct interchange is a mess.  ConnDOT has plans to fix it.  Historically, the old I-84 East to I-91 North connection was a joke in which one would have to get off and use Morgan St and Columbus Blvd to connect to I-91 North.
Title: Re: Clusterfucked interchanges
Post by: LM117 on April 19, 2017, 08:19:51 PM
Quote from: ColossalBlocks on April 19, 2017, 07:31:02 PM
Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

PS: For those wondering why I travel 60+ miles for a primary doctor, the healthcare in Danville fucking sucks (like most everything else in this godforsaken town) and the local hospital is one of the worst hospitals in Virginia. I'm definitely not the only one that drives miles for decent healthcare.

Speaking of Danville, why did you move there if the town is a shithole?

It wasn't really my choice. We were all living together. My grandmother had a brother living there, who had lung cancer, so she wanted to move to be close to him. We came here in 2011. She ended up suffering a massive stroke and passed away here at the house in 2014. Her brother died a year later in 2015. Neither she nor her brother were fond of the town, either.

I'm originally from eastern NC and if I had a way right now, I'd move out in a heartbeat.
Title: Re: Clusterfucked interchanges
Post by: LM117 on April 19, 2017, 08:37:40 PM
Quote from: 1995hoo on April 19, 2017, 07:04:38 PM
Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

....

That entire area was always a pain in the arse. I lived on Erwin Road just east of Anderson Street from 1995 to 1998 and getting from I-85 to my apartment was a perpetual nuisance, with the portion south of Durham (heading to or from Charlotte) being the worst because NC-147 ended at 15/501 back then and everything else right around there required going through too many traffic lights. I know it's better now.

The worst part about that interchange (besides the weaving involved) is that very sharp curve at the end of the ramp going from NC-147 South to 15/501 South. There are no signs there warning people about that sharp curve and I almost flipped over when I went through there for the very first time last year. I was practically standing on the brake pedal. Scared the shit outta me.

That's the only thing I dread about my trips to Durham...well, other than the mind-numbing drive on NC-86 between Danville and Hillsborough since I usually get stuck behind a convoy of trucks more often than not.
Title: Re: Clusterfucked interchanges
Post by: TheHighwayMan3561 on April 19, 2017, 09:15:08 PM
Minneapolis's worst is I-94/35W. That interchange has sharp curves on both ends of I-35W, several messy left exits and entrances with short acceleration lanes, the traffic on the NB 35W-WB 94 ramp frequently backs up all the way onto the mainline, and this spills over onto the adjacent city streets.
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on April 19, 2017, 10:41:38 PM
every exit on 279 and 376 in the pittsburgh area
Title: Re: Clusterfucked interchanges
Post by: broadhurst04 on April 19, 2017, 11:01:21 PM

Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

....

The worst part about that interchange (besides the weaving involved) is that very sharp curve at the end of the ramp going from NC-147 South to 15/501 South. There are no signs there warning people about that sharp curve and I almost flipped over when I went through there for the very first time last year. I was practically standing on the brake pedal. Scared the shit outta me.

That's the only thing I dread about my trips to Durham...well, other than the mind-numbing drive on NC-86 between Danville and Hillsborough since I usually get stuck behind a convoy of trucks more often than not.

I just looked at that interchange on Google Street View. Looks like they tried to fit a cloverleaf in where there wasn't room for one.


Title: Re: Clusterfucked interchanges
Post by: LM117 on April 20, 2017, 05:20:31 AM
Quote from: broadhurst04 on April 19, 2017, 11:01:21 PM

Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

....

The worst part about that interchange (besides the weaving involved) is that very sharp curve at the end of the ramp going from NC-147 South to 15/501 South. There are no signs there warning people about that sharp curve and I almost flipped over when I went through there for the very first time last year. I was practically standing on the brake pedal. Scared the shit outta me.

That's the only thing I dread about my trips to Durham...well, other than the mind-numbing drive on NC-86 between Danville and Hillsborough since I usually get stuck behind a convoy of trucks more often than not.

I just looked at that interchange on Google Street View. Looks like they tried to fit a cloverleaf in where there wasn't room for one.

That was my impression as well.
Title: Re: Clusterfucked interchanges
Post by: jeffandnicole on April 20, 2017, 08:11:53 AM
Quote from: oscar on April 19, 2017, 02:37:44 PM
Quote from: ColossalBlocks on April 19, 2017, 11:16:29 AM
What are some interchanges in your state/city that always seem to be completely clusterfucked?

ColossalBlocks, what are your your examples?

I don't know if I've ever seen him actually answer his own questions. Pretty annoying, imo.
Title: Re: Clusterfucked interchanges
Post by: ColossalBlocks on April 20, 2017, 12:12:22 PM
Quote from: LM117 on April 19, 2017, 08:19:51 PM
Quote from: ColossalBlocks on April 19, 2017, 07:31:02 PM
Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

PS: For those wondering why I travel 60+ miles for a primary doctor, the healthcare in Danville fucking sucks (like most everything else in this godforsaken town) and the local hospital is one of the worst hospitals in Virginia. I'm definitely not the only one that drives miles for decent healthcare.

Speaking of Danville, why did you move there if the town is a shithole?

It wasn't really my choice. We were all living together. My grandmother had a brother living there, who had lung cancer, so she wanted to move to be close to him. We came here in 2011. She ended up suffering a massive stroke and passed away here at the house in 2014. Her brother died a year later in 2015. Neither she nor her brother were fond of the town, either.

I'm originally from eastern NC and if I had a way right now, I'd move out in a heartbeat.

Ahh, sorry for your losses.
Title: Re: Clusterfucked interchanges
Post by: JMAN_WiS&S on April 20, 2017, 01:35:32 PM
I-94 & I-494/694 Cloverleaf in Woodbury MN.
Title: Re: Clusterfucked interchanges
Post by: kphoger on April 20, 2017, 01:58:47 PM
Quote from: TheHighwayMan394 on April 19, 2017, 09:15:08 PM
Minneapolis's worst is I-94/35W. That interchange has sharp curves on both ends of I-35W, several messy left exits and entrances with short acceleration lanes, the traffic on the NB 35W-WB 94 ramp frequently backs up all the way onto the mainline, and this spills over onto the adjacent city streets.

I agree.  The last time I drove through there (headed from Wichita to Blaine), it was after rush hour, so I was very glad to have traffic be reasonable.
Title: Re: Clusterfucked interchanges
Post by: LM117 on April 20, 2017, 02:34:41 PM
Quote from: ColossalBlocks on April 20, 2017, 12:12:22 PM
Quote from: LM117 on April 19, 2017, 08:19:51 PM
Quote from: ColossalBlocks on April 19, 2017, 07:31:02 PM
Quote from: LM117 on April 19, 2017, 05:45:54 PM
Nothing to really speak of regarding Danville, but I hate the NC-147/US-15/501 interchange in Durham, NC. I have to commute there a lot since our primary care doctor is at one of Duke's clinics on Pickett Road.

PS: For those wondering why I travel 60+ miles for a primary doctor, the healthcare in Danville fucking sucks (like most everything else in this godforsaken town) and the local hospital is one of the worst hospitals in Virginia. I'm definitely not the only one that drives miles for decent healthcare.

Speaking of Danville, why did you move there if the town is a shithole?

It wasn't really my choice. We were all living together. My grandmother had a brother living there, who had lung cancer, so she wanted to move to be close to him. We came here in 2011. She ended up suffering a massive stroke and passed away here at the house in 2014. Her brother died a year later in 2015. Neither she nor her brother were fond of the town, either.

I'm originally from eastern NC and if I had a way right now, I'd move out in a heartbeat.

Ahh, sorry for your losses.

Thanks.
Title: Re: Clusterfucked interchanges
Post by: plain on April 20, 2017, 05:15:23 PM
Around here I would have to say the interchanges at either end of the I-95/I-64 overlap, take your pick.

The worst I've actually had the non-pleasure of driving through though is the Bruckner interchange in New York and the I-10/US 90 BUS/US 90 interchange in New Orleans  :banghead:
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.
Title: Re: Clusterfucked interchanges
Post by: Brandon on April 20, 2017, 05:57:02 PM
Quote from: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.

Clusterfucked freeway, not a clusterfucked interchange.
Title: Re: Clusterfucked interchanges
Post by: roadman65 on April 20, 2017, 06:01:52 PM
I-135 and I-235 north of Wichita as the ramp going NB on I-135 to I-235 SB gets backed up real bad during peak travel times.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 20, 2017, 06:08:02 PM
Quote from: Brandon on April 20, 2017, 05:57:02 PM
Quote from: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.

Clusterfucked freeway, not a clusterfucked interchange.
The interchange with the ramps is what causes the bad weaving....
Title: Re: Clusterfucked interchanges
Post by: Roadgeek2500 on April 20, 2017, 06:31:54 PM
One could consider the I-95 / I-76 interchange in Philly a major clusterfuck. Missing several movements due to the former both-direction tollbooth, and, most importantly, there's a traffic light at Front Street between 76 West and 95 South.
Title: Re: Clusterfucked interchanges
Post by: formulanone on April 20, 2017, 06:42:23 PM
I-476 and I-81 in Scranton strikes me as an elegant exercise in bureaucracy with all the tangled complexity of my vas deferens.

For sure, there's topography to get around; yet it seems like either a planned extension of I-476 just never occurred, somebody didn't want to give up the sweet lucre by installing a time-wasting tollbooth at the end, and nobody wanted it to connect directly to I-81 and US Route 11 for fear of missing Scranton by a mile.

Or something else? I'm not an expert in this area.
Title: Re: Clusterfucked interchanges
Post by: ColossalBlocks on April 20, 2017, 07:27:14 PM
Quote from: jakeroot on April 19, 2017, 06:40:08 PM
Quote from: kkt on April 19, 2017, 06:21:34 PM
Quote from: jakeroot on April 19, 2017, 05:14:48 PM
Quote from: kkt on April 19, 2017, 02:25:29 PM
I-90 to I-5.

Washington's official cluster fuck is the 167/18 interchange (https://goo.gl/So2CIR)...

18-167 is annoying, but not as bad for sheer person-hours of delay, I think...

I suspect you may be right. But the 90/5 junction isn't much of a "clusterfuck". It provides ramps for all movements, the ramps are all well-designed and are capable of supporting high speeds and lots of volume. Just turns out that today's volume is too much for it.

I think of the 167/18 junction as a true clusterfuck because the whole thing, from start to finish, was very poorly executed. It takes up a titanic amount of land, yet it provides low capacity movements in limited directions.

ColossalBlocks, please define clusterfuck. There seems to be too many ideas of what it could mean.

I mean't it with two things. Like say, an interchange with so many ramps leading in too many different directions. Or say an outdated interchange in an area seeing traffic increases every day.
Title: Re: Clusterfucked interchanges
Post by: DeaconG on April 20, 2017, 07:59:01 PM
I-4 and FL 408 in Orlando...still partially a trumpet along with those two new ramps they built, but still a mess. The I-4 Ultimate HOT lanes are also including the buildout of this interchange and the elimination of the rest of the trumpet, which can't happen soon enough.

Also, I-4 and Florida's Turnpike is a major pain in the ass at rush hour and the Beachline/Turnpike/OBT clusterfuck is well...a clusterfuck!
Title: Re: Clusterfucked interchanges
Post by: Max Rockatansky on April 20, 2017, 08:05:07 PM
Quote from: DeaconG on April 20, 2017, 07:59:01 PM
I-4 and FL 408 in Orlando...still partially a trumpet along with those two new ramps they built, but still a mess. The I-4 Ultimate HOT lanes are also including the buildout of this interchange and the elimination of the rest of the trumpet, which can't happen soon enough.

Also, I-4 and Florida's Turnpike is a major pain in the ass at rush hour and the Beachline/Turnpike/OBT clusterfuck is well...a clusterfuck!

From the 408 they actually back up sometimes for a mile or two from the ramp heading onto I-4.  Usually you can blow by people in the left lane but you always had to look out for someone getting fed up and jumping back into traffic suddenly.
Title: Re: Clusterfucked interchanges
Post by: DeaconG on April 20, 2017, 08:14:27 PM
Quote from: Max Rockatansky on April 20, 2017, 08:05:07 PM
Quote from: DeaconG on April 20, 2017, 07:59:01 PM
I-4 and FL 408 in Orlando...still partially a trumpet along with those two new ramps they built, but still a mess. The I-4 Ultimate HOT lanes are also including the buildout of this interchange and the elimination of the rest of the trumpet, which can't happen soon enough.

Also, I-4 and Florida's Turnpike is a major pain in the ass at rush hour and the Beachline/Turnpike/OBT clusterfuck is well...a clusterfuck!

From the 408 they actually back up sometimes for a mile or two from the ramp heading onto I-4.  Usually you can blow by people in the left lane but you always had to look out for someone getting fed up and jumping back into traffic suddenly.

Too true, and the northbound ramp from I-4 (the old trumpet) will create backups too; inside the trumpet you will slow to a crawl while folks jockey for position. We're gonna have to wait at least two years for that to get resolved...and not soon enough in my opinion.

Not including a modification/rebuild with the Turnpike at I-4 was borderline criminal in my opinion, the Turnpike will 'eventually' get to it but in the meantime we suffer. I used to work in that area two years ago and I could guarantee a major backup at that interchange during rush hour all the way down to Kirkman. If they'd have built C/D lanes from the Conroy Blvd exit south to just past where the Turnpike crosses over it would have alleviated it, but no, we can't do that...
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on April 20, 2017, 08:51:27 PM
Quote from: formulanone on April 20, 2017, 06:42:23 PM
I-476 and I-81 in Scranton strikes me as an elegant exercise in bureaucracy with all the tangled complexity of my vas deferens.

For sure, there's topography to get around; yet it seems like either a planned extension of I-476 just never occurred, somebody didn't want to give up the sweet lucre by installing a time-wasting tollbooth at the end, and nobody wanted it to connect directly to I-81 and US Route 11 for fear of missing Scranton by a mile.

Or something else? I'm not an expert in this area.

we have a winner!  that has to be the worst design i've ever seen, but i'm sure someone will mention another pennsylvania highway will be worse.
Title: Re: Clusterfucked interchanges
Post by: Arkansastravelguy on April 20, 2017, 10:08:33 PM
I'll nominate the 55 cloverleaf at Crump Blvd for Tennessee


iPhone
Title: Re: Clusterfucked interchanges
Post by: CrystalWalrein on April 20, 2017, 10:15:02 PM
Garden State Parkway and Atlantic City Expressway. I'll say it before and I'll say it again.

ACE exits 9 and 28 certainly qualify as well.
Title: Re: Clusterfucked interchanges
Post by: jakeroot on April 20, 2017, 11:12:17 PM
Quote from: CrystalWalrein on April 20, 2017, 10:15:02 PM
I'll say it before

Too late.

:D
Title: Re: Clusterfucked interchanges
Post by: sparker on April 21, 2017, 04:39:25 AM
Quote from: Arkansastravelguy on April 20, 2017, 10:08:33 PM
I'll nominate the 55 cloverleaf at Crump Blvd for Tennessee


iPhone

I was under the impression that that interchange was in the process of rebuilding (unless for some reason TNDOT pulled the funding) with through lanes for 55.  For several years in the early '00's I was on that very road on trips to Atlanta and -- just like anyone with any sense -- found the arrangement almost laughable in either direction.  I certainly hope the project is still active and underway!
Title: Re: Clusterfucked interchanges
Post by: fillup420 on April 21, 2017, 09:05:00 AM
Death Valley in Greensboro, NC is the merge point of I-40, I-85 Business, US 29/70 and US 220. There are left and right exits/entrances within half-mile of each other. I-40 and Business 85 merge so close to the Randleman Rd exit that 2 separate ramp sets are required. For about a mile, the road is signed as:
I-40, I-85 Business, US 29/70/220 (and US 421 used to be routed along here too).

https://www.google.com/maps/@36.0309201,-79.8052442,15z
Title: Re: Clusterfucked interchanges
Post by: Max Rockatansky on April 21, 2017, 09:33:54 AM
Quote from: fillup420 on April 21, 2017, 09:05:00 AM
Death Valley in Greensboro, NC is the merge point of I-40, I-85 Business, US 29/70 and US 220. There are left and right exits/entrances within half-mile of each other. I-40 and Business 85 merge so close to the Randleman Rd exit that 2 separate ramp sets are required. For about a mile, the road is signed as:
I-40, I-85 Business, US 29/70/220 (and US 421 used to be routed along here too).

https://www.google.com/maps/@36.0309201,-79.8052442,15z

(https://c1.staticflickr.com/3/2835/32766569953_d7f500c973_h.jpg) (https://flic.kr/p/RVteFg)85IBLb (https://flic.kr/p/RVteFg) by Max Rockatansky (https://www.flickr.com/photos/151828809@N08/), on Flickr
Title: Re: Clusterfucked interchanges
Post by: vdeane on April 21, 2017, 12:48:19 PM
Quote from: formulanone on April 20, 2017, 06:42:23 PM
I-476 and I-81 in Scranton strikes me as an elegant exercise in bureaucracy with all the tangled complexity of my vas deferens.

For sure, there's topography to get around; yet it seems like either a planned extension of I-476 just never occurred, somebody didn't want to give up the sweet lucre by installing a time-wasting tollbooth at the end, and nobody wanted it to connect directly to I-81 and US Route 11 for fear of missing Scranton by a mile.

Or something else? I'm not an expert in this area.
I-476 was indeed planned to extend north, all the way to NY along what is now I-81.  Thus, "exit" 131 was originally intended to, in fact, be a true exit (with US 6/11).  The connection to I-81 was grafted on later.  There are plans to fix this as part of the "Scranton Beltway" idea.  Could take a while to get done though.

Quote from: silverback1065 on April 20, 2017, 08:51:27 PM
Quote from: formulanone on April 20, 2017, 06:42:23 PM
I-476 and I-81 in Scranton strikes me as an elegant exercise in bureaucracy with all the tangled complexity of my vas deferens.

For sure, there's topography to get around; yet it seems like either a planned extension of I-476 just never occurred, somebody didn't want to give up the sweet lucre by installing a time-wasting tollbooth at the end, and nobody wanted it to connect directly to I-81 and US Route 11 for fear of missing Scranton by a mile.

Or something else? I'm not an expert in this area.

we have a winner!  that has to be the worst design i've ever seen, but i'm sure someone will mention another pennsylvania highway will be worse.
Breezewood?
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:
Title: Re: Clusterfucked interchanges
Post by: hotdogPi on April 21, 2017, 12:58:11 PM
Quote from: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:

I-95 has many interchanges with I-295...
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 01:03:00 PM
Quote from: 1 on April 21, 2017, 12:58:11 PM
Quote from: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:

I-95 has many interchanges with I-295...
I-95 thru Delaware or thru Pa and jersey?
Title: Re: Clusterfucked interchanges
Post by: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 01:21:25 PM
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
Yes I am thank you kp. I wish they would realize that lack of transportation in delaware is the reason it isnt growing as fast. Maybe the new 301 highway will change things.
Title: Re: Clusterfucked interchanges
Post by: D-Dey65 on April 21, 2017, 01:37:57 PM
Quote from: jakeroot on April 19, 2017, 05:14:48 PM
Washington's official cluster fuck is the 167/18 interchange (https://goo.gl/So2CIR)...

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F2xMnRpH.png&hash=7bc23b437038f74a43fb09e91bb0a294ea63161d)

Actually, that doesn't look so bad. It sure beats Southern State Parkway at Meadowbrook Parkway and Meadowbrook Road.

Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 01:45:19 PM
https://www.google.com/maps/@39.7050403,-75.5874447,15z/data=!3m1!1e3 (https://www.google.com/maps/@39.7050403,-75.5874447,15z/data=!3m1!1e3)
Look at this beauty.
Title: Re: Clusterfucked interchanges
Post by: kkt on April 21, 2017, 02:16:35 PM
Quote from: vdeane on April 21, 2017, 12:48:19 PM
Breezewood?

In order to be a clusterfucked interchange, it first must be an interchange.   :D
Title: Re: Clusterfucked interchanges
Post by: jakeroot on April 21, 2017, 02:29:10 PM
Quote from: D-Dey65 on April 21, 2017, 01:37:57 PM
Quote from: jakeroot on April 19, 2017, 05:14:48 PM
Washington's official cluster fuck is the 167/18 interchange (https://goo.gl/So2CIR)...

http://i.imgur.com/2xMnRpH.png

Actually, that doesn't look so bad. It sure beats Southern State Parkway at Meadowbrook Parkway and Meadowbrook Road.

It's not as bad as some of the junctions out east, for sure. I think of it as a clusterfuck because it takes up a massive amount of land (relative to other interchanges around here), yet there are several busy movements that are not provided for. The movements that are provided for are low-capacity.
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on April 21, 2017, 02:31:21 PM
Quote from: 1 on April 21, 2017, 12:58:11 PM
Quote from: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:

I-95 has many interchanges with I-295...
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
I have to wonder if Tonytone's US 1 reference, as opposed to the correct DE 1, was what threw 1 off; especially since the current I-95/295 handoff in NJ is at the US 1 interchange.
Title: Re: Clusterfucked interchanges
Post by: Rothman on April 21, 2017, 02:35:50 PM
Quote from: Tonytone on April 21, 2017, 01:21:25 PM
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
Yes I am thank you kp. I wish they would realize that lack of transportation in delaware is the reason it isnt growing as fast. Maybe the new 301 highway will change things.
I don't know about that.  I think the bigger issue is lack of population and no attractions for increased move-ins in the Slower Lower.  Building larger roads will not fix those conditions.

It just isn't on the way to anywhere.

See: Binghamton, NY or Duluth, MN...
Title: Re: Clusterfucked interchanges
Post by: kphoger on April 21, 2017, 03:11:36 PM
Quote from: PHLBOS on April 21, 2017, 02:31:21 PM
Quote from: 1 on April 21, 2017, 12:58:11 PM
Quote from: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:

I-95 has many interchanges with I-295...
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
I have to wonder if Tonytone's US 1 reference, as opposed to the correct DE 1, was what threw 1 off; especially since the current I-95/295 handoff in NJ is at the US 1 interchange.

Oh yeah, for sure.  I didn't catch that.  US-1 is miles away from the interchange in question.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 03:18:49 PM
Quote from: kphoger on April 21, 2017, 03:11:36 PM
Quote from: PHLBOS on April 21, 2017, 02:31:21 PM
Quote from: 1 on April 21, 2017, 12:58:11 PM
Quote from: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:

I-95 has many interchanges with I-295...
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
I have to wonder if Tonytone's US 1 reference, as opposed to the correct DE 1, was what threw 1 off; especially since the current I-95/295 handoff in NJ is at the US 1 interchange.
How did it throw it off if it was the first portion that was built?
Oh yeah, for sure.  I didn't catch that.  US-1 is miles away from the interchange in question.
U.S-1 By the mall is the first portion of the "US-1 Highway system" It was built in 93 and from the mall past to the toll after the bridge is a problem area.
Title: Re: Clusterfucked interchanges
Post by: kphoger on April 21, 2017, 03:25:27 PM
Quote from: Tonytone on April 21, 2017, 03:18:49 PM
Quote from: kphoger on April 21, 2017, 03:11:36 PM
Quote from: PHLBOS on April 21, 2017, 02:31:21 PM
Quote from: 1 on April 21, 2017, 12:58:11 PM
Quote from: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:

I-95 has many interchanges with I-295...
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
I have to wonder if Tonytone's US 1 reference, as opposed to the correct DE 1, was what threw 1 off; especially since the current I-95/295 handoff in NJ is at the US 1 interchange.
How did it throw it off if it was the first portion that was built?
Oh yeah, for sure.  I didn't catch that.  US-1 is miles away from the interchange in question.
U.S-1 By the mall is the first portion of the "US-1 Highway system" It was built in 93 and from the mall past to the toll after the bridge is a problem area.

Wait, what?  Christina Mall is near the interchange of Interstate 95 and Delaware State Route 1.  US-1 doesn't even enter the state of Delaware at all.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 03:29:10 PM
Quote from: Rothman on April 21, 2017, 02:35:50 PM
Quote from: Tonytone on April 21, 2017, 01:21:25 PM
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
Yes I am thank you kp. I wish they would realize that lack of transportation in delaware is the reason it isnt growing as fast. Maybe the new 301 highway will change things.
I don't know about that.  I think the bigger issue is lack of population and no attractions for increased move-ins in the Slower Lower.  Building larger roads will not fix those conditions.

It just isn't on the way to anywhere.

See: Binghamton, NY or Duluth, MN...
I believe a major roadway connecting to another major roadway causes development around the area. Its is even said because of a "lack" of Thru roadways in the area there is not that much people and development in that area of Middletown and up. Also new communities and stores are being planned around that area of highway. I-95 connects to the 1 and 301 is gonna complete that connection around 95 to the north. I wouldn't be surprised if people driving thru the area where the highway is located find interest in moving to delaware.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 03:30:56 PM
Quote from: kphoger on April 21, 2017, 03:25:27 PM
Quote from: Tonytone on April 21, 2017, 03:18:49 PM
Quote from: kphoger on April 21, 2017, 03:11:36 PM
Quote from: PHLBOS on April 21, 2017, 02:31:21 PM
Quote from: 1 on April 21, 2017, 12:58:11 PM
Quote from: Tonytone on April 21, 2017, 12:54:25 PM
I-95 interchange with I-295. It goes from 5-6 lanes to 2 lanes, currently they are rebuilding i-295 but the traffic still backs up to the Christina mall which if some of you are familiar is by the U.S 1 I-95 Interchange!!! :colorful:

I-95 has many interchanges with I-295...
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
I have to wonder if Tonytone's US 1 reference, as opposed to the correct DE 1, was what threw 1 off; especially since the current I-95/295 handoff in NJ is at the US 1 interchange.
How did it throw it off if it was the first portion that was built?
Oh yeah, for sure.  I didn't catch that.  US-1 is miles away from the interchange in question.
U.S-1 By the mall is the first portion of the "US-1 Highway system" It was built in 93 and from the mall past to the toll after the bridge is a problem area.

Wait, what?  Christina Mall is near the interchange of Interstate 95 and Delaware State Route 1.  US-1 doesn't even enter the state of Delaware at all.
Thats the problem when I say U.S 1 I mean Delaware route 1. it's all the same thing lol.
Title: Re: Clusterfucked interchanges
Post by: kkt on April 21, 2017, 03:39:35 PM
Quote from: jakeroot on April 21, 2017, 02:29:10 PM
Quote from: D-Dey65 on April 21, 2017, 01:37:57 PM
Quote from: jakeroot on April 19, 2017, 05:14:48 PM
Washington's official cluster fuck is the 167/18 interchange (https://goo.gl/So2CIR)...

http://i.imgur.com/2xMnRpH.png

Actually, that doesn't look so bad. It sure beats Southern State Parkway at Meadowbrook Parkway and Meadowbrook Road.

It's not as bad as some of the junctions out east, for sure. I think of it as a clusterfuck because it takes up a massive amount of land (relative to other interchanges around here), yet there are several busy movements that are not provided for. The movements that are provided for are low-capacity.

Yes, it shows its age.  What, they Kent valley isn't all farmland anymore?  The interchange was built on the cheap to allow some movements directly, but others through the existing interchange with the West Valley Highway...
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on April 21, 2017, 04:21:54 PM
Quote from: Tonytone on April 21, 2017, 03:30:56 PM
Quote from: kphoger on April 21, 2017, 03:25:27 PMWait, what?  Christina Mall is near the interchange of Interstate 95 and Delaware State Route 1.  US-1 doesn't even enter the state of Delaware at all.
Thats the problem when I say U.S 1 I mean Delaware route 1. it's all the same thing lol.
This is one case where it's might've been better just to say Route XX rather than US XX or SR XX.  It's what most people refer to routes in the Northeast/Mid-Atlantic regions anyway.

Nonetheless, I agree w/Kphoger that US 1 and DE 1 are not the same road/thing.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 05:05:10 PM
I got it now thanks. But the chance for SR1 & US1 to connect is still possible.


iPhone
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on April 21, 2017, 06:00:25 PM
Quote from: Tonytone on April 21, 2017, 05:05:10 PMBut the chance for SR1 & US1 to connect is still possible.
We'd sooner see DE 1 become the real I-99 (in terms of the grid) than it being extended to US 1.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on April 21, 2017, 06:02:46 PM
Quote from: PHLBOS on April 21, 2017, 06:00:25 PM
Quote from: Tonytone on April 21, 2017, 05:05:10 PMBut the chance for SR1 & US1 to connect is still possible.
We'd sooner see DE 1 become the real I-99 (in terms of the grid) than it being extended to US 1.
Yea, i think de 1 has some problems to fix before it can even become I-99


iPhone
Title: Re: Clusterfucked interchanges
Post by: D-Dey65 on April 22, 2017, 10:03:23 AM
Quote from: Rothman on April 21, 2017, 02:35:50 PM
Quote from: Tonytone on April 21, 2017, 01:21:25 PM
Quote from: kphoger on April 21, 2017, 01:18:03 PM
His location says "Delaware," so I assume the Wilmington area.
Yes I am thank you kp. I wish they would realize that lack of transportation in delaware is the reason it isnt growing as fast. Maybe the new 301 highway will change things.
I don't know about that.  I think the bigger issue is lack of population and no attractions for increased move-ins in the Slower Lower.  Building larger roads will not fix those conditions.
301 can be viewed as a reliever route for I-95, though. I took that to get to a film festival in Middletown back in 2015, and on my most recent road trip to NYC, I took that way both north and south. I'm kind of disappointed I didn't stop at that restaurant in Port Royal Crossroads, Virginia on my way up, but I wasn't that hungry at the time.


Anyway, getting back on topic, how about I-87-287-NY 17 in Suffern, New York. Did I mention that I liked it better before? I think I have.

Title: Re: Clusterfucked interchanges
Post by: noelbotevera on April 22, 2017, 10:46:43 AM
Quote from: formulanone on April 19, 2017, 07:28:35 PM
Quote from: oscar on April 19, 2017, 02:37:44 PM
Quote from: ColossalBlocks on April 19, 2017, 11:16:29 AM
What are some interchanges in your state/city that always seem to be completely clusterfucked?

ColossalBlocks, what are your your examples?

Thanks, now I know it's not just me that finds the daily "post-thread-and-runaway" tactic a bit annoying.
I'll admit, I have done it before. I should post more often in my threads, but my posts aren't terribly substantial and arguments I make are weak.

Let's give it up for...the Eisenhower Interchange in Harrisburg! (https://www.google.com/maps/@40.2533121,-76.8119431,2280m/data=!3m1!1e3)
Title: Re: Clusterfucked interchanges
Post by: Arkansastravelguy on April 23, 2017, 06:08:09 PM
Quote from: sparker on April 21, 2017, 04:39:25 AM
Quote from: Arkansastravelguy on April 20, 2017, 10:08:33 PM
I'll nominate the 55 cloverleaf at Crump Blvd for Tennessee


iPhone

I was under the impression that that interchange was in the process of rebuilding (unless for some reason TNDOT pulled the funding) with through lanes for 55.  For several years in the early '00's I was on that very road on trips to Atlanta and -- just like anyone with any sense -- found the arrangement almost laughable in either direction.  I certainly hope the project is still active and underway!

Since I've been there (about a month ago) it's just a 2 lanes cloverleaf 55 northbound. Which if a semi is taking is really one lane.


iPhone
Title: Re: Clusterfucked interchanges
Post by: jlwm on April 24, 2017, 02:49:18 AM
The 610 West Loop/ I-69/US59 Southwest Freeway interchange.
https://www.google.com/maps/@29.7298623,-95.4569902,16.29z

It's an early 4-level stack completed in 1962. It was Houston's first stack interchange that's remained relatively unchanged over the last 55 years save a few modifications. Since it originally opened, it's become one of the state's largest bottlenecks, complicated by the fact that it's in close proximity to the Galleria and Uptown, the nearby terminus of the Westpark Tollway, sharp ramps with not enough capacity, and weaving issues caused by exit and entrance ramps to and from nearby Chimney Rock Blvd. on 69/59.

There's a fix coming soon. Over the next few years, the interchange will be rebuilt to eliminate many of the problems. Construction is slated to start later this year and wrap up in 2021.
http://www.txdot.gov/inside-txdot/projects/studies/houston/59-610.html
Title: Re: Clusterfucked interchanges
Post by: roadman65 on April 24, 2017, 06:23:25 AM
I think this whole thread, though interesting topic for discussion, is pretty ambiguous as pretty much every urban interchange could be classified as that.  I-4 at Florida's Turnpike is one that backs up on to WB I-4 through a trumpet interchange, thus making traffic merging onto I-4 from Conroy Road have to wait in stand still traffic.  The weaving between the merge and exit and the double lane drop causes that of course, but the reason for the slowdown around the trumpet is a mystery.

The ramp is not a high speed flyover, but not one where you need to slow down to 5 mph either, although traffic does slow to a creep.  It is volume but then again even with the large amounts of cars and the fact the road is wide open after the curves and its not like every human is over paranoid to drive the trumpet its a mystery.  If it were the fact the volume of traffic, that would only account for a jam leading into the interchange not inside it.

Right now the I-4 ultimate is only doing some work to relieve it.  There are no plans to braid the ramps to stop the traffic problem from Conroy to WB I-4 which really needs, so its clusterfucked for a long time this one.  Maybe inside the ramp we will see improvements though, but not as long as you have the two ramps so close the before hand weave bottleneck won't go away.

I guess its which clusterfuck stands out more, so in Orlando that one takes the cake unless there are some on other freeways I have not yet discovered, but still one to be mentioned anyway.
Title: Re: Clusterfucked interchanges
Post by: JMoses24 on April 25, 2017, 01:18:20 PM
I present for your consideration, the I-71/Ridge Road/Norwood Lateral interchange. ESPECIALLY northbound.

https://goo.gl/maps/E9fq7xoNreJ2

Why? Mainly, this.

https://goo.gl/maps/HsDZUguWUWq

The two right lanes drop (although exit 8C is a not-insignificant distance past exit 8B), causing weaving as people realize too late that they are in an exit only lane. That leads to the requisite cluster-foxtrot every afternoon around, oh, 4:30pm or so.
Title: Re: Clusterfucked interchanges
Post by: kphoger on April 25, 2017, 01:24:41 PM
Quote from: JMoses24 on April 25, 2017, 01:18:20 PM
I present for your consideration, the I-71/Ridge Road/Norwood Lateral interchange. ESPECIALLY northbound.

https://goo.gl/maps/E9fq7xoNreJ2

Why? Mainly, this.

https://goo.gl/maps/HsDZUguWUWq

The two right lanes drop (although exit 8C is a not-insignificant distance past exit 8B), causing weaving as people realize too late that they are in an exit only lane. That leads to the requisite cluster-foxtrot every afternoon around, oh, 4:30pm or so.

That reminds me of where NB I-635 hits SB I-29 on the north end of Kansas City (a useful bypass of downtown if following I-35).  Two lanes of 635 traffic enter the highway, and then both of those lanes are exit-only at the next exit.  Fortunately, there's about a mile between the two points and traffic isn't super thick.
Title: Re: Clusterfucked interchanges
Post by: RobbieL2415 on April 25, 2017, 02:51:02 PM
I-95 and the Hutchison River Pkwy, Bronx, NY.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FNpsl3Em.jpg&hash=4dfb7f68dcb3af586ac32b93f591c9838e963892)
Title: Re: Clusterfucked interchanges
Post by: roadman on April 25, 2017, 03:10:47 PM
Since it hasn't been mentioned yet, I'll add I-95 (MA 128) at I-93 in Woburn/Reading/Stoneham (MA).  Failing a complete rebuild, which was first proposed in the early 1990s but has been stalled by the NIMBYS on one side and the Woburn politicians on the other side ever since, there are actually two relatively simple things MassDOT could do to improve traffic flow through this area.

First would be to extend the fourth lane on southbound I-95 (128), which currently begins at the end of the ramp from I-93 southbound, to the on-ramp from Route 28 southbound.  By adding an additional lane through the interchange, this would reduce much of the current conflict between southbound through traffic and traffic weaving to/from I-93 north and south.

Second would be to extend the added lane on northbound I-95 (128) between the ramps from I-93 northbound and Route 28 southbound to north of both Route 28 ramps.  This would give the traffic coming from the right "exit only" lane (former shoulder) between Montvale Avenue and I-95 north additional area to merge with the mainline traffic.  Of course, I-95 (128) should really be widened to four lanes each way between Stoneham and Lynnfield anyway, but that's a different subject altogether (that's a different subject).
Title: Re: Clusterfucked interchanges
Post by: freebrickproductions on April 25, 2017, 05:56:40 PM
The I-65 and I-20/I-59 interchange in Birmingham, AL will be one of these once ALDOT's done with it.
Title: Re: Clusterfucked interchanges
Post by: lordsutch on April 25, 2017, 10:22:00 PM
Quote from: sparker on April 21, 2017, 04:39:25 AM
Quote from: Arkansastravelguy on April 20, 2017, 10:08:33 PM
I'll nominate the 55 cloverleaf at Crump Blvd for Tennessee

I was under the impression that that interchange was in the process of rebuilding (unless for some reason TNDOT pulled the funding) with through lanes for 55.  For several years in the early '00's I was on that very road on trips to Atlanta and -- just like anyone with any sense -- found the arrangement almost laughable in either direction.  I certainly hope the project is still active and underway!

It was supposed to have started already but they delayed it to study doing the rebuild under traffic - originally the plan was to close the adjacent "old bridge" entirely during construction so it could be done faster and cheaper. Apparently there were also some problems with the traffic estimates, according to the project website (http://www.tn.gov/tdot/topic/i-55-crump).

A few years ago they did widen the NB loop ramp to two lanes and close the loop from EB Crump to NB Riverside, so it's no longer a full cloverleaf, which has helped a little bit.
Title: Re: Clusterfucked interchanges
Post by: RestrictOnTheHanger on April 25, 2017, 11:13:10 PM
My vote is the Kew Gardens interchange in Kew Gardens, Queens, NY. The Grand Central Parkway, Jackie Robinson Parkway, Van Wyck Expressway (I-678),  and Union Turnpike all intersect here.

Van Wyck Expy
Van Wyck Expy, Jamaica, NY 11435

https://goo.gl/maps/YXuzh5E4CTA2
Title: Re: Clusterfucked interchanges
Post by: Roadsguy on April 26, 2017, 09:48:31 AM
Title: Re: Clusterfucked interchanges
Post by: hotdogPi on April 26, 2017, 09:50:07 AM
Quote from: roadman on April 25, 2017, 03:10:47 PM
Since it hasn't been mentioned yet, I'll add I-95 (MA 128) at I-93 in Woburn/Reading/Stoneham (MA).  Failing a complete rebuild, which was first proposed in the early 1990s but has been stalled by the NIMBYS on one side and the Woburn politicians on the other side ever since, there are actually two relatively simple things MassDOT could do to improve traffic flow through this area.

First would be to extend the fourth lane on southbound I-95 (128), which currently begins at the end of the ramp from I-93 southbound, to the on-ramp from Route 28 southbound.  By adding an additional lane through the interchange, this would reduce much of the current conflict between southbound through traffic and traffic weaving to/from I-93 north and south.

Second would be to extend the added lane on northbound I-95 (128) between the ramps from I-93 northbound and Route 28 southbound to north of both Route 28 ramps.  This would give the traffic coming from the right "exit only" lane (former shoulder) between Montvale Avenue and I-95 north additional area to merge with the mainline traffic.  Of course, I-95 (128) should really be widened to four lanes each way between Stoneham and Lynnfield anyway, but that's a different subject altogether (that's a different subject).

That section of 128 is really bad during rush hour, but outside of rush hour, it's fine.
Title: Re: Clusterfucked interchanges
Post by: Roadgeekteen on April 26, 2017, 10:11:58 AM
It's not there anymore, but the Peobady interchange between I-95 and 128 used to make me carsick.
Title: Re: Clusterfucked interchanges
Post by: roadman on April 26, 2017, 10:51:54 AM
Quote from: Roadgeekteen on April 26, 2017, 10:11:58 AM
It's not there anymore, but the Peabody interchange between I-95 and 128 used to make me carsick.
I presume you mean when you had to use US 1 between Lynnfield and Danvers to get from I-95 to 128, before there was a direct interchange between the two roads.
Title: Re: Clusterfucked interchanges
Post by: Roadgeekteen on April 26, 2017, 11:02:56 AM
Quote from: roadman on April 26, 2017, 10:51:54 AM
Quote from: Roadgeekteen on April 26, 2017, 10:11:58 AM
It's not there anymore, but the Peabody interchange between I-95 and 128 used to make me carsick.
I presume you mean when you had to use US 1 between Lynnfield and Danvers to get from I-95 to 128, before there was a direct interchange between the two roads.
No, ment between I-95 and 95.
Title: Re: Clusterfucked interchanges
Post by: capt.ron on April 26, 2017, 11:50:56 AM
Quote from: Arkansastravelguy on April 20, 2017, 10:08:33 PM
I'll nominate the 55 cloverleaf at Crump Blvd for Tennessee


iPhone
Argh... I HATE that interchange with the intensity of 1000 suns! A while back TNDOT bandaided the interchange by adding a lane from NB i-55 to the bridge section but still, the interchange was a POS to begin with.
Title: Re: Clusterfucked interchanges
Post by: formulanone on April 26, 2017, 11:54:14 AM
Quote from: vdeane on April 21, 2017, 12:48:19 PM
Quote from: formulanone on April 20, 2017, 06:42:23 PM
I-476 and I-81 in Scranton strikes me as an elegant exercise in bureaucracy with all the tangled complexity of my vas deferens.

For sure, there's topography to get around; yet it seems like either a planned extension of I-476 just never occurred, somebody didn't want to give up the sweet lucre by installing a time-wasting tollbooth at the end, and nobody wanted it to connect directly to I-81 and US Route 11 for fear of missing Scranton by a mile.

Or something else? I'm not an expert in this area.
I-476 was indeed planned to extend north, all the way to NY along what is now I-81.  Thus, "exit" 131 was originally intended to, in fact, be a true exit (with US 6/11).  The connection to I-81 was grafted on later.  There are plans to fix this as part of the "Scranton Beltway" idea.  Could take a while to get done though.

Ah, that makes sense. Thanks for that.
Title: Re: Clusterfucked interchanges
Post by: capt.ron on April 26, 2017, 11:55:33 AM
Not exactly a clusterf**k but a crappy design to begin with: The I-15 / I-40 interchange in Barstow. For some reason, there is NO direct ramp from I-40 westbound to I-15 northbound. Why Caltrans after all these years didn't put one in is beyond me. The interchange dates back to the mid 60's!
Title: Re: Clusterfucked interchanges
Post by: Roadgeekteen on April 26, 2017, 12:25:06 PM
Quote from: capt.ron on April 26, 2017, 11:55:33 AM
Not exactly a clusterf**k but a crappy design to begin with: The I-15 / I-40 interchange in Barstow. For some reason, there is NO direct ramp from I-40 westbound to I-15 northbound. Why Caltrans after all these years didn't put one in is beyond me. The interchange dates back to the mid 60's!
there is little reson to go that way. Only the residents of a few select towns would use it.
Title: Re: Clusterfucked interchanges
Post by: hm insulators on April 26, 2017, 12:32:15 PM
The I-405 interchange with US 101 in L.A.'s San Fernando Valley and I-605 and I-5 in I think it's Santa Fe Springs or Whittier or something like that. I-10 at the I-605 used to be another "clusterfuck" but didn't they do some construction work on that or is it still just a mess?
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on April 26, 2017, 02:34:27 PM
Quote from: Roadgeekteen on April 26, 2017, 11:02:56 AM
Quote from: roadman on April 26, 2017, 10:51:54 AM
Quote from: Roadgeekteen on April 26, 2017, 10:11:58 AM
It's not there anymore, but the Peabody interchange between I-95 and 128 used to make me carsick.
I presume you mean when you had to use US 1 between Lynnfield and Danvers to get from I-95 to 128, before there was a direct interchange between the two roads.
No, ment between I-95 and 95.
I think you need to elaborate regarding "not there anymore" (your words).  Both the direct-connection between I-95 & MA 128 (opened circa 1988) (https://www.google.com/maps/place/Peabody,+MA/@42.5257005,-70.979305,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) and the once-temporary/now permanent, partial-movement I-95/US 1 connection in Peabody built circa 1974 (https://www.google.com/maps/place/Peabody,+MA/@42.5418955,-70.9876768,16.25z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) that Roadman referred to are still there.

If you were referring to the I-95 (MA 128)/US 1 interchange built circa 1962 (https://www.google.com/maps/place/Peabody,+MA/@42.522241,-71.0006416,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) at the Peabody/Lynnfield line; that one's still there as well.
Title: Re: Clusterfucked interchanges
Post by: Roadgeekteen on April 26, 2017, 04:00:06 PM
Quote from: PHLBOS on April 26, 2017, 02:34:27 PM
Quote from: Roadgeekteen on April 26, 2017, 11:02:56 AM
Quote from: roadman on April 26, 2017, 10:51:54 AM
Quote from: Roadgeekteen on April 26, 2017, 10:11:58 AM
It's not there anymore, but the Peabody interchange between I-95 and 128 used to make me carsick.
I presume you mean when you had to use US 1 between Lynnfield and Danvers to get from I-95 to 128, before there was a direct interchange between the two roads.
No, ment between I-95 and 95.
I think you need to elaborate regarding "not there anymore" (your words).  Both the direct-connection between I-95 & MA 128 (opened circa 1988) (https://www.google.com/maps/place/Peabody,+MA/@42.5257005,-70.979305,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) and the once-temporary/now permanent, partial-movement I-95/US 1 connection in Peabody built circa 1974 (https://www.google.com/maps/place/Peabody,+MA/@42.5418955,-70.9876768,16.25z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) that Roadman referred to are still there.

If you were referring to the I-95 (MA 128)/US 1 interchange built circa 1962 (https://www.google.com/maps/place/Peabody,+MA/@42.522241,-71.0006416,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) at the Peabody/Lynnfield line; that one's still there as well.
Maybe I'm just stupid, but I clearly remember a big loop to stay on 95 north that is now gone.
Title: Re: Clusterfucked interchanges
Post by: hotdogPi on April 26, 2017, 05:25:38 PM
Quote from: Roadgeekteen on April 26, 2017, 04:00:06 PM
Quote from: PHLBOS on April 26, 2017, 02:34:27 PM
Quote from: Roadgeekteen on April 26, 2017, 11:02:56 AM
Quote from: roadman on April 26, 2017, 10:51:54 AM
Quote from: Roadgeekteen on April 26, 2017, 10:11:58 AM
It's not there anymore, but the Peabody interchange between I-95 and 128 used to make me carsick.
I presume you mean when you had to use US 1 between Lynnfield and Danvers to get from I-95 to 128, before there was a direct interchange between the two roads.
No, ment between I-95 and 95.
I think you need to elaborate regarding "not there anymore" (your words).  Both the direct-connection between I-95 & MA 128 (opened circa 1988) (https://www.google.com/maps/place/Peabody,+MA/@42.5257005,-70.979305,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) and the once-temporary/now permanent, partial-movement I-95/US 1 connection in Peabody built circa 1974 (https://www.google.com/maps/place/Peabody,+MA/@42.5418955,-70.9876768,16.25z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) that Roadman referred to are still there.

If you were referring to the I-95 (MA 128)/US 1 interchange built circa 1962 (https://www.google.com/maps/place/Peabody,+MA/@42.522241,-71.0006416,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) at the Peabody/Lynnfield line; that one's still there as well.
Maybe I'm just stupid, but I clearly remember a big loop to stay on 95 north that is now gone.

There is a 120° change in direction, but a large angle by itself doesn't mean anything in terms of traffic.
Title: Re: Clusterfucked interchanges
Post by: vdeane on April 26, 2017, 09:12:35 PM
Maybe he meant the Canton interchange?
Title: Re: Clusterfucked interchanges
Post by: ftballfan on April 26, 2017, 11:10:32 PM
The worst I can think of in Michigan is the I-96/I-196/M-21/M-37/M-44 interchange system.
Dishonorable mention to I-96/US-31/BUS US-31 and I-96/US-23 (which likely was the worst prior to MDOT bridging I-96 over the whole thing to eliminate left entrances onto mainline I-96)
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on April 27, 2017, 10:30:43 AM
Quote from: 1 on April 26, 2017, 05:25:38 PM
Quote from: Roadgeekteen on April 26, 2017, 04:00:06 PM
Quote from: PHLBOS on April 26, 2017, 02:34:27 PM
Quote from: Roadgeekteen on April 26, 2017, 11:02:56 AM
Quote from: roadman on April 26, 2017, 10:51:54 AM
Quote from: Roadgeekteen on April 26, 2017, 10:11:58 AM
It's not there anymore, but the Peabody interchange between I-95 and 128 used to make me carsick.
I presume you mean when you had to use US 1 between Lynnfield and Danvers to get from I-95 to 128, before there was a direct interchange between the two roads.
No, ment between I-95 and 95.
I think you need to elaborate regarding "not there anymore" (your words).  Both the direct-connection between I-95 & MA 128 (opened circa 1988) (https://www.google.com/maps/place/Peabody,+MA/@42.5257005,-70.979305,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) and the once-temporary/now permanent, partial-movement I-95/US 1 connection in Peabody built circa 1974 (https://www.google.com/maps/place/Peabody,+MA/@42.5418955,-70.9876768,16.25z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) that Roadman referred to are still there.

If you were referring to the I-95 (MA 128)/US 1 interchange built circa 1962 (https://www.google.com/maps/place/Peabody,+MA/@42.522241,-71.0006416,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) at the Peabody/Lynnfield line; that one's still there as well.
Maybe I'm just stupid, but I clearly remember a big loop to stay on 95 north that is now gone.

There is a 120° change in direction, but a large angle by itself doesn't mean anything in terms of traffic.

Eh, I'm not sure I agree with that, the curve itself can cause traffic to slow down, which can cause a backup.  lane drops also tend to happen at these jogs too which makes it worse
Title: Re: Clusterfucked interchanges
Post by: roadman on April 27, 2017, 10:41:36 AM
Quote from: vdeane on April 26, 2017, 09:12:35 PM
Maybe he meant the Canton interchange?
That would make more sense.  On the north end of the I-95/128 overlap, the only 'big loop' within the Lynnfield interchange complex to get onto I-95 is going from Goodwin Circle/MA 129 to I-95(128) south.  That ramp was put in after I-95 was re-routed onto 128 in early 1975, whereas the "suicide ramp" from I-95 north to I-95 (128) north in Canton has been in place since the highway was built in the 1960s.
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on April 27, 2017, 11:01:31 AM
Quote from: roadman on April 27, 2017, 10:41:36 AM
Quote from: vdeane on April 26, 2017, 09:12:35 PM
Maybe he meant the Canton interchange?
That would make more sense.  On the north end of the I-95/128 overlap, the only 'big loop' within the Lynnfield interchange complex to get onto I-95 is going from Goodwin Circle/MA 129 to I-95(128) south.  That ramp was put in after I-95 was re-routed onto 128 in early 1975, whereas the "suicide ramp" from I-95 north to I-95 (128) north in Canton has been in place since the highway was built in the 1960s.
Given that he lives in Needham; one would hope he would at least know which towns are north & south of Boston.  Saying Dedham or Randolph instead of Canton is forgivable IMHO; but Peabody, come on.

And again, he stated that the interchange is not there anymore.  Regardless of which interchange he's referring to; no interchange along the entire stretch of I-95/MA 128 between Canton & Peabody has been eliminated.
Title: Re: Clusterfucked interchanges
Post by: Roadgeekteen on April 27, 2017, 01:03:36 PM
Quote from: PHLBOS on April 27, 2017, 11:01:31 AM
Quote from: roadman on April 27, 2017, 10:41:36 AM
Quote from: vdeane on April 26, 2017, 09:12:35 PM
Maybe he meant the Canton interchange?
That would make more sense.  On the north end of the I-95/128 overlap, the only 'big loop' within the Lynnfield interchange complex to get onto I-95 is going from Goodwin Circle/MA 129 to I-95(128) south.  That ramp was put in after I-95 was re-routed onto 128 in early 1975, whereas the "suicide ramp" from I-95 north to I-95 (128) north in Canton has been in place since the highway was built in the 1960s.
Given that he lives in Needham; one would hope he would at least know which towns are north & south of Boston.  Saying Dedham or Randolph instead of Canton is forgivable IMHO; but Peabody, come on.

And again, he stated that the interchange is not there anymore.  Regardless of which interchange he's referring to; no interchange along the entire stretch of I-95/MA 128 between Canton & Peabody has been eliminated.
well my brain is apparently messed up or something. Maybe the Peabody interchange is still there
Title: Re: Clusterfucked interchanges
Post by: vdeane on April 27, 2017, 01:31:51 PM
I'm guessing you may have misremembered Canton as Peabody and then assumed it was removed when you couldn't find it.  Or misjudged the geometry (I know I did that once or twice when I was younger).
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on April 27, 2017, 01:45:08 PM
Quote from: Roadgeekteen on April 27, 2017, 01:03:36 PMwell my brain is apparently messed up or something. Maybe the Peabody interchange is still there.
With all due respect, are you even reading any of the inserted posts... particularly the one containing Google Map links showing all 3 Peabody area interchanges (reposted below):

Quote from: PHLBOS on April 26, 2017, 02:34:27 PMBoth the direct-connection between I-95 & MA 128 (opened circa 1988) (https://www.google.com/maps/place/Peabody,+MA/@42.5257005,-70.979305,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) and the once-temporary/now permanent, partial-movement I-95/US 1 connection in Peabody built circa 1974 (https://www.google.com/maps/place/Peabody,+MA/@42.5418955,-70.9876768,16.25z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) that Roadman referred to are still there.

If you were referring to the I-95 (MA 128)/US 1 interchange built circa 1962 (https://www.google.com/maps/place/Peabody,+MA/@42.522241,-71.0006416,15.5z/data=!4m5!3m4!1s0x89e3125bb7f609f1:0xe0c86ab48e23439f!8m2!3d42.5278731!4d-70.9286609) at the Peabody/Lynnfield line; that one's still there as well.
Click on any one of those links ('hot' links appear as different-colored text) and you will plainly see that they're all still there and haven't changed in decades.  The same holds true for the Canton interchange (regarding no change in ramp geometry in decades).
Title: Re: Clusterfucked interchanges
Post by: TXtoNJ on April 27, 2017, 02:03:25 PM
Quote from: jlwm on April 24, 2017, 02:49:18 AM
The 610 West Loop/ I-69/US59 Southwest Freeway interchange.
https://www.google.com/maps/@29.7298623,-95.4569902,16.29z

It's an early 4-level stack completed in 1962. It was Houston's first stack interchange that's remained relatively unchanged over the last 55 years save a few modifications. Since it originally opened, it's become one of the state's largest bottlenecks, complicated by the fact that it's in close proximity to the Galleria and Uptown, the nearby terminus of the Westpark Tollway, sharp ramps with not enough capacity, and weaving issues caused by exit and entrance ramps to and from nearby Chimney Rock Blvd. on 69/59.

There's a fix coming soon. Over the next few years, the interchange will be rebuilt to eliminate many of the problems. Construction is slated to start later this year and wrap up in 2021.
http://www.txdot.gov/inside-txdot/projects/studies/houston/59-610.html

Not even half as bad as 45/59/288. I've seen VMS predictions of 90 minutes to get through that beast.
Title: Re: Clusterfucked interchanges
Post by: jflick99 on April 27, 2017, 03:16:32 PM
I-35/I-435/K-10: https://www.google.com/maps/@38.9434001,-94.7593641,15.21z?hl=en (https://www.google.com/maps/@38.9434001,-94.7593641,15.21z?hl=en)

Before the Johnson County Gateway Project, I-435 had separate interchanges with K-10 (Exit 1B) and I-35 (Exit 83), with an interchange for Lackman Rd. (Exit 1A) in between. Now the K-10 and I-35 interchanges are linked together with a bunch of new ramps and C/D roads, and Lackman almost seems to have been lost. Heading SB/EB on 435, the exit for I-35 comes just after the exit for K-10. Due to a lack of signage for Lackman, most people would not notice that Exit 1A no longer exists in that direction, and that you have to follow signs for I-35 to get to Lackman Rd.

There is still one more phase to the project that will just add to the mess. Here's what it will look like when it's complete: http://jocogateway.com/wp-content/uploads/2014/04/2014-04-10-Ultimate-Exhibit_sized.pdf (http://jocogateway.com/wp-content/uploads/2014/04/2014-04-10-Ultimate-Exhibit_sized.pdf)

The I-435/US-69 interchange just to the east is almost close enough that it could be lumped in with all of this too.
Title: Re: Clusterfucked interchanges
Post by: ukfan758 on April 28, 2017, 01:29:06 PM
The Preston Hwy/I-65/I-264/Freedom Way/Terminal Dr/Crittenden Dr interchange.

https://www.google.com/maps/@38.1852311,-85.7370921,14z/data=!3m1!1e3 (https://www.google.com/maps/@38.1852311,-85.7370921,14z/data=!3m1!1e3)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fg1OYrpE.jpg&hash=f10636d9bd87cc9f826c408776e1f5e36804ccd9)

It originally was two cloverleafs directly next to each other with Preston Hwy and Crittenden Dr being isolated. The interchange was upgraded in the late 80s or early 90s. A challenge with upgrading the interchange was having Louisville International Airport directly south, so they had to make all roads at or below runway level.
Title: Re: Clusterfucked interchanges
Post by: cl94 on April 28, 2017, 07:51:43 PM
I'm shocked we got this far without mentioning any of the craziness along the Van Wyck. Let's see...

Kew Gardens Interchange: https://www.google.com/maps/@40.7164004,-73.825302,974m/data=!3m1!1e3
Northern Blvd Connector: https://www.google.com/maps/@40.7607567,-73.8447964,1685m/data=!3m1!1e3
Bruckner Interchange: https://www.google.com/maps/@40.8287647,-73.8395274,817m/data=!3m1!1e3
Title: Re: Clusterfucked interchanges
Post by: Bickendan on April 28, 2017, 07:57:26 PM
The Ross Island Maze in Portland, moreso for US 26/OR 10/43/99W than for I-5/405.
Title: Re: Clusterfucked interchanges
Post by: Rothman on April 29, 2017, 11:44:44 PM
KGI and Bruckner both have upcoming major projects.
Title: Re: Clusterfucked interchanges
Post by: cl94 on April 29, 2017, 11:49:25 PM
Quote from: Rothman on April 29, 2017, 11:44:44 PM
KGI and Bruckner both have upcoming major projects.

KGI is ongoing, with a decent amount of it done.
Title: Re: Clusterfucked interchanges
Post by: Rothman on April 30, 2017, 12:05:06 AM
Another phase is coming.
Title: Re: Clusterfucked interchanges
Post by: SteveG1988 on April 30, 2017, 09:11:28 AM
Quote from: cl94 on April 28, 2017, 07:51:43 PM
I'm shocked we got this far without mentioning any of the craziness along the Van Wyck. Let's see...

Kew Gardens Interchange: https://www.google.com/maps/@40.7164004,-73.825302,974m/data=!3m1!1e3
Northern Blvd Connector: https://www.google.com/maps/@40.7607567,-73.8447964,1685m/data=!3m1!1e3
Bruckner Interchange: https://www.google.com/maps/@40.8287647,-73.8395274,817m/data=!3m1!1e3

Title: Re: Clusterfucked interchanges
Post by: sandwalk on April 30, 2017, 09:51:12 AM
The I-70 / I-270 / Quebec Street (CO Hwy 35) / Northfield Boulevard / Smith Road cluster in northeast Denver is a mess.

https://goo.gl/maps/Gi97cEnC5jP2

I-70 has a full interchange with Quebec Street and I-270 has a partial interchange with Quebec Street.....while Quebec Street has a full interchange with Northfield Boulevard and an exit ramp set-up with Smith Road. Quebec Street is a winding road, lanes get dropped, lanes are either excessively wide or too narrow at different points, merge points are always choked, etc.  It's a perplexing area to drive through. Take a look on StreetView if you have a minute.

In general I-70 and I-270 and their interchanges are a general mess east of I-25. Each interchange affects the other thanks to outdated infrastructure and unprecedented volumes of traffic. That should hopefully be remedied in the years to come with the Central 70 project: https://www.codot.gov/projects/i70east
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on April 30, 2017, 02:28:17 PM
Quote from: sandwalk on April 30, 2017, 09:51:12 AM
The I-70 / I-270 / Quebec Street (CO Hwy 35) / Northfield Boulevard / Smith Road cluster in northeast Denver is a mess.

https://goo.gl/maps/Gi97cEnC5jP2

I-70 has a full interchange with Quebec Street and I-270 has a partial interchange with Quebec Street.....while Quebec Street has a full interchange with Northfield Boulevard and an exit ramp set-up with Smith Road. Quebec Street is a winding road, lanes get dropped, lanes are either excessively wide or too narrow at different points, merge points are always choked, etc.  It's a perplexing area to drive through. Take a look on StreetView if you have a minute.

In general I-70 and I-270 and their interchanges are a general mess east of I-25. Each interchange affects the other thanks to outdated infrastructure and unprecedented volumes of traffic. That should hopefully be remedied in the years to come with the Central 70 project: https://www.codot.gov/projects/i70east

i was in denver earlier this year, would you say that traffic has significantly increased in the past few years? 
Title: Re: Clusterfucked interchanges
Post by: bing101 on April 30, 2017, 03:44:56 PM
East LA interchange of course.
Title: Re: Clusterfucked interchanges
Post by: sandwalk on April 30, 2017, 10:18:47 PM
Quote from: silverback1065 on April 30, 2017, 02:28:17 PM
Quote from: sandwalk on April 30, 2017, 09:51:12 AM
The I-70 / I-270 / Quebec Street (CO Hwy 35) / Northfield Boulevard / Smith Road cluster in northeast Denver is a mess.

https://goo.gl/maps/Gi97cEnC5jP2

I-70 has a full interchange with Quebec Street and I-270 has a partial interchange with Quebec Street.....while Quebec Street has a full interchange with Northfield Boulevard and an exit ramp set-up with Smith Road. Quebec Street is a winding road, lanes get dropped, lanes are either excessively wide or too narrow at different points, merge points are always choked, etc.  It's a perplexing area to drive through. Take a look on StreetView if you have a minute.

In general I-70 and I-270 and their interchanges are a general mess east of I-25. Each interchange affects the other thanks to outdated infrastructure and unprecedented volumes of traffic. That should hopefully be remedied in the years to come with the Central 70 project: https://www.codot.gov/projects/i70east

i was in denver earlier this year, would you say that traffic has significantly increased in the past few years? 

I have lived here for just under 3 years and have noticed quite a bit of gridlock and bottleneck. Talking to Colorado natives, it seems like things have gotten really congested over the last 10 to 15 years.
Title: Re: Clusterfucked interchanges
Post by: Ned Weasel on April 30, 2017, 10:35:50 PM
Quote from: jflick99 on April 27, 2017, 03:16:32 PM
I-35/I-435/K-10: https://www.google.com/maps/@38.9434001,-94.7593641,15.21z?hl=en (https://www.google.com/maps/@38.9434001,-94.7593641,15.21z?hl=en)

Before the Johnson County Gateway Project, I-435 had separate interchanges with K-10 (Exit 1B) and I-35 (Exit 83), with an interchange for Lackman Rd. (Exit 1A) in between. Now the K-10 and I-35 interchanges are linked together with a bunch of new ramps and C/D roads, and Lackman almost seems to have been lost. Heading SB/EB on 435, the exit for I-35 comes just after the exit for K-10. Due to a lack of signage for Lackman, most people would not notice that Exit 1A no longer exists in that direction, and that you have to follow signs for I-35 to get to Lackman Rd.

There is still one more phase to the project that will just add to the mess. Here's what it will look like when it's complete: http://jocogateway.com/wp-content/uploads/2014/04/2014-04-10-Ultimate-Exhibit_sized.pdf (http://jocogateway.com/wp-content/uploads/2014/04/2014-04-10-Ultimate-Exhibit_sized.pdf)

That's not a cluster****ed interchange; that's a cleaned-up interchange.

Quote
The I-435/US-69 interchange just to the east is almost close enough that it could be lumped in with all of this too.

See above.
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on May 01, 2017, 12:18:25 PM
Quote from: sandwalk on April 30, 2017, 10:18:47 PM
Quote from: silverback1065 on April 30, 2017, 02:28:17 PM
Quote from: sandwalk on April 30, 2017, 09:51:12 AM
The I-70 / I-270 / Quebec Street (CO Hwy 35) / Northfield Boulevard / Smith Road cluster in northeast Denver is a mess.

https://goo.gl/maps/Gi97cEnC5jP2

I-70 has a full interchange with Quebec Street and I-270 has a partial interchange with Quebec Street.....while Quebec Street has a full interchange with Northfield Boulevard and an exit ramp set-up with Smith Road. Quebec Street is a winding road, lanes get dropped, lanes are either excessively wide or too narrow at different points, merge points are always choked, etc.  It's a perplexing area to drive through. Take a look on StreetView if you have a minute.

In general I-70 and I-270 and their interchanges are a general mess east of I-25. Each interchange affects the other thanks to outdated infrastructure and unprecedented volumes of traffic. That should hopefully be remedied in the years to come with the Central 70 project: https://www.codot.gov/projects/i70east

i was in denver earlier this year, would you say that traffic has significantly increased in the past few years? 

I have lived here for just under 3 years and have noticed quite a bit of gridlock and bottleneck. Talking to Colorado natives, it seems like things have gotten really congested over the last 10 to 15 years.

It has to be all the new people moving there, it's a great city, I'd love to live there. 
Title: Re: Clusterfucked interchanges
Post by: Strider on May 05, 2017, 03:15:10 PM
Quote from: fillup420 on April 21, 2017, 09:05:00 AM
Death Valley in Greensboro, NC is the merge point of I-40, I-85 Business, US 29/70 and US 220. There are left and right exits/entrances within half-mile of each other. I-40 and Business 85 merge so close to the Randleman Rd exit that 2 separate ramp sets are required. For about a mile, the road is signed as:
I-40, I-85 Business, US 29/70/220 (and US 421 used to be routed along here too).

https://www.google.com/maps/@36.0309201,-79.8052442,15z




I agree.. This one.. is a pain. I often use The Southern Loop to avoid this part.

Eventually that part of the road will be fixed, starting with the widening of the Buffalo creek bridge between Randleman and Elm-Eugene St interchanges in 2019. They are currently working on the widening of the bridges that carry I-40 West as well as the ramp to MLK Jr. Dr. over US 29. Then, after the Beltway is completed, they plan on fix that dangerous section.. although I don't know when it will happen.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on May 06, 2017, 01:50:15 AM
Any interchange in Pa.
Title: Re: Clusterfucked interchanges
Post by: D-Dey65 on May 06, 2017, 01:14:42 PM
Quote from: cl94 on April 28, 2017, 07:51:43 PM
I'm shocked we got this far without mentioning any of the craziness along the Van Wyck. Let's see...

Kew Gardens Interchange: https://www.google.com/maps/@40.7164004,-73.825302,974m/data=!3m1!1e3
Northern Blvd Connector: https://www.google.com/maps/@40.7607567,-73.8447964,1685m/data=!3m1!1e3
Bruckner Interchange: https://www.google.com/maps/@40.8287647,-73.8395274,817m/data=!3m1!1e3

The Kew Gardens interchange was mentioned on this post:

https://www.aaroads.com/forum/index.php?topic=20055.msg2221171#msg2221171

Would the I-75 interchanges with Fletcher and Fowler Avenues count? Because I think they could eliminated some median crossings with those.

Title: Re: Clusterfucked interchanges
Post by: roadgeek01 on May 06, 2017, 01:31:33 PM
The Eisenhower Interchange in Harrisburg.  I always thought that there was a much better way to build that.  Such a pain in the rear-end during rush hour.

https://www.google.com/maps/@40.2525293,-76.8114632,16.35z
Title: Re: Clusterfucked interchanges
Post by: dzlsabe on May 14, 2017, 07:49:31 AM
Quote from: Brandon on April 19, 2017, 01:19:04 PM
Around Chicago, The Circle (https://goo.gl/maps/PtjNxBiF4rq).  This one has the power to fuck up not just the Ryan, Kennedy, and Ike expressways, but also the Stevenson (with the interchange near it), the Edens, the Bishop Ford, and I-57.
Quote from: sparker
At least IDOT had the good sense back in the '70's to reroute I-90 as a through route through Chicago's Circle interchange rather than turning it 90 degrees onto the Ike at that location!

Dont think theres anyone in Chicago that would call I-90 AND 94 "good sense" or a through route. And you know what 90 degrees infers? Hint. Its NOT that its hot outside.

The Ryan/Kennedy and Ike (Byrnecircle) need to be bypassed and the Strangler flown over. And no IDOT/ISTHA geniuses, the Tri-state, even after another $4B soon to be spent on it, or Ike HOVing is going to resolve the problem. Not a day goes by where these roads dont slow to a crawl. The other day I actually backed off an entrance to the Kennedy because it came to a complete STOP. We waste a minimum of $10B annually in time, fuel, lost productivity etc around here, an area with the GDP of OH or NJ. Times THIRTY years? Its time. No more 90/94.
Title: Re: Clusterfucked interchanges
Post by: roadman65 on May 16, 2017, 11:56:52 PM
Quote from: roadgeek01 on May 06, 2017, 01:31:33 PM
The Eisenhower Interchange in Harrisburg.  I always thought that there was a much better way to build that.  Such a pain in the rear-end during rush hour.

https://www.google.com/maps/@40.2525293,-76.8114632,16.35z

The I-83 movements were an afterthought.  US 230 Bypass used Eisenhower and the freeway north of where US 322 enters I-83 was part of it.  So the US 322 interchange with Derry Street was the first of that freeway north of Paxtang Street where the arterial ended.

Remember PennDOT likes to ad lib things hence why I-80 and I-99 do not have the proper interchange two freeways need.  I-99 was sort of forced on the state thanks to one politician who had congress write the number into law and made it what was just to be a US route freeway into an interstate.  If US 220 alone intersected I-80 the way it did, it would not be breaking any rules and would not even get pushed for an upgrade there unless some sort of bottlenecks or accidents occur.

Yes pretty much correct as I-83 narrows to one lane through there.  In addition the interchange with PA 581 also needs to be redone as I-83 exits itself for a loop on the outside of a trumpet.  But that at least remains two lanes and not a drop down.
Title: Re: Clusterfucked interchanges
Post by: dfwmapper on May 17, 2017, 09:19:56 PM
The I-30/I-35E "Mixmaster" interchange in Dallas qualifies on both counts. The original design was a clusterfuck of insufficient capacity, left exits, excessive weaving, and missing movements, while the new design mostly eliminates the bad design decisions but replaces them with an incredible amount of complexity with multiple C/D roads that have their own ramps in addition to the direct freeway-to-freeway connectors.
Title: Re: Clusterfucked interchanges
Post by: sparker on May 18, 2017, 03:27:27 AM
It's not so much clusterfucked as it is just plain weird:  the interchange between I-5 and CA 120 at Manteca.  NB 5 to EB 120 is the only "normal" movement; the opposite direction (WB 120>SB 5) utilizes the original US 50 bascule-type drawbridge (now disabled) across the San Joaquin River as part of its alignment.  And those two are the higher-volume/more direct ramps.  The other two movements are WB 120 to NB 5, this features a bridge over the adjoining UP rail line that has a very sharp curve at its apex; the opposite movement from SB 5 to EB 120 features a "hook" U-turn that ducks under the I-5 San Joaquin River bridges before merging with the NB 5>EB 120 lanes.  While originally designed that way due to lower anticipated volumes, the growth of the adjoining area has made the SB>EB/WB>NB movements much more utilized than before in order for folks living in west Manteca and Lathrop, the town directly NW, to access jobs and commerce in Modesto, some 20 miles southeast.  These ramps are fast becoming substandard for the volume they're being required to handle. 
Title: Re: Clusterfucked interchanges
Post by: cpzilliacus on May 19, 2017, 03:39:43 PM
Quote from: epzik8 on April 19, 2017, 12:42:27 PM
I-95/695, Exit 33/64 in Rosedale, Maryland (just northeast of Baltimore) might be one, to some extent. I think both highways lose a lane within that interchange. It's sort of difficult for traffic to merge from the ramps onto each highway.

I disagree.  That interchange has been upgraded to a modern stack (one of only two in the state) and appears to work well since it was completed.

Now there are three full cloverleaf interchanges in Maryland that do not work well and routinely break  down under heavy  traffic load (there are several more cloverleafs that the state has modified or totally rebuilt over the years, including one in Prince George's County at the junction of I-95/I-495 (Capital Beltway, Exit 22) and U.S. 50 ("secret" I-595, John Hanson Highway, Exit 7) (https://www.google.com/maps/place/38%C2%B056'43.8%22N+76%C2%B051'29.8%22W/@38.945491,-76.8670187,15z/data=!4m5!3m4!1s0x0:0x0!8m2!3d38.945491!4d-76.858264), which was once a creaking and overloaded cloverleaf).

On the other side of Baltimore from Rosedale is the junction of I-695 (Baltimore Beltway, Exit 7) and MD-295 (Baltimore-Washington Parkway) (https://www.google.com/maps/place/Linthicum+Heights,+MD/@39.2187533,-76.665216,15z/data=!4m5!3m4!1s0x89b7e298a4b0db27:0x7590c9c5d8a301e0!8m2!3d39.2051077!4d-76.6527456) in Linthicum Heights, Anne  Arundel County, which might be the worst full cloverleaf in the state.  This fails routinely during peak commute times due to weaving and suffers from an elderly design.

South of there, at the junction of I-95/I-495 (Capital Beltway, Exit 22) and "secret" MD-295 (Baltimore-Washington Parkway) (https://www.google.com/maps/place/Greenbelt,+MD/@38.9906106,-76.8938184,15z/data=!4m5!3m4!1s0x89b7c3d894c1509b:0xa50738adf244f411!8m2!3d39.0045544!4d-76.8755282) in Greenbelt, Prince George's County is another full cloverleaf.  This one is not as bad as its counterpart to the north but it also suffers badly during peak traffic periods, especially weekday afternoons.

Even further south in Forestville, Prince George's County is the junction of I-95/I-495 (Capital Beltway, Exit 11) and MD-4 (Pennsylvania Avenue Extended) (https://www.google.com/maps/place/Forestville,+MD/@38.8387723,-76.8706042,16z/data=!4m5!3m4!1s0x89b7bef2261a18d9:0x9cc74f3fbd783338!8m2!3d38.8451131!4d-76.8749722). It suffers from crashes on the mainline and on the ramps (even though this is probably the best-designed of the  three).
Title: Re: Clusterfucked interchanges
Post by: I-90 on May 19, 2017, 09:09:27 PM
(https://upload.wikimedia.org/wikipedia/commons/thumb/9/91/I88i294i290interchange.svg/220px-I88i294i290interchange.svg.png)
I also would include the il64 interchange with us 20 I-290/I-294 and st Charles rd and the other interchanges near oak brook terrace
Title: Re: Clusterfucked interchanges
Post by: intelati49 on May 21, 2017, 08:50:27 AM
Still half of a cluster...

https://en.m.wikipedia.org/wiki/Grandview_Triangle

Loads better with the design build project
Title: Re: Clusterfucked interchanges
Post by: mvak36 on June 30, 2017, 10:05:41 AM
Quote from: intelati49 on May 21, 2017, 08:50:27 AM
Still half of a cluster...

https://en.m.wikipedia.org/wiki/Grandview_Triangle

Loads better with the design build project

Design-wise it's not so bad. The problem is there are just so many cars.
Title: Re: Clusterfucked interchanges
Post by: Buffaboy on June 30, 2017, 11:30:46 AM
Breezewood, I-70/I-76 if nobody mentioned that
Title: Re: Clusterfucked interchanges
Post by: ekt8750 on June 30, 2017, 12:03:20 PM
Quote from: Buffaboy on June 30, 2017, 11:30:46 AM
Breezewood, I-70/I-76 if nobody mentioned that

It was but it doesn't qualify as an interchange cause well, there's no interchange lol
Title: Re: Clusterfucked interchanges
Post by: thenetwork on July 01, 2017, 09:23:32 PM
Quote from: silverback1065 on May 01, 2017, 12:18:25 PM
Quote from: sandwalk on April 30, 2017, 10:18:47 PM
Quote from: silverback1065 on April 30, 2017, 02:28:17 PM
Quote from: sandwalk on April 30, 2017, 09:51:12 AM
The I-70 / I-270 / Quebec Street (CO Hwy 35) / Northfield Boulevard / Smith Road cluster in northeast Denver is a mess.


https://goo.gl/maps/Gi97cEnC5jP2

I-70 has a full interchange with Quebec Street and I-270 has a partial interchange with Quebec Street.....while Quebec Street has a full interchange with Northfield Boulevard and an exit ramp set-up with Smith Road. Quebec Street is a winding road, lanes get dropped, lanes are either excessively wide or too narrow at different points, merge points are always choked, etc.  It's a perplexing area to drive through. Take a look on StreetView if you have a minute.

In general I-70 and I-270 and their interchanges are a general mess east of I-25. Each interchange affects the other thanks to outdated infrastructure and unprecedented volumes of traffic. That should hopefully be remedied in the years to come with the Central 70 project: https://www.codot.gov/projects/i70east

i was in denver earlier this year, would you say that traffic has significantly increased in the past few years? 

I have lived here for just under 3 years and have noticed quite a bit of gridlock and bottleneck. Talking to Colorado natives, it seems like things have gotten really congested over the last 10 to 15 years.

It has to be all the new people moving there, it's a great city, I'd love to live there. 

Originally, those ramps were designed to bring people South of those interchanges to Stapleton (DEN) Airport.  When DEN moved out east to the new DIA airport 20-some years ago, that area was not too crowded. 

Now that most of old Stapleton has been converted to residential/commercial developments south of I-70 traffic counts have gone up.  But the Northfield Shopping district north of I-270 is where most of the gridlock is nowadays, as very little has been done to modify both Quebec interchanges to better move traffic north.  Instead they built the Central Park interchange on I-70 east of I-270 (where the runways used to be).as a relief route for Stapleton/Northfield traffic.

AND if you plan to move to Denver, be prepared to pay a lot for an abode as Denver currently has a housing shortage and it's quite expensive right now to even rent.
Title: Re: Clusterfucked interchanges
Post by: CapeCodder on July 02, 2017, 11:58:20 AM
On the Cape, it's most of the interchanges on the Mid-Cape. The Exit lanes are almost nil, and when someone has an accident, holy crap.
Title: Re: Clusterfucked interchanges
Post by: RG407 on July 02, 2017, 11:20:13 PM
Golden Glades, the convergence of I-95, Florida's Turnpike, US 441, FL 9 and FL 826/Palmetto Expressway north of Miami.
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on July 04, 2017, 05:49:00 PM
Quote from: thenetwork on July 01, 2017, 09:23:32 PM
Quote from: silverback1065 on May 01, 2017, 12:18:25 PM
Quote from: sandwalk on April 30, 2017, 10:18:47 PM
Quote from: silverback1065 on April 30, 2017, 02:28:17 PM
Quote from: sandwalk on April 30, 2017, 09:51:12 AM
The I-70 / I-270 / Quebec Street (CO Hwy 35) / Northfield Boulevard / Smith Road cluster in northeast Denver is a mess.


https://goo.gl/maps/Gi97cEnC5jP2

I-70 has a full interchange with Quebec Street and I-270 has a partial interchange with Quebec Street.....while Quebec Street has a full interchange with Northfield Boulevard and an exit ramp set-up with Smith Road. Quebec Street is a winding road, lanes get dropped, lanes are either excessively wide or too narrow at different points, merge points are always choked, etc.  It's a perplexing area to drive through. Take a look on StreetView if you have a minute.

In general I-70 and I-270 and their interchanges are a general mess east of I-25. Each interchange affects the other thanks to outdated infrastructure and unprecedented volumes of traffic. That should hopefully be remedied in the years to come with the Central 70 project: https://www.codot.gov/projects/i70east

i was in denver earlier this year, would you say that traffic has significantly increased in the past few years? 

I have lived here for just under 3 years and have noticed quite a bit of gridlock and bottleneck. Talking to Colorado natives, it seems like things have gotten really congested over the last 10 to 15 years.

It has to be all the new people moving there, it's a great city, I'd love to live there. 



AND if you plan to move to Denver, be prepared to pay a lot for an abode as Denver currently has a housing shortage and it's quite expensive right now to even rent.

this basically describes every city worth moving to
Title: Re: Clusterfucked interchanges
Post by: jeffandnicole on July 05, 2017, 06:17:52 AM
Quote from: ekt8750 on June 30, 2017, 12:03:20 PM
Quote from: Buffaboy on June 30, 2017, 11:30:46 AM
Breezewood, I-70/I-76 if nobody mentioned that

It was but it doesn't qualify as an interchange cause well, there's no interchange lol

Sure there is.  It's just not a conventional highway-highway interchange.
Title: Re: Clusterfucked interchanges
Post by: longhorn on July 05, 2017, 04:26:21 PM
https://www.google.com/maps/@40.6869259,-74.1638452,8579m/data=!3m1!1e3

The area around EWR Newark Airport, try getting to the hotels around the airport perimeter on I-78 or down by The Mills outlet mall. The interchanges make NO SENSE and are counter intuitive.
Title: Re: Clusterfucked interchanges
Post by: intelati49 on July 06, 2017, 09:33:28 AM
Quote from: longhorn on July 05, 2017, 04:26:21 PM
https://www.google.com/maps/@40.6869259,-74.1638452,8579m/data=!3m1!1e3

The area around EWR Newark Airport, try getting to the hotels around the airport perimeter on I-78 or down by The Mills outlet mall. The interchanges make NO SENSE and are counter intuitive.

Well, that will take a half hour to decode even for me. Jeez :ded:
Title: Re: Clusterfucked interchanges
Post by: ixnay on July 16, 2017, 05:10:36 PM
Quote from: Tonytone on April 20, 2017, 06:08:02 PM
Quote from: Brandon on April 20, 2017, 05:57:02 PM
Quote from: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.

Clusterfucked freeway, not a clusterfucked interchange.
The interchange with the ramps is what causes the bad weaving....

Tonytone might be referring to exit 3 northbound where U.S. 322 eb merges on the left.  For the next mile 95 and 322 are multiplexed and I imagine much of the weaving is caused by drivers accessing the Barry Bridge or PA 291 near the river, especially when the Union has a game at Talen Energy.

Further up at exit 7, the right lane nb is exit only for I-476, although since the ramp to nb 476 became a two laner, the center lane through the Chester trench has given its users a choice between 476 and staying on 95, so less excuse for weaving between exits 4 and 7 since the ramps for Kerlin St. and PA 352 don't remove any lanes from the mainline.

ixnay
Title: Re: Clusterfucked interchanges
Post by: Tonytone on July 16, 2017, 05:42:31 PM
Quote from: ixnay on July 16, 2017, 05:10:36 PM
Quote from: Tonytone on April 20, 2017, 06:08:02 PM
Quote from: Brandon on April 20, 2017, 05:57:02 PM
Quote from: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.

Clusterfucked freeway, not a clusterfucked interchange.
The interchange with the ramps is what causes the bad weaving....

Tonytone might be referring to exit 3 northbound where U.S. 322 eb merges on the left.  For the next mile 95 and 322 are multiplexed and I imagine much of the weaving is caused by drivers accessing the Barry Bridge or PA 291 near the river, especially when the Union has a game at Talen Energy.

Further up at exit 7, the right lane nb is exit only for I-476, although since the ramp to nb 476 became a two laner, the center lane through the Chester trench has given its users a choice between 476 and staying on 95, so less excuse for weaving between exits 4 and 7 since the ramps for Kerlin St. and PA 352 don't remove any lanes from the mainline.

ixnay
That's exactly what it is but, when I-95 & 495 merge, I-95 going from 2 lanes to 1 & I-495 going from 3 lanes to 2 doesnt help this area either, so now you have highways that both get significant traffic (maybe back in the 70s this area moved smoothly) but the only for traffic to get better is to add an extra lane between the merge & up to the airport where 4 lanes are & the traffic gets better.


iPhone
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on July 17, 2017, 04:09:41 PM
Quote from: ixnay on July 16, 2017, 05:10:36 PM
Quote from: Tonytone on April 20, 2017, 06:08:02 PM
Quote from: Brandon on April 20, 2017, 05:57:02 PM
Quote from: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.

Clusterfucked freeway, not a clusterfucked interchange.
The interchange with the ramps is what causes the bad weaving....

Tonytone might be referring to exit 3 northbound where U.S. 322 eb merges on the left.  For the next mile 95 and 322 are multiplexed and I imagine much of the weaving is caused by drivers accessing the Barry Bridge or PA 291 near the river, especially when the Union has a game at Talen Energy.
FWIW, there is a long-term plan to reconfigure the I-95/US 322 West interchange into an enlarged trumpet with the eastbound 322 traffic merging onto the right of I-95 northbound.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on July 18, 2017, 02:54:38 AM
Quote from: PHLBOS on July 17, 2017, 04:09:41 PM
Quote from: ixnay on July 16, 2017, 05:10:36 PM
Quote from: Tonytone on April 20, 2017, 06:08:02 PM
Quote from: Brandon on April 20, 2017, 05:57:02 PM
Quote from: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.

Clusterfucked freeway, not a clusterfucked interchange.
The interchange with the ramps is what causes the bad weaving....

Tonytone might be referring to exit 3 northbound where U.S. 322 eb merges on the left.  For the next mile 95 and 322 are multiplexed and I imagine much of the weaving is caused by drivers accessing the Barry Bridge or PA 291 near the river, especially when the Union has a game at Talen Energy.
FWIW, there is a long-term plan to reconfigure the I-95/US 322 West interchange into an enlarged trumpet with the eastbound 322 traffic merging onto the right of I-95 northbound.
Where are the documents? & does that include widening I-95 to 4 lanes thru to Plymouth meeting & Philly Airport? Also will Pa ever update their welcome sign? Will those state troopers ever stop pulling people over?


iPhone
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on July 18, 2017, 11:46:38 AM
Quote from: Tonytone on July 18, 2017, 02:54:38 AM
Quote from: PHLBOS on July 17, 2017, 04:09:41 PMFWIW, there is a long-term plan to reconfigure the I-95/US 322 West interchange into an enlarged trumpet with the eastbound 322 traffic merging onto the right of I-95 northbound.
Where are the documents? & does that include widening I-95 to 4 lanes thru to Plymouth meeting & Philly Airport? Also will Pa ever update their welcome sign? Will those state troopers ever stop pulling people over?
Allow me to break apart your post & answer your questions.

1.  I only saw the proposed improvements on an overall site plan for a future I-95/US 322 interchange improvement project prepared by a consulting engineering firm.  I am not presently aware of the existence of any construction documents for this project.  Such was the reasoning for the long-term wording in my earlier post.

2.  The site plan only focuses on the US 322 West & Highland Ave. interchanges along I-95 in Chester (Township) as well as the somewhat-hidden US 322/Bethel Road interchange.

3.  Your "widening I-95 to 4 lanes thru to Plymouth meeting & Philly Airport" is somewhat vague & confusing because: a. I-95 goes nowhere near Plymouth Meeting (were you referring to I-476?) & b.  I-95 is already/at least 4 lanes in both directions (aka 8 lanes) between I-476 (Exit 7) and the Airport area (Exits 10-12).

4.  Updating the Welcome signs.  What needs to be updated?  PA stopped placing the Governor's name on those signs since the Rendell Administration (SPIRIT OF INDEPENDENCE was placed over the Governor's name); so that can't be the update.

5.  In your "Will those state troopers ever stop pulling people over?" question; are you referring to state troopers that pull over people at random or ones that actually pursue someone who's driving to endanger (i.e. weaving, excessive speeding and/or OUI)?  Granted, the posted speed of 55 mph along I-95 is a joke IMHO; from my personal experience, if one's doing 70 or below (& nothing else major) on that stretch of I-95, the troopers usually leave one alone.
Title: Re: Clusterfucked interchanges
Post by: Tonytone on July 18, 2017, 12:04:31 PM
Well this right here was a great answer ladies & gents.

1: I asked about documents because Id like to see the graphics for how they will be redoing the area, its a very tight area & anyone who has drove it knows, barrier in the middle of I-95 which means no left shoulder only a right one. & yea if it isnt getting done this year it wont be anytime soon , sadly.

2:I dont really see those exits as being a problem, its more of lack of lanes.

3: Yes from the PA-DE line I-95 is 3 lanes all the way to Plymouth meeting, Even though its 2 lanes for the Philadelphia exit & I-476 its still a bad area because if the tight turns & lanes, now dont get me wrong its not bad, but if they want traffic jams to stop in that area they need to take action. Yes & notice how when I-95 is 4 lanes it moves smoothly, 3 lane highways are not possible unless you're in the rural, not a fuckin city.

4: The design, that sign has been the same blue & white since I was little & im 19 now. Lol

5: This was a joke, I say that because of the state troopers that wait at the De-Pa line, I know the areas the police are in & the speeds that gets attention, Im a driver, I driver everyday all most all day, so I know what roads need fixing & what roads are the best.


iPhone
Title: Re: Clusterfucked interchanges
Post by: jeffandnicole on July 18, 2017, 12:29:45 PM
Quote from: Tonytone on July 18, 2017, 12:04:31 PM
Well this right here was a great answer ladies & gents.

1: I asked about documents because Id like to see the graphics for how they will be redoing the area, its a very tight area & anyone who has drove it knows, barrier in the middle of I-95 which means no left shoulder only a right one. & yea if it isnt getting done this year it wont be anytime soon , sadly.

This interchange was looked at years ago (last decade).  Even though they apparently have decided on a revised interchange, current budgeting documents do not have any funding available for this project for the next 6 years.  The DVRPC did have a website for this project; it's since been closed.  I tried looking for documents recently on this project and didn't come across anything.

That said, not sure what you mean about a barrier in the middle of 95...are you talking about an everyday jersey barrier separating NB and SB traffic??  That has nothing to do with the lack of a shoulder.  The fact that they wedged in 95 in the first place is why (probably a major concession from knocking down too many homes in Chester when 95 was designed thru the area).  Also, there's no right shoulder either in much of the area, due to that wedgie.  They need to take out a row of homes along 95 in order to significantly widen this area.

Quote3: Yes from the PA-DE line I-95 is 3 lanes all the way to Plymouth meeting, Even though its 2 lanes for the Philadelphia exit & I-476 its still a bad area because if the tight turns & lanes, now dont get me wrong its not bad, but if they want traffic jams to stop in that area they need to take action. Yes & notice how when I-95 is 4 lanes it moves smoothly, 3 lane highways are not possible unless you're in the rural, not a fuckin city.

You've been told already I-95 doesn't go to Plymouth Meeting.

Numerous examples can be cited of where 4 lanes in a city doesn't move well at all (just look at the area north of I-676).  There are numerous factors in how well a highway moves, which includes alternate routes, bypasses, interchanges, etc.  That 4 lane section Northbound tends to move well because of how 95 and 476 are squeezed prior to North of that point.  95 South near the airport can be a parking lot some days...even though it's 4 lanes wide...due to the downstream issues.[/quote]

Quote from: longhorn on July 05, 2017, 04:26:21 PM
https://www.google.com/maps/@40.6869259,-74.1638452,8579m/data=!3m1!1e3

The area around EWR Newark Airport, try getting to the hotels around the airport perimeter on I-78 or down by The Mills outlet mall. The interchanges make NO SENSE and are counter intuitive.

You cited an entire region, not an interchange.  Some of the interchanges are fine.  Others are a bear.  Many are too close together.  But the interchanges within the Turnpike really aren't that bad - they're just like every other turnpike interchange.

Quote from: ixnay on July 16, 2017, 05:10:36 PM
Quote from: Tonytone on April 20, 2017, 06:08:02 PM
Quote from: Brandon on April 20, 2017, 05:57:02 PM
Quote from: Tonytone on April 20, 2017, 05:49:40 PM
I-95 thru Chester, Pa no left shoulder, Pa's suicide ramps and a zipline barrier altogether makes traffic backup. Also noted that people dont move over to let merging traffic on the highway so they just slowdown and cause the backup for miles.

Clusterfucked freeway, not a clusterfucked interchange.
The interchange with the ramps is what causes the bad weaving....

Tonytone might be referring to exit 3 northbound where U.S. 322 eb merges on the left.  For the next mile 95 and 322 are multiplexed and I imagine much of the weaving is caused by drivers accessing the Barry Bridge or PA 291 near the river, especially when the Union has a game at Talen Energy.

Sadly, it's only a 1/2 mile area. It would preform much better if 322 traffic didn't have a 300 foot merge zone, after which traffic continuing on 322 needs to merge over 4 lanes in a very short span in usually very heavy traffic.

The Union is fairly new, and plays approximately 17 home games per year.  This interchange congests on a daily basis from rush hour traffic, and was a problem even in the 1980's and 1990's.  The stadium doesn't help matters, but it has very little effect on the well documented, multi-decade issue that exists here.
Title: Re: Clusterfucked interchanges
Post by: PHLBOS on July 18, 2017, 12:50:44 PM
J&N beat me to the punch answering Tonytone's questions/replies but I'll add where needed:

Quote from: Tonytone on July 18, 2017, 12:04:31 PM3: Yes from the PA-DE line I-95 is 3 lanes all the way to Plymouth meeting, Even though its 2 lanes for the Philadelphia exit & I-476 its still a bad area because if the tight turns & lanes, now dont get me wrong its not bad, but if they want traffic jams to stop in that area they need to take action. Yes & notice how when I-95 is 4 lanes it moves smoothly, 3 lane highways are not possible unless you're in the rural, not a fuckin city.
Tip: most people refer to I-95's Exit 7 as either the I-476 or Blue Route interchange; they do not refer to it as the Plymouth Meeting interchange.

Quote from: Tonytone on July 18, 2017, 12:04:31 PM4: The design, that sign has been the same blue & white since I was little & im 19 now. Lol
So, there's no rule I'm aware of that requires states to redesign their welcome signs every few years.  They only need to replacement if they're either damaged, vandalized and/or no longer readable (faded or loss of reflectivity).

Quote from: Tonytone on July 18, 2017, 12:04:31 PM
5: This was a joke, I say that because of the state troopers that wait at the De-Pa line, I know the areas the police are in & the speeds that gets attention, Im a driver, I driver everyday all most all day, so I know what roads need fixing & what roads are the best.
Assuming that the listed age on your profile is true & current (plus you mentioned your age further up in your post); you need to keep in mind that there are not only others on this board that reside near/at your geographic region, many of them (myself included) have been around & have driven these roads longer years before you were even born.  As a matter of fact, this week marks my 27th anniversary of moving down to the Delaware Valley area from the Greater Boston area.

That said, many of the traffic issues you mention regarding I-95 in that area have been experienced by others on this board (myself) included as well and agree that it could've been designed better.  Both many of us here know that shoehorning the current alignment was enough of a challenge back then (1960s-1970s).
Title: Re: Clusterfucked interchanges
Post by: northeast_roadgeek on July 28, 2017, 11:16:05 AM
The interchange of the New York Thruway (87) with 90 north of Albany is a complete mess.
Dropped Pin
near I-90 & Adirondack Northway & New York State Reference Rte 910F, Albany, NY 12205
https://goo.gl/maps/N8Phbyc8Mt82
Title: Re: Clusterfucked interchanges
Post by: silverback1065 on July 29, 2017, 06:36:49 PM
Quote from: northeast_roadgeek on July 28, 2017, 11:16:05 AM
The interchange of the New York Thruway (87) with 90 north of Albany is a complete mess.
Dropped Pin
near I-90 & Adirondack Northway & New York State Reference Rte 910F, Albany, NY 12205
https://goo.gl/maps/N8Phbyc8Mt82

they need to fix these stupid toll road interchanges
Title: Re: Clusterfucked interchanges
Post by: brycecordry on July 29, 2017, 08:03:55 PM
The US 63/I-70 Interchange in Columbia MO.

It does not look bad, but due to the fact that all the services are also along this interchange, it is simply too much traffic there when also combined with all the through traffic.

I put my concept for improvements on Fictional, but I will also put it here. https://drive.google.com/file/d/0B1URDteA8SWyTzRFdUVXcC13cXM/view?usp=sharing
Title: Re: Clusterfucked interchanges
Post by: mrsman on August 28, 2017, 02:13:53 PM
You can't forget the perennially under powered 4-level interchange in Downtown LA.  It seems that at any time day or night there is a backup, especially heading to the Hollywood Fwy.  One lane from the Pasadena merges in to the two lane transition road from the Harbor and those two lanes merge into the three main-line US 101 lanes that emanate from the Santa Ana to form a 4 lane freeway with an inside lane merge.
Title: Re: Clusterfucked interchanges
Post by: Flint1979 on August 29, 2017, 02:01:05 PM
The Mixing Bowl interchange in Southfield, Michigan just outside of Detroit has I-696 (Ruether Freeway), M-10 (Northwestern/Lodge Freeway), US-24 (Telegraph Rd), Franklin Rd. and Lahser Rd. all meeting at the same point.
Title: Re: Clusterfucked interchanges
Post by: SidS1045 on September 21, 2017, 03:03:43 PM
Quote from: roadman on April 25, 2017, 03:10:47 PM
Since it hasn't been mentioned yet, I'll add I-95 (MA 128) at I-93 in Woburn/Reading/Stoneham (MA).  Failing a complete rebuild, which was first proposed in the early 1990s but has been stalled by the NIMBYS on one side and the Woburn politicians on the other side ever since, there are actually two relatively simple things MassDOT could do to improve traffic flow through this area.

First would be to extend the fourth lane on southbound I-95 (128), which currently begins at the end of the ramp from I-93 southbound, to the on-ramp from Route 28 southbound.  By adding an additional lane through the interchange, this would reduce much of the current conflict between southbound through traffic and traffic weaving to/from I-93 north and south.

Second would be to extend the added lane on northbound I-95 (128) between the ramps from I-93 northbound and Route 28 southbound to north of both Route 28 ramps.  This would give the traffic coming from the right "exit only" lane (former shoulder) between Montvale Avenue and I-95 north additional area to merge with the mainline traffic.  Of course, I-95 (128) should really be widened to four lanes each way between Stoneham and Lynnfield anyway, but that's a different subject altogether (that's a different subject).

As I live about a mile from this clusterfuck (even in the 1960's, when I-93 was built, who's the brain surgeon who decided to intersect two major arterial highways with a cloverleaf???):

Both of your suggestions should have been no-brainers, in part because the last reconstruction of the 128 overpass over MA 28 in Reading (also a cloverleaf interchange) left plenty of room on both sides of 128 for an extra lane of traffic.  The same is true of the Hopkins Street overpass over 128, since it was built wide enough to accommodate the on- and off-ramps for 28 north.  The I-93 overpass over 128 is also extra wide to accommodate on- and off-ramps.  Maybe they were envisioning what you suggested way back when?