In the 1910s and early 20s, the Boston Elevated Railway Company (BERy, predecessor to the MTA and MBTA) expanded and modified their streetcar subway, making critical additions that transformed it into something recognizable as an early version of the Green Line.
I have written about these changes in the past, but want to briefly summarize the two models that emerged from BERy’s modifications. In both cases, BERy was trying to address the problem of long trolley routes that stretched from the suburbs all the way into downtown, running slowly at street level, usually in mixed traffic, the buses of their day. The original Tremont Street Subway was built with the relatively narrow goal of getting trolleys off of downtown’s congested streets. BERy’s expansions broadened the scope of the streetcar subway significantly.
Kenmore Model
To the west ran some of the oldest surface lines in Greater Boston, the predecessors to today’s B and C Lines, and the now defunct A Line. When the Tremont Street Subway first opened, these trolleys trundled all the way down Boylston St at surface level, entering the subway at the Public Garden Incline between Arlington St and Charles St.
In 1914, the Boylston Street Subway opened, adding a new tunnel that extended through Back Bay with stations at Copley and Massachusetts (now Hynes Convention Center) before emerging at the surface just before Kenmore Square. (A one-stop extension underneath Kenmore Square opened about twenty years later, giving us the station we know today.)
The proto-A, B, and C Lines thereafter entered the portal at Kenmore and ran “express” underground into downtown. Other shorter distance routes continued to operate into the now-relocated Public Garden Incline, but those longer distance routes were given a (comparatively) high speed bypass.
This was BERy’s first attempt to address the needs of suburban surface lines. Under the Kenmore Model, surface routes run like buses before entering a subway in which streetcars run in a dedicated ROW at high speed into downtown, often producing rapid transit-like service as multiple routes layer to form very high frequencies.
The two other legacy streetcar subway networks in the US – San Francisco’s MUNI Metro and Philadelphia’s SEPTA – also utilize the Kenmore Model. The need to travel underground is arguably what spared these systems from “bustitution”, since buses couldn’t adequately run in the subways.
(San Francisco’s Kenmore Model is actually somewhat coincidental: its Market Street Subway, which mimics the Boylston Street Subway, wasn’t built until the late 1960s; instead, the need for streetcars in order to utilize the Twin Peaks Tunnel, to the west, was likely the protective factor in that system.)
When BERy extended their dedicated streetcar ROW out of the subway at Haymarket north to an elevated along Causeway Street and across the Charles River, they initially employed the Kenmore Model at Lechmere as well. Streetcars from Harvard Square, Union Square, Davis Square, and Clarendon Hill ran directly from street-level on to the viaduct and eventually into the subway.
In 1922, BERy constructed a transfer terminal at Lechmere Square. Surface cars from the northwest terminated at what became the bus terminal, while cars coming from the subway looped within the dedicated ROW of the station. This marked a key transformation in BERy’s treatment of its streetcar subway, now treating it as a service that could potentially act as rapid transit.
The Lechmere Model mirrored BERy’s approach at its other rapid transit terminals. At Sullivan, Harvard, Dudley, and Maverick, surface routes that had once run all the way into downtown were truncated, with riders transferring to high-speed rapid transit service. This model remains in use across the system today.
BERy intended to eventually deploy a Lechmere Model approach in the Kenmore area as well. The C would have been truncated to the Kenmore Loop, while the Central Subway itself would’ve been converted similarly to the Blue Line, and extended to a transfer station in Allston to meet truncated versions of the A and B. Obviously, that never happened.
Broader Implications
The Lechmere and Kenmore Models speak to the various factors that govern a transit service’s character:
The dedicated ROW of a subway or elevated, versus (semi-)mixed traffic-running at surface level
The close stop spacing of a slower surface line, versus the fast speed of a subway line with fewer stops
The rider experience of a one-seat ride, versus transferring at a hub
Both models present benefits and drawbacks. The B and C are among the highest ridership surface routes, in favor of the Kenmore Model. After the opening of Lechmere Terminal, BERy was able to run higher-capacity cars in the subway. On the other hand, reliability in the Central Subway is impacted by the amalgamation of multiple surface routes; and transfers exact a penalty on both ridership and rider experience.
Differentiating between the Kenmore and Lechmere Models allows for a more precise analysis of existing services and potential future expansions.
Last year, I attempted to redesign the MBTA’s rapid transit + key bus routes map. My first iteration was just downright ugly (and yet somehow I still decided to post it), while my second iteration was a bit better, though still unsatisfying.
This year, I have returned to this concept, with the same goals as before, to design a diagram that includes:
Key (frequent) bus routes, designed into the map from the start
All stops on the Green Line branches
Walking transfers, such as State – Downtown Crossing and Brookline Village – Riverway
All stops on the Fairmount Line (future-proofed for its eventual conversion to near-rapid transit standards)
All information included on the present map
And achieve all of the above while fitting into a square and attempting to comply with relevant ADA visual design requirements by using the same canvas and font sizes as the official diagram. I also set a goal of having all labels appear on a solid background, not intersecting or overlapping any lines or other visual elements, and having all labels be horizontal for readability.
While I hestitate to trust my own judgement (like I said, it did somehow seem like a good idea last year to post my previous redesign), I do think that this iteration is more successful.
screenshots below are from the initial version of the diagram and have some minor differences
Design details
Many elements from last year’s version are carried over here, including:
Alignment of bus routes
Stations are aligned so that connecting bus routes form strong visual links
Color-coded bus routes
Bus routes are given colors based on the transfer hub they operate into; in the example below, orange bus routes feeding into Ruggles are contrasted with the green routes that feed into Kenmore/Longwood or Back Bay; the two routes in red both go to Harvard:
The transfer system at Park St & Downtown Crossing
The proposed realignment of SL4/SL5 will relocate its Downtown Crossing stop to Chauncy St, where it will provide a good transfer to the Red Line, but a more distant transfer to Orange; Silver <> Orange riders will be better off transfering at Tufts Medical Center. I’ve attempted to convey that here, along with the Red <> Blue walking transfer at State
Coequal bus routes
The most important change is that this diagram incorporates the key bus routes as coequal “stakeholders” in the design of the map, meaning, for example, that the complexity of the bus network in Longwood was treated as equally important to accommodate as the complexity of the subway network in Downtown. This meant, among other things, that labels for bus stops were sized identically to labels for rapid transit stops.
An organic by-product of the coequal emphasis on bus routes is an expansion of the “grid” formed by Park-DTX-State-GC downtown:
The parallel Red and Blue Lines, horizontal on the Cambridge Seven diagram, are now joined by the parallel lines of:
the 9, 8, 1, 15, the Longwood-Nubian bus corridor, the 23, and 22.
The historically vertical Orange and Green Lines are now joined by:
the Ashmont Branch, the 16, Fairmount Line, portions of the 8 and 1, SL4, the 32, the E Line, the Brookline Ave bus corridor, and the D Line
In particular, the lengthy parallel alignment of the Ashmont, Fairmount, SL4, and Orange Lines created a strong “ladder” effect, where the complex Dorchester bus network can be articulated in terms of which anchor stations a route connects to. For example, my diagram more clearly articulates that Newmarket sits on the same cross-street as Mass Ave and Symphony, and that Uphams Corner sits on the same cross-street as Nubian, Roxbury Crossing, and Brigham Circle.
(The fact that the Uphams Corner <> Brigham Circle street changes names four times — Dudley St, Malcom X Blvd, Tremont St, Francis St — points to the utility of a mildly simplified visualization of Boston’s [apocryphal] cow paths.)
Complexity and tradeoffs
Now, it has to be said that this diagram is complex and still rather visually overwhelming. In general, I argue that’s inevitable with this much information being put into this little space. Fellow ArchBoston contributer TheRatmeister has created a gorgeous map that presents an elegant counterargument, as his map does indeed show all of the above information while still looking amazing.
A key difference between our maps is that his utilizes non-horizontal text and overlapping text. (His text is also slightly smaller than mine, although I believe it still falls well within accessibility guidelines.) So this highlights a tradeoff: the visual complexity of overlapping/non-horizontal text, vs the visual complexity of a highly visible bus network.
Lines on a map
An earlier draft of this map took the emphasis on coequal bus representation even further, by depicting the very highest frequency bus routes (as currently planned in the Bus Network Redesign) with visually distinct medium-thickness lines (nearly as thick as the rapid transit lines) bisected by a thin white line.
This iteration made the Longwood-Nubian corridor too busy. It also ultimately is misleading — the differences in proposed frequencies between my “thick” and “thin” bus routes just aren’t that stark.
However, this version of the diagram presents something worth closer examination: a visualization that vaguely suggests what the subway map might look like if the T’s most important bus routes were full rapid transit:
(no high res link because I didn’t build out a high res version of this, just a screenshot as a proof-of-concept)
As a political position, I submit that we should not tolerate “slow zones” on the bus corridors depicted above — important enough that they have a legitimate claim to being “on the map” — any more than we’ve been willing to tolerate slow zones on the subway.
Boston, the “Hub(s) of the Universe”
Both in my final map and in the proof-of-concept screenshot above, it is Back Bay that sits visually centered. On the one hand, this is partially an artifact of compression that I implemented on the northern half of the map. On the other hand, that compression was only possible because the T’s system is less complex (and less robust) on the north side. The network out of Longwood/Nubian alone could be its own map.
The fact is that Boston no longer has a single downtown, but at least three, if not more: Downtown, Back Bay, Longwood, and arguably the Seaport, and maybe Kendall Sq. To depict the full breadth of the T’s system, a diagram can’t be solely focused on the historical Park-DTX-State-GC core.
In the past, I’ve argued that a poorly understood aspect of the Urban Ring proposal was the extent to which it was actually designed to provide radial transit services to Boston’s “other” downtowns. This diagram illustrates the pluricentric nature of the region’s transit needs.
A Map-Making Note
With respect to avoiding overlapping text, one of the key pieces, I discovered, is finding the “critical triangles” — places where the horizontal label is constrained by the two legs of crossing triangular lines. I found at least three such triangles on this diagram:
Prudential: bound by the E and the 1 (and the Central Subway too)
Chinatown (or Tufts Medical Center, depending on font size and spacing tweaks): bound by Red/Silver and Orange/Silver, and hemmed in by the commuter rail as well
And finally Longwood Medical Area: bound by the E/39 and the Francis St buses
These “critical triangles” in turn govern both stop spacing and line spacing.
For example, the “Prudential critical triangle” needs to also place the Prudential stop marker itself roughly halfway between Copley and Symphony, thereby setting up a general “cadence” for the stop spacing.
In this design, I found that the “LMA critical triangle” ultimately forms the lowest denominator; the spacing of everything else on the entire map unfolds from the stop spacing between LMA and Brigham Circle arising from that critical triangle:
Brigham Circle<>Longwood Medical Area need to be far enough apart to fit labels, but also need to be roughly as far apart as Longwood Medical Area<>Museum of Fine Arts
(I cheated a little bit here: the stop icons are unevenly spaced, but the texts of the labels appear less severely unevenly spaced)
In turn, Brigham Circle <> Museum of Fine Arts need to be roughly as far apart as Roxbury Crossing <> Ruggles — the Orange Line stop spacing becoming twice that of the E
Museum of Fine Arts <> Northeastern <> Symphony needs to match up with Ruggles <> Mass Ave, again emphasizing the Orange Line’s stop spacing being 2x that of the E
…which gets recapitulated again with Symphony <> Prudential <> Copley needing to broadly match Mass Ave <> Back Bay
The “ladder effect” I described above then in turn means that the Fairmount Line’s Uphams Corner <> Newmarket spacing needs to match Roxbury Crossing <> Mass Ave, and Newmarket <> South Station needs to broadly align with Mass Ave <> Downtown Crossing — giving the Fairmount Line 4x that of the E
Now, obviously, there’s a lot more nuance than this. Both the Orange Line’s and Fairmount Line’s stop spacing get mildly compresssed toward the outer sections of the map — I didn’t rigidly copy-and-paste the spacing. But in general, the principle holds that the “atomic” spacing unit for most of the map derives from the E Line. I hesitate to draw too strong of a conclusion here, but I suspect that this principle will hold true for any T map that seeks to show all of the surface stops on the E Line.
In my previous post, I described how large swaths of today’s MBTA run on land that was set aside for transit use anywhere from 140 to 170 years ago. (The converse of this is also notable: how little new space has been set aside in the last five generations.) I described how, outside of the core, the T almost entirely runs on the ROWs of 19th century railroads. And I mentioned that the downtown subways were, in a sense, the “original” North South Rail Link.
The “Boston Metropolitan Railway” imagines, in loose alternate history fashion, a system where those railroads built a turn-of-the-century North South Rail Link and ran their suburban services directly through downtown, filling the niche currently occupied by the T’s subway lines. This produces a system with some similarities to Tokyo’s system or Philadelphia’s SEPTA… with some surprises.
This map essentially superimposes Boston’s early 20th century railroad network on top of a modified version of its streetcar network. There are three key differences (with loose but not developed alternate history “lore” behind each):
The Washington St, Atlantic Ave, and Charlestown Elevateds are built for streetcars, using the “Kenmore Model” still used by today’s B and C Lines, in which surface routes feed into a transfer station before running in a grade-separated ROW into downtown. The Washington St Subway (today’s Orange Line) is never built.
The Cambridge Subway is built as an extension of the East Boston Tunnel (today’s inner Blue Line), as was originally considered in initial planning; an extension to a transfer station with the BRB&L (outer Blue Line) gave that railroad a reliable link across the harbor, allowing it to survive the rise of the automobile; the cross-harbor cross-Charles subway is called the Central Line.
The suburban railroads somehow (magically?) build a “Suburban Rail Link” tunnel connecting North and South Stations, electrify their inner routes, and start running mid-high frequency service directly into downtown, with transfers to the Streetcar Subway, Streetcar El, and Central Line.
Don’t look too hard at the alternate history lore behind the scenes here — it’s not meant to be precise, and instead serves as source material for reimagination.
I’ll probably write more about this map in a future post, but previous readers of my blog will recognize a challenge here: core and branch capacity.
To provide “show-up-and-go” (SUAG) headways of 12 minutes or better to all Suburban stations on the above map, the core tunnel would need a capacity of 40 tph or more in each direction. SEPTA’s Center City connection, and recent analysis of the proposed NSRL, suggest that a realistic capacity for a single dual-track mainline tunnel would be about 22 tph. This imaginary “Suburban Rail Link” would need to be quad-tracked (and I don’t even know if that would’ve been possible at the time). This also illustrates a key point: providing SUAG frequencies to all suburbs requires at least two dual-track subways across downtown.
A single tunnel Suburban Rail Link
Let’s imagine what the system looks like if the Suburban Rail Link is a single tunnel with a constrained capacity of about 22 tph:
Now we get a map that looks much more like the subway maps we are familiar with, where there is a division between higher frequencies in the inner section, and lower frequencies further out. In our real MBTA, this division is largely between the subway lines and the commuter rail, whereas for the BMR it is the division between higher frequency mainline trunks (“Metropolitan” services) and lower frequency branches (“Suburban” services).
While not exactly the same, the BMR has transition points in several of the same places as today’s MBTA:
Somerville Junction (today’s Magoun Square)
Cambridge station (Porter Square)
Forest Hills
Likewise, Harrison (playing the role of JFK/UMass) and Brookline Junction (Kenmore) serve as branch points for the T’s unusually long lines to Braintree and Riverside.
One key difference is the character of the SUAG frequencies: in a well-functioning version of today’s MBTA, the SUAG headways on its subway lines are usually 5-6 minutes, whereas the BMR’s Metropolitan headways would be roughly 12 minutes. The Suburban branch lines to Braintree, Riverside, and Malden would be relegated to roughly half-hour headways. On the other hand, stations like Newtonville, Hyde Park, and Chelsea would see much higher frequencies than they do today.
A pair of Suburban Rail Links
Finally, let’s imagine a third version of this map, in which two separate dual-track subways (instead of a single quad-track tunnel) are built across downtown, providing sufficient capacity for SUAG frequencies on most Suburban branches:
Now we start to see a convergence between the BMR’s system and the MBTA’s, made more obvious by my use of orange for the “Washington Tunnel Suburban” network. With the increased capacity, the BMR can match the MBTA’s 5-6 minute headways to
Sullivan
Magoun Square
Porter
Kenmore
Forest Hills
Mattapan
Braintree
And provide 12-minute headways to the entire MBTA rapid transit system, as well as to the target corridors for higher-frequency Regional Rail, including:
Lynn
Reading
Winchester
Lexington
Waltham
Watertown
Auburndale
Needham
(The Fairmount Line is harder to analyze in this context, since it lost most of its passenger stations much earlier on, and has current stations in greenfield locations. However, it could easily be added to the purple “Franklin Suburban” network, with 6 min headways to Fairmount, and 12-min to Braintree and Mattapan.)
(The Fairmount Line was also going to be harder to map as a full line, so I admit I took the easy way out to avoid mapping it.)
Are the BMR systems “fit for purpose”? Are they better than today’s MBTA network? There are definitely pros and cons to each, but I will save those for a later post (along with some comments about the BMR’s Central Line and “Revere-Lynn High Speed Line”).
Tunnels and takeaways
These maps illustrate that serving Boston’s suburbs with SUAG frequencies physically requires the capacity of at least two downtown tunnels. The MBTA’s Orange Line addresses the need for one of these. The other “tunnel equivalent” is split between the Green Line and Red Line: the northern Red Line fulfills the Central Line’s obligation to link Cambridge and downtown, and then attempts to capture some of the niche occupied by the BMR’s Watertown, Waltham, and Lexington/Bedford branches; the southern Red Line captures the BMR’s Braintree and Mattapan branches; and the Green Line handles the BMR’s Winchester/Woburn, Lexington/Bedford, and Riverside branches.
But note that that second “tunnel equivalent” is also pulling double duty, shouldering some of the burden of the BMR’s (absurd and surely barely functional) Subway-Streetcar network, plus half of the Central Line. And note that today’s Green Line runs services in all four niches described above: Surface (B, C, E), Subway (e.g. to Kenmore), Metropolitan (e.g. to Medford), and Suburban (to Riverside).
Those niches demonstrate the final point I want to make today: the BMR thought exercise elucidates characteristics about different components of the MBTA network, in particular by dividing services up based on their distance from downtown and number of interlined branches. By better understanding those characteristics, we can design a better MBTA for the future.
Let’s look at a map of Boston’s railroads (courtesy of Alexander Rapp, links at end of post).
Let’s add highlighting to show the railroad ROWs that are now used by, or shared with, rapid transit.
Let’s also add dashed marks to indicate common proposals. Aside from the Red-Blue Connector, most of the SLX alignment, and the North-South Rail Link, all common proposals travel along historical ROWs. (The Union Freight RR doesn’t count.)
And now let’s also add (imprecisely drawn) solid lines to indicate the new subways that were built across downtown, which now connect historical ROWs on opposite sides of the city. (This reveals that the subway was in fact “the original North South Rail Link”.)
Now, here’s the kicker: the original underlying map showing Boston’s railroads… shows how they looked in 1890.
Which brings us to our first point: the large majority of the T’s (rapid transit) route miles run on the same paths that were carved out before 1890 (many before 1870, and quite a few as early as 1855).
What’s more: many common proposals to expand the T simply reactivate ROWs that were first carved out in the 19th century (in some cases, as much as 170 years ago).
The core of Greater Boston was the exception to this. Like London’s railroads forbidden from entering the City of London, the late 19th century saw railroad terminals circling downtown, with clusters at the sites of today’s North and South Stations, and one terminal near today’s Back Bay. As a result, when rapid transit was first built around the turn of the century, new routes across downtown had to be built from scratch.
But there are three other corridors, outside of downtown, which also needed to be built for the burgeoning network. These three corridors – and why they were needed – still hold lessons for us today. And it comes down to water, wetlands, and peninsulas.
Wetlands and Peninsulas
While today’s Orange Line runs along the historical Boston & Providence ROW along the Southwest Corridor, its original route ran down Washington St to what is now Nubian Square, and then further south to Forest Hills. The lack of a historical ROW continues to vex transit designs to Nubian to this day.
So, if so much of today’s network did already exist in 1890, why wasn’t there a railroad ROW to Nubian? A map from 1852 sheds some light:
(courtesy of mapjunction.com, this is the 1852 Boston McIntyre map from their collection)
For much of the 19th century, Boston northwest of Tremont St in what is now the South End… was wetland. (Technically a mudflat.) When the Boston & Providence went to survey the route between their eponymous cities, they opted to build a nearly-straight route on a trestle over the mudflat – entirely bypassing the long-settled Boston Neck, which centered on Washington St from downtown to Nubian Square.
For an intercity railroad, this made a lot of sense. They weren’t in the business of providing local service, and plowing through a long-standing neighborhood in the city would have been costly and complicated.
What is now the Fairmount Line had a similar story. Built by the Norfolk County Railroad as an alternative to the B&P’s route through Back Bay, they opted for a route that reached downtown Boston by way of the South Bay… which, at the time, like Back Bay, was an actual “bay” but also was basically wetlands. Again, the new ROW bypassed the Boston Neck altogether.
And Boston Neck hardly lacked access to downtown. Horsecars and streetcars ran down Washington and Tremont, and Boston Neck held the only route into downtown that did not require a water crossing by bridge or ferry.
By the turn of the century, Boston’s built-up environment had expanded significantly. No longer a bucolic suburb, Dorchester was now indisputedly part of the city. Streetcars trundled on a long slow journey into the center of the city, where they joined streetcars coming in from all across the region. Congestion was extreme and the city needed a way to get streetcars off its downtown streets.
So, a subway was built to send local streetcars from nearby neighborhoods underground, and an elevated was constructed to reimagine the commutes from more distant neighborhoods and suburbs: instead of a single long streetcar ride, commuters would make a short streetcar trip to a transfer station, and then take an express rapid transit train into downtown.
The El running south of downtown traveled directly down Washington St, the heart of the historic settlements on Boston Neck. Unlike the steam railroads’ avoidance of the neighborhood, the elevated railroad was designed to be woven into the expanding cityscape.
The rest is an ironic history. Arguably because it was among the oldest part of the city, Boston Neck never received the kind of railroad ROW which, by the end of the 20th century, was essentially the only place rail transit was allowed to run.
The wetlands surrounding Boston Neck were easier to go through than the neighborhood itself, which doomed the neighborhood to miss out on the “transit land grab” of the 19th century, which continues to govern the location of rapid transit to this day.
Water – Rivers
Rivers divide and unite cities. They split cities into left banks and right banks, and they simultaneously attract settlement to their shores as urban centers of gravity. The city of Boston-Cambridge is no different.
In their earliest days, the cores of Cambridge and Boston/Charlestown sat about 3 miles apart as the crow flies, with Boston/Charlestown sitting at the mouth of the Charles as it empties into Boston Harbor, and Cambridge (its earliest village located in Harvard Square) located about 4 miles upriver. By road, it was a circuitous journey of 8 miles via Boston Neck, Roxbury, and Brookline (along a route likely similar to today’s Silver Line and 66 buses) to cross between them.
(Map courtesy of mapjunction.com and the Library of Congress; this is from the 1775 Boston and Environs map.)
A bit more than 150 years after their founding, the effective distance between Boston and Cambridge was cut in half by the construction of the West Boston Bridge (where the Longfellow Bridge is today) in 1792.
(Map reproduction courtesy of the Norman B. Leventhal Map & Education Center at the Boston Public Library; this is a 1795 map with a lengthy titled which begins To the select-men of the town of Boston; the West Boston Bridge is visible in the top left.)
In the ensuing hundred years, Cambridge’s center of gravity drifted closer and closer to Boston, as main thoroughfares stretched from the West Boston Bridge straightaway across to Harvard Square.
Broadway (originally a turnpike), Harvard St, and today’s Main St and Mass Ave ran in parallel between the two poles of Old Cambridge and Boston, forming the backbone of the city that would eventually develop along their roughly east-west axes. Cambridge St connected East Cambridge to the rest of the town, and gradual land reclamation filled in Cambridgeport and expanded East Cambridge, bringing the edge of Cambridge’s shores literally closer to Boston.
The Charles River, in its meandering, deposited Old Boston and Old Cambridge a mere three miles apart. The settlements were far enough apart to develop separately, but close enough that they were inevitably drawn toward each other. Boston was anchored by the Harbor and could not move, but Cambridge had plenty of open space to expand into. The opening of the West Boston Bridge created a focal point for Cambridge’s expansion.
(Map reproduction courtesy of the Norman B. Leventhal Map & Education Center at the Boston Public Library; this is James Hayward’s 1838 A map of Cambridge, Mass, showing Cambridge’s east-west growth.)
The combination of the new river crossing and the original location of the settlement at Harvard Square effectively ensured Cambridge’s development stretching west from downtown Boston.
Notably absent, once again, were the railroads. A mid-century short-lived branchline to Harvard Square lasted a mere six years. Cambridge’s expansion was instead fueled by its horsecar and streetcar connections to Boston via the bridges. (Indeed, the first horsecars in the region ran across the bridge, from Bowdoin Sq to Harvard Sq.)
Municipal boundaries notwithstanding, Cambridge became indisputably part of the Boston-Cambridge city, just as Dorchester had. And just like Dorchester, its streetcars were choking Downtown. Dorchester got an elevated railway, and while an elevated was also considered for Cambridge, eventually a subway was chosen instead – a fateful stroke of luck that continues to impact transit access inequity to this day.
Just as the geography of the Boston Neck did, the opening of the West Boston Bridge meant that, by the time railroads started being built, the corridor between downtown Boston and Harvard Square was already well-settled. The railroads had incentive to avoid the area, not serve it.
The dual examples of Cambridge and Boston Neck demonstrate that the construction of railroad ROWs has frozen in time the idiosyncratic mid-19th century divisions between “old” and “new” settlements.
A note on South Boston and the South Bay
I exclude the southern half of the Red Line from my set of corridors that needed to be created to tie the emerging rapid transit network together, beyond merely stringing together railroad ROWs.
While it is true that the subway between Andrew and South Station was not itself ever a railroad ROW, it runs parallel to the historical Old Colony ROW (which ran in part along what is now Old Colony Ave), and to the historical ROW of the Midland Route (which ran along what is now Track 61 before curving west to a terminal near South Station, producing a route of similar shape, though different location, to today’s Red Line). The decision to run the subway under Dorchester Avenue was not forced by a lack of other options.
(Map reproduction courtesy of the Norman B. Leventhal Map & Education Center at the Boston Public Library; this is an excerpt from JG Chase’s 1865 railroad map showing how the Old Colony and Norfolk County railroads presaged the path of today’s Red Line.)
The South Bay was, and remains, an odd no-man’s-land separating South Boston from the rest of the city. 150 years ago, water separated the two, and today they are divided by railroad yards and a highway. As such, like Back Bay, it is unsurprising that the Old Colony and Norfolk County Railroads used it as their route in and out of the city.
I argue that the Dorchester Ave subway is essentially a modest relocation and consolidation of these two historical ROWs, and therefore does not represent a “new” taking of land for transit use in the way that the Cambridge Tunnel and the Washington St El did.
(To put it another way, in some alternate history, BERy used either/both of the ROWs in lieu of the Dorchester Ave subway, producing a Red Line very similar to our real one.)
South Boston provides a third example to support the pattern demonstrated by Cambridge and Boston Neck: areas already-settled by the mid-19th century were bypassed by the new railroad ROWs that now serve as our primary space for transit. The Old Colony RR built their ROW along the edge of Southie, just as they built their Dorchester ROW along the edge of the neighborhood hugging the shoreline.
Water – Harbors
The last piece of today’s MBTA rapid transit system that was not built on land set aside in the 19th century (see below) is the East Boston Tunnel, crossing the waters of Boston Harbor.
(In this piece, I don’t discuss the Green Line’s development, as I’ve covered that elsewhere — see links above. I will note, however, that the B and C’s reservations on Beacon and Commonwealth both also date from the 19th century. The vast majority of our dedicated transit land comes from this era.)
There’s an argument to make that the East Boston Tunnel was, in fact, set aside by private railroads in the 19th century. The Boston, Revere Beach and Lynn Railroad ran from the wharves of East Boston to Lynn along what is today the Blue Line. The railroad was enormously successful, running high frequency electric trains with (I believe) near-24 hour service at some points. The “last mile” of the journey was completed by ferry across the Harbor to Rowes Wharf (likely the reason for BERy’s construction of an el station there).
Given the close connection between the rail service and the ferry service, there’s an argument to make that the cross-Harbor corridor was, in fact, “claimed” by a private railroad in the 19th century, just as I argue most of the T’s current network was.
The popularity of the BRB&L, and the 1924 conversion of BERy’s East Boston Tunnel to heavy rail, speaks to the importance of a Boston Harbor Crossing. East Boston itself, originally an island, remained isolated from the mainland by Chelsea Creek. And Revere, though served by the B&M’s Eastern Route (today’s Newburyport/Rockport Line), was much more directly served by the near-direct 4.5 mile corridor via East Boston, compared to the 7 miles via Chelsea.
Crossing Boston Harbor has a similar effect to crossing the Charles River – providing an alternative to the roundabout route (whether via Brookline or Chelsea or via an unreliable ferry) creates a strong focal point at the crossing, drawing the previously remote far shore closer (both metaphorically and sometimes literally).
(Off-topic but I always want to emphasize this: the BRB&L ran rapid-transit-like service to Lynn until 1940; only eight years later, the MTA began construction of a true rapid transit line along that ROW, intended to once again reach Lynn. The first phase opened in 1952, and the second phase, to Wonderland, opened in 1954, truncated short of Lynn for budgetary and political reasons. There was only an eight year gap in service before public plans were made to restore service to Revere and Lynn, and Revere’s service was restored a mere four years after that. We shouldn’t talk about extending the Blue Line to Lynn – we should talk about restoring the Blue Line to Lynn.)
Like the rapid transit lines across Boston Neck and Cambridge, a rapid transit line across Boston Harbor was needed precisely because it had been too expensive and unappealing for a private intercity railroad company to build the ROW.
And that’s where the rubber hits the road on this topic, even today.
Implications
Most of the MBTA is built along corridors where for-profit railroads found it advantageous to build in the mid-19th century, usually through areas that were lightly settled, avoiding the historical cores that had driven the growth of the region until that point.
Setting aside the Green Line, there are four exceptions to this pattern:
Downtown: where the Main Line’s Washington St Subway provided the “original North-South Rail Link”
Boston Neck: where the El ran above one of Boston’s earliest pieces of land, to serve the large streetcar suburbs in Dorchester beyond, in the 1.6 mile gap between the Boston & Providence RR and the Norfolk County RR’s Midland Route – the largest gap between railroad lines in Boston’s immediate suburbs, except for the gap in Cambridge
Cambridge: where the subway ran along an east-west axis that had been rapidly settled starting at the dawn of the century, filling a 2 mile gap between the B&A’s railroad in Allston and the Fitchburg Railroad’s line in Somerville
Boston Harbor: where a tunnel literally was dug under the ocean to clear a 3,000 foot gap, replacing the choice between an unreliable ferry and a detour of 4 miles (or more)
Among other things, this highlights – yet again – how damaging the loss of a radial line to Nubian is. Imagine if the Red Line had been relocated out of its tunnel to a route along the B&A ROW with a Ruggles-like transfer station near Braves Field, or along the Fitchburg ROW, with a transfer station at Union Square.
I believe this demonstrates that a transit approach that limits itself to existing transit ROWs threatens to overlook corridors that could be as vital in the 21st century as the above corridors were in the 20th.
In December of last year, I submitted two maps to the Boston Public Library’s Norman B. Leventhal Map & Education Center’s Transportation Dreams contest. The first is entitled “Project Electric Sheep,” and the second is “Project Gold Line.”
I’m a firm believer in dual creative processes — “campaign in poetry, govern in prose,” “write drunk, edit sober” (in the metaphorical sense), creation and refinement. These two maps present a similar duality: one is wider-ranging in its creativity; the other is a refinement into a focused proposal.
I do want to emphasize that, even on the creative map, all proposals are grounded in examinations of feasibility, cost-effectiveness, and efficiency. These are indeed “transportation dreams”, but they absolutely could be realities.
(I am told these and the other submissions will be on display at the BPL through the end of February!)
“Project Electric Sheep” — a feasible yet fun “crayon map”
This is the statement accompanying my submission:
This map has been perhaps a decade or more in the making. Drawing heavily on discussions I’ve participated in on ArchBoston, I have sought to generate a vision for Boston transit that is both inspiring and feasible.
This design adds over 44 miles of rail to the T’s existing network, only about 9 miles of which would require new tunneling. By focusing on existing infrastructure, extant ROWs, and opportunities for low-cost construction (such as wide streets and areas with well-mapped geologies), we can achieve a radical increase in transit access across the region.
My proposals are built on data from a range of sources, including:
newspaper clippings sourced through Wikipedia (with grateful thanks to the tireless contributors there), and
numerous historical works by Frank Cheney, Anthony Sammarco, Bradley Clarke, O.R. Cummings, George Chiasson, Jr, Jonathan Belcher, Thomas Humphrey and others
I have also drawn on the qualitative experiences of myself and other T riders.
This map would not have been possible without the years of collaborative discussion at ArchBoston. Much of my thought process in developing this map is documented there, and some proposals are also documented on my website (ever a work in progress).
A small number of stations have been renamed on this map, for ease of wayfinding and to celebrate a fuller array of figures from Boston’s rich history.
This diagram includes the “Gold Line,” an articulation of a long-discussed idea on ArchBoston, which is presented in greater detail in my second submission (below) and here on my website.
(The submitted map had the Bronze Line J service terminating at West Station rather than Boston Landing. Further details in the appendix. The submitted map also had the labels for Edgeworth, River’s Edge, and Wellington in incorrect order, which I have fixed here.)
This diagram is, in some ways, meant to be “fun” (in a way that crayon maps are supposed to be). There isn’t a specific date tied to this map, and it neither represents a “preferred build” nor a “full build” nor a “must build”. Rather, it’s a vision of one possible future.
Project Gold Line
This is the statement accompanying my submission:
Like my other submission, this map has also been long in the making.
Over the last decade, an ongoing discussion on ArchBoston has examined ways to remake the Green Line into a better version of itself. These discussions have been wide-ranging, at times ruthless in pragmatism, and equally unbound in imagination.
Only in the last couple of years has a consensus emerged on certain key pieces of this “Green Line Reconfiguration”. I myself have struggled to find a way to articulate the possibilities afforded by these (relatively mundane and unflashy) key pieces.
Which brings us to: the Gold Line. The “Gold Line” concept seeks to pithily capture the key projects needed to unlock the system’s full potential:
Reroute the E Line via Back Bay to utilize the unused Tremont St Subway
Extend the E Line’s subway west down Huntington, at least to Brigham Circle
Construct a short subway to South Station and run trains through the Silver Line tunnel, linking the Seaport, Downtown, Back Bay, and Longwood
There are additional components beyond these, including connecting the D and E Lines to create a full-length rapid transit line, as well as extending the Green Line to Nubian Square, but the three investments listed above would, in tandem, be transformative.
Beyond ArchBoston, some of these proposals are also documented on my website (ever a work in progress).
Additional details on the Gold Line concept are available here on my website.
~~~
Teban54Transit also submitted a map to Transportation Dreams detailing the Green Line Reconfiguration concept. He and I corresponded while creating our maps and we decided to intentionally pursue different approaches. My Gold Line map focuses on a set of core components, while Project Electric Sheep shows the Gold Line in a systemwide context with other extensions, such as a Bronze Line through Kendall; his map falls in between, showing a larger and more detailed view of the expansions to the existing Green Line that become possible through the Green Line Reconfiguration. Our maps have some differences, which intentionally demonstrates the flexibility of the improvements we propose.
I can never stop fiddling with things, and my redesign of the MBTA’s system diagram is no different. In organizing some files as I finished up the BPL’s Transportation Dreams map contest, I found a few revisions of my redesign that I hadn’t posted here yet. They are also far from perfect, but they’re definitely improvements on my last.
Version 10.0.1 looked somewhat promising:
This version adjusted the Red Line branches, which were probably the ugliest part of the last diagram. I also extended out the southern part of the Orange Line to take better advantage of the extra space at the bottom of the diagram.
Definitely still had problems though — lots of crowding at the top, for one.
Version 10.0.3 looked to address that spacing issue at the top:
I do feel this is the strongest version yet. The spacing is gentler, as are the curves. I feel that the subway lines on a map should create an image that is distinctive but simple enough to remember, and I think this version comes closest to that.
Having experimented with designs that are exclusively 45° / 90°, exclusively 30°/ 60°/ 90°, and a mix of the two (like this one), I wish I had designed this diagram with fewer angles. The bend at Brookline Village, for example, is distracting; my goal had been to align it with the straightaway of the E Line, but that didn’t really have the visual effect I was hoping for. I think that this concept could work with 45° / 90°, so I might eventually give that a try.
The other big change with this version was getting rid of the coloring of the bus routes. It certainly makes the diagram “quieter”, which ultimately is a good thing. I had originally been very opposed to the idea of uniformly brown bus routes, because I didn’t want it to look like cobwebs criss-crossing all over the map. But I don’t think that turned out to be the outcome, and in fact if anything it seems like the quieter bus routes provide a stronger “grounding” for the map.
I also added a text inset to call out the key bus routes that are gonna have really high frequencies, as I feel that’s a valuable piece of information.
I still would like to try to bring some color back into the bus routes. But for now, that version 10.0.3 seems like a satisfying enough place to leave things.
Everything old is new again. The T is, once again, shuttering significant parts of its network this summer, in order to accommodate maintenance and construction. The Red Line is seeing a string of late evening closures, while the Green Line is seeing much longer shutdowns — including over 40 days of closure on the Union Square branch.
Naturally, I have made some maps.
(I didn’t want to sink too much time into this project, so the maps below are not free from imperfection.)
During this period, the Union Sq shutdown will overlap with a bustitution of the B Line.
The T will apparently not be providing a shuttle for the Union Sq branch, instead directing riders to local bus routes with transfers at Lechmere and East Somerville. I’ve tried to illustrate those here. Alas, it is a bit cramped.
Phase 2: July 29 – August 9
Following the resumption of service on the B Line, a complete shutdown of service between North Station and Government Center will be instituted to accommodate demolition work on the Government Center Garage. It appears that no shuttle will be provided, and the T’s advice is simply to walk from one station to the other.
Phase 3: August 10 – August 28
During these two-and-a-half weeks, the core segment will be restored and the only ongoing long-term disruption will be the unshuttled closure of the Union Sq branch.
As often happens when one returns to something, on review several months later, I strongly dislike this one, and I am mildly dismayed to have been satisfied enough with it to post. Alas. Please please, I beg you to ignore the version below, and instead see the latest iteration of this concept.
To be clear, this is a proof of concept; there are a number of small details that need correcting, and while I think the overall concept works, there are some clear areas for improvement in a subsequent revision. But, I think it does prove out the concept.
Background
The current diagram draws clear lineage to the Cambridge Seven Associates’ original diagram (which captured my imagination as a child with its simplicity and elegance, particularly when it looked more like this). Today’s diagram is much more complicated than the original, due to the need to add additional information, including
Accessibility markers
Explicit markers for all stops on the Riverside Line
Explicit labels for all stops on the B, C, E, and Mattapan Lines
The Silver Line
Commuter rail stops (particularly along the Fairmount Line)
Key bus routes
Plus the editorial decision to include the geographic markers of the shoreline.
That last point reveals a fundamental difference between the original and current diagrams: the original made zero effort to appear geographically accurate, while the current makes some effort to hint at accurate geography… in some places.
The right half of the map – the South Shore, South Boston, the Shawmut Peninsula (a.k.a. Downtown), Charlestown, East Boston, and the communities along the Mystic River – is vaguely accurate, albeit somewhat compressed.
The left half, by contrast, is much more diagrammatic: straightening and simultaneously stretching & compressing the four branches of the Green Line, straightening and simplifying the Red Line and Key Bus Routes, while maintaining some suggestion of a geographically accurate Charles River.
Kenneth Dumas, the designer of the current diagram (and its previous iterations going back to 2000 when the shift was made away from a purely non-geographic diagram), has spoken about the process by which we arrived at today’s diagram; it’s a fascinating watch that I highly recommend if you enjoy transit maps. Suffice it to say, the current diagram represents an effort to harmonize the desires of a wide range of stakeholders.
My goals
I have long wanted to design a diagram for the T that includes the following:
Key bus routes, shown as cleanly as possible and designed into the map from the start
All stops on the Green Line branches
(I actually have not particularly wanted to list out all of the surface stops on the B/C/E Lines, but my understanding is that there is user research showing clear preference for their inclusion)
Walking transfers, including
State – Downtown Crossing,
Copley – Back Bay,
Symphony – Mass Ave,
Brookline Village – Riverway, and
Reservoir – Cleveland Circle
All stops on the Fairmount Line (future-proofed for its eventual conversion to near-rapid transit standards)
The design concept: geographically accurate inner zone & diagrammatic outer zone
Achieving my goals, while maintaining the information on the current diagram, posed several challenges. But as I thought about it further, I realized that several of the thornier issues could all be solved by a highly-geographically accurate diagram, including:
Walking transfers,
the Silver Line, and
to a lesser extent, baking the key bus routes harmoniously into the design of the map
The physical paths of the Green and Orange Lines themselves provided a design to show the walking transfers; this was a key revelation for me: use the physical paths as the starting point for the design, rather than abstract ideas such as “I want the Orange Line to be as straight as possible and form a perfect right angle with a Red Line that is also as straight as possible” (see for example Michael Kvrivishvili’s original design).
At the other end of the spectrum, I got to thinking about Harry’s Beck’s use of a “To” box, listing off-map stops on a line. Cameron Booth offers a modern illustration of this in his Tube map redesign. This is probably the most extreme version of a non-geographic diagram: just a straightforward list of stops.
But, I wondered: was the use of the “To” box really that different from the current diagram’s treatment of the B/C/D/E Lines (and to a lesser extent the Blue Line and Braintree Line)?
There’s very little geographic information being conveyed on those outer lines; there are few or no transfers being shown; there are few or no eye-catching bends that might provide implicit visual cues. Especially on the Green Line branches, the current diagram really just uses a list of stations, along a colored line with white dots.
So, I wondered, what would happen if we had a diagram with a geographically accurate inner section and a maximally diagrammatic outer section?
Hence, the map above.
Notes on the map
A few things to draw attention to:
Sizing
This design uses the original map’s labels and other elements at their original size relative to the page. If printed on a piece of paper the same size as the current map, all of the labels (along with the widths of the subway and bus lines) should be the same size. I know there are ADA guidelines around things like sizing and visual contrast; by reusing as much of the original map’s design language as possible, I’m hoping to generally satisfy those requirements, even if I’m unfamiliar with them.
Alignment for bus routes
Stations are aligned so that connecting bus routes (in this design, the highest frequency “all-day-15-min” routes from the Bus Network Redesign) are maximally straight. These include:
T101: Kendall/MIT – Lechmere – Community College
T9: Copley – Broadway
T12: Andrew – World Trade Center
T109: Sullivan – East Somerville – Union Sq – Harvard
T1: the various stations along Mass Ave
Non-geographic diagram in outer zone
Outside of the “inner zone”, the geographic fidelity of the diagram drops so severely that there’s no way it can be interpreted as being anything other than what it is: a list of stations. This is reinforced by the disappearance of the bus routes and the coastline, and the addition of the “transfer labels” at each station. An earlier version of the diagram featured an explicit “box” delineating the inner vs outer zone; this became unwieldy, however, especially when dealing with the Green Line branches, so I opted instead for an implicit transition.
Color-coded bus routes
Instead of using the current diagram’s “light brown” for the Key Bus Routes, or the official brand guidelines’ “Brand Bus Yellow”, the bus routes have been color-coded based on the hub they operate into. This is far from a perfect system, and in some cases I had to make arbitrary choices. (For example, the T7 and many of the routes running through Roxbury Crossing are colored based on running through State St and Roxbury Crossing respectively, e.g. major transfer points the route travels through rather than to.) Still, I think it is a useful way to differentiate the routes, and somewhat inadvertently highlights the new connectivity of the redesigned routes (e.g. the T28 being a Green route, or the T110 connecting Wonderland to the Orange Line).
Fairmount Line
With today’s timetables, the Fairmount Line should not appear on the map using equal visual language to the rapid transit lines. However, increasing frequencies to “turn-up-and-go” levels should be a major priority for the T and the City, and I wanted this diagram to be future-proofed to enable that.
Silver Line, simplified
The Bus Network Redesign has given us would-be transit map designers a godsend: the elimination of the SL4/SL5 reverse branching & loops. Now we have a simple dog-leg that slots nicely alongside the Orange and Red Lines. The only hiccup is (as I interpret the Remix map), Chinatown will receive northbound service only. I have opted to subtly mark this using a directional triangular for the stop, instead of a circle, and excluding a Silver-Orange transfer indicator at Chinatown (compare to Tufts Medical Center). On a “real” version of this map, the Chinatown label would probably get an asterisk with a note in the legend to the effect of, Silver Line stops at Chinatown going northbound only.
Park St, Winter, Summer, and Washington
This probably falls under the heading of “too clever by half”, but I’m still pleased with it. In general, this map does not mark transfers particularly explicitly. I experimented using black circles, or black dots within circles, but the black circles created contrast problems and the black dots were too subtle.
Instead, the indication of transfers is derived from the physical positions of the stops. For example, the Blue-Green transfer at Government Center is indicated by the Blue and Green Lines sharing a stop indicator. As it happens, only two transfers are marked in this manner: Park St and Government Center.
The rest are marked using transfer bars to connect visually distinct stops. In some cases, the visual distance is a design artifact: for example, the Green-Orange transfer at North Station or the SL1/2/3-Red transfer at South Station are in reality basically as proximate as, e.g., the Red-Green transfer at Park St.
But one benefit is that two of the more complicated transfers are visualized accurately: State, and Park/Downtown Crossing.
State
The transfer between the Blue Line and the southbound Orange Line (the platform formerly known as “Milk” after the cross-street above) is, I believe, the longest in-station transfer on the system. From the western end of the Blue Line platforms to the northern end of the Milk Street platform (I believe under the intersection with School St) is about 800 feet, as I estimate. By comparison, the Green-Orange transfer via the Winter Street Concourse is about 550 feet.
All things being equal, I don’t see a particular need to visually indicate this lengthy transfer distance. However, I chose to add it because I wanted to implicitly indicate that the T7 transfer (on Congress St) is more proximate to the Blue Line than to the Orange Line. So I wanted to separate out the Blue Line station from the Orange Line.
The offset Red Line platforms historically haven’t mattered too much from a map-making perspective. However, with the redesigned SL4/5 route, there will be a minor distinction worth making:
In a clever bit of route design, SL4 and SL5 are going to be combined into a single route that serves Tufts Medical Center, Downtown Crossing, and South Station in a linear fashion, with bidirectional service at each stop. However, instead of serving Downtown Crossing at Temple Place, the new Silver Line stop will be flipped over to Chauncy St – directly outside the entrance to Downtown Crossing at the far end of the Red Line platform.
So, I wanted to indicate on the map that Downtown Crossing will provide a good Silver-Red transfer but subtly suggest that Silver-Orange transfers are better taken at Tufts Medical Center. By separating out the Red Line station (nee “Washington”) from the Orange Line stations (“Winter” and “Summer”), the diagram is able to show exactly that. Again, in this case the physical layout of the network in the real-world has provided the needed design specification.
Drawbacks
There are two sets of problems with my diagram: some problems are execution-related and presumably could be remedied by the touch of a professional; others are conceptual and endemic to the idea of the map itself. Of the drawbacks listed below, I’m not sure which are execution-related and therefore “salvageable”, but I’ll make some guesses.
Busy margins and excess inner blank space
This one I think is execution-related and could be ameliorated by some mild tweaking. This diagram is very busy at the margins overall. To a certain extent, this is by design: I always knew that the outer regions of the diagram were going to be busy with station lists. However, I think the “inner map” section could be compressed by maybe 20%, and free up much needed space, especially at the bottom of the diagram. (For example, there really doesn’t need to be that much space between stops on the Southwest Corridor; the SL4/5 stops probably are the limiting factor here, but they too definitely could be closer together.)
Likewise, I think the “inner map” could also be further compressed along the “Red Line axis”, particularly in the northeast corner. Harvard and Central could both be moved in closer to the core, which would free up more space. For example, the T47 does a small bend at Central right now: in a future revision, I would move Central in closer to the core so that the T47 could run in a straight line between BU Bridge and Union Sq, which would “tug” the northern branches of the Green Line and Red Line further in toward the center. (Looking at it now, I think this would also actually place Central in a more geographically correct location, for what it’s worth.)
Ironically, even though I’m talking about freeing up more space in the top left quadrant of the diagram, in all likelihood I would instead use that space to simply relocate the rest of the map upward, in order to free up more space in the bottom half. The centerpoint of the diagram is currently roughly at the Hatch Shell on the edge of the Charles. In a future revision, I would probably shift things so that the centerpoint is at Back Bay Station.
The busyness of Longwood and Dorchester
These are the parts of the diagram where the shape of the bus network is most germane. The criss-crossing lattice of the Dorchester network does not lend itself to simple labels like “to Ashmont” placed just south of Nubian (which would mirror what I did at Harvard and Sullivan). As for Longwood, the Bus Network Redesign will radically increase bus service to LMA, which definitely merits inclusion on the map, but is challenged by:
Fitting in labels for four bus routes on one segment (between Roxbury Crossing and Brigham Circle)
Fitting in a parallel-but-nearby route for the T47
Showing appropriate proximity to the E Line
Showing appropriate proximity to the D Line (farther away from the E Line)
Illustrating connectivity to Kenmore and Ruggles
Fitting in labels for the E Line and D Line
Fitting everything within the obtuse triangle defined by Copley, Kenmore, and Brookline Village/Riverway
I think the busyness can be partially alleviated by adjusting the compression of the inner core and re-centering the inner core a bit higher up in the diagram to open up a bit more space.
That being said, I think this is a conceptual shortcoming of the map: Longwood and Dorchester both represent areas where higher geographic fidelity is needed, in part simply because the topologies are complicated enough that the geographic representation already is pretty close to the maximally simplified representation of the network.
Unfortunately, this diagram is less effective at fitting in geographic accuracy the further away from the core you get. That’s why re-centering the diagram on Back Bay (or even something further south) is necessary – we need to provide more space for Longwood to fit comfortably within the inner zone.
Dorchester, on the other hand, will likely still have to remain within the “diagrammatic outer zone”, although I think it would also benefit from a little more “breathing” room. That being said, this may be where my design concept for this diagram really breaks down: I dislike the current diagram’s treatment of the Dorchester bus network because I think it looks confusing and hard to read, but I’m not sure mine does that much better.
The “starfish” design centered on Franklin Park feels pleasantly clever, but I worry is still too noisy. Likewise, I’m not wild about the physical disconnect: the bus line ends with an arrow, followed by a “To Destination” label, followed by a relatively small amount of blank space, followed by the diagrammatic stop label with the transfer label (e.g. the T16 going toward Forest Hills). Why not just extend the bus lines all the way to their destination?
Look how close the T16’s to Forest Hills marker is to the actual FOREST HILLS label, alas
(The reason I didn’t do that is because I’m using the absence of the bus and regional rail lines as a visual cue to the shift from geographic fidelity to diagrammatic lists. Now, it is true that the visual distortion would still remain so extreme that the transition would probably still remain visible. But, that corner of the diagram is already so busy that I’d be hesitant to layer on additional visuals.)
I suppose it could be possible to redesign the diagram such that the geographically accurate “inner zone” extends as far south as Forest Hills and Ashmont. Looking at the diagram now, that actually might be more feasible than it sounds, particularly with some compression and reduced scale, so I may need to play around with that!
Branches on the Green Line
The Green Line branches pose a problem: there are way more stops on the B, C, and D branches than there are on any other leg of the network (though Ashmont + Mattapan come close). What’s more, they are the only legs of the network that fan out to the side of the map, rather than the top or bottom, which makes the “diagrammatic list of stations” less obviously different in appearance. And on top of that, I ultimately wanted to make sure all three branches terminated “lower” on the map than Kenmore – meaning I couldn’t, say, turn the B Line upwards to fit it in as a list of stations.
I’m not thrilled with how the Green Line branches turned out, but I do think the concept can be sound, particularly if I can free up a bit more space to let me put the B Line labels on the outside rather than the inside (where they mix confusingly with C Line labels).
(One note: this design is meant to be future-proofed for an addition of a Needham branch: flip the D Line labels past Newton Highlands over to the left side, and use an upside-down tuning fork approach to add the Needham labels on the right, similar to the Red Line branches.)
Conclusion
Does the design concept of a geographic inner zone and a diagrammatic outer zone “work”?
Ultimately, I think the answer is “yes”: I think the fundamentals of this concept are sound, and it’s a question of execution.
As the “15-minute Bus Network” is rolled out over the next few years, it’ll be more and more important for the T to update its map to integrate those routes properly into the design. I hope that an approach similar to what I’ve illustrated here can be helpful in such a redesign.
The following is purely a fun exercise for a highly hypothetical scenario. I’m posting it more as an illustration of thought process, and not really in advocacy of the proposal itself. (There are many things I would prioritize above an Urban Ring LRT station in the Seaport!)
The scenario
Let’s assume a few things are true for this scenario:
The Piers Transitway (currently serving SL1, SL2, and SL3) is converted to light rail and connected to the larger light rail network via a subway running from Huntington Ave to Back Bay to South Station — we’ll call this the “Magenta Line”
“T-under-D” has been completed, meaning the subway now extends from World Trade Center station under the current grade crossing at D St to a portal near the current Silver Line Way station
Center-running bus lanes on Congress St in downtown and Summer Street in the Seaport have been built, and the T7 upgraded into a full bus rapid transit service, which we’ll call the “Navy Line”
SL1 service has been transferred to the Navy Line, to provide a one-seat ride connecting North Station, the Financial District, South Station, the Seaport, and the Airport
We’ll loosely assume that a lane in each direction of the Ted Williams Tunnel has been dedicated to mass transit use
An LRT iteration of the Urban Ring has been built on the southside of the network, connecting Longwood, Nubian, and the Seaport, approaching the Seaport via the Track 61/South Boston Haul Road ROW
In short, our starting point looks like this:
The satellite image doesn’t tell us the whole story, however. This is a highly three-dimensional space, where Summer St and World Trade Center Ave sit elevated above the rest of the street grid, and where a slew of highway tunnels sit under the surface.
World Trade Center Ave looking east, as seen from Summer StWorld Trade Center Ave from above, looking north, with Haul Road below and to the rightWorld Trade Center Ave at “elevated street level” looking north, from nearly the same vantage point as above, but lower downTrack 61 and Haul Road passing underneath Summer St, from above World Trade Center Ave, looking west; the Boston Convention and Exhibition Center is visible at the far leftOpenStreetMap showing the tunnels below the surface
Where to place an Urban Ring LRT station?
“The gravel pile”
As visible in the photo above looking west along Summer St, there is a triangular plot of land bounded by Track 61, the embankment of Summer St, and (effectively) the elevated WTC Ave. (There’s actually an access road that cuts off the corner of the plot slightly east of WTC Ave.) That plot currently is occupied by a massive pile of gravel. (Last I checked, the plot is owned by MassPort, though I assume they would sell it off to a developer if/when they could.)
This is probably the most obvious place to plop down an LRT platform. It’s accessible from the current ROW with minimal modification and landtaking required; it provides good access to BCEC and easy transfer to the Navy Line services (including services to the airport); the Magenta Line subway station at World Trade Center is about 400′ away, which isn’t ideal but is certainly manageable, especially if one of the sidewalks can be covered for protection from the elements.
There are some downsides. The plot is a little small; if we leave the access road untouched, it’s just about 230′ along the long edge, which would be barely long enough for a double-set of the 114′ Type 10 “supertrains” that are expected on the Green Line in the next several years. So it’s likely the modifications at the east end, west end, or both would be needed to fit a center platform, two side tracks and a crossover. (Depending on how the Track 61 ROW is converted to double track LRT, some space might already be reclaimed from Haul Road at the western end, which might simplify the design somewhat.)
The other downside is that this location serves the Seaport, but only somewhat so. A lot of the Seaport is located on the other side of the “highway canyon” that Track 61 and Haul Road sit within, so Urban Ring passengers would need to go “up-and-over” for the last segment of their journey. The current World Trade Center station is much more centrally located.
The gravel pile is potentially an adequate location for a station, and would likely be the least expensive option. On the other hand, if we are going to go to the expense of building an LRT Urban Ring, there’s an argument that it should be built for maximum efficacy, rather than just minimal cost.
The underground parking lots
As can be seen in the photos, there are a number of parking lots at the grade level of Track 61, including one parking lot that directly abuts the southern wall of the current World Trade Center station; open that wall up, and you have a strong transfer to the Magenta Line.
The problem here is that you need to cut across Haul Road and the Mass Pike ramps in order to access the lot. And while that’s doable, it’s far from ideal. There actually already is a traffic light directly underneath WTC Ave on Haul Road, so in theory the disruption to traffic flow would not be new. On the other hand, you could only run trains so often if they need to disrupt traffic, probably capping headways at 5 minutes. Again, that is doable, but seems to trigger the same question as above — if we’re gonna build this thing, why not do it properly?
World Trade Center Ave
One thing that bothered me when thinking about mini-project was how to provide good transfers to both Summer St BRT and Transitway LRT. The distance between a stop in front of BCEC and the entrance to WTC station is roughly 650′, which is long for a transfer but not unheard of. (If I recall correctly, it’s roughly the distance of the transfer between Southbound Orange and Blue at State. Of course, State has the benefit of being entirely indoors, while BCEC <> WTC would have significant exposure to the elements, even if the sidewalk were covered.)
Having two Urban Ring stations — one for the Transitway and one for Summer St — seemed excessive. So then I got to thinking more about what the objectives are for stations/connections at each location.
Summer St
Boston Convention and Exhibition Center
Transfer to Summer St BRT toward downtown: South Station, Post Office Square, Haymarket, North Station
Transfer to Summer St BRT toward Logan
Transfer to Summer St BRT toward South Boston
Transitway (World Trade Center)
Seaport core, including Congress St and Seaport Boulevard
Transfer to Magenta Line westbound: western Seaport, South Station, Back Bay, Longwood
Transfer to Magenta Line eastbound: eastern Seaport
On paper, that looks like a lot of reasons for each, and maybe even more in favor of Summer St due to its connectivity, but when you look closer, some are less relevant:
Summer St
Boston Convention and Exhibition Center
Transfer to Summer St BRT toward downtown: South Station, Post Office Square, Haymarket, North Station
By definition, the Urban Ring will have multiple connections to downtown, so this is not a vital benefit
Also, Urban Ring riders will all but certainly be coming from locations that already have direct service to downtown — it’ll be a very uncommon journey to transfer in the Seaport
Transfer to Summer St BRT toward Logan
As you’ll see below, this benefit is in fact not going to be unique to Summer St
Transfer to Summer St BRT toward South Boston
I won’t put strikethrough on this one, but I will point out that most of the previous connection points along the Urban Ring corridor (e.g. Broadway, Mass Ave/BU Medical Center, Nubian) will hopefully have — and will be better served anyway — by direct bus service from South Boston
Again, the Seaport itself wouldn’t be a common transfer point
Transitway (World Trade Center)
Seaport core, including Congress St and Seaport Boulevard
Transfer to Magenta Line westbound: western Seaport, South Station, Back Bay, Longwood
As mentioned above, pretty much all of the Urban Ring stops between Nubian and the Seaport will have better ways to connect to South Station, Back Bay, and Longwood than via the Seaport
Transfer to Magenta Line eastbound: eastern Seaport
So, to me, the goal of an Urban Ring LRT station would be twofold: connect to the Seaport, and connect to Logan. A stop anchored by the Transitway station better serves the Seaport and, as you will shortly see, also serves Logan. So, insofar as we need to choose which connection to prioritize, we should focus on a Magenta Line connection at World Trade Center station.
Getting to Logan
In some alternate timeline, the Ted Williams Tunnel was built with a third tunnel to carry rapid transit rail service to Logan. This would’ve been so much better than today’s system, but alas.
In the scenario I’ve outlined here (and, in my opinion, in any vaguely realistic scenario), service to Logan is provided by BRT. Now, to be clear, BRT can be a lot better than what we have today. For one, a lane in each tunnel could be dedicated to transit and perhaps very-high-occupancy vehicles, with semi-permanent lane protection to ensure speedy and unencumbered journeys.
But our BRT services still need to get in to the tunnel, and the solution to that problem also solves the problem of Summer St vs the Transitway.
Today’s SL1 and SL3 services make a semi-unadvertised stop at street level on Congress St just outside of World Trade Center station; they do this immediately after exiting the off-ramp, which has the benefit of getting travelers from Logan to a stop in the Seaport quickly, without needing to double back from Silver Line Way.
This stop is marked on my diagram from the top of the post (though I am supposing that the simple sidewalk stop has been expanded into something more like a proper BRT platform):
As far as I can tell, absent a major rework of the Mass Pike tunnels, Logan-originating buses will exit from that off-ramp for the foreseeable future. Now, it is true that Logan buses could instead turn left and use Congress St bus lanes to head toward downtown. However, that would duplicate the lanes on Summer St which would still be needed for South Boston service (i.e. the T7), and would be more awkward to connect to South Station. And while Logan -> South Station is mildly more direct via Congress, the journey in the opposite direction is significantly worse, requiring a lengthy diversion down Haul Road in order to reach the on-ramp.
Funneling Downtown <> Logan service through Summer St maximizes frequencies on the shared trunk, minimizes redundant infrastructure, and maintains good Logan -> World Trade Center service. It is somewhat more roundabout, but connects to more places. (And if we are really worried about an express South Station <> Logan connection, using dedicated lanes in the Mass Pike tunnel running direct into the South Station Bus Terminal is probably a stronger solution anyway.)
So we’ve identified a way for our Logan -> South Station service to transfer at WTC station, but what about the other direction? Well, that’s where those parking garages can come in handy.
Running directly parallel to the Transitway is a small side street/alley that runs into the lower level of the parking garage, and which, I think exits on to Haul Road just underneath World Trade Center Ave. Visible in the second Streetview photo are two large metal doors: I am pretty sure that those lead directly into the lobby of the World Trade Center station — meaning that with some modifications, you could put a BRT platform near there, and have buses immediately proceed to the on-ramp.
This would then provide a strong transfer point to Logan-bound services at World Trade Center proper — benefitting Magenta Line riders, but also providing a crucial transfer point enabling an Urban Ring station at World Trade Center.
Placing an Urban Ring LRT station at World Trade Center
So, where to put a new LRT station at World Trade Center?
We can’t put it at grade level without disrupting all the highway ramps, or otherwise settling for a station at Summer St instead.
We can’t put it below grade level because of the highway tunnels.
What about above grade along the World Trade Center viaduct?
Building a short rising viaduct on the gravel pile’s plot and claiming some of World Trade Center Ave (more details on that below) to add a above-grade LRT platform, combined with building an at-grade BRT platform for Downtown -> Logan services by reclaiming some space under the parking garage and adding a BRT platform on Congress St for Logan -> Downtown service, enables all three services to be centralized in a single station for easy transfers between all three.
So how do you reach the World Trade Center Ave viaduct?
Some of this will depend on how Haul Road is reconfigured for double-track LRT, particularly in terms of the horizontal alignment (do you steal a lane, or eat into the gravel pile?), but I think there’s enough open space to feel comfortable that something could fit, even if we don’t work out the details right now.
One area we have less flexibility on is the vertical alignment: there’s approximately 310 feet of horizontal running space between the Summer St underpass and the edge of the World Trade Center Ave viaduct, and we have to fit our rising viaduct in there.
The WTC Ave viaduct is approximately 25 feet high; 25 feet rise over 310 feet run yields a grade of 4.61°, which is well within the comfort zone for LRT grades. Even a rise of 33 feet over that distance would still come in at our 6° threshold. Likewise, rising 25 feet at <6° is doable in as little as 240 feet. Therefore, even with the known limits, it should be possible to rise from the Summer St underpass to the World Trade Center Ave viaduct at a reasonable grade.
Fitting a terminal on the World Trade Center Ave viaduct
The main question facing us here is whether to maintain some level of automobile access through WTC Ave. I believe I’ve come across proposals to fully pedestrianize that street, which, honestly, based on my experience, seems pretty reasonable. Mostly it seems like the street is used to deliver goods to the World Trade Center proper.
If I needed to maintain some level of automobile access, I would use a staggered pair of side platforms to maintain LRT capacity and keep a shared bidirectional lane open for vehicles to pass through on a limited as-needed basis, placing signals/traffic lights at each entry to coordinate passes through the right-of-way.
Obviously, this arrangement is complicated and would create some disruption to the system, depending on the road traffic volume. This option would need to be considered carefully to assess the cost vs benefit.
The key thing to note is that there is horizontal space to fit all the necessary elements:
First 230′ platform (enough to accommodate a doubleset of the 114′ Type 10 supertrains)
90′ to fit a crossover to provide passing access
Second 230′ platform
A 100′ radius curve from the rising viaduct on to WTC Ave
Reasonably short walking distance between platform and current headhouse to streamline transfers
Maintain pedestrian access to the elevated greenspace between Congress St and Seaport Blvd
The second option is more conventional and straightforward: pedestrianize the whole viaduct, and claim part of it for a GLX-style center-platform terminal station.
There are lots of potential variations on this design — adjusting the width, length, and placement of the platform, trying out different methods of pedestrian access — but they all more-or-less look like this.
Keen observers will note that none of these designs feature fare gates or paid-access vs unpaid-access areas. Numerous transit systems, both in the US and around the world, have demonstrated that it is possible to run ticketed transit systems that do not require metal barriers to enforce payment. Eliminating fare gates makes it possible to build transit access more directly into the fabric of a neighborhood. Both station designs, but particularly the staggered platforms alternative, see no clear demarcation of the “edge” of the station, but rather allow the space to be woven together into a seamless whole.
So how do you site an Urban Ring LRT station in the Seaport?
To me, it looks like this:
Add a BRT platform at World Trade Center station for Downtown -> Logan services (under the parking garage just south of the station)
Build a viaduct to connect Track 61 LRT to the WTC Ave viaduct
Add an LRT station at-grade on the elevated World Trade Center Ave viaduct
Should you put an Urban Ring LRT station in the Seaport?
One thing this exercise illustrates is that the Seaport is not very wide. This sounds obvious and trivial, but one result is that there isn’t really space nor need for a “crosstown” service. The Piers Transitway and Summer St already form strong “east-west” transit corridors (whose elevation difference reduces their overlapping walksheds slightly). But they’re still close enough that a perpendicular service between/across them wouldn’t make much sense (particularly since both originate at South Station and come very close to connecting again at World Trade Center).
So a Track 61 LRT service basically needs to choose a particular point along the “linear Seaport corridor” to terminate. That increases the pressure on that station to be located optimally to maximize access to jobs as well as to transfers. World Trade Center does reasonably well on that front, but both the eastern Seaport (e.g. Design Center) and western Seaport (e.g. Courthouse) would require transfers for short last-mile journeys. But this need to choose lies at the heart of why siting an Urban Ring LRT station in the Seaport is difficult in the first place.
A Track 61 LRT service will likely reach the Seaport in part by passing near Broadway station. Regardless of origin point beyond there, a service near Broadway likely could instead be aligned to pass through South Station instead — and then continue to Seaport along one of the east-west corridors. (For reasons I won’t get into here, a Piers Transitway LRT corridor would very likely have excess capacity to absorb Urban Ring LRT in addition to the Magenta Line LRT I’ve described here.)
Sending an “Urban Ring” LRT service down one of the east-west corridors would provide better access to the entire Seaport, and reduce/eliminate the need for transfers. Running LRT service via Track 61 may in fact be unnecessary.
This brings us to a key difference between an LRT Urban Ring and a BRT one: BRT can continue to Logan Airport and on to Chelsea much more easily than LRT. Rapid transit on the Track 61 ROW, with a transfer station roughly at World Trade Center, and continuing service to Logan is able to catch a much broader swath of journeys (in italics below), compared to service terminating in the Seaport:
Longwood <> Seaport
Nubian <> Seaport
Red Line transfer point TBD (e.g. Broadway) <> Seaport
Longwood <> Logan
Nubian <> Logan
Red Line transfer <> Logan
Longwood <> Chelsea
Nubian <> Chelsea
Red Line transfer <> Chelsea
Seaport <> Chelsea
Logan <> Chelsea
The concept of the Urban Ring was to provide circumferential service that bypasses downtown, for speedier journeys and reduced crowding in the core. A route that terminates at Seaport curtails possible destination pairs, and becomes less competitive against transferring downtown via the radial services (especially for long circumferential journeys).
Returning to the point about connecting at Broadway vs South Station: South Station is, to be clear, the bigger fish. Nubian <> South Station journeys surely outnumber Nubian <> Broadway journeys. Urban Ring concepts usually favor a transfer at Broadway or to the south — but can justify skipping South Station because they are providing speedier service to Logan and Chelsea. Track 61 LRT can’t do that.
So I think Urban Ring LRT service via Track 61 presents a weaker case than it first appears. Now, it bears mentioning that capital costs for a Track 61 LRT route would probably be less expensive than a journey via South Station. If given the choice between Track 61 LRT and nothing, I’ll be entirely in favor of the former.
Conclusion
Ultimately, this is a fun thought exercise. The scenario I’ve contrived here presupposes a lot of things, so its “real-world relevance” is somewhat limited. A few final thoughts:
The problems I’ve outlined here will impact any Track 61 proposal; Track 61 will always be on the wrong side of the Mass Pike between Summer and Congress Streets, so you’ll always need to figure out a way to bridge that gap
This conversation becomes radically different if an LRT connection between Seaport and Logan is built — although even then, Track 61 will still be on the wrong side relative to the Transitway
Urban Ring considerations aside, I’d suggest that a Navy Line service to Logan would significantly benefit from the “under-the-garage” platform I propose here, especially if the Transitway is converted to LRT and thus cut off from Logan
The Seaport is centered on two east-west corridors, and there’s an argument to make that almost all services, even circumferential ones, would do well to feed into or otherwise align with those
For all the reasons outlined here, and others, most of my crayon maps going forward will favor both LRT and BRT Urban Ring services that run via South Station, rather than Track 61/Haul Road. At most, I can see Haul Road being useful for express service to Logan that bypasses the Seaport — that, it could do quite well. But for serving the Seaport proper, I think it comes up short.
As a holiday treat for myself, I went on a purely recreational trip to see the new Green Line Extension in action. Truth be told, I had a ball. Sitting in the so-called “railfan” seat, peeking out the front window as we sped along the Medford Branch, all of the politics and the delays could be momentarily forgotten, and I could enjoy the moment and say to myself, “Wow, this is so cool!”
The Green Line Extension has been in the works for decades. Its 2022 opening means that the one-seat ride between downtown and Union Square and other Somerville neighborhoods has returned after almost exactly 100 years. It is truly a delight to see it open at last. And make no mistake: any operational or aesthetic shortcomings notwithstanding, the bones of this extension are solid and will last for another 100 years if not longer. This is what long-term public investment looks like.
I took lots of notes and photos. Presented below are some of my observations. It is undisputable that many aspects of GLX remain in progress – there is still lots and lots of ongoing construction, for example. So I’m going to present my observations largely without commentary. I pay a lot of attention to details, and will share some of the particular details I noticed – I defer to more knowledgeable voices to assess the significance (or lack thereof) of those details.
All photos are dated Dec 26 2022. I’m writing this about a week after the fact, so it is possible that some of things have changed since my trip, though given the holidays, that seems unlikely.
Maps
Many maps across the system do not currently show GLX. By my observation, all four of the core Green Line transfer stations – Park St, Government Center, Haymarket, and North Station – have maps that omit the Green Line extension and physical signage that points to Lechmere.
The map at North Station is a typical example:
On closer inspection, someone (or multiple people, given the different ink colors) had tried to add in GLX by hand:
A similar situation on Park Street’s Red Line platform:
Park Street’s Green Line northbound island platform had a map and diagram with a sticker that read “Open Spring/Summer 2022”:
By contrast, all of the GLX stations had updated diagrams:
The GLX stations also all have those lovely neighborhood maps:
Quincy Adams (undergoing renovations) also shows GLX on its map in the paid lobby:
Maps within Green Line cars themselves were a mix, with some showing the extension and others omitting it. (Probably there was a pattern based on the older Type 7 vs newer Type 8 cars, but I wasn’t paying close enough attention to tell.)
Signage and wayfinding
“Stop Requested”
On my trip outbound on the Medford Branch, the operator came on the PA after departing Lechmere and said something to the effect of, “For stops on the Medford branch, please request your stop prior to arrival.” (She said something slightly clearer and more elaborate, but I don’t remember the exact phrasing.) The Stop Request sign lit up at every stop, and we made every stop.
On the inbound journey, there was no announcement. When we pulled in to Magoun Sq, no one had made the request, so the train came to a complete stop, but the doors did not open, and the train set off again.
In full candor, the Stop Request system seems reasonable on the B, C, and E branches, where stations are about 750-1000 feet apart; it does not seem reasonable to me on the D and Medford Branches, where stations are much farther apart, and where the often 10-min wait between trains means that a missed stop costs you an additional 15 minutes of travel time (whether you walk or double back on a train).
I should also note that there is no in-car signage on the Type 8’s to explain to riders how to request stops. (I didn’t specifically check while on a Type 7.) There also was no physical signage that I saw in any station about the presence of a Stop Request policy on the Medford Branch.
Next train indicators
I didn’t get a good photo, but the dot matrix indicators that display when the next train will come (e.g. “Heath St – 3 min”) often would just show something like “Trains every 8-13 minutes” on the inbound Medford Branch. As I understand it, this is because a specific countdown doesn’t begin until the incoming train departs Medford/Tufts. However, given that the travel time from Medford/Tufts is relatively short, that means that the countdown indicator will only ever give a few minutes’ worth of notice.
A similar problem happened on the northbound platform at Park Street: because the indicators only show the next two trains, there was a Union Square train only 3 minutes away, but it wasn’t visible on the board.
Next departure track indicators
At Union Square (and also at Medford/Tufts, though I spent less time there), hanging above the platforms are a pair of arrows which are intended to light up to tell passengers which train will depart first. I didn’t get a great photo of them, but you can somewhat make them out in this one (under the overhang, bracketing a white lit panel):
I departed Union Square multiple times during my trip, but only tried to use the indicators during one of those departures; as it happened, the indicator pointed to the wrong track that time.
Miscellaneous
A sign from the Aug-Sept 2022 Green Line shutdown sits tucked away next to the fare machines at Union Square:
The ramp appears to remain under construction at Union Square. As you can see, a small printed sign notes, “MBTA Ramp Closed, Please Use Elevator”.
But in fact, the ramp was unblocked and appeared open, and had a series of small placards with details about the neighborhood (including some evidence of a Somerville-Saugus rivalry over the origins of marshmallow fluff):
Returning to that first photo of the ramp, you’ll notice that there is also an open staircase on the left, which appears to offer an alternative to both the ramp and the elevator. When you get to the top of the staircase, however, it is sealed off with a chain link fence; I did not see any signage to note this.
Operations
Travel over the Lechmere Viaduct remains slow (at or under 10 mph). There was a small sign at the western end on the outbound track, saying “Resume speed.” Trains really fly on the Medford Branch, though – I would guess at least 35 mph.
The automated announcement at Union Square said, “Doors will open on the left hand side,” but the train had already switched over to the other track – meaning the doors would open on the right. (Trains arrive and depart from both tracks at Union, meaning sometimes the doors will open on the left, and other times on the right.)
On one train as we entered Lechmere, the automated announcement said something to the effect of, “This is Union Square. The destination of this train is Heath St/VA Medical Center.” (Beyond announcing the wrong stop, this announcement also doesn’t make sense in that Union Sq trains now go to Riverside, not Heath.)
The inbound Medford train I was on got stuck at a “red over red” signal at East Somerville station (i.e. just before entering the junction with the Union Square branch). The driver eventually had to reset it manually. I overheard chatter on the radio later that suggested there was still an issue at that signal.
One of the outbound Union Sq trains I took needed to have its destination swapped to Medford; we pulled in to Lechmere, and the operators directed people out on to the platform where we waited for the next train (itself originally for Medford) to pull in. I wasn’t able to figure out why the first train needed to change destinations.
On the Green Line Extension, the signals before switches say, “Stop, check for proper signal & switch”, and have little labels below – right arrow for Union, left arrow for Medford, that kind of thing; I’m sure that will make for a fun “Easter egg” for young railfans for many years to come.
On a very nerdy note: now that B and C trains both terminate at Government Center, the Park St Loop in theory does not see any regularly scheduled use (perhaps for the first time ever?). However, I saw at least one train getting short-turned on the so-called “fence track” at Park St, meaning that the loop continues to be used to short-turn trains to reduce bunching.
Infrastructure
The labels for platform level in the elevators at Union Square and Medford/Tufts used different styles for writing “Green Line” – the label at Union Square omits the space between the words.
Elevator buttons at Union Square
Elevator buttons at Medford/Tufts
One of the two elevators at Medford/Tufts was out of service.
Both doors to the Pedal & Park at Medford/Tufts had placards reading “Tap Charlie Card Here,” pointing to an empty space along the fence, where unconnected hookups were visible on the other side; I couldn’t see any place to tap a Charlie Card.
You get some really cool views of the Commuter Rail Maintenance Facility (Boston Engine Terminal) and the new Green Line maintenance facility from the Lechmere-to-Union viaduct:
I didn’t get good photos, but you also get a really cool view looking west from the Medford-to-Lechmere viaduct, from which you can see the Fitchburg Line commuter rail tracks, the Green Line’s flying junction tracks to/from Union, and the under construction Community Path that flies over everything:
And from the Lechmere-to-Medford viaduct, you get a cool view of the curved viaduct ducking under to go to Union, with the Green Line Maintenance Facility in the background.
While GLX stations are not unique in this regard, it is always cool to see level low-floor boarding, which I tried to capture in this quick shot:
The elevator at Lechmere has a lovely botanical pattern on its glass:
And finally, just before I was about to head home, I managed to snag a ride on one of the new Type 9 trains – I had tried earlier in the day to catch one but had barely missed it, and so had given up; as I was heading down to the Red Line platform at Park, I happened to turn around and see a Type 9 rolling in; so I delayed my departure in favor of a quick excursion up to North Station:
