(Of course, that also raises the question of whether it would be a problem to send 25-40 tph from Kenmore to the Seaport.)
I'd guess that's much more feasible than turning 25-40 tph at Park St, simply because the Seaport Transitway has a lot more options on the eastern end to terminate trains.
Obviously I'm not a train operator myself, but AFAIK, a lot of the time-killers in terminal operations actually come from the "software" side: ensuring that everyone gets off, adjusting displays and announcements to change directions, etc. Seaport has at least two such terminals to do this: Silver Line Way and Design Center. And SLW makes it very easy to set up separate terminating vs. through-running eastbound platforms.
In any case, I think the Criss Cross vs Tripod dynamic does elucidate underlying comparative strengths: Tripod may be viable, but ultimately it requires Park Street to absorb trains from three trunks: Kenmore, Huntington, and Nubian; Criss Cross requires it to absorb only two. Tripod limits Kenmore branches to whatever can fit in the Park St Inner Loop; Criss Cross provides a dedicated subway that's able to be fully isolated. Those dynamics stay true regardless of the Inner Loop's actual capacity.
I'm confused. Why should the
total tph across all 4 tracks at Park St matter under Tripod, if, under regular operations, the two inner tracks and the two outer tracks can be largely independent of each other?
(Or, in other words: Assuming we can comfortably send 30 tph from Boylston Outer to Government Center, why should it affect those trains if we add another 10-20 tph from Boylston Inner to Park St Inner?)
One possible answer is signaling, but I remain unconvinced. The NYC subway, despite its notoriously old-school operational practices, has no trouble with two trains departing or entering a platform on express and local tracks respectively at the same time. Unless there's a need for a train to switch between the inner and outer tracks, I don't see why other trains at Park St can't do this.
------------------------
From an earlier comment:
I know what you mean here, but I'm always pretty skeptical when this line of reasoning is brought up. The tunnel's proximity to the "Main St" of a neighborhood doesn't matter: it's the station locations that matter. In this case, the only possible intermediate station would be some counterpart to the current Arlington station -- such as at Arlington St itself, or at Bay Village. Realistically, there are two potential station locations: something near Park Plaza, and something near the Pleasant St Portal. Park Plaza is obviously close to stuff, but it's also quite close to Arlington. Bay Village at least fills a gap in coverage (including providing better access to the South End on the other side of the Pike).
For one, I imagine that if there's one crucial intermediate station that any "Essex Criss-Cross" or "Stuart-Kneeland Criss-Cross" will need, it's not Arlington -- but
an interchange with the Orange Line, around either Chinatown or Tufts Medical Center. An Arlington replacement (or the ability to stop at present-day Arlington) pales in comparison.
Let's also not forget that, especially for Criss-Cross, the goal of any intermediate stations is not so much to "add something onto the T map for the first time", but
"as a replacement for Kenmore/B/C riders heading downtown". Such riders treat the intermediate stations as destination nodes, whether they're for Public Garden and Boston Common, shops at the eastern end of Newbury St, jobs at Park Plaza, Asian restaurants in Chinatown
(including for the Asian populations living in Allston), or TMC. Stopping at Bay Village and maybe Chinatown Gate is a huge inconvenience for the first three, and a minor inconvenience for the last two.
Yes, having a Bay Village station
really helps nearby residents, especially those south of the Pike. But
the existence of a Bay Village station is practically guaranteed thanks to the Nubian branch, regardless of where the second east-west LRT trunk will be and which routes it serves. I doubt the benefits of additional service at Bay Village outweigh the inconvenience of riders who now need a transfer for their old commute patterns.
(This discussion can still be had for Tripod and rerouting the D/E to Bay Village, but at least they would still stop at Boylston.)
But the only thing I do want to highlight, as folks consider how to achieve the Full Criss Cross: improbably, downtown Boston has not one but two fully intact flying junctions that sit unused. No matter how you cut it, flying junctions are harder and more expensive to build than simple flat tunnels. Designing around those, ensuring that both get used, seems like a good pay to supercharge any cost-benefit analysis.
(I think BosMaineaic's suggestion does end up using both? But I'm not clear what happens on Boylston between Charles on Tremont?)
Interestingly, Tripod actually makes much better use of
both flying junctions, particularly the Pleasant St incline, than Criss-Cross:
- Tripod: The Pleasant St junction sorts out Huntington trains (taking Bay Village West) and Nubian trains (taking Bay Village South). Then, the Boylston junction separates both from Central Subway trains. Both junctions can operate at full capacity in theory.
- Criss-Cross: The Boylston junction can operate at full capacity, but the Pleasant St junction only sees Nubian trains. Firstly, it remains debatable whether Nubian needs two branches in the first place. Even if we assume it does (which is my preference), that still means Criss-Cross will inherently see much lower utilization of the Pleasant St junction, in terms of tph passing through it.
This is not an argument against Criss-Cross, not even close; but while I do think that utilizing at least one of the two flying junctions is hugely beneficial and should be factored in, it shouldn't be a constraint to aim to utilize both. Especially when a part of the analysis for Pleasant St comes from Nubian, which has been largely detached from discussions of Full Criss-Cross above.