Crazy Transit Pitches

Updated future MBTA map. Big change here is sorting the GL cluster I had going into a much more readable diagram based on trunk line (Boylston or Tremont subway).

Still a few things to add (Neponset stop, Rte. 16, etc.) but feeling much better about this.


MBTA-New-Map-Green-Expansion-V2 by ecbrads, on Flickr
 
I actually don't think they would be any different than what the branch lines have for headways currently it spreads the load across more tracks than today. The only cutbacks may have to be D2 stopping at Park Street because of the track reduction past Park Street aside from that I don't think they headways would get below the headways that are currently supported on the branch lines.

F-Line could probably give a better idea of any issues that might occur.
 
I like it. But - shouldn't there be a one-seat ride from seaport to BBY, if we're going to do this right?

As far-fetched as it sounds, I'm still angling for a OL wye around Tufts, sending a new branch out down the pike and re-using the eastbound HOV tunnel to bring the OL out to the Seaport. The wye can be used to ease headways, so that it is not just a simple branch. And yes, it misses South Station, but the way the Seaport is developing I don't think that should much matter for ridership.
 
I think the Seaport branch need a bit of stop realignment.

The "D Street" stop really need to be further out than D Street -- you can see D Street from the WTC stop.

Also the Drydock area is huge and becoming a serious employment center. Probably need at least two stops in that area to service it well.
 
Cool stuff here..

no A-line to harvard?
SL gateway?
Any D-E cross-routing through Tufts to the G-line?
 
I actually don't think they would be any different than what the branch lines have for headways currently it spreads the load across more tracks than today. The only cutbacks may have to be D2 stopping at Park Street because of the track reduction past Park Street aside from that I don't think they headways would get below the headways that are currently supported on the branch lines.

F-Line could probably give a better idea of any issues that might occur.

Reopening the Tremont tunnel for any services can be accommodated without overstressing the subway by modding the Park St. inbound inner track with crossovers for thru service. The T was awarded a $12M fed grant 7 years ago to do exactly that, which entailed moving some supports and electrical boxes behind the Red Line stairs so they had a clear path to spur a crossover off the loop track. Engineering assessment turned up some complications that effectively doubled the price, and since for GLX's purposes this was a "nice to have" but not essential piece they canceled it and returned the grant.

Revisiting that now that they know what it would entail greatly helps the traffic sorting because:

  • You can wave trains running past GC to their spot on the far-end GC platform without getting stuck behind a GC-turning train on the near-end. Important OTP check on the longer-haul schedules to always give them priority.

  • GC-turning trains can turn faster with the orderly sorting if they also aren't stuck in an inbound traffic jam, making trains (esp. B's) less likely to start their runs late.

  • With outer-tracks Tremont trains (esp. whenever E's get relocated off Copley Jct.) you can keep them track assignments completely grade-separated through Boylston and Park without needing to cross over each other, simplifying downtown dispatching to just the GC-Park pick-'em.
The Park inner crossover install would be one of the very first capacity management things you do upon first post-GLX service addition. And then benefits accrue from there.

---------------

These things--all very short-term and NOW priorities--done in a package solve most of the bunching problems that grind the subway to a halt:

  1. Signal priority on B/C/E. This fixes the "garbage-in, garbage-out" bunching situation at the portals that leaves schedules hopelessly hosed before they ever mash into each other at Kenmore or Copley. Can't be understated how much chaos evaporates when there's some sane degree of projectable schedule certainty on the branches. The GL would work for the first time in decades if real trolley signal priority were implemented.
  2. 3-car trains at peak and any off-peak surge slots (e.g. Fri./Sat. evenings on B) on all lines except E (Heath St. loop limited to 2-car unless widened out slightly onto the VA Hospital back employee lot). You can relax headways very slightly (minus 1-2 mins max) and still achieve a net increase in capacity by restoring the uncertainty-cushion in the schedule that's been stripped out in recent years. This covers any remaining variance left on the surface branches that signal priority doesn't account for, and allows for very precise subway dispatching. And possibly expansion slots to assign to a new service if that locktight precision frees up more infill slots.
  3. Proof-of-payment and all-doors boarding. Goes without saying that is massive for taming variable platform dwell times that contribute to blown schedules.
  4. Time to whack Brandon Hall and Dean St. on the C, and Fenwood + Back o' th' Hill on E. Time to flip Chestnut Hill Ave. to the opposite side of the intersection so alt. routed C run-thrus to BC are possible. Obviously this whole stop spacing reconfig process is beginning on the B with Comm Ave. Phase II.
  5. Time to triage with MassHighway, BTD, and BRA/BDPA on street-level reconfig with some redevelopment overspill to correct some deteriorated traffic conditions that have harmed transit reliability on specific streets. It'd be huge if Comm Ave. Phase II were accompanied by a reconfig of the BU Bridge intersection clusterfuck, a real B schedule-murderer. Get rid of the Carlton St. chaos and consolidate to a single-point intersection with single thru + protected-left light cycle. Do later Comm Ave. Phase III right by moving the reservation to the center, widening the cramped Harvard Ave. platforms, and sticking a pocket yard between Harvard and Griggs for short-turns and stuffing dead trains. See if the ugly-ass gas station on the corner of Huntington/S. Huntington can possibly be taken to bump-out the intersection around a realish platform...and maybe (caveat: abutter resistance) negotiate with Mission Park Apt.'s on their front parking row to bump out Huntington ultra-wide for a one-block cameo reappearance of the full trolley reservation for a real ADA platform @ MP. More platforms on all the reservation branches also need to be ADA'd as offset on either side of an intersection to maximize the precision of the traffic light signal priority.
---------------

De-congestion effects at overcrowded transfer stations from other builds. . .

  • Red-Blue takes beneficial foot-traffic off the crowded Park St. platforms and stairs by taming the double-transfers going from Blue to Red. Saves on Green dwell times at both Park (where it matters most) and GC.

  • Any service running to Tufts, with its west-side Orange transfer, has moderate amounts of the same effect. Fewer people getting on/off and milling around the Park platforms (especially when it's changing off a GC-turning train to catch a North Station or Lechmere train), more people staying on the train. Think how many people are jumping across the tracks to hit the Winter St. concourse, and how much that harms dwells.

  • Direct South Station/Seaport connector does VERY dramatic savings to both levels of Park. You're now at the point where foot traffic is outright uncongested.
---------------

De-congestion effects from other Green builds. . .

  • E relocation is huge by load-shifting to Back Bay over Copley. Eliminates the awful traffic-killing at-grade junction and frees up MORE capacity for branches out of Kenmore.

  • E relocation via Back Bay puts another branch under grade separation between Park and Boylston, making the inner and outer tracks more or less load-balanced on traffic. In combo with the Copley de-congestion flow improves greatly all points Park & west.

  • If Blue replaces Storrow, you have an immense load reduction on all Kenmore branches since Blue will be the fastest and highest-capacity one-seat out there. Many more branching or Urban Ring opportunities if this happens.

  • Urban Ring north half via the Grand Junction obviously does a lot in its own right from alternate service patterns leveraging Lechmere and the less-congested north end of GC/Brattle loop for a downtown terminus. Makes the traffic skew through the gut of GC/Park far less pronounced.

  • Urban Ring south half (assuming you can fashion it coherently on LRT...excessive surface running does give BRT some advantages) can leverage E-to-Brookline Village and D-to-Kenmore Loop for fast cross-platform transfers to all destinations without overburdening Kenmore-Park sending every single train through. More Kenmore capacity for 'traditional' branching and north-half Ring (Kenmore loop inaccessible from the B portal). Cross-platform definitely has huge advantages the more diverging routes you have available at Kenmore: Blue, UR, diverging branches, alt. E service patterns via the Brookline Vill. connection, alt. South Station/Seaport-via-E and Dudley-via-E patterns. Fully built-out, Kenmore cross-platform can get you literally anywhere.


Just keep in mind, the 1897 subway as originally built was a big circulator blender of routes fanning out all over the city and running in a blur of alt. routes. It didn't change into a fixed-route trunkline until the 1910's. It didn't change into a rigid long-haul line mimicking Red until 1959. It didn't shed the art of mixed short-turning (i.e. the "slash" letter rollsigns) until the MBTA era early-60's to mid-80's. It didn't start really decaying under load until late-90's New Boston boom times sent demand and congestion spiraling through the roof, deferred maintenance started taking its toll, and the Breda lemons started imposing schedule-lengthening speed restrictions.


Today's brokenness was not an everlasting condition. It can not only be rolled back by those sensible and not-very-expensive ^^short-term^^ fixes, but these other *NECESSARY* critical load relief builds like Red-Blue and Downtown-Seaport have the same effects on Park & GC dwells on GL as they do bailing out Red's slow death SS/DTX/Park. Then throw on all the universe of alt. patterns, interconnections, radials, other transfer nodes (Tufts, etc.) spread out from the Central Subway & Park/GC center of the universe and you end up re-casting Green as less a Red-like trunk that has to carry the world on its back and more that circulator it was originally built to be in 1897. In no way do you have to build everything on the fantasy map. I'd expect E-to-BBY to trail the more critical Seaport connector by many, many years simply on project priority, and stuff like Blue-Kenmore has other dependencies like a Storrow Dr. teardown that are beyond prediction in 2016. But all it takes is a couple of the non-optional ones like Seaport-Boylston and Red-Blue to start evolving things back in that direction.

The role starts changing and the bandwidth for other things starts coming available the second you start prying away the extracurricular transfer hordes at Park & GC. And of course we know we don't have a choice but to do that much before New Boston's growth cap starts getting pinched off by those choked transfers. Green's evolution is not that far-fetched. How far you want to ultimately take it is up for debate; we have the whole Green Line Reconfig thread for that. But evolution is non-optional with the stark economic consequences of not evolving. Baseline functioning with the ^^short-term^^ fixes is even less far-fetched, less a reach on resource commitments, and more necessary. That in itself is an evolution.



So think of this in terms of scalability. Eat-your-peas fixes for healthy functioning starts on the scale by restoring lost capacity and reliability. The non-optional Downtown de-clogger builds accelerate it by cleaning up the transfer congestion. And every little thing big and small you pile on top of that adds greater degrees of scale until you pass a point where Green is back to being a real circulator and not so much a square-peg trunk.
 
Updated future MBTA map. Big change here is sorting the GL cluster I had going into a much more readable diagram based on trunk line (Boylston or Tremont subway).

Still a few things to add (Neponset stop, Rte. 16, etc.) but feeling much better about this.


MBTA-New-Map-Green-Expansion-V2 by ecbrads, on Flickr

For map changes I'd do these:

Green

  • Finish GLX to Route 16.

  • Add D-to-E surface connecting trackage (thin or dashed line for alt. service). Back when Arborway was still running the T double-barreled all peak E service with alternating Arborway-Park St. and Heath-Lechmere short-turns. You'll want to do the same to strengthen Huntington Ave. headways when Hyde Sq. is in the picture, and BV has the highest ceiling for that.

  • Add the C-to-B Chestnut Hill Ave. connecting trackage (thin or dashed line for alt. service). Have it flow into the Chestnut Hill Ave. stop (i.e. platforms relocated to other side of intersection).

  • Geographically, BU West is better off still being called BU Central. Actual West Campus as defined by the school is out by Babcock way further from the bridge.

  • Think seriously about an Ink Block intermediate in the Tufts-Transitway connector tunnel (if you're tunneling under Marginal St., then the tennis courts on the Washington-Harrison block serve up the width).

  • Latest Needham GL proposals from Town of Newton (see recent Needham/Newton redev thread in the Dev Forum) stick intermediates at Needham St. halfway between the line split and Upper Falls to serve big new TOD, and another right next to 128 in the office park roughly at Wexford St. Town of Needham has traditionally wanted the 128 stop on the west side of the highway at TV Place, so that's going to be a point of negotiation. Your choice whether you think the Needham St. intermediate is necessary, but the 128 stop is a must-have. Give it a generified "Needham Highlands" name (per the 1945 map) so we don't have to guess which side of the highway it ultimately goes on.

Blue

  • Add Lynnport (a.k.a. River Works) intermediate before Lynn.

  • Add Oak Island intermediate between Wonderland & Point of Pines. Serves a sizeable demand pocket that's not very accessible to Wonderland and could appear even on the Eastern Route/non-PoP routing depending on where they choose to hop across the swamp.

Red

  • Add Neponset (or Port Norfolk or whatever you want to call it) infill on Braintree Branch between JFK and N. Quincy. There's latent advocacy for that.

  • Your choice whether you want to keep Mattapan trolley or convert to heavy rail. If heavy rail, Milton (not Central Ave.) would be the lone intermediate between Ashmont and Mattapan.

Orange

  • Your choice if you want to entertain the recently-proposed Edgeworth infill between Wellington and Malden.

Commuter Rail

  • Old Colony trains can't ever access Newmarket, so move onto Fairmount exclusively.

  • Kendall unfortunately can never be direct-connected to Red given the block's difference between Red main entrance and the Grand Junction. Will have to ditch the transfer and make it offset like Yawkey vs. Kenmore (maybe call it "Cambridge Center" or "MIT" to distinguish?). Also, if you're doing the NSRL there'll never be a need to use the GJ for thru service, as it'll never be capable of acceptable headways. Recommend deleting altogether. Note that the Worcester-North Station study only ID'd demand for 5 peak-only direction unidirectional trips per peak, because all other hours of the day transfers to Orange BBY-NS and Red SS-Kendall did equal-or-better on travel time. If you fix Red/Orange's infamous downtown decay under load the patronage for any Worcester-NS direct more or less evaporates and more demand gets served keeping CR headways uniformly stiff on 1 routing.

  • Forest Hills CR goes away if Needham Line converted to Orange. That's the only CR line that has ever used the stop; no others have bandwidth for it.

  • Hyde Park CR most likely goes away if Fairmount gets real Indigo frequencies, since service already very diffuse and can only decline from there. Cleary Sq. buses can just loop down the street at Fairmount.

  • Blue Hill Ave. needs to be positioned much closer to Mattapan. Same offset as Yawkey vs. Kenmore.

  • Re-space Boston Landing closer to town, add Newton Corner infill where the BosLand square currently is.
 
I like it. But - shouldn't there be a one-seat ride from seaport to BBY, if we're going to do this right?

I subscribe to davem's generally well-thought plan for a GL station at Tufts. With that in mind, I don't think it'd be too big a deal to take the GL one stop from BBY to Tufts and wait for the correct train on the same platform.

I think the Seaport branch need a bit of stop realignment.

The "D Street" stop really need to be further out than D Street -- you can see D Street from the WTC stop.

Also the Drydock area is huge and becoming a serious employment center. Probably need at least two stops in that area to service it well.

You're right re: D Street- that was a sloppy job on my end; I was just trying to tack a less esoteric name on Silver Line Way, which is where I intend for the stop to be. I guess I could do "Haul Rd" instead.

Agree less about 2 stops at Drydock- my vision is taking the BPDA building and at least some of the western abutter at the Northern Ave/Tide Street/Drydock Ave intersection and placing a station and loop there. It seems quite central for the area IMO. Wouldn't be hard to get an area the size of Lechmere's loop/storage there at all.

SL gateway?

The map's already pretty crowded; not sure that adding another layer/mode like BRT would work.

Think seriously about an Ink Block intermediate in the Tufts-Transitway connector tunnel (if you're tunneling under Marginal St., then the tennis courts on the Washington-Harrison block serve up the width).

I think this is the only suggestion of yours I disagree with. I agree Ink Block needs to be served- that was my original intention with the Herald Street stop- but in retrospect I'm not sure the geometry of ducking under the Pike and surfacing so quickly would work. I'm going to adjust to Traveler St. instead and leave Tufts-Transitway stopless unless there's sufficient demand for an infill station.

Thanks for all the suggestions, they've been super helpful.
 
I think this is the only suggestion of yours I disagree with. I agree Ink Block needs to be served- that was my original intention with the Herald Street stop- but in retrospect I'm not sure the geometry of ducking under the Pike and surfacing so quickly would work. I'm going to adjust to Traveler St. instead and leave Tufts-Transitway stopless unless there's sufficient demand for an infill station.

You wouldn't cross the Pike twice because you don't have the option to. West of Shawmut you have the Orange Line tunnel crossing the Pike, and east of Washington you have to keep clear for the North-South Rail Link's NEC tunnel portal (and a too slowly-descending RR tunnel to play any criss-crossing subway games between Washington and Albany).

See here. The Orange Line slip-under @ Marginal was vetted in the mid-70's, so that's well-established. Yellow shade is the universe of wiggle room you have for Green Line tunneling east of that Orange slip-under.

32zqjro.jpg


As you can see you've only got the Shawmut-Washington block available for crossing to the other side of the Pike, and that's obviously where the Dudley branch is going to split off. South Station has to stay north of the Pike on whatever alignment you use to get there.

Blue square is where you've got a slab of cleanroomed urban renewal street corner with nothing on top of it as potential subway station fodder that won't kill you on budget. It's a crow-flies full half-mile from Tufts GL entrance to SS, so an intermediate would be desirable (though wholly negotiable) if site costs wash. This block constitutes the crow-flies halfway point, at a street corner that's a fair 1000 ft. from the nearest Tufts Orange entrance, and about 1200 ft. from where the old Northampton stop was on the El. I call it "Ink Block" even though it's across the street from the actual start of the IB; you can call it what you want. It would probably absorb more total patronage than a streetcar stop right in front of the IB since headways to SS/Seaport are naturally going to be much denser than they are on the Dudley street-running branch.



Your map, your decision. Just thought tunnel footprints vs. Pike was worth the clarification because between Orange and that verboten NSRL provision it's a bit of a traffic jam on what has to go where on that part of the corridor.
 
God.

btw,

Updated future MBTA map

have you guys ever discussed the track that runs from Needham Jct to Cliquot??

Even if service only went to Medfield Junction, you'd have served Sherborn, Dover, Medfield, etc....
 
Last edited:
God.

btw,



have you guys ever discussed the track that runs from Needham Jct to Cliquot??

Even if service only went to Medfield Junction, you'd have served Sherborn, Dover, Medfield, etc....

Can't use that if the Orange Line is gobbling up the ROW to West Roxbury. And the NEC congestion to Forest Hills makes it a moot point because the frequencies would be beyond-abysmal. There was a time and a place for that CR proposal, but it's gone now that Amtrak's traffic modeling for 2030 shows what a hopeless and permanent bind the Needham Line frequencies are in for as long as it stays on the Purple Line.


FWIW...if you build Foxboro commuter rail and double the frequencies on the Franklin Line out to Walpole to 32 round trips per day like the max-build study suggests, a Medfield-Millis shuttle bus down Routes 27 & 109 to Walpole station timed with CR frequencies can arguably give those two towns more total slots into Boston than they would've gotten on a frequency-crippled Purple Line one-seat. So long as those shuttle buses are run frequently enough to gobble up those ample train slots at Walpole. It's pretty much the most equitable transit solution you're going to find for them now that the Needham Line's been pinched off of any growth slots.

The MPO studied such a bus service a few years ago...but used Norfolk via MA 115 as the transfer station. You'd obviously swap that transfer over to Walpole in order to catch all the extra train frequencies out of Foxboro, but the bus was studied out in enough detail that it should be wholly viable and easy to implement once the amped-up train schedules hit Walpole.
 
Can't use that if the Orange Line is gobbling up the ROW to West Roxbury. And the NEC congestion to Forest Hills makes it a moot point because the frequencies would be beyond-abysmal. There was a time and a place for that CR proposal, but it's gone now that Amtrak's traffic modeling for 2030 shows what a hopeless and permanent bind the Needham Line frequencies are in for as long as it stays on the Purple Line.

FWIW...if you build Foxboro commuter rail and double the frequencies on the Franklin Line out to Walpole to 32 round trips per day like the max-build study suggests, a Medfield-Millis shuttle bus down Routes 27 & 109 to Walpole station timed with CR frequencies can arguably give those two towns more total slots into Boston than they would've gotten on a frequency-crippled Purple Line one-seat. So long as those shuttle buses are run frequently enough to gobble up those ample train slots at Walpole. It's pretty much the most equitable transit solution you're going to find for them now that the Needham Line's been pinched off of any growth slots.

The MPO studied such a bus service a few years ago...but used Norfolk via MA 115 as the transfer station. You'd obviously swap that transfer over to Walpole in order to catch all the extra train frequencies out of Foxboro, but the bus was studied out in enough detail that it should be wholly viable and easy to implement once the amped-up train schedules hit Walpole.

Thanks F-Line.
 
Dover also salted over that ROW with a railtrail.

That too...but it's the Amtrak modeling that ends it forever as a viable transit proposal for any era. The ridership figures (which were pretty decent) documented in the last study instantly became obsolete and unachievable when the cap on now-and-forever traffic levels branching off Forest Hills got spelled out in the last 4 years.

Unfortunately a Walpole Jct.-Medfield Jct.-Millis zigzag is too dog-slow--even at perfect track speeds--the way it bends back on itself. A one-seat that way will never beat a two-seat MA 27/109 bus transfer tapping the primo Franklin/Foxboro mainline frequencies @ Walpole. Bus literally is the best overall perma-fix transit solution Medfield, Millis, and Medway commuters. And that's a totally new revelation ever since the Amtrak math revealed the bad news about frequencies to Forest Hills.

Dover commuters have always bogarted Town of Needham's park-and-ride spots at Junction, Center, & Hersey--T and municipal lots--so they need it the least to begin with. They'll just keep on stealing those spots from the townies if the Green Line displaces Purple @ Center & Junction. And they'd probably be just as hostile to a bus route to Needham.
 
MASCO is pitching a long-term grade separation plan for Longwood Ave:

C4uXq2DXAAAEnPI.jpg


Hopefully we get more details beyond this blurry slide. It looks like they are proposing a walking and biking deck over the top of the existing road, a bus tunnel built into existing buildings alongside, and rail in a tunnel beneath? Very high modernist of them.
 
Re: Longwood Ave

Having both a dedicated busway and a rail tunnel might be getting excessive, and perhaps having a transitway serving both modes would be more cost effective.

I've started wondering if Longwood Ave is the logical place to build the D-E connector, given that the Longwood folks seem to keep talking about wanting more transit, whereas the Mission Park folks don't seem to be in any hurry to lose a bit of parking to fix ADA compliance for their E branch stop.

I'm also wondering how much need there is for buried utilities under Longwood Ave. Obviously there are likely to be some utilities crossing Longwood Ave where streets cross Longwood Ave, there probably need to be storm drain pipes along Longwood Ave, and if the existing buildings have sewer connections to Longwood Ave, the slopes might make redirecting those pipes to other streets problematic.

But most buildings abutting Longwood Ave seem to also abut other streets; would it be practical to rely on those other streets for fresh water pipes, natural gas pipes, electrical grid connections, and telecommunications, and remove any existing water pipes, natural gas pipes, electrical cables, and telecommunication cables that run along Longwood Ave to simplify a shallow cut and cover tunnel?

Have the Longwood folks identified a specific location where they'd be comfortable having the west portal for their tunnel to connect to the D branch, or is that a magic asterisk that is going to cause their proposal to morph into NIMBY once they start looking at what is physically possible there?

Can we bury the Northeastern, Museum of Fine Arts, and Longwood stops on the E branch and have a portal somewhere between Longwood and Brigham Circle?

Could we have a portal on Ruggles St between Huntington Ave and Parker St and then continue on the surface to Ruggles Station and along Melnea Cass Blvd?

Could we modify the 15 bus to delete the Roxbury Crossing to Ruggles segment, and instead have it follow Tremont St to St Alphonsus St, disappear into a portal on the west side of St Alphonsus St near the north end of the street, continue through the tunnel, then after coming out of the west portal follow Longwood Ave to Coolidge Corner?
 

Back
Top