Alewife T Station, Garage, Bus, & Trails

1 lane flowing full time should have greater capacity than 2 lanes flowing half time, and be safer too. The outside of this intersection should have been a triangle of "right turn" ramps.

The inside should have been a rotary for all left-turn movements

See the Kingston NY Traffic Circle.

And the Alewife Station exit should have been routed back out along its access road and given part of the over-wide underpass under route 2 and come up with a sharp left onto its own onramp onto 2 (teensy taking on the margin of Magnolia Field)

CTPS did a study on this intersection back in 2009 that included a couple of Modern Roundabout alternatives. While a straight-up two lane roundabout failed, a two-laner with slip lanes for the right turns works spectacularly. So spectacularly that it increases flow towards Fresh Pond Parkway so much that it breaks the downstream intersections. As a result, they dropped the option. Seriously, they dropped it because it was TOO GOOD.

http://www.ctps.org/Drupal/data/pdf/studies/highway/alewife/Alewife_Traffic_and_Bus_Operations.pdf

See Option 7.

This link to Kingston NY isn't working for me but I found pictures of it online easily enough. Does this design have a name?

It's just your standard modern roundabout with bypass lanes. We're a bit behind in MA, but these are common practice in much of the country.
 
CTPS did a study on this intersection back in 2009 that included a couple of Modern Roundabout alternatives. While a straight-up two lane roundabout failed, a two-laner with slip lanes for the right turns works spectacularly. So spectacularly that it increases flow towards Fresh Pond Parkway so much that it breaks the downstream intersections. As a result, they dropped the option. Seriously, they dropped it because it was TOO GOOD.

http://www.ctps.org/Drupal/data/pdf/studies/highway/alewife/Alewife_Traffic_and_Bus_Operations.pdf

See Option 7.
To paraphrase Tevye from Fiddler on the Roof, if expanded capacity is a curse, may the Lord smite Alewife with it. Let's transition to crushed-with-traffic roads (Mass@MVP or Concord@Fresh Pond) *after* we've move the T's park-and-ride customers in and out quickly.

It's just your standard modern roundabout with bypass lanes. We're a bit behind in MA, but these are common practice in much of the country.

I've seen a lot of new rotaries in my travels (particularly exurban Virginia), but most of these, given their emphasis cost-control and calming do not have the bypass lanes.

Seems to me the land is available to upgrade the rotaries along MVP and Fresh Pond Parkway (FPP?) and that that would be the better plan (with adequate bike/ped provisions)
 
The Fresh Pond rotaries aren't bad at all for queue management. They got successfully rebuilt for much better law-and-order only 15 years ago. The pedestrian signals spread all around are quick and painless, Cambridge's much more recent re-striping of Concord Ave. out to the Belmont town line really cleaned that area up and made the Wheeler Ct. developments more easily accessible for left-turns without getting stuck, the other side of Concord Ave. was traffic-calmed with curb juts a decade ago, the bike access is all-around superlative, and those are some of the safest ped crossings you'll ever find on roads with those kinds of volumes.

It is high-traffic, and those rotaries do back-up. But it's orderly, drivers obey the yields, they obey the ped signals, and there's little-to-no lane cheating. So it flushes cleanly. You'll never sit there at a total dead stop for minutes on end. It can usually even flush itself entirely in one ped signal cycle (and there are a LOT of pedestrians punching those buttons). Those are all the outward signs of good road design. It's not the full-speed running capacity, it's the recovery time when overtopped by circumstances outside of control and the rotaries' ability to keep near-constant flow under overload that make them well-designed.

Whoever shit all over that CTPS report seems to think that the only measure of a good road design is maximum speed limit, and that these rotaries are somehow brittle because you can't barrel through them at 45 MPH continuous all hours of the day. When that's the one and only design standard cro-magnon traffic engineers will consider, nothing helpful gets considered and you end up getting acutely counterproductive designs like "Brownsberger Square" just throwing more lanes and lane-cheating into the same vat of shit. The Concord Ave. duo are well-designed rotaries because you can overload them with an acute wave and they quickly recover. It either takes an accident, locking the entire hill to Alewife on 16E, or locking the entire hill to Huron on 16W to hose 'em. And those are not conditions related to the rotaries themselves. Not even the neverending sewer construction project that's tearing the crap out of North Cambridge with shifting detours and the the 2 years late the Concord Ave. reconstruction to Belmont has put any noticeable additional stress on the rotaries.




If they were worried about the rotaries in the CTPS study, they'd be doing these things first instead of burying it, coming back with "Brownsberger Square", and wondering why the locals violently reject that.

1) Do the Cambridge Park Dr./Rindge realignment. Because when they say they fear "Fresh Pond" backing up, they mean the hills on either side of Rindge. Yeah...damn right the hills back up! I wonder what's right at the base of them that might be causing that?

2) Tweak the 16 @ Huron Ave. signal if they're concerned about the resiliency of the other side of the Concord Ave. rotaries. 16W does back up frequently from the Huron intersection to Cambridge Honda when there's more than one car in the left lane signaling for a left turn onto Huron. There's no left-turn lane or protected left there, so first sight of a flashing blinker when cars are rounding the curve up that hill gets everybody gunning for position to pass in the right lane with a slow-speed weaving mess. That gets worse when the largely unfixable Brattle and Mt. Auburn intersections are backed up further downwind. 16W needs a protected left onto Huron at the top of the hill, so 3 out of 4 directions (excepting geometry-constrained Fresh Pond NB) have a protected-left cycle. There's plenty of room with the little grassy knoll at the top of the hill to widen it out. There isn't even a sidewalk there to inconvenience walkers.

Also, since 16W deviates off-parkway around around the block Huron-to-Aberdeen to get onto Mt. Auburn for Watertown they might as well do a free-movement right traffic island at the top for the right that keeps to the signed state highway. Again, no sidewalk on that not-special grass patch for the next 2 blocks (should be, but that's city's problem), so no inconvenience if it's shaved to fit the protected-left lane and the free-movement right island.

No change whatsoever needed on low-volume Huron itself which has protected lefts both directions. No change whatsoever needed on the parkway down to Mt. Auburn which has unimprovable geometry. And total cost of not more than a few hundred grand to shave that grass patch and achieve the complete permanent fix for this intersection.



There...you fixed the hills bookending Rindge and fixed the hill at Huron. No potential whatsoever for a backup from Huron reaching within 2000 ft. of the second Concord Ave. rotary. And as previously outlined at length the station entrance/Cambridge Park Dr. realignment means no potential for a backup from the station or interchange going up the hill to the Mall and breaching the first Concord Ave. rotary. Both rotaries become irrelevant to the job at the 2 interchange, and any further bitching and moaning from MassDOT about the CTPS study becomes moot and baseless.


Why doesn't MassDOT want to do any of those straightforward fixes, and why do they want to intentionally concern-troll the rotaries to push their "Brownsberger Square" loser at the interchange? Because they're pouting at the notion of making parkway-grade infrastructure improvements with baked-in traffic calming and just want an excuse to build expressway-grade infrastructure. More lanes, more 50 MPH speed limits, a 1972 mentality forever...and who gives a fuck who gets stuck anywhere else because the naive little local yokels wanted "traffic calming".

Totally caustic attitude. But they may actually get chastened a little for it when they see how negative the reaction is going to be to the "Brownsberger Square" concept. They'll never ever revisit anything halfway-productive, but it might actually be better to kill that add-a-lane now and let anger fester and boil a few more years at this situation so a little more of this attitude gets beaten out of them by force and some officials who don't/won't get it have 'teachable moments' made at the expense of their careers (*cough*...Senator).
 
I would support any measure to kill this current rebuild project. The current intersection configuration is a heinous disaster. Any attempt to "upgrade" it without a full configuration of some sort is severely misguided.
 
T1) Do the Cambridge Park Dr./Rindge realignment. Because when they say they fear "Fresh Pond" backing up, they mean the hills on either side of Rindge. Yeah...damn right the hills back up! I wonder what's right at the base of them that might be causing that?

An interesting tidbit related to that - I work on CPD and got a construction update last week for 130 and 88 CPD behind us. The site plan for 88 did not show vehicular access from the access road behind Summer Shack (bike/ped only), but this presentation did, both in diagram and paragraph form. The overall impact would be a parallel road to CPD to the South as far as the Hanover. With the future parking garage access point on the other side of 125, that would bring access for our side of the street up from one point to three, with one of them (the one that everyone would use) independent of CPD.

I've found no indication that Cambridge actually approved that change, but if it's happening that would be wonderful.
 
An interesting tidbit related to that - I work on CPD and got a construction update last week for 130 and 88 CPD behind us. The site plan for 88 did not show vehicular access from the access road behind Summer Shack (bike/ped only), but this presentation did, both in diagram and paragraph form. The overall impact would be a parallel road to CPD to the South as far as the Hanover. With the future parking garage access point on the other side of 125, that would bring access for our side of the street up from one point to three, with one of them (the one that everyone would use) independent of CPD.

I've found no indication that Cambridge actually approved that change, but if it's happening that would be wonderful.

Definitely room for one if they're planning to take the parking lot wasteland and stacking that capacity vertical to free up more development acreage. You'd have makings of a street grid spanning the alley on the west side of the Hanover, the alley on east side of Cambridge Systematics, a new street at the rear fence of the commuter rail maint yard, street-facing development on the parking lots facing that new street, and extension of Cambridge Park Pl. from the cul de sac through the Summer Shack lot to the T facility front gate where it would turn onto the new street. Possibly even with driveway access from the Rindge apartments under the bridge claiming the little Cambridge DPW lot.


The catch is that if it's dumping onto CPD at the same light with no thought of eventual realignment a horrible situation gets that much worse.
 
Definitely room for one if they're planning to take the parking lot wasteland and stacking that capacity vertical to free up more development acreage. You'd have makings of a street grid spanning the alley on the west side of the Hanover, the alley on east side of Cambridge Systematics, a new street at the rear fence of the commuter rail maint yard, street-facing development on the parking lots facing that new street, and extension of Cambridge Park Pl. from the cul de sac through the Summer Shack lot to the T facility front gate where it would turn onto the new street. Possibly even with driveway access from the Rindge apartments under the bridge claiming the little Cambridge DPW lot.


The catch is that if it's dumping onto CPD at the same light with no thought of eventual realignment a horrible situation gets that much worse.

AFAIK, the site plan has the new street along the back of Vecna, 100 CPD, and 150 CPD, as opposed to along the MBTA fence. They've got pedestrian access (emergency egress) back there, but the spur off of CambridgePark Place would either access the new street with a right turn or proceed straight into resident parking beneath 88 CPD. No indication of access from the east side of the bridge, but nothing to really preclude it except for landscaping.

It's not the "makings of" a street grid - this stuff is permitted and U/C. The first garage opens next month, then 130, then 88 starting in late 2016.
 
Who was the idiot who decided to send buses to Alewife and make them take 30 minutes to go half a mile out of it?
 
Who was the idiot who decided to send buses to Alewife and make them take 30 minutes to go half a mile out of it?
Seriously. Reasonable Transit Pitch: have the 79 and 350 buses operate to/from Porter Sq. Its better than trying to do Alewife<->Mass Ave at rush hour.

Isn't Alewife better though for The other buses going to/from non-Mass-Ave origins? (Arlex stuff like 62, 67, 76, 84). They just gotta find a way to make an HOV/BUS lane somewhere.
 
Seriously. Reasonable Transit Pitch: have the 79 and 350 buses operate to/from Porter Sq. Its better than trying to do Alewife<->Mass Ave at rush hour.

Isn't Alewife better though for The other buses going to/from non-Mass-Ave origins? (Arlex stuff like 62, 67, 76, 84). They just gotta find a way to make an HOV/BUS lane somewhere.

I'll bet that bus routes don't terminate at Porter because there are no good places to reverse direction there without going into the shopping plaza lot, or going way out of the way.
 
I'll bet that bus routes don't terminate at Porter because there are no good places to reverse direction there without going into the shopping plaza lot, or going way out of the way.

There isn't even a curb jut. That's something I wish they'd do right now with a little reshaping of the headhouse plaza on Mass Ave. NB. And maybe an idea to expand upon if they ever air-rights over the canyon from the station to Beacon St. Still not a terminal-terminal, but proper traffic-separated unloading spots for that many bus routes would be a big thing.


Alewife just needs those busways built to Mass Ave. as the little transit footnote to the exclamation point that is making the other sensible (i.e. not "Brownsberger Square") fixes to mitigate the conjoined-twin Parkway clusterfucks. Small-money addendum to it all. Busways, unfortunately, are only so useful when going the first 1000 ft. out the station to reach them is the same exercise in futility it is today.
 
Given that they totally punted on the 2/16 interchange cluster on Alewife Brooke Pkwy I don't have high hopes...
 
Given that they totally punted on the 2/16 interchange cluster on Alewife Brooke Pkwy I don't have high hopes...


Sen. Will Brownsberger said:
The state Department of Conservation and Recreation is responsible for the maintenance of Fresh Pond Parkway and the river intersections and will be the lead agency in the study, but the study is a collaboration among the communities of Belmont, Watertown and Cambridge and several state agencies, including the MBTA.

Aaaaaaaaaaaaaaand we're done here.
 
Yup, we'll spend a lot of money to make something marginally better for cars (if we're lucky) and probably somehow worse for everyone else.

But more likely, a preliminary study will be done and then sit on a shelf for 30+ years.
 
I agree completely. It should be plainly obvious to anyone watching or using that intersection with an eye to traffic flow that the problem has nothing to do with lane capacity. In addition to lights, they also need to fix lane weaving and cheating by solid-lining lanes on Route 2. Cheap fixes would make a huge difference here, but these are the wrong ones.

The permanent solution to this intersection is extending the Red Line to a park-and-ride further up Route 2, but that's not happening.

Equilib -- while I'm all for extending the Red Line to Rt-128 in Lexington -- that is unlikely

The realistic permanent solution is to widen the bridge at the beginning of Rt-2

That will let the cars from Alewife Pkwy heading S who want to head West on Rt-2 have their own acceleration lane to Rt-2
that in turn frees up the existing W bound lanes for the traffic coming from Fresh Pond Pky and Alewife Station clearing the Westbound bottleneck

Similarly the Eastbound Bottleneck can be reduced by taking some parking from the Bowling Alley for a dedicated lane for the Alewife Garage all the way to the Lake Street Exit. -- then the widened bridge can provide a private lane to those heading north on Alewife Pkwy to keep them from plugging the approach to the bridge

The poor man's alternative is a connector from Lake Street via Acorn Park Drive that ultimately connects to Cambridge Park Drive to bypass the Rt-2 bottleneck
 
Cambridge is exploring (again) this transit pitch:
1) A bike-ped overpass over the Fitchburg line in the Cambridgepark Dr area
2) A Fitchburg Line commuter rail platform under that overpass
Roughly, the idea is to connect "the Qudrangle" to "the Triangle" in this map:
080213i-Alewife.jpg

The Cambridge City Manager has requested $190k to study this afresh (last looked at in 2013 but a TIGER grant failed and DMUs arent' going anywhere)
City Manager Says:
This appropriation will be used to pay for completion of the feasibility study and preliminary design of a bicycle and pedestrian bridge over the Fitchburg Line commuter rail tracks to link the Alewife Triangle and the Alewife Quadrangle. The study is also reviewing the feasibility of incorporating a commuter rail station into the design, to be built at either the same time, or at a later date. The estimate for completing one or both projects ranges from $25 - $50 million. The City will continue to pursue federal, state, and other funding sources. Funds for the construction of these projects are not in the City's long-range financial plan.

A connection between these two areas has been contemplated for many years as a way to facilitate trips between the two areas and reduce vehicle trips through the congested Alewife area.

Also check it out in Bing: http://binged.it/1JzJ340
It is a $25m bridge, but if it is undertaken, it really ads value to the Quadrangle, giving it a decent walk to Alewife. If that bridge happens, adding a CR stop seems a big benefit for small incremental cost. Obviously, they have to be careful where it goes (not to mess up the MOW yard/shop), but since the main goal is not a direct tie to Alewife T, they're freer in what locations they consider than past Red-to-Fitchburg superstation pitches here (they are free to push it fairly far west).
 
How about if Alewife Brook Parkway was realigned to go down New Street behind the mall. That way the parkway would only have to go through one roundabout on Concord Ave.
 
How about if Alewife Brook Parkway was realigned to go down New Street behind the mall. That way the parkway would only have to go through one roundabout on Concord Ave.

That would have happened if the original 1960's plan for the Northwest Expressway (Routes 2 and 3) had been implemented.

I suppose an elevated highway could now be located above New Street, go over Alewife Brook Parkway, and continue behind the T station to connect with Route 2 where it crosses the Minuteman Trail. All of this new route would be elevated to minimize impacts on wetlands near the T station. But of course an elevated highway would ignite a storm of protest and would never happen
 
Last edited:
You could do split one-ways tho....EBonly going through the current station access road (under the empty / elevated part of the parking garage) and then on the current FPP alignment in front of the strip mall, and westbound following new street from the gas station past the movie theater, then in front of the projects and along the current parkway alignment to 2/16. You could leverage some of the existing overpasses at the 2/16 interchange to reduce the number of turn conflicts.
 

Back
Top