^Slicing the Kenmordian knot, as it were.
Yeah, that's the general idea. By adjusting the trunk of the Green Line to the south, Longwood becomes a radial destination. That opens up a lot more options for connectivity, especially because you can then layer circumferential connections on top of that. Moreover, using radial service solves some of the problems caused at the eastern ends of the B, C, and D branches: St Mary's St is just a little too far to provide a good conncetion at Audubon Square, but if the C turns southeast toward Longwood anyway, you have an easy transfer at Fenway station itself. The story's a little more complicated on Commonwealth, but the idea is similar.
I mean, looking at the OnTheMap job numbers really is startling:
Huge employment center in Longwood, the edge of a huge employment center in Back Bay, with a modest concentration at Boston University. Practically an employment cavity around Kenmore Square by comparison.
The population maps aren't as pretty visually but:
And from the City of Boston:
And Bostonography's map:
The two tracts immediately north and south of Kenmore Square see lower population density; the walkable neighborhood is bounded to the north by the Charles, to the east by Charlesgate, and to the South by the railroad tracks, the Mass Pike, and then Fenway Park.
Compared to all the surrounding neighborhoods, Kenmore Square is neither a major center of population or employment. The Fenway-Kenmore neighborhood to the south -- whose walkable access to Kenmore Square is substantially limited by the aforementioned barriers -- sees higher density, a higher population, and closer proximity to jobs in Longwood.
All other things being equal, why wouldn't we try to anchor our rapid transit network to Longwood?
~~~
There are some downsides. The biggest probably is cutting off Beacon St from its direct connection to Kenmore Square (if you choose to reroute the C to Longwood, which I should note you don't have to). This can be ameliorated with a bus route, potentially continuing on from Kenmore to Copley via Comm Ave, Mass Ave and Huntington (similar to today's 55).
Likewise, traveling via Park Dr etc does add additional traffic lights and other slowdowns. Some of these can be ameliorated with good planning (organization before electronics before concrete), but probably there will always be some speed penalty compared to running in a tunnel.
We would also need to modify plans for an extended Huntington Subway, and would need to maintain a portal somewhere near the current one. Huntington is wide enough that this is likely doable, but it does complicate things.
Finally, it does have to be said that -- even with all this -- Longwood still remains indirectly served: to the south along Huntington, to the northeast along Fenway, and to the northwest along the Highland Branch. The heart of Longwood remains accessible only by foot, bus, or auto. This is germane because (in my opinion) the obvious alternative to LRT via Fenway is BRT via Longwood Ave -- perhaps a transit mall of some sort. This would serve Longwood centrally, but relegates it again to circumferential service...
...unless you take the Bus Network Redesign approach, and build a sub-network radiating out from Longwood Medical Area across the region. I think this is the more realistic approach, and frankly if done right it could certainly be a very strong proposal.
Still: being able to string together Harvard, West Station, BU, LMA, Prudential, Back Bay, South Station, and the Seaport (and Charlie-willing someday the airport) on a single line is very tempting. (And based on my quick math, would actually provide a slightly shorter route between South Station and Harvard, believe it or not -- and certainly a shorter one between Back Bay and Harvard.) So, even if you don't reroute the C via Longwood, you could still get a lot of mileage out of an east-west Harvard-LMA-Seaport and north-south Kendall-LMA-Ruggles pairing. Running via Fenway might be slightly less useful for Longwood specifically, but could enable much larger change across the system.
~~~
For fun, here's a back-of-the-napkin sketch of what service patterns might look like with a reroute & connection via LMA:
- Harvard-Kenmore-Park: 10 tph (6 min)
- Harvard-LMA-Seaport: 12 tph (5 min)
- Oak Square-Kenmore-Park: 6 tph (10 min)
- plus 57 bus Watertown-Kenmore every 10 min, for cumulative service every 5 min, like today's 57/57A split
- Commonwealth-Kenmore-Park: 10 tph (6 min)
- Beacon-LMA-Park-points north: 10 tph (6 min)
- Riverside-LMA-Park-points north: 7.5 tph (8 min)
- Needham-Kenmore-Park: 6 tph (10 min)
- Heath/points south-LMA-Seaport: 10 tph (6 min)
- Nubian-Park-points north: 15 tph (4 min)
- Kendall/points north-BU-LMA-Ruggles/points south: 10 tph (6 min)
You have lots of flexibility here: send Beacon trains to the Seaport instead, run Oak trains via Huntington instead of Kenmore, use the Kenmore Loop to short-turn some trains, etc etc.