so crude it breaks my rule on using Silver as a color, I'll pick a new one later.
You could just use Copper for both, since they share the trunk along Boylston Street.
Beware of sunk-cost fallacy. The existence of those flying junctions gives us great options to build new transit going forward, but it should not dictate what that transit looks like.
I want to come back to this, and I guess maybe briefly step back and talk about objectives here. For me, the GLR concept is not exactly about figuring out what transit should look like. Rather, I see two objectives in parallel:
1) Identify a viable design that achieves basic objectives. By "viable", I mean "physically viable" and "financially viable insofar as reduced costs can be targeted through lower-risk builds". I say "lower-risk" because I'm not a professional -- I don't
actually have a way of assessing the viability of these proposals in absolute go/no-go terms. So my goal is to find low-risk options for as many components as possible, and identify the strongest possible cases to justify the higher risk components. "Viability" does not mean "addresses all drawbacks"; it just means achieving basic objectives (including integrated subway service to the Seaport, better transit to Longwood, and increased capacity and reliability systemwide) in a way that minimizes costs as much as possible.
2) Identify options and alternatives for enhancements. With a basic MVP identified, we can then highlight options for higher-spend builds, articulating the pros and cons for each. Critically though, I don't see a way (or reason) to identify
the single best alternative*. A host of factors -- geological, physical, political, financial, social, community, operational -- will dictate what the best alternative will be, and so it's an unanswerable question.
* (unless we choose to operate purely hypothetically with no regard for cost; as I've mentioned elsewhere, I am a huge proponent of this approach as I think it's a vital part of the conversation, but it needs to be clearly articulated when we are in the "no costs mode". [The other side of that coin is to operate in "Robert Moses mode" and I doubt any of us have interest in doing that either.])
Tripod and Criss Cross both achieve minimum viability, from what I can tell. They both have pros and cons. I prefer Criss Cross, but ultimately choosing the
best option of the two is unanswerable. Criss Cross creates an Allston <> Seaport 1SR but loses the Allston <> Boston Common 1SR. Tripod creates a Huntington <> Seaport 1SR, but rules out a resurrected A Branch through the Central Subway. Absent formal study and community engagement, there's no way to meaningfully say which of those options would be best; it's only possible to note the knowable pros and cons. That's what I tried to do in my graphics a couple pages back.
Both Tripod and Criss Cross have options for enhancement. As
@Teban54 has laid out, a connection between Arlington Station and Bay Village to create the "Full Criss Cross" would enable Seaport 1SRs for both Allston and Huntington. The cost is increased operational complexity, and more complex tunneling (including some of the more invasive modifications of the current Central Subway that have been discussed), in turn increasing cost.
Re-reading my reply from earlier this weekend, I think I lost sight of these goals a little bit.
@Teban54 is right: Criss Cross disrupts existing Allston <> Arlington journeys, with modest but insufficient mitigation. That's pretty straightforwardly a con, and I should have just agreed.
There will be no perfect proposal raised through discussion on ArchBoston and we should be okay with that (and skeptical of ourselves when we think we've miraculously generated a seemingly-perfect proposal).
"Full Criss Cross" addresses the needs of a larger scope: not merely "integrated subway service to the Seaport" but "integrated subway service to the Seaport with no disruption to existing 1SRs" or "subway service to Seaport with 1SRs from Kenmore and from Huntington". If that larger scope is a must-have, then Tripod and Criss Cross are not fit for purpose, and that's fine.
Speaking purely personally, I'm less interested in solving that larger scope using the Green Line Reconfiguration approach, so while obviously everyone else should continue to discuss that as much as they want, I probably won't participate in that aspect as much.
And circling back to this:
Beware of sunk-cost fallacy. The existence of those flying junctions gives us great options to build new transit going forward, but it should not dictate what that transit looks like.
What I think transit should look like in this domain is closing the Mass Pike within 128 and turning it entirely over to transit, with a line that picks up the Transitway to go through the Seaport and across to the airport before turning north toward Chelsea and maybe Everett. Then build a new heavy rail subway from Nubian (and/or points south) through the South End (probably under Harrison) to South Station, Congress St, and North Station, before turning northeast to serve Chelsea and Revere. Put Huntington into a subway that runs under Longwood and then out to Riverside and Needham, with a spur built into JP to Hyde Square, connecting to the Central Subway via Pleasant Street. And I would reroute the Red Line to serve the Seaport more directly.
None of that achieves the goals that I see as specific to the Green Line Reconfiguration concept. I'll raise it in Fantasy T Maps, God Mode, or Crazy Transit Pitches, but I see it as out of scope for this particular discussion.