Where you live, which intersection annoys you?
For me in Missoula, MT, it's South Avenue, Russell Street, and Brooks Street, known as "Malfunction Junction". Fittingly so.
The intersection of PA 320 and Bullens Lane near Wallingford is my new least favorite intersection around here. They recently installed a traffic signal at that intersection that has actually increased back ups dramatically. Before the signal, the intersection wasn't a problem at all. Now that the signal is there, I avoid going that way as much as possible because of all the back ups it has created.
Annoying? Plenty.
But ones that I truly dislike are the ones with frequent wrecks.
Here are some near Washington, D.C. that I believe are a hazard to the traveling public:
U.S. 29 (Columbia Pike) and Fairland Road (https://maps.google.com/maps?q=columbia+pike+%26+fairland+road,+silver+spring,+md&hl=sv&ll=39.073328,-76.955752&spn=0.004656,0.009645&sll=38.804821,-77.236966&sspn=2.392779,4.938354&t=h&hnear=Columbia+Pike+%26+Old+Columbia+Pike,+Silver+Spring,+Montgomery,+Maryland+20904&z=17), just south of the new Md. 200 interchange in Montgomery County. Over and over again there have been injury wrecks there. The local master plan contains provisions that call for this signalized intersection to be replaced by a grade separation. Can't happen soon enough for me, though there is no funding currently to build it (presumably, the next signalized intersection to the south, at Musgrove Road, would also be eliminated as part of the same project).
Md. 355 (Frederick Road) and Shady Grove Road (https://maps.google.com/maps?q=shady+grove+road+%26+frederick+road,+rockville,+md&hl=sv&ll=39.122486,-77.176166&spn=0.004653,0.009645&sll=38.776018,-77.294869&sspn=0.004676,0.009645&t=h&hnear=Frederick+Rd+%26+Shady+Grove+Rd,+9,+Montgomery,+Maryland+20877&z=17) near the west end of Md. 200 in Montgomery County has had many bad wrecks.
In Prince George's County, Maryland 4 (Pennsylvania Avenue Extended) has three at-grade signalized intersections just outside the Capital Beltway (I-95/I-495) that have many crashes, at Westphalia Road (https://maps.google.com/maps?q=pennsylvania+avenue+and+westphalia+road,+forestville,+md&hl=sv&sll=39.12793,-76.893311&sspn=0.595506,1.234589&t=h&hnear=Pennsylvania+Ave+%26+Westphalia+Rd,+Upper+Marlboro,+Maryland+20774&z=16), the federal Suitland Parkway (https://maps.google.com/maps?q=pennsylvania+avenue+and+westphalia+road,+forestville,+md&hl=sv&ll=38.829846,-76.856618&spn=0.009344,0.01929&sll=39.12793,-76.893311&sspn=0.595506,1.234589&t=h&hnear=Pennsylvania+Ave+%26+Westphalia+Rd,+Upper+Marlboro,+Maryland+20774&z=16) and at Dower House Road (https://maps.google.com/maps?q=pennsylvania+avenue+and+dower+house+road,+forestville,+md&hl=sv&ll=38.821103,-76.848443&spn=0.009345,0.01929&sll=38.820986,-76.848571&sspn=0.009345,0.01929&t=h&hnear=Pennsylvania+Ave+%26+Dower+House+Rd,+15,+Mellwood,+Prince+George%27s,+Maryland+20772&z=16).
Va. 286 (Fairfax County Parkway) at Va. 644 (Old Keene Mill Road) (https://maps.google.com/maps?q=fairfax+county+parkway+%26+old+keene+mill+road,+springfield,+va&hl=sv&ll=38.769242,-77.287982&spn=0.004676,0.009645&sll=39.073328,-76.955752&sspn=0.004656,0.009645&t=h&hnear=Fairfax+County+Pkwy+%26+Old+Keene+Mill+Rd,+Burke,+Fairfax,+Virginia+22015&z=17), in Fairfax County has had many serious crashes (including some fatalities). The next intersection to the north, at Va. 645 (Burke Lake Road) (https://maps.google.com/maps?q=fairfax+county+parkway+%26+old+keene+mill+road,+springfield,+va&hl=sv&ll=38.776018,-77.294869&spn=0.004676,0.009645&sll=39.073328,-76.955752&sspn=0.004656,0.009645&t=h&hnear=Fairfax+County+Pkwy+%26+Old+Keene+Mill+Rd,+Burke,+Fairfax,+Virginia+22015&z=17) has also had quite a few wrecks.
Idaho 55 and Railroad Avenue in McCall, Idaho.
Try making a left turn from Railroad onto 55 south on weekends. I dare you.
I can't think of any intersections in Wichita that are really annoying. Traffic here is pretty good.
This one (http://maps.google.com/maps?hl=en&ll=37.751876,-97.26236&spn=0.001755,0.001725&t=k&z=19) bothers me, but not because it ties up traffic. Why end the lane on northbound Woodlawn before the light?
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi917.photobucket.com%2Falbums%2Fad16%2FBJFRacing01%2Fmalfunctionjctthenandnow.png&hash=89e6db6ddda3eb3fccf3ee8d73b5cfb168bb44b0)
Here is why I'm not fond of Malfunction Junction in Missoula. As you see in these Google Earth snapshots, the one on the left is from far back as 2002 when on South Avenue, you actually can cross BOTH Russell Street AND Brooks Street/US 12 Business. But, just as recently as 2006, Missoula decided to hash that idea and stub off South Avenue, hence what you see on the right. Now, you CAN'T cross BOTH Russell OR Brooks. When heading eastbound on South Avenue, it dead ends at Blackjack Pizza. That means you have to loop back, head to Washburn Street, then make a right onto Brooks. Okay, yeah, that's confusing for those who never been to Montana and have never visited Missoula. Now, that goes for when you head westbound on South Avenue. It doesn't dead end, but, you have to make a right turn only onto Brooks. Heading southbound on Russell Street, you can turn right onto South Avenue, same with heading southwestbound on Brooks/US 12 Business, but you CAN'T go left from either street.
Ah, I love it when a name like Malfunction Junction lives up to its bidding. Imagine what would happen next if either route were to be bypased. What a mess that will make!
There is really none that stand out above the others around my way. Just your typical bad signal timings and of the sort, but nothing that really has something uniquely bad about it to mention.
Maybe the John Young Parkway and LB. McLeod Road intersection would come close if any.
Basing it entirely on safety, here are some annoying intersections in Southeast Michigan. Data compiled from SEMCOG and looks at 5 years of crash data from 2007-2011.
The intersection with the highest crash rate in SE Michigan...
Ford Road @ Haggerty Rd (Total Crashes = 402; Injury crashes = 75):
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi478.photobucket.com%2Falbums%2Frr144%2Ftradephoric%2FTransportation%2520Pictures%2FRandom%2FFordRdHaggertyRd.jpg&hash=9cf843d6a65d14611f748908f4fd4512db0eec8e)
The intersection with the highest number of injury accidents in SE Michigan...
12 Mile @ Dequindre (Total crashes = 368; Injury crashes = 97):
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi478.photobucket.com%2Falbums%2Frr144%2Ftradephoric%2FTransportation%2520Pictures%2FRandom%2F12MileDequindre.jpg&hash=4e8ae28f1bb0c5c08cf2f62190bb83c2cca9bd75)
Both intersections seem innocuous enough but for one reason or another they are plagued by high accident rates.
Washington Circle in the District of Columbia. Poorly designed in many ways, uses traffic lights whose cycles often make little sense, and a general feeling of anarchy whenever I drive there (so I avoid it).
I can think of other intersections that annoy me at certain times of day (such as the one nearest my house because the red light is too long, but if I said what intersection it is, I'd basically be pinpointing where I live) or if I'm in a certain lane (due to poor traffic flow or the like). But those are more esoteric.
In my area, southeastern PA, the most annoying intersections are local (township-controlled roads) that have STOP signs placed in completely illogical locations as a means of speed control; which is an MUTCD No-No BTW... regardless of which authority owns the road (state, county or town).
One annoying intersections near me:
(Secane) Upper Darby/Springfield Township: Providence Road/North Ave./South Ave. intersection/traffic/train signal at the SEPTA train station. Northbound traffic along South Ave. (heading towards the intersection) can sometimes back up for about 1/2 mile during and after the gates go down (for a train). The reason: despite having a center/left turn lane, many don't completely move over to that center lane; traffic turning onto eastbound Providence Road aren't obstructed when the gates are down and have a green right-turn arrow.
In Boston: Kenmore Square. Too many separate crossings for pedestrians, too many diverging routes with signals for vehicles. Cars frequently get confused by seeing two adjacent signals, one for traffic going slightly to the left, one for traffic going slightly to the right.
In Ipswich: Every intersection along Central/East Main Street (MA 1A) because there is too much traffic to ever get to turn unless you just go, oncoming traffic be damned. Also, East Street and County Street is pretty bad. It's a T where East ends at County, but it's on the outside of a curve on County and there is a building right against the road on the corner that blocks any view of oncoming traffic, plus people tend to do 40-45 through there since it is just south of where the speed limit changes from 25 to 40 on County. Google Maps: http://goo.gl/maps/UoVXk
[Also, looking at that map, I had always thought that the through road was County on both sides. I guess that's what you get when you never post street signs.]
Quote from: 1995hoo on November 07, 2012, 10:09:12 AM
Washington Circle in the District of Columbia. Poorly designed in many ways, uses traffic lights whose cycles often make little sense, and a general feeling of anarchy whenever I drive there (so I avoid it).
Most traffic circles in the District of Columbia are terrible in terms of traffic engineering (they are
definitely not roundabouts). Dupont Circle is
bad, but perhaps the worst two are on the D.C./Maryland border.
Chevy Chase Circle (https://maps.google.com/maps?q=chevy+chase+circle+chevy+chase+md&hl=en&ll=38.967651,-77.077149&spn=0.002332,0.003648&safe=off&hq=chevy+chase+circle+chevy+chase+md&t=h&z=18) on the border where Connecticut Avenue (Md. 185 north of the line) crosses Western Avenue has had more than a few bad wrecks.
16th Street at Eastern Avenue and Colesville Road (https://maps.google.com/maps?q=colesville+road+and+16th+street,+silver+spring+maryland+20910&hl=en&ll=38.991579,-77.035763&spn=0.002331,0.003648&sll=38.992488,-77.035875&sspn=0.009323,0.014591&t=h&hnear=Colesville+Rd+%26+16th+St&z=18) on the south side of Silver Spring is (unlike most other circles in D.C.) mostly unsignalized and very crash-prone, yet there has been no serious effort at re-engineering this busy intersection.
In San Francisco: Oak and Octavia (https://maps.google.com/?ll=37.774785,-122.424645&spn=0.019233,0.042272&t=m&z=15&layer=c&cbll=37.774799,-122.424524&panoid=sQG7jEBQW_CYBvIEIFrKlw&cbp=12,87.53,,0,-4.66). I live very close to the stub end of the Central Freeway, and I generally think think the re-do of Octavia was reasonably well done, even when I'm walking through the area on foot. But this intersection is always a mess, with lots of aggression in drivers trying to get to the right-turn lane (or lanes, depending on time of day), and making illegal turns from the left lanes.
Next up: Mission, South Van Ness, Otis, and 12th St (https://maps.google.com/?ll=37.773188,-122.418498&spn=0.001712,0.002642&t=k&z=19), which includes US 101. I may not drive through here very often, but when I do, I always get confused. This needs more advance lane signage and/or pavement markings.
Next: Alemany, Crescent, Peralta, Putnam, and an I-280 ramp (https://maps.google.com/?ll=37.734915,-122.410915&spn=0.001713,0.002642&t=k&z=19), which gets easily overwhelmed. The Alemany/Bayshore/San Bruno/Industrial mess below the US 101/I-280 interchange is also extremely convoluted.
Honorable Mention: Howard and South Van Ness (heading south on Howard and want to continue south? no can do), Fell and Divisadero, Duboce and Guerrero, pretty much any intersection involving 13th St.
When I lived in San Diego: Torrey Pines, North Torrey Pines, and La Jolla Village Dr.
In San Francisco: Hayes and Gough. If you're making a right turn from Hayes EB to Gough SB, here's your traffic signal cycle:
* 00:00: Red: about 60 seconds (not sure of exact duration, but there's no right turn on red, so it doesn't matter)
* 01:00: Walk signal for pedestrians across Gough begins, with about a 10-second countdown
* 01:01: Your green begins (but yield to pedestrians!)
* 01:10: Your green ends (as pedestrians are still crossing; continue to yield to them, and no turn on red!); restart cycle
This adds seasoning to your simmering "can't find parking" rage.
(Yes, Caltrain + Muni, etc. which is fine for us, but not as much for the grandparents and kids)
in San Diego, CA-52 at CA-125. it's a freeway interchange that completely clogs up between 6:15am and 9:30am on a weekday. if I don't leave my house by 5:50, I am cooked.
There are probably a good many intersections in Baton Rouge that could qualify, but my personal nomination is actually a series of too-closely spaced signalized intersections - College Drive @ Rabey/Bennington, College @ Constitution/I-10, and College @ Corporate Boulevard. Avoid at all cost during rush hour.
Honorable mention: Airline Highway @ Old Hammond Highway
In my particular neighborhood of Seattle, NE 75th St. & 25th Ave. NE. Fairly heavy traffic in all directions, no left turn phase of the signal, lots of drivers going 40+ in both directions even though the posted limit is 30, no left turn lanes going E-W. Pedestrian traffic due to fairly busy bus stops and a middle school 1/4 mile away. It's really having no left turn phase of the signal that's the biggest problem; if drivers wait to make their turns until the intersection is clear there's often no chance during the green light. So they run the yellow/red or try to turn quickly before oncoming traffic and cause an accident.
Rochester, NY: Winton Rd, Elmwood Ave, and Monroe Ave (NY 31) (Twelve Corners). Lots of lights, lots of traffic turning left and right. Takes about five minutes to get through, as you can count on getting two lights red most of the time. No right on red, for reasons unknown.
Potsdam, NY: US 11, NY 345, Clarkson Ave, and Maple St; this 5-way intersection takes a long time to cycle. If you're a pedestrian here, you also have to wait for the light to cycle. Amazingly, rights of red are allowed, but they're dangerous if you don't know which "spoke" of the intersection has the green light. For example, turning right from US 11 north to Clarkson Ave, you have no less than three different conflicting movements (Maple to Clarkson Ave, US 11 south to Clarkson Ave, and straight from NY 345).
Quote from: deanej on November 07, 2012, 02:18:45 PM
Rochester, NY: Winton Rd, Elmwood Ave, and Monroe Ave (NY 31) (Twelve Corners). Lots of lights, lots of traffic turning left and right. Takes about five minutes to get through, as you can count on getting two lights red most of the time. No right on red, for reasons unknown.
Two words: school crossing.
Quote from: Billy F 1988 on November 06, 2012, 10:13:24 PM
Where you live, which intersection annoys you?
Damn near every intersection in my neighborhood is annoying. So I'll just examine one: http://goo.gl/maps/TMZeI
It's the intersection of:
1) Van Cortlandt Park South, the west leg. VCPS continues through the NE quadrant as a pedestrian/stair street, but the roadway itself becomes:
2) Van Cortlandt Avenue West, erroneously known to NAVTEQ, and thus much of the world, as Van Cortlandt
Park West. (Such a street, if it existed, would actually be Broadway.) That's the east/southeast leg.
3) Bailey Avenue, the south leg.
4) I-87 NB on/off ramps, along with the Van Cortlandt Park golf course access road, as the north leg.
Much of what's annoying has to do with signals and timing. The north and south legs have their own separate green phases, but there are no arrow indications, so it's not evident that you have a protected green. Motorists in the know who want to turn left will just barrel through the green lights (creating conflict with pedestrians of course), and get impatient with unfamiliar motorists, who might be inclined to yield to oncoming traffic, not knowing that it still faces a red light.
Pedestrian signal timing is even more annoying. Imagine you're a pedestrian at the SW corner and want to cross Bailey Ave. Traffic next to you, on VCPS, gets a green light along with a left arrow onto I-87. There is absolutely no traffic that conflicts with you, since there's no turn on red in NYC, and even so, right turning traffic off of VCPS has its own channelized lane behind you.
Then the left arrow goes out, and it's green both ways, for VCPS and VCAW. Now you get a Walk signal...but of course, there's left-turning traffic coming at you from VCAW, and it makes up a significant percentage of the intersection's traffic. And this being an outer borough, turning motorists are hazardous because they try to beat the oncoming traffic, and don't encounter as many pedestrians as in Manhattan.
(Incidentally, the same Walk signal timing exists on the next eastward intersection as well.)
A few other annoyances stem from the confusing array of street names, traffic speeds and volume in relation to pedestrians, and from the existence of the park access road, an unexpectedly two-way street merging into the I-87 ramps. Wisely, at least, it's park traffic that has to yield to freeway ramp traffic and not vice-versa.
But yeah, head east up VCAW to the intersection with Sedgwick Avenue, Gouverneur Avenue and Stevenson Place, or further to the intersection of Sedgwick, Goulden and Dickinson Avenues with Mosholu Parkway (the signal situation here is especially weird) and you have enough annoyances for a week.
Quote from: empirestate on November 07, 2012, 02:59:31 PM
Quote from: deanej on November 07, 2012, 02:18:45 PM
Rochester, NY: Winton Rd, Elmwood Ave, and Monroe Ave (NY 31) (Twelve Corners). Lots of lights, lots of traffic turning left and right. Takes about five minutes to get through, as you can count on getting two lights red most of the time. No right on red, for reasons unknown.
Two words: school crossing.
Wouldn't the no right on red be only during school hours then, rather than 24/7/365? Plus they have crossing guards during the morning and afternoon rushes, and even a ped-only light placed in the worst possible location (between the middle school and high school, close to twelve corners such that it's arguable un-needed for northbound ped traffic and useless to southbound ped traffic).
Quote from: deanej on November 07, 2012, 03:51:27 PM
Quote from: empirestate on November 07, 2012, 02:59:31 PM
Quote from: deanej on November 07, 2012, 02:18:45 PM
Rochester, NY: Winton Rd, Elmwood Ave, and Monroe Ave (NY 31) (Twelve Corners). Lots of lights, lots of traffic turning left and right. Takes about five minutes to get through, as you can count on getting two lights red most of the time. No right on red, for reasons unknown.
Two words: school crossing.
Wouldn't the no right on red be only during school hours then, rather than 24/7/365?
Maybe, if that were the only reason, which I admittedly gave by way of simplicity. But the complex geometry of the intersection(s), combined with traffic volumes, adjacent driveways and all of that are also contributing factors, no doubt. It's my observation in that area that anything other than a bread-and-butter four way intersection with no arrow signals tends to get the NTOR treatment. Just look up north on Winton Road at East and University Avenues...simple, 4-way intersections (save for the I-490 WB on ramp from East/Winton), but also NTOR because of these added factors.
Tulsa is on a grid, so there aren't very many odd surface street intersections where 3 streets cross or anything like that. The worst intersections here are freeway to freeway interchanges. One of the worst is US 64/US 169/OK 51, which is a cloverleaf. It gets backed up during rush hour, especially the movement from NB 169 to WB 51. There are no C/D ramps, so the loop ramp just dumps you onto the highway. There are several other underpowered interchanges in the metro, but this is the one that stands out to me.
Oh, hey, NJ's not here yet.
* Any intersection in Essex County with a pretimed traffic signal. This isn't the 1960s, we have technology to solve this problem now. I don't need to sit for 60 seconds in backed up traffic at a light with no cross traffic.
* US 46 @ Beverwyck Rd., Parsippany (https://maps.google.com/?ll=40.862783,-74.384461&spn=0.001049,0.002422&t=h&z=19) - Every afternoon, 46 reliably backs up half a mile or more, often taking 10 minutes to get through the intersection. The problem is a 4-phase traffic signal with a busy cross street. The solution is not only obvious, but easy to implement - 3 through lanes each way on 46 instead of 2, and a longer WB second left-turn lane so that demand isn't getting starved on each cycle. There's room to do this through restriping and maybe a little curbline modification without taking anyone's property.
* US 46 @ Smith Rd., Parsippany (https://maps.google.com/?ll=40.867599,-74.412873&spn=0.002097,0.004844&t=h&z=18) - Timed so that you can't get a green light at Vail Rd. (just to the east) and a green light turning onto Smith. The problem at Smith Rd. is that a 2-phase signal at 46 is right next to a 3-phase signal at Smith/Littleton Rd. The timing is coordinated between them, but 46 has WAY too much green time for its own good. The WB left turn to Smith Rd. is largely going to Littleton, but whereas both WB left-turn lanes go to Smith, only the right one has the option for Littleton. The intersection should be restriped to let both lanes turn onto Littleton (with the left lane going to 287 North) and retimed to give more time to cross traffic and less to the 46 mainline.
Quote from: kphoger on November 06, 2012, 11:04:26 PMI can't think of any intersections in Wichita that are really annoying. Traffic here is pretty good.
We are indeed blessed in Wichita, but so much goodness causes the moderately bad to stand out more--I-235/Zoo Blvd. comes to mind.
QuoteThis one (http://maps.google.com/maps?hl=en&ll=37.751876,-97.26236&spn=0.001755,0.001725&t=k&z=19) bothers me, but not because it ties up traffic. Why end the lane on northbound Woodlawn before the light?
Given that the hatched-off area approaches the width of a full traffic lane at the light, I think it is an interim treatment until a later project widens Woodlawn (probably to a five-lane curb-and-gutter section) north of 37th Street.
In Bend, some annoying ones were Powers Rd. at Brookswood Blvd, and Simpson Ave. at Mt. Washington Dr. During after school hours and rush hour, it can be nearly impossible to turn left (it was 2 way stops on Powers and Simpson, with the cross traffic free flowing). One time, I saw cars backed up for about a half mile on Simpson behind the stop sign at Mt. Washington, to the point where people were just turning around rather than waiting 20 minutes at the stop sign. Luckily, they just built roundabouts at both intersections, that should fix that.
And look at this silly Google sattelite timing. I wonder how long there will be no road shown at Brookswood/Powers? They took the pic during construction https://maps.google.com/maps?hl=en&ll=44.028248,-121.319361&spn=0.006611,0.016512&t=h&z=17 And same exact thing at Simpson and Mt. Washington: https://maps.google.com/maps?hl=en&ll=44.04581,-121.343157&spn=0.006609,0.016512&t=h&z=17 ...and Empire and 18th: https://maps.google.com/maps?hl=en&ll=44.089997,-121.279192&spn=0.006604,0.016512&t=h&z=17 Great timing Google, 3 major intersections not shown on your new sat images :P And if you're guessing that traffic has been hell all summer in Bend, you'd be right :D
Another bad one is Reed Market Rd. and the intersections with American Ln. and 9th St. https://maps.google.com/maps?hl=en&ll=44.036827,-121.289119&spn=0.002337,0.004128&t=h&z=19
Combine the constant stream of traffic on Reed Mkt with people attempting to turn left off the narrow bridge at American, and the train that goes through there at seemingly the worst times, backing up traffic on Reed Mkt for a mile, and it can be pretty bad at times.
The terminus of Northwestern Hwy at Orchard Lake Road forms the 'Bermuda triangle' of traffic signals in Farmington Hills, Michigan. At least one direction of travel gets poorly timed green-to-red signal coordination due to the geometry of the area. There are plans to construct a multi-lane roundabout in the coming years but only time will tell if this helps improve traffic flow in the area.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi478.photobucket.com%2Falbums%2Frr144%2Ftradephoric%2FTransportation%2520Pictures%2FRandom%2F14mile-orchardcurrent.jpg&hash=ad076b8cd03a829482ae0f5c37ef0581ecf35a34)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi478.photobucket.com%2Falbums%2Frr144%2Ftradephoric%2FTransportation%2520Pictures%2FRandom%2F14-orchardlk.jpg&hash=e6ded3fe7b9a6d9ae8a56fa109c42edf2b4c6c19)
While not the most congested intersection by any means, the most annoying intersection in my hometown is Conduit Road and Old Town Creek Way, which is home to a few businesses (including Sheetz). The signal often changes for just one car on the cross street while traffic on Conduit is flowing normally. Conduit northbound traffic is just past the busiest signal in the city and southbound heads down a hill to the signal.
In Omaha, I can't really think of anything that's truly annoying. There used to be some, but with reconstruction, I think a good number of intersections are better than they used to be. The only thing that really irritates me is in Bellevue, they still have the traffic lights on Fort Crook Road set up as if US 75 still follows it, which means the timing of the traffic lights makes absolutely no sense if you are unfamiliar with that fact.
Beauharnois: Hwys 132 and 236 (http://maps.google.ca/maps?q=Rue+Saint-Laurent+%26+Chemin+Saint-Louis,+Beauharnois&hl=fr&ie=UTF8&ll=45.314129,-73.878599&spn=0.00278,0.004823&sll=45.558042,-73.730303&sspn=0.677891,1.234589&t=m&hnear=Rue+Saint+Laurent+%26+Chemin+Saint+Louis,+Beauharnois,+Beauharnois-Salaberry,+Qu%C3%A9bec+J6N+1X8&z=18). Here's a quick chart (chevrons denote traffic direction, X's denote stops) :
X
132 <<<<<<<<<< |<<<<<<<<<<<<< 132 WB
>>>>>>>>>> |<<<<<< (< must turn left)
v¯X
v^
132/236 v^
v^
v^>>>>>>>>>>>>>> 132 EB
v^>>>>>>>>>>>>>>
v^
v^ ^
236 N
In case you don't know about Québec's numbering scheme, 132 is a primary and 236 is a secondary. Traffic counts are consistent with this (12,100 vs. 2,800).
Traffic from 132 EB (from the left on the chart) does not stop nor yield (despite the presence of a ramp). Traffic from 132 WB does stop. Traffic from 236 stops too. It's a two-way stop in a T.
Technically, when turning from 132 WB onto 236, it's the same as having to cross the other lane of traffic in the absence of a couplet. It would be a nightmare during rush hour no matter what.
However, with people being people, and Greater Montreal drivers being Greater Montreal drivers, it doesn't quite work that way in practice. Turning traffic from 132 WB will try to wedge themselves into traffic, possibly making dangerous manoeuvers, or just sit there honking because they think 132 EB has to yield; often in the middle of the thing, blocking everyone else. People sitting at the stop line like they should will get honked at by the drivers behind them, and the quickly-filling turn lane will spill on the mainline.
Coming from 132 EB, you have to be on the watch for drivers cutting you off as explained above. Or the driver in front of you slamming the brakes because he's been cut off. Or the driver in front of you yielding or even letting several vehicles pass. You get the idea.
Add to the equation vehicles trying to leave the Subway restaurant on 132, in the middle of the T. Usually, nobody cares about those.
Coming from 236 and turning right on 132 EB, you have to watch for oncoming drivers turning into 132 EB's right lane by automatism or pure ignorance. And if you're a pedestrian on 236, I wish you good luck crossing that intersection despite the marked crosswalk.
The opening of A-30 next month will put a long-awaited relief on this.
This (http://maps.google.com/?ll=37.679494,-97.264189&spn=0.004551,0.004801&t=k&z=18) is the closest I get to being annoyed at an intersection in Wichita. Almost all cars exiting eastbound Kellogg onto the frontage road are either going straight through the Woodlawn light or turning right at it–either of which requires changing lanes (http://maps.google.com/maps?saddr=US-400+E&daddr=E+Kellogg+Dr+S&hl=en&sll=37.680415,-97.265922&sspn=0.006436,0.009602&geocode=FRjxPgIdnccz-g%3BFRTwPgIdVOUz-g&t=k&mra=dme&mrsp=1&sz=17&z=17), since their lane turns into a crossover. At the afternoon rush, red light traffic frequently backs up to the gore point, leaving no room for drivers to merge. I drive through there at least once a week during this rush period. However, I'm usually starting out on the frontage road and making the U-turn to go back west (http://maps.google.com/maps?saddr=S+Christine+Rd&daddr=E+Kellogg+Dr+S&hl=en&ll=37.68039,-97.266008&spn=0.006436,0.009602&sll=37.680415,-97.265922&sspn=0.006436,0.009602&geocode=FW3tPgId7sUz-g%3BFSDwPgIdGuQz-g&t=k&mra=dme&mrsp=1&sz=17&z=17). So it's actually quite nice for me, because I (1) don't have to wait behind 700 cars for a green light, and (2) find it rather fun to box my way through everybody into the (empty) U-turn lane.
This (http://goo.gl/maps/JvELQ) intersection in Monroe is the worst... traffic merging in from US 165B/LA 15 onto I-20 East goes from one ramp lane to two, then back down to one, in a short distance. Not only that, but look to the west, and Layton Avenue doesn't even have an acceleration lane, just a yield sign. Combine that traffic that's slowly speeding up to 60 MPH, along with the bottlenecked LA 15 traffic, and you have a danger for the traffic going from I-20 to LA 594 (the next exit).
Other than that, Monroe is relatively fine with intersections.
Quote from: tradephoric on November 07, 2012, 08:12:19 PM
The terminus of Northwestern Hwy at Orchard Lake Road forms the 'Bermuda triangle' of traffic signals in Farmington Hills, Michigan. At least one direction of travel gets poorly timed green-to-red signal coordination due to the geometry of the area. There are plans to construct a multi-lane roundabout in the coming years but only time will tell if this helps improve traffic flow in the area.
Is everything in that roundabout proposal at grade?
Quote from: mcdonaat on November 08, 2012, 05:55:53 PM
Other than that, Monroe is relatively fine with intersections.
The West Monroe end of the Endom Bridge. (http://maps.google.com/maps?q=Endom+Bridge,+Monroe,+LA&hl=en&ll=32.499721,-92.121033&spn=0.000981,0.001629&hnear=Endom+Bridge,+West+Monroe,+Ouachita,+Louisiana+71201&gl=us&t=h&z=20) A stop sign for North Riverfront Street traffic, a yield sign for Coleman Street traffic, and nothing at all for traffic coming off the bridge. Trying to make a left turn onto the bridge from North Riverfront Street can be pretty fun because you can't see traffic coming off the bridge unless you pull dangerously far into the intersection. Trying to make a left turn on North Riverfront from Coleman during rush hour can get pretty hairy, too, because it blocks off all the bridge-bound traffic and anyone trying to get off South Riverfront.
Quote from: InterstateNG on November 09, 2012, 10:25:51 AM
Quote from: tradephoric on November 07, 2012, 08:12:19 PM
The terminus of Northwestern Hwy at Orchard Lake Road forms the 'Bermuda triangle' of traffic signals in Farmington Hills, Michigan. At least one direction of travel gets poorly timed green-to-red signal coordination due to the geometry of the area. There are plans to construct a multi-lane roundabout in the coming years but only time will tell if this helps improve traffic flow in the area.
Is everything in that roundabout proposal at grade?
Yes it is.
There may be issues with traffic backing up through the roundabout due to the close proximity of the traffic signal just north of the roundabout on Orchard Lake Road (roughly 300 feet away). However, the design calls for Orchard Lake, 14 Mile, and Northwestern to be widened to 6-lanes before the roundabout (currently all 4-lane roads) which should help increase capacity and queuing space. Also, the traffic signals in the surrounding area are simple 2-phased signals making shorter cycle lengths possible (which should also help reduce the length of queues between the signal and the roundabout). That being said, having a traffic signal just 300 feet away from a multi-lane roundabout may be problematic.
Here in Salinas, it would have to be Natividad Rd. at Boronda Rd. Very jammed on Boronda as it is a very busy two-lane road which no one with the right mind would even think about not widening it. On the other hand, Natividad Rd. is six-lanes south of Boronda while it it only two lanes north of Boronda. Traffic is backed up until a mile to the east and half a mile to the west.
Actually I stand corrected about intersections in my hometown. I forgot about the Orange Blossom Trail and Hunter's Creek Blvd./ Falcon Trace Blvd. intersection with TWO left turn lanes that have no traffic to warrant it. Then nearby, the Orange Blossom Trail & Town Center Boulevard Intersection has only ONE turn lane going NB to WB with far more traffic than that going from SB OBT to Falcon Trace. Furthermore, both intersections were modified during the Orange Blossom Trail widening 7 years ago under the same engineer.
Then you have the the Central Florida Parkway & Orange Blossom Tail intersection with the signal mast arms on the wrong side of the intersection. A simple fix is to unbolt the current assembly and turn them 90 degrees and you have them where they need to be along with reversing the default setting of the timers so its not reverse in operation. The thing is the County who maintains the signal says that because the stop bar is 40 feet from the signal installation no rules are being broken. However, as true as that is that is what makes it so annoying is the fact the stop bar is too far away from the actual intersection. It makes you feel that you are being reprimanded from being too close to an intersection for an unknown reason.
Quote from: roadman65 on November 10, 2012, 11:57:04 AM
Orange Blossom Tail
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ftvmedia.ign.com%2Ftv%2Fimage%2Farticle%2F114%2F1147540%2Fbeavis-and-butthead_1278532869_1296688382.jpg&hash=232cdab9e4df85325adc163c297e76ab7fc63998)
http://goo.gl/maps/sxMSJ
Rogers Ave (AR 22) at 19th St and A St in Ft Smith
3 different green sequences and if you're not paying close attention, you forget which signal is yours.
Oh, NE 2 if you think OBT is annoying then you should see what they did from Landstreet to Oakridge. Now they paved the two right lanes as well as the auxillary lanes, so all signal loops are inoperative and you can get nailed at both Lancaster and Orlando Central Parkway waiting for the long timed greens on the two side roads. I mean you get stopped at one, wait a while, then proceed to the next to repeat the process again. Two lights in almost five minuets to pass at times.
I do not think it will be fixed as the project is no where near started, as it is to rid the center turn lane for a grassy median like from Oakridge to I-4 was done all Winter and Spring. I do not even know why the two right lanes were resurfaced anyway because they cannot do the left lane until after the median is completed that may be months as FDOT gives the contractor until May 13 to take their time and finnish the job. Plus, they have to add the water lines for the sprinkler system that requires to dig up some of the newly laid asphalt to have it reach. So prepare yourself if you travel through the area.
Good news is they finally started work on Desination Way from John Young Parkway as you stated that will ease some congestion through that area upon completion.
Quote from: roadman65 on November 10, 2012, 11:39:31 PM
Good news is they finally started work on Desination Way from John Young Parkway as you stated that will ease some congestion through that area upon completion.
Uh, they started work on this a couple years ago. What they're doing now is temporarily connecting it to Futures Drive.
Quote from: tradephoric on November 09, 2012, 12:18:27 PM
There may be issues with traffic backing up through the roundabout due to the close proximity of the traffic signal just north of the roundabout on Orchard Lake Road (roughly 300 feet away). However, the design calls for Orchard Lake, 14 Mile, and Northwestern to be widened to 6-lanes before the roundabout (currently all 4-lane roads) which should help increase capacity and queuing space. Also, the traffic signals in the surrounding area are simple 2-phased signals making shorter cycle lengths possible (which should also help reduce the length of queues between the signal and the roundabout). That being said, having a traffic signal just 300 feet away from a multi-lane roundabout may be problematic.
I would guess that they would place a detector (loop or otherwise) several feet downstream of the roundabout, which would call for a green to prevent from queues backing up into the roundabout/locking the roundabout up. That was the plan on a another project I worked on a few years ago, where there was a roundabout and a signal with no more that 250 feet between them.
In the Phoenix area, the Grand Avenue (US 60) corridor with a closely paralleling railroad track and the three-way intersections was always a bear. In recent years, many of the intersections were improved somewhat with overpasses to eliminate some of the hassles, but I still usually avoid trying to cross Grand Avenue unless I use a bridge. I've never been much for waiting for trains to go by.
Six words: Avoid Bancroft Street and South Avenue! Why? I hate crossing there as a foot pedestrian because some idiots in Missoula just don't know when to stop or where to stop. I nearly got run over on 39th and Reserve this summer, and again approaching Russell and McDonald Avenue. But Bancroft and South Avenue tops my cake. It is a four-way intersection with a blinking red light hovering over it. Not exactly perfect traffic control now, is it? I really didn't think any of it until I started noticing how people can be so plum rude as I walk around town crossing Malfunction Junction, especially Bancroft and South Avenue.
Walking across the street in a short skirt? You're asking for it.
Almost all intersections here are completely sensor-actuated, therefore the level of service outside of rush-hour is pretty good.
So I don't have any annoying intersections to state. Thank you, CalTrans. <3
Quote from: Federal Route Sixty-Nine on November 13, 2012, 05:12:18 PM
the level of service outside of rush-hour is pretty good.
that's like saying that your car's crumple zones work well, except during a crash.
Flashing red lights should be outlawed. People can't be expected to see them and stop.
Every four-way intersection should have neon stoplights, rumble strips, spike strips, and armed police officers.
Quote from: agentsteel53 on November 13, 2012, 05:13:11 PM
Quote from: Federal Route Sixty-Nine on November 13, 2012, 05:12:18 PM
the level of service outside of rush-hour is pretty good.
that's like saying that your car's crumple zones work well, except during a crash.
It's like having health insurance but having to pay the doctor's office whenever you actually get sick. Oh, wait, that's how insurance works.
It's like saying your child is well behaved, except when you tell him to do something he doesn't want to do.
It's like saying you're committed to your wife for life, except in the event she does something unforgiveable.
It's like saying your sofa is really comfortable, as long as you don't sit there for very long.
On the other hand.....
It's like saying planes and trains run on time, except when there's a blizzard.
It's like saying orders are processed very quickly, except during the holiday season.
It's like saying you're a brave man, except when facing death.
I mean, really, what do you expect?
53rd Street and Ripley in Davenport, just outside of my high school. The problem is that it's a 3-cycle light (NB and SB are separate) that runs on a timer, NOT a sensor, and 53rd has a 90-second green. This gets incredibly bad when school gets let out, especially because the majority of the students make a right turn out of the school. (Link) (https://maps.google.com/maps?hl=en&ll=41.574664,-90.577268&spn=0.001374,0.003262&t=k&z=19)
Quote from: Federal Route Sixty-Nine on November 13, 2012, 05:12:18 PM
Almost all intersections here are completely sensor-actuated, therefore the level of service outside of rush-hour is pretty good.
So I don't have any annoying intersections to state. Thank you, CalTrans. <3
This logic is flawed. Signals with sensors don't fix the underlying problems of a poorly designed arterial system. The 1/2 mile grid is a nightmare to provide good signal progression and this is exactly what you deal with in Orange County, CA. Here's a typical time-distance along a major high speed arterial with traffic signals every 1/2 mile (ie. Beach Blvd).
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi478.photobucket.com%2Falbums%2Frr144%2Ftradephoric%2FTransportation%2520Pictures%2FRandom%2F05milespacingtimedistance.jpg&hash=c53e7de2b300ca510778c45b4146381aefe937a6)
^ I should have specified DUAL signal progression. :pan:
It's not too hard to provide good signal progression in one direction of travel.
Quote from: kphoger on November 13, 2012, 05:33:11 PM
It's like saying planes and trains run on time, except when there's a blizzard.
It's like saying orders are processed very quickly, except during the holiday season.
It's like saying you're a brave man, except when facing death.
I mean, really, what do you expect?
only the middle of those is analogous. it's an even whose timing and intensity can be predicted with almost complete certainty, and therefore infrastructure should be capable of handling it.
Lake Oswego's six-way, ALL STOP intersection of Country Club Road, Iron Mountain Boulevard, C Avenue, and Bayberry Road.
http://maps.google.com/maps?q=Lake+Oswego,+OR&hl=en&ll=45.422891,-122.67812&spn=0.00144,0.002642&sll=37.269174,-119.306607&sspn=9.454681,21.643066&hnear=Lake+Oswego,+Clackamas,+Oregon&t=h&z=19
This newly constructed Parclo A4 interchange is annoying because it ruins good traffic signal progression along Crooks Road. Crooks road is designed for good 2-way signal progression but this is lost once you get to the Parclo A4 off-ramp signals that stop both directions of travel. Freeway off-ramp signals naturally create those "half mile" signals that are nearly impossible to coordinate.
Had a Parclo B4 interchange been constructed, good signal progression could have been maintained along Crooks Road (since Parclo B4 traffic signals only need to stop one-direction of travel) but MDOT decided against that design. SPUI's and Diverging Diamond interchanges have the same problem of ruining any potential 2-way signal progression between major mile roads.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi478.photobucket.com%2Falbums%2Frr144%2Ftradephoric%2FTransportation%2520Pictures%2FRandom%2FCrooksRoad.jpg&hash=f6df6544697bcafe5f8ac9fc8bf5326b9e605582)
Wow. That's just plain stupid. What a way to waste taxpayer money for such a stupid interchange like the Crooks Road interchange.
Quote from: Billy F 1988 on November 15, 2012, 12:20:56 PM
Wow. That's just plain stupid. What a way to waste taxpayer money for such a stupid interchange like the Crooks Road interchange.
I'm assuming they named the road after the parties responsible.
Maybe.
I just found out from an engineer who wishes to remain annonymous that his firm conducted a study on the stoplight timing at the I-235/Zoo Blvd interchange in Wichita, and determined that it is likely to have been timed poorly in order to cause traffic to back up onto I-235, as a passive-aggressive way to push for the construction of another I-235 access point.
Any intersection on US 280 in Birmingham. ALDOT has failed to upgrade a road with a capacity of 50,000 when traffic counts are now nearly 100,000 daily and are projected to reach 150,000 by 2030.
Not quite in my hometown (it's about 3 towns away), but in Chelmsford MA there is a 5-way intersection with routes 110, 4, and 129 (all state routes, and west end of 129). It is a bit confusing.
Similarly, but 2 hours away, in East Longmeadow MA, there is an intersection with routes 83, 186, and 220 (and Maple Street), with part of it being a rotary. However, it says "dangerous intersection".
Apparently, 1 has a habit of resurrecting old threads over 4 months old. :pan:
In Toronto, there is no single most annoying intersection, although Yonge / Bloor comes close with construction on all sides and the single walk cycle where pedestrians can cross from any corner to any corner. >.>
(I'm not from here, but there's nothing I can say about my *actual* hometown.)
This (http://goo.gl/maps/LnWaO) intersection near my house. The rightmost lane has a divider to prevent traffic from I-64 from weaving across the road in order to reach the Wal-Mart. However, this divider also makes it almost impossible to make a right turn from Jefferson Ave NB to Brick Kiln Blvd during rush hour. The fact that there is a bottleneck on 64 WB just past this interchange (with no exits for another 5 miles) does not help things at all.
This (https://maps.google.com/?ll=37.1745,-76.551425&spn=0.007352,0.016512&t=h&z=17) interchange between I-64 EB and VA-105. Traffic on the leaves (going about 25 mph) has about 400 feet to merge with traffic going 70 on an already crowded road. Worse, traffic going from 64 WB to 105 EB or 105 WB to 64 WB has to make both a left and a right turn. Just a poorly designed interchange all around.
87th Street and Pulaski Ave in Chicago, where the intersection is a heavy truck route and has a railroad crossing right in the middle.
Don't even bother during rush hour :banghead:
Quote from: hm insulators on November 12, 2012, 01:22:56 PM
In the Phoenix area, the Grand Avenue (US 60) corridor with a closely paralleling railroad track and the three-way intersections was always a bear. In recent years, many of the intersections were improved somewhat with overpasses to eliminate some of the hassles, but I still usually avoid trying to cross Grand Avenue unless I use a bridge. I've never been much for waiting for trains to go by.
Interchanges Coming Soon to Grand Avenue
Bell Road Overpass with either Diamond or SPUI from Bell To Grand (Under Construction will be complete in 2014)
Bethany Home Road Underpass Under Grand and the Tracks
(Planed for 2016-> )
19th Avenue/Mcdowell Road
(19th Avenue Overpass over Grand Avenue & Mcdowell Road, Ramps From NB 19th Avenue to NW Grand Avenue & SE Grand Avenue to SB 19th Avenue)
(Planed for 2016-> )
The only good answer in Boone is the infamous "big" intersection where US 321 and NC 105 meet. Crossing it on 105 isn't too bad, but if you hit that intersection on 321 on a busy day or trying to turn left from NC 105, you could be waiting for 5 minutes.
I wish something could be done about it, but part of the problem is the fast food restaurants lining 321 on both sides of the intersection.
The street view image (http://goo.gl/maps/Wcfzv) is old, but it hasn't really changed since then.
Not in town, but this one is a pain in the ass to cross. Not to mention that it's frequently backed up: http://goo.gl/maps/r7djc
Discussion about thread exhumation was moved to https://www.aaroads.com/forum/index.php?topic=10156 – discussion about yawns and the yawny yawners who yawn them has been sent to Alanland.
Quote from: Scott5114 on August 16, 2013, 05:46:13 AM
Discussion about thread exhumation was moved to https://www.aaroads.com/forum/index.php?topic=10156 – discussion about yawns and the yawny yawners who yawn them has been sent to Alanland.
yawn
If by "hometown" we mean native and not current, my choice would probably be the roughly six-way intersection at Market and Hepburn Streets in Williamsport, PA. It's known as "Confusion Corner" locally. The reason this intersection exists in the first place is that the city grew outward from two sections–one which had a grid that was more or less north-south and another that was diagonal. Both sections grew outward from the Susquehanna River and met here in the late 19th century.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fbit.ly%2F15QgJF6&hash=5bf15b6cb417d0e12b35defdd8760704487c3ab5)
The intersection has no signals, which is perhaps a little unusual for an intersection with such odd geometry that passes more than 10,000 vehicles per day. Five of the six inbound lanes have stop signs–northbound Market has no stop whatsoever. This is a holdover from when US 220 was routed on city streets and through traffic had to make an almost 180° turn from Market to Hepburn. So northbound Market St. was given preference, and it remains this way today even though 220 moved to its present freeway alignment over 30 years ago.
If you're heading south on Market, you have to take turns with all of the other STOPs including anyone on southbound Hepburn–who would actually behind you to your left. You also need to yield to any northbound Market vehicles which may be turning, many of which might not have their signals on–particularly if the driver thinks Hepburn is "left" and Rural Ave. is "slight left". A little further down Rural is Williamsport Hospital, which is a significant generator of traffic, including many people who may legitimately be in a hurry or have their mind elsewhere.
If you're driving north on Hepburn, you have to yield to vehicles on northbound Market who are obscured by trees that go right up to the edge of the intersection.
In most cases, the intersection becomes something of a chicken match.
Let's discuss this intersection, shall we? The red light applies to the cars on the left, which have stopped for it, and the green light is for the road we're on. Except, see that Yield sign? That also controls the same merge as the traffic lights, so there's a conflict of information.
And routinely, motorists coming in from the left will shunt themselves over as far to the right as possible and decide that the right-hand signal face now applies to them, because it turns green first. (Note that the right turn only lane is no longer striped as such, but that doesn't really matter.)
What's your interpretation of this mess?
https://www.google.com/maps?ll=40.883047,-73.887126&spn=0.001783,0.003473&cbp=12,244.85,,0,1.29&layer=c&panoid=4uG-KaBCQgAkHjuOcNUVFg&cbll=40.883046,-73.887639&t=m&z=19
Seeing as how there's another Yield sign and no-left-turn sign out of the image to the right, clearly those apply to traffic coming through where the GSV car is. Seems odd there's no separator curb or other channelizing setup there to prevent what I'd expect to see–I'd expect the guy in the silver SUV (looks like a Nissan–the guy waiting on line behind the blue Honda CR-V) to cut over to the right and then go through the green light without stopping. That's what would happen around here in the DC area.
Quote from: 1995hoo on October 07, 2013, 09:04:50 PM
Seeing as how there's another Yield sign and no-left-turn sign out of the image to the right, clearly those apply to traffic coming through where the GSV car is. Seems odd there's no separator curb or other channelizing setup there to prevent what I'd expect to see–I'd expect the guy in the silver SUV (looks like a Nissan–the guy waiting on line behind the blue Honda CR-V) to cut over to the right and then go through the green light without stopping. That's what would happen around here in the DC area.
Yup, that's exactly what happens here as well, which is what I meant by the shunting over thing. But that raises the point of whether, if the green signal face on the right applies to the right lane, wouldn't it apply just as well to the left lane, meaning you don't have to shunt over at all? In other words, don't all the signal faces at an intersection have to apply equally to all lanes making the same movement?
And yes, the Yield signs control the approach from the north, where the Street View car is coming from. But how is this movement controlled by a Yield sign, if it's also controlled by the traffic signal ahead? Because if you argue that there's first a merge (controlled by the Yield sign) and
then the signal, the signal indication would apply equally to traffic coming from the right as from the left, because those two streams have already been combined into a single one governed by the same signal, which can't then be both red
and green.
But it's clear that the signal configuration suggests this is a five-way intersection, and the merging streams shown here are two of those five. In that case, the Yield sign is meaningless because there's nothing to Yield to, as all conflicting traffic is governed by the red signal.
So to summarize my two basic questions: 1) Is this intersection governed by both a sign and a traffic signal, and if so, how is that permissible and which device takes priority? And 2) for those motorists who do shunt over from left to right and then drive through the green, can we find fault in this maneuver, or is it a reasonable way of interpreting which signal indication applies to this traffic? (Or does it, in fact, need to be treated as a signal malfunction because conflicting aspects are displayed?)
Do all the lights ever go green at the same time? If so, then perhaps the yield signs serve a purpose in terms of helping drivers coming from the left who want to turn right at the second light (although from looking at the map I'm unsure why they'd want to do that except to park on the curb along there).
Quote from: 1995hoo on October 08, 2013, 10:31:46 AM
Do all the lights ever go green at the same time? If so, then perhaps the yield signs serve a purpose in terms of helping drivers coming from the left who want to turn right at the second light (although from looking at the map I'm unsure why they'd want to do that except to park on the curb along there).
Not all at the same time. When the signal in the background is green, one or the other of the foreground signals will also be, but not both. I think the only time the second signal goes red is when Dickinson Ave. has the green.
And you're right, there's not much non-redundant reason to turn right on Dickinson other than parking and a couple of service entrances for the senior apartments there.
The intersection of Bellevue Ave and W Highland Ave in lower Bucks County, PA.
The three stoplights at Exit 14 in Spearfish. It's not even close!
The intersection of Isabella, Flora, Tolita and E in Coronado. Drivers who are going straight through the intersection on Isabella don't need to stop. However, when you stop at the intersection from Flora, Tolita or E. There is no stop sign, there is only a yield sign. Another problem is that drivers on Isabella speed through and there is a parking lot on that street, which blocks your view around the cars, so you can't see the car that might speed and make a T-bone collision with your car.
The intersection is literally like a gamble. Sometimes, you have to stop in the middle of the intersection when you finally spot the speeding car from Isabella.
Here's the street view of the intersection: http://goo.gl/maps/QjIDD (http://goo.gl/maps/QjIDD)
Quote from: empirestate on October 08, 2013, 07:41:06 PM
Quote from: 1995hoo on October 08, 2013, 10:31:46 AM
Do all the lights ever go green at the same time? If so, then perhaps the yield signs serve a purpose in terms of helping drivers coming from the left who want to turn right at the second light (although from looking at the map I'm unsure why they'd want to do that except to park on the curb along there).
Not all at the same time. When the signal in the background is green, one or the other of the foreground signals will also be, but not both. I think the only time the second signal goes red is when Dickinson Ave. has the green.
And you're right, there's not much non-redundant reason to turn right on Dickinson other than parking and a couple of service entrances for the senior apartments there.
That certainly is a frustrating intersection, and if the combination of the traffic signal and yield sign isn't a clear violation of Section 2B.04, paragraph 10 of the MUTCD, it certainly violates the intent.
I've seen yield signs used in conjunction with traffic signals before, but only where it falls under the permissible use for a "channelized turn lane...not controlled by a traffic control signal" (from the section cited above).
This example, however, while it should be permissible under the above-referenced MUTCD provision, is a little confusing because of the presence of a green right turn arrow: https://maps.google.com/?ll=38.942079,-94.706655&spn=0.004656,0.010568&t=k&z=17&layer=c&cbll=38.942147,-94.706847&panoid=nwgAu1DoXJykGnshMcw2vg&cbp=12,306.42,,0,4.66
I suppose that green arrow is just there to say, "Ignore the yield sign; you're good."
In Port Washington, NY: The intersection of Shore Road, Sands Point Road, Cow Neck Road, and Manorhaven Boulevard. Even though all four streets are major thoroughfares, the traffic light takes forever to change if you're coming from Sands Point Road. Probably because it's a town road and the other three are county roads.
There are a couple here in Sioux Falls that are slightly confusing, but not too terribly rage inducing.
Arriving at Cleveland Avenue's intersection with 26th Street from the north, I still forget where I am sometimes because the only street blade telling me I'm at 26th Street is a really small on the middle of the stoplight post on the other side of the street (see for yourself (https://maps.google.com/?ll=43.529385,-96.69136&spn=0.072808,0.169086&t=m&z=13&layer=c&cbll=43.529486,-96.691366&panoid=0Qe44GGXcgbvq-sJpRUkcA&cbp=12,192.68,,0,8.68)).
The other used to be fine until they repainted the lanes when the intersection of N 60th Street and Cliff Avenue was undergoing construction. They're painted so horribly, and it confuses me all the time because you have to drive at a weird diagonal angle when crossing Cliff Avenue to stay in your lane, and the right lane abruptly ends a few meters after the intersection. Sadly, it's not updated on Google Maps yet, so I can't show you at the moment.
Hmmm....too many to chose from in Baton Rouge! :spin:
Before it was signalized in the early 2000s - principally due to the high crash rate, the worst intersection in Wakefield, MA (and one that I would go well out of my way to avoid) was North Ave and Albion Street. Standard 90 degree 4 way intersection, except that a) Albion Street on the east side of the intersection was (and still is) one-way into the intersection, so that eastbound traffic approaching on Albion from the west has to turn left or right onto North Ave, and b) the MBTA Reading/Haverhill commuter rail line crosses at grade across Albion through the west leg of the intersection, which meant it was impossible for traffic approaching eastbound on Albion to pull up far enough into the intersection to see approaching traffic on North Ave without straddling the tracks.
Since North at Albion has been signalized, my current "worst" intersection in Wakefield I normally try to avoid is Salem Street at Vernon Street. While both streets are minor collectors with relatively low traffic volumes, they intersect at about a 60 degree skew. Vernon is under stop control, which actually doesn't help much because you can't see approaching traffic on Salem when you're sitting at the stop lines.
Improving the intersection geometrics and installing signals has been on the state's Chapter 90 wish list for some time, but the abutters and other locals have continually objected to the project going forward - citing the need for takings.
Since this was brought up, the intersection of PA 320 and US 30 near Villanova is annoying. Not only is it the intersection of two major state routes, there are also two offset residential streets that have their own signal phases. One of them is often used as a shortcut around the Villanova campus. Furthermore, because of those side streets, there is a No Turn on Red condition for traffic coming south on PA 320, which prohibits the majority movement (right turn on red) and causes big backups. Traffic also gets bad coming from the Villanova campus on major event days due to the long light cycle.
http://goo.gl/maps/iKDTf
Quote from: Federal Route Sixty-Nine on November 13, 2012, 05:12:18 PM
Almost all intersections here are completely sensor-actuated, therefore the level of service outside of rush-hour is pretty good.
So I don't have any annoying intersections to state. Thank you, CalTrans. <3
I tend to agree, given the size and capacity of Los Angeles, the actual construction of the intersections are reasonably good. But there are some notable bad intersections:
I grew up in Los Angeles, and one of the worst intersections was Westwood/Santa Monica (and Veteran/SM and Beverly Glen/SM), because of the way that "Little SM" and "BIg SM" would conflict with each other. It was basically designed as two very closely parallel streets with lights. Making a left from BIg SM to Westwood and I'd immediately face a red light. If two more cars followed me, We'd block the intersection. But these problems have largely been eliminated thanks to the Santa Monica Blvd Parkway Project that converted the street onto one boulevard. But problems remain in Beverly Hills. See Santa Monica / Beverly Drive.
6-way intersection with no lights: Beverly/Canon/Lomitas in Beverly Hills
Other bad multi-ways with lights: La Cienega/San Vicente/Burton Way, Sunset/Hollywood/Virgil/Hillhurst, Temple/Virgil/Silver Lake, Fairfax/Olympic/San Vicente
Another bad intersection, and my vote for the worst in L.A.: Wilshire / Sepulveda. I-405 has a full cloverleaf exit with Wilshire. Cloverleafs are their own problem, but the only way they can even try to work is if there are no traffic lights involved. Right in the middle of the cloverleaf, we have a fairly busy traffic light of Sepulveda to contend with.
https://www.google.com/maps?q=sepulveda+and+wilshire+los+angeles&hl=en&ll=34.056019,-118.4515&spn=0.009155,0.014677&sll=40.867704,-73.928719&sspn=0.066335,0.117416&hnear=Wilshire+Blvd+%26+S+Sepulveda+Blvd,+Los+Angeles,+Los+Angeles+County,+California+90025&t=h&z=16
Quote from: 1995hoo on November 07, 2012, 10:09:12 AM
Washington Circle in the District of Columbia. Poorly designed in many ways, uses traffic lights whose cycles often make little sense, and a general feeling of anarchy whenever I drive there (so I avoid it).
I can think of other intersections that annoy me at certain times of day (such as the one nearest my house because the red light is too long, but if I said what intersection it is, I'd basically be pinpointing where I live) or if I'm in a certain lane (due to poor traffic flow or the like). But those are more esoteric.
If voting for my current hometown (DC area), I would have to include the Seven Corners in Falls Church. Traffic goes in every direction there. Don't forget Mount Vernon Square, and the area by RI/Connecticut/M Street that doesn't seem to have a name.
The intersection of Dixie Highway, Main Street, Rose Street and Turfway Road. It's a 5 leg intersection. The through movement for Dixie Highway involves a curve, and the intersection takes forever to get completely through unless you just say "screw it".
Quote from: mrsman on December 22, 2013, 08:32:21 AM
Quote from: 1995hoo on November 07, 2012, 10:09:12 AM
Washington Circle in the District of Columbia. Poorly designed in many ways, uses traffic lights whose cycles often make little sense, and a general feeling of anarchy whenever I drive there (so I avoid it).
I can think of other intersections that annoy me at certain times of day (such as the one nearest my house because the red light is too long, but if I said what intersection it is, I'd basically be pinpointing where I live) or if I'm in a certain lane (due to poor traffic flow or the like). But those are more esoteric.
If voting for my current hometown (DC area), I would have to include the Seven Corners in Falls Church. Traffic goes in every direction there. Don't forget Mount Vernon Square, and the area by RI/Connecticut/M Street that doesn't seem to have a name.
Seven Corners (https://maps.google.com/maps?q=38.872266,-77.155921&ll=38.872258,-77.155974&spn=0.004085,0.007929&num=1&t=h&gl=us&z=17)
is bad, though it would be
much worse if U.S. 50 (Arlington Boulevard) did not "bypass" much of it in a trench.
My candidate for such scorn - U.S. 29 (Columbia Pike) and Fairland Road (https://maps.google.com/maps?q=39.073278,-76.955692&num=1&gl=us&t=m&z=16), in Silver Spring, just south of the Md. 200 interchange. The local master plan calls for this intersection to be replaced by an overpass, but there is predictable opposition from the usual suspect groups in Montgomery County.
All of the turning movements southbound have been replaced by a jughandle, but crashes here are frequent and sometimes high-speed (posted limit is 50 MPH).
Katherine Lee Bates Road/Gifford Street/Main Street in Falmouth.
You turn right onto Gifford Street and it's only fifty yards to Main. At Main you have a Quick Lube and a fire station. When the fire station is dispatching vehicles, the emergency traffic light turns solid red and it backs up quickly. You're blocked in on KLB and if you have somewhere to go, don't plan on going too quickly.