Author: Riverside

The Kenmore Model and the Lechmere Model

Posted on by Riverside

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.)

The Kenmore Model’s persistence today creates an odd inequity, where residents of Brookline and Allston get to enjoy the convenience of a surface route (with frequent, nearby stops) with a one-seat ride directly into downtown. Residents of neighborhoods much closer to downtown (such as Roxbury) do not enjoy that benefit.

EDIT: I am reminded the Pittsburgh also enjoys a long-surviving first generation streetcar system. Topologically, it’s similar to the Kenmore Model, with a lengthy subway running into the core. However, after leaving the subway, the Pittsburgh Light Rail branches operate primarily on dedicated railroad ROWs, with rapid transit spacing. For this reason, I would not classify Pittsburgh Light Rail as a “streetcar subway”, its street-running segments notwithstanding. Its at-grade routes do not behave like buses the way that the T’s, SEPTA’s, and MUNI Metro’s do. In that sense, the term “Kenmore Model” isn’t applicable.

Lechmere Model

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. 

Addendum

Dec 21 2024

Following discussion on ArchBoston, I’m adding two additional models to the framework above.

Tremont Model

This was the original model of the Tremont Street Subway, whose purpose was simple: just get the dang trolleys off of downtown’s streets.

The Tremont Model is marked primarily by having a short distance of grade-separated ROW through a congested core. Rapid transit-like features may emerge, but as a side effect rather than an objective.

The Downtown Seattle Transit Tunnel operated under the Tremont Model for about 25 years before being converted exclusively to rapid transit-style light rail service. Bus routes from across the region converged and traversed downtown in their own grade-separated right-of-way. (Many of those buses also ran on highways, making them a bit less like the local streetcar service that originally ran into the Tremont Street Subway.)

The Newark City Subway historically would not have fit the Tremont Model, as its originally sole service ran in its own ROW on the surface with rapid transit stop spacing. However, with the opening of the Broad Street Extension, the network has now assumed characteristics of a Tremont Model, where a surface route making local stops enters a subway for a relatively short segment to avoid congestion on the surface.

Perhaps the clearest example of an extant Tremont Model is in Toronto (unsurprisingly), where a short streetcar subway runs from Union Station to Queens Quay before emerging to run at street level. Queens Quay in particular highlights a good example of the non-rapid transit goals of a Tremont Model subway: the station itself does not have fare control. Passengers pay as they board, just as they do on the street. This reflects the primary purpose of a Tremont Model: just get the surface vehicles off the street; any rapid transit-like results are secondary.

Medford Model

While the Medford Branch does feature bus connections, I argue that it does not prioritize integration with the surface network the way the Lechmere Model does. Its transfer points notwithstanding, none of its stops (aside from Lechmere) serves as a transfer hub or even a terminus point. Rather, the Medford Branch, particularly with its closer stop spacing, seeks to serve its suburbs directly, rather than relying on the 2SR of the Lechmere Model or the 1SR of the Kenmore Model.

The Medford Model was really first implemented on the Highland Branch in the 1950s when it was converted from a commuter rail line. As modern light rail lines acquire more and more characteristics and responsibilities of rapid transit, the Medford Model has emerged as a predominent model in the 21st century.

Another version of the MBTA map

Posted on by Riverside

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.

Ferries of New York City: a map of New York’s commuter ferries

Posted on by Riverside

What could be more patriotic than posting a map of New York City ferries? (That comment was unserious, but it belatedly occurs to me that I probably could have cleverly woven in something about the Statue of Liberty. “Fourth of July” -> “Lady Liberty” -> “The ferry that goes to the Statue of Liberty” -> “all the other ferries” -> “here’s a map”, something like that.)

As described in the top right of the map, there are something like half a dozen of companies running commuter and/or full-time ferry services on the waters surrounding New York City. As far as I can tell, no one has made a consolidated map showing all of these services in one place. I suspect this is because there isn’t a huge amount of geographical overlap between the “territories” of the companies.

  • NY Waterway operates on the Hudson, with criss-crossing network of peak-only services and a smaller set of core services which also run during the off-peak and weekend.
  • NYC Ferry runs a dense network on the East River and along Brooklyn’s shores (plus a Hudson River route to Staten Island)
  • Seastreak runs services to the Jersey Shore; these are mostly peak-only, but there are handful of mid-day and late-evening trips sprinkled in, plus a Sandy Hook Beach service that mostly runs on weekends
  • Liberty Landing City Ferry runs to its namesake, with an additional stop just across the Morris Canal at Warren St in Jersey City (which I omitted here, bowing to the challenges of a complex diagram)
  • Statue City Cruises runs ferries to Liberty Island and Ellis Island, primarily between 9am and 5pm, though with some later evening departures available from the islands only
  • The Trust for Governors Island runs a network of routes, alongside a weekend-only route run by NYC Ferry
  • The famous Staten Island Ferry is run by the NYC Department of Transportation

NYC Ferry and the Staten Island Ferry are publicly owned, while the rest are privately owned.

Beyond the companies listed above, there are also excursion and sightseeing ferries, but I drew the line at drawing those lines on the map. (Ha.)

For those who are interested, some details on frequencies, this mapmaking process, and analysis of this ferry system in the context of others, below.

Frequencies

  • NY Waterway operates on the Hudson, with criss-crossing network of peak-only services and a smaller set of core services which also run during the off-peak and weekend.
    • The all-day services usually run on 20-minute frequencies,
    • while the peak-only services are usually every 30 or 40 minutes.
    • The Paulus Hook <> Brookfield Place route runs on 15-minute frequencies, except during the morning peak when it increases to 7.5-minute frequencies
    • NY Waterway also runs two services much further north, connecting cross-river to Metro-North’s Hudson Line
  • NYC Ferry runs a dense network on the East River and along Brooklyn’s shores (plus a Hudson River route to Staten Island)
    • Most routes run approximately 45-minute frequencies, with some falling to 60 minutes off-peak, and the Staten Island and Hunters Point South routes increasing to 20-25 minutes during peak
  • Seastreak runs services to the Jersey Shore; these are mostly peak-only, but there are handful of mid-day and late-evening trips sprinkled in, plus a Sandy Hook Beach service that mostly runs on weekends
    • Frequencies vary widely, but usually see an hour or more between departures
  • Liberty Landing City Ferry runs to its namesake, with an additional stop just across the Morris Canal at Warren St in Jersey City (which I omitted here, bowing to the challenges of a complex diagram)
    • This route runs hourly from 6:30am to 7:00pm
  • Statue City Cruises runs ferries to Liberty Island and Ellis Island, primarily between 9am and 5pm, though with some later evening departures available from the islands only
    • The New York route runs on 25-min frequencies on weekdays, which gets bumped to 20-min frequencies on weekends and holidays. The New Jersey route runs every 35-40 minutes
  • The Trust for Governors Island runs a network of routes, alongside a weekend-only route run by NYC Ferry
    • Its Manhattan Route runs daily with half-hour frequencies most of the day
    • The weekend-only routes to Brookyln run hourly
  • The famous Staten Island Ferry is run by the NYC Department of Transportation
    • This service runs 24 hours a day, 7 days a week, with 30-min frequencies off-peak that rise to 15-20-min during peak

Almost none of these services run SUAG (“show up and go”) frequencies, with the exception of peak Paulus Hook <> Brookfield Place service, which bops back and forth between Jersey City and Downtown (only 4000 feet apart) every 7.5 minutes during rush hour.

The higher-frequency services might be considered “SUAW” (show up and wait). Many of the ferry terminals are enclosed, with seating and sometimes light food options, making a wait more tolerable. Other routes do not reach this threshold, and a traveler must take the schedule into account when planning journeys.

Larger Implications

Ferries are cool but weird, embodying a cool but weird tension in our urban spaces.

In an earlier era — we might call it the “modern era” or the “industrial era” or the “pre-war” era –, cities grew up around water. Rivers were transportation corridors, harbors were doorways to the rest of the world. Being close to the water was an unambiguous asset.

In the current era — “post-modern”, or “post-industrial”, or “post-war” –, water has lost its primacy and now vies among a family of other factors in shaping our cities. Being close to “pretty water” is an asset to commercial and residential development, but being close to “industrial water” is a strong negative. Water becomes an obstacle for transit to build around or navigate through, seen as a constraint rather than an enabler of mobility.

Where cities were once drawn to water, now it is often a neutral or slightly repelling force, as cities instead develop in other directions. This in turn impacts transportation.

Boston had a dramatic example of this: the Atlantic Avenue Elevated, built along the city’s wharves, stupendously underperformed as water’s royal status was gradually revoked in the early twentieth century. With the docks no longer a transportation center of gravity, the El became a rapid transit route whose walkshed was half water. Its demolition seems inevitable in hindsight.

For ferries to work at large scale, they need to be connected to unusually strong centers of gravity. This is visible in New York’s ferry network, which is heavily weighted toward Lower Manhattan. For many commuters, the ferry is probably their last mode of transit before walking the last few steps to work — there are just that many jobs crammed into Downtown, within a 10 minute walk of the pier.

The problem with ferries is illustrated by NY Waterway‘s free bus shuttle network, which radiates out from their Midtown West pier, running along major cross-streets to 3rd Avenue. The edge of the traditional core of Midtown is about a mile inland, limiting the ferry’s ability to get people where they need to go. A subway can travel under both water and road, creating a seamless journey where the ferry requires a transfer.

(New development around, for example, Hudson Yards, is increasing the ferry’s usefulness, of course, which reflects a larger trend in New York’s ferries: they often connect to formerly industrial redeveloping areas.)

The continued role of ferries is illustrated by NY Waterway’s full-time network (seeing 20-min headways all day) and the Staten Island Ferry (with 15-30 min headways 24/7): crossing water that lacks bridges and tunnels. Along New York City’s entire 14 mile Hudson shore, there are only six fixed crossings, most of which are in the southernmost four miles. By contrast, the East River has eight crossings just in its southernmost two miles (from the Williamsburg Bridge to the subway tunnels). The Hudson ferries essentially double the number of cross-river connections.

Ferries will probably never again enjoy the popularity of their heyday. But, at least in New York, they clearly still have a part to play.

Design Process

This is another early attempt at mapmaking using Illustrator. (Very late to the party.) From a design perspective, there were two key challenges (beyond the logistical challenge of finding, cataloguing, and untangling the web of overlapping services).

First, the scope and scale. The distant edges of the network stretch anywhere from 12 to 20 miles away from Downtown. At the same time, most of the network was constrained to a much smaller area. And in terms of mapping, the real painpoint is a pair of very small areas where there are lots of overlapping routes (the lower Hudson and the mouth of the East River), with extra space required to accommodate the necessary level of detail.

The physical nature of the ferry network meant that the diagram would inevitably have a bare minimum of geographic fidelity. But I tried not to provide much more detail than that — not only to simplify my own work, but to avoid the appearance of more precision than intended. For example, Paulus Hook, Liberty Harbor, and Liberty Landing are all a stone’s throw from each other. In fact, “The Battery/South Ferry/Whitehall” as I’ve drawn it is actually a consolidation of three terminals that are pretty far apart. In both cases, the contraction and expansion of geography was needed in order to show complicated service patterns clearly.

The second challenge was the range of service levels that needed to be readily distinguishable. I wanted the full-time network to be immediately visible and unambiguously distinct from the other services. In practice, this meant that I had to come up with three visual tiers “below” a “standard full thickness” line similar to what I’d use on a subway diagram. I opted to use two dimensions to create the four levels: weight and solid/dashed. How effective that strategy was is a question I will leave to the reader.

Finally, one unexpected challenge was the multiplicity of names used for “stops”. Some of this challenge was self-imposed, such as the aforementioned consolidation of The Battery, South Ferry, and Whitehall Terminal. But, for example, nearly all of the NY Waterway piers had double names, such as Pier 11 Wall Street or Brookfield Place/Battery Party City. In some cases, their second name was an indication of their city — for example, the two piers in Weehawken. This was a convention I expanded a bit, such as including Staten Island alongside St. George.

The Boston Metropolitan Railway: an imaginary version of the MBTA

Posted on by Riverside

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):

  1. 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.
  2. 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.
  3. 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.

The long-lasting impact of the “transit land grab” in Boston

Posted on by Riverside

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. 

(Map reproduction courtesy of the Norman B. Leventhal Map & Education Center at the Boston Public Library; this is an 1814 map, descriptively titled A plan of those parts of Boston, and the towns in its vicinity, with the waters and flats adjacent, which are immediately or remotely connected with the contemplated design of erecting perpetual tide-mills, illustrating the new “backbone” streets mentioned above.)

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. 

The map at the beginning of this post is from Alexander Rapp’s utterly delightful timeline of transit routes in Greater Boston by mode, modified to show just the steam/diesel train routes.

Transportation Dreams submissions

Posted on by Riverside

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: 

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.

Additional details on the various proposals in Project Electric Sheep can be found in the appendix to this post.

(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.

Particular data sources include:

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 redesigned my redesign of the MBTA’s system diagram

Posted on by Riverside

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.

Mapping Boston’s 1921 Subway-Streetcar Network

Posted on by Riverside

Last summer, I wrote that 2022 marks the (true) centennial of the Green Line, with the 1922 opening of the Lechmere transfer station commencing a transition from the “local streetcar network” model to the “rapid transit” model. I point to the rapid demise of the streetcar network in the ensuing two decades as evidence of an intentional transformation. 

Understanding the pre-transformation network

To understand the scope and scale of that transformation, it’s worth looking at what the “subway-streetcar network” looked like immediately before that transformation. One might think that that would be a simple task: simply Google 1921 BERy map boston and this is the first result:

https://commons.wikimedia.org/wiki/File:1921_BERy_system_map.jpg

Except… this map doesn’t tell the whole story. A little bit of further digging reveals that many of the surface lines on this map didn’t actually operate into the subway – the far-flung lines in West Roxbury, for example. Moreover, this map omits the foreign cars that weren’t run by the Boston Elevated Railway but still operated into the subway, turning at the Brattle Loop. 

Finding the “subway-streetcar routes”

Identifying which routes operated into the subway 101 years ago is actually not a simple task. Again, I believe this is a consequence of how BERy saw the Tremont Street Subway: it wasn’t a rapid transit line and it wasn’t a “trunk” of the network – it was just a way to get streetcars off of congested streets in downtown. From what I’ve seen, it probably never would have even occurred to BERy officials to publish a map of the “subway-streetcar network” – they were all just “surface lines”.

Making matters more difficult is that BERy also did not (to my knowledge) publish public timetables for specific routes. There were internal timetables, though my understanding is that they were very internal indeed, and are difficult to parse a century later. Most notifications of changes in routes, for example, appear to have occurred in newspaper announcements. 

The Map

Here I am indebted to the labors of love of numerous local transit historians. Building on their work, I have created what I believe is the first map of its kind: a full diagram of all BERy services that offered one-seat rides into the downtown subways in 1921. 

Click to enlarge

Applying the anachronistic visual language of today’s Green Line and Blue Line, I’ve framed the 1921 network with modern points-of-reference, to make it easier to understand its scope and complexity.

Again, it’s important to understand that this diagram does not represent how BERy officials or riders would have conceptualized their system. However, thinking of the streetcar network in these terms is also vital for understanding the decline of Boston’s streetcar network (which began much earlier than we often think of it as.)

List of Routes

The routes operating into the subways included the following (note that many routes had short-turn turnbacks, the same way some trains on today’s E Line terminate at Brigham Circle); I have included some modern comparisons based on today’s routes in parentheses:

Kenmore Portal lines

  • Watertown (57)
  • Lake Street [Boston College] via Commonwealth Ave (B)
  • Reservoir [Cleveland Circle] via Beacon Street (C)

Ipswich Street lines

  • Chestnut Hill and the Cypress St Carhouse (55 + 60)

Huntington Ave lines

  • Lake Street [Boston College] via Village Sq [Brookline Village] (E + 65)
  • Jamaica Plain Carhouse (just south of Jamaica St) (E + 39, but not all the way to Arborway/Forest Hills)

Pleasant St Portal lines

  • Egleston (43)
  • Dudley [Nubian] (similar to SL5, but on Dover St [East Berkeley St] from Washington to Tremont)
  • City Point (9)

East Boston lines

  • Central Square, Cambridge via Joy St Portal (no equivalent, but somewhat similar to the proposed Blue-Red Connector)
  • Jefferies Point (120)
  • East Boston and Chelsea (114/116/117, 112, and 121)
  • Orient Heights (120)
  • Revere Beach (paralleling the route of today’s Blue Line on Bennington St and Ocean Ave)

Lechmere lines

  • Harvard (69)
  • Davis, and Clarendon Hill, via Somerville Ave or Highland Ave (87 and 88)

Canal Street Incline lines

  • Sullivan via Main St (92)
  • Sullivan via Bunker Hill (93)

Foreign streetcars

  • Beachmont (using part of today’s 119)
  • Revere Beach (116 and 117)
  • Lynn (probably most similar to today’s 455)
  • Salem and the North Shore (450)
  • Woodlawn (111)
  • Melrose Highlands via Malden & Chelsea (I believe roughly using today’s 131 north of Malden Center)

Acknowledgements

This has been a gargantuan project, far more perhaps than the map itself would suggest. The details needed to pinpoint the system exactly as it existed in 1921 are numerous and scattered. As in my previous post, I must heartily thank the army of transit historians who have come before me, including Ron Newman, Bradley Clarke, O.R. Cummings, Frank Cheney, and Anthony Sammarco.

I want to extend a special thanks to DAS, who has expertly collated the primary source material upon much of this map is based, enabling us to expand, contextualize, and occasionally correct the work done by Newman, Clarke, Cummings, Cheney, Sammarco, and others. His expert review caught many errors of mine, answered numerous arcane questions of mine, and uncovered the fine details at the margins of this project to ensure this map was as accurate as possible.

When I was a child, reading the copy of Trolleys Under The Hub my parents had given me, my imagination was enchanted by the idea of a “Green Line” that apparently had so many branches. This is the map that I had wanted to see then, so it is a profound delight to finally see it brought to life; as such, I offer my profound thanks to all those who helped me create it.

Notes and Further Reading

As printed in the image:

  • Services on this map operated into the Tremont Street Subway and the East Boston Tunnel in 1921.
  • Street names included here are illustrative and not exhaustive; some routes used additional streets not marked.
  • Additional transfer points existed but are not shown here.
  • Huntington and Ipswich services ran at street level along Boylston, paralleling the subway below.
  • Additional surface-only services ran over shared stretches of track, but are not marked here (for example, an Allston-Dudley service that ran through Village Square).
  • Services intermingled in the Central Subway, and sometimes were through-routed on to new routes once exiting the subway as needed.
  • Occasional additional suburban services may have been through-routed in the subway (for example, from Arlington), but these services appear to have been irregular.
  • Some foreign transfers may have been available at additional locations than are marked here (e.g. Watertown, which likely almost certainly had transfers to the Middlesex & Boston Street Railway).

I recommend the following books on this topic:

References

Tracking down which routes were running into the subway in 1921 was surprisingly difficult. When possible, I’ve used primary sources, but in some cases have relied on secondary sources, particularly since some transit historians have obtained access to archive materials that are more difficult to access remotely or as a member of the public.

I did a poor job of cataloguing my references when building this map. As such, I am currently in the process of rebuilding the reference list for this post. My WIP reference list is available as an appendix to this post.

Mapping the T’s Summer 2023 Closures

Posted on by Riverside

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.)

UPDATE: as of July 5, the Union Square branch closure has been postponed til September.

Phase 1: July 18 – July 28

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.

I redesigned the Framingham/Worcester schedule

Posted on by Riverside

In an effort to provide more frequent service to the three stations in Newton, I’ve developed a rework of the Framingham/Worcester Line schedule; there are lots of open questions that I can’t answer at this point, but from what information I do have, I believe the rework would be feasible, and would in fact improve service for the majority of riders on the line.

I propose switching from a “zonal express” model to a “skip-stop” model; this would keep travel times under control, while enabling trains to stop more frequently within the higher density suburb of Newton. Based on my analysis, this would require no additional rolling stock, and possibly may be able to use one fewer train than today. Operational expenses would potentially increase mildly, but no capital expenditures should be required to enable this proposed schedule, aside from the already-underway Worcester Union Station platform project.

Here is a tentative draft of my proposed schedule; background, methodology, and details described below.

proposed skip-stop schedule

Background and current conditions

The Framingham/Worcester Line is a difficult line to run. It presents multiple challenges:

  • It is long: about 43 miles as the crow flies from Worcester to Boston – comparable to the Providence Line (measured from Providence) 
  • But, unlike the Providence Line, which has lengthy straightaway segments, the Worcester Line has curves aplenty, including a pair of modestly tight S-curves as the rails wind their way into Worcester
  • It has lots of stops: 15 between Worcester and Back Bay (compared to 8 on the Providence Line)
  • It has operational constraints due to the locations of platforms (see this post by Dave Perry explaining the track numbers, and detailing some of the operational constraints):
    • “The Newtons” (Newtonville, West Newton, Auburndale) currently have platforms only on Track 2
    • At Wellesley Hills and West Natick, the parking lots are located next to the platform on Track 2; the platform for Track 1 is only accessible via an at-grade crossing across the tracks
      • The T therefore runs all peak direction trains on Track 2 through these stations to avoid having large crowds of commuters crossing live tracks
    • Worcester’s platform is currently only accessible from Track 1, though the T is building a center platform to allow access from both tracks and enable more than one train to occupy the station at once

The T addresses these challenges through two methods.

First, peak direction trains are divided into “Worcester expresses” and “Framingham locals”, where hourly trains depart from Worcester and make all stops to West Natick before expressing to Boston Landing, while offset hourly trains depart from Framingham and make all local stops. A single “Heart to Hub” (or “H2H”) train leaves Worcester and runs express to Framingham and then express again to Lansdowne, to provide Worcester commuters an option that arrives within Boston’s borders in less than an hour. (Journey time to South Station is 1h5m.)

current schedule

Second, to accommodate the single platforms at the Newtons, as well as the pedestrian-unfriendly conditions at Wellesley Hills and West Natick, the T runs all peak-direction trains on Track 2 between Framingham and Boston. In essence, Track 2 acts as the “inbound” track in the morning and transforms into the “outbound” track in the afternoon. 

Reaching toward frequent Regional Rail service for the Newtons

This project began with an effort to identify ways to increase the frequency of service to the Newtons, which sit in modestly walkable neighborhoods of similar density to the villages served by the Green Line to the south, but which only see hourly service during rush hour. 

density map of Newton along the Worcester Line,
from https://mtgis-portal.geo.census.gov/arcgis/apps/MapSeries/index.html?appid=2566121a73de463995ed2b2fd7ff6eb7

What’s more, there are trains running through these stations during rush hour, roughly every thirty minutes; the problem is that those Worcester expresses run non-stop in order to keep travel times down for the longer commutes.

If only there were a way for those Worcester expresses to stop at the Newtons without impacting the commute times for riders west of Framingham.

Then something occurred to me: what about a skip-stop service?

Skip-Stop Services

For those unfamiliar, skip-stop services are a technique to speed up journeys on lengthy routes by dividing trainsets into two groups, with consecutive stations alternating between the two groups, punctuated by periodic “all trains” stops served by both groups.

Skip-stop service was used throughout the 20th century on major American subways. New York, Chicago, and Philadelphia all used skip-stop patterns to varying extents, though today I believe only one set of services remains in use (the J/Z in New York). They have fallen out of favor in part because they make the system more confusing for new riders and because (in my opinion) the time savings on a rapid transit system simply aren’t particularly large. And particularly for “local” journeys on a subway line – e.g. in New York if you’re only looking to go 30 blocks, about 3 stops – skip-stop service is much more disruptive, requiring a transfer.

Skip-stop service potentially can be effective, but it needs to be on a corridor where there are both significant time-savings and minimal intra-corridor (“local”) journeys.

So, I wondered, could skip-stop service patterns generate enough time-savings to “free up” space in the schedule for Worcester expresses to stop at the Newtons?

The answer, I believe, is yes.

Generating a schedule

To test different service patterns, I built an interactive spreadsheet that allows you to

  1. Assign stations to different service groups (e.g. “A” or “B”)
  2. Set each train’s departure times from Worcester
  3. Assign each train to one of the service groups

And from there, the spreadsheet will auto-generate the schedule for each train. Critically, this spreadsheet takes into account the time-savings from skipping a stop. (It also takes into account the significant speed restriction due to the curve in eastern Worcester, which will slow trains regardless of whether they make the subsequent stop in Grafton.)

To confirm the accuracy of the spreadsheet’s predictions, I provided it with the service patterns and Worcester origination times for the current schedule. (One major limitation of the spreadsheet is that it only supports calculations for trains originating in Worcester, so I used a hypothetical Worcester departure time that calculated a Framingham departure time matching the current schedule.)

The schedule predicted by the spreadsheet matches the current schedule with high accuracy, in most cases deviating from the current schedule by less than 60 seconds. (The deviations are slightly higher for the H2H service, but my spreadsheet overestimates travel times, and only by 3 or 4 minutes.) So, I am modestly confident in the accuracy of my model’s predictions.

current schedule, as inferred by my model, based on inputted stopping patterns and departure times from Worcester
actual current schedule

Presenting: Half-hourly skip-stop service from Worcester

By moving the stops between Worcester and Framingham, and the stops between West Natick and Auburndale, into a skip-stop pattern, we get the following schedule.

proposed skip-stop schedule

This schedule achieves the primary objective: providing more frequent (half-hourly) peak direction service to the Newtons, without requiring additional rolling stock or capital improvements (beyond the new platform at Worcester, currently under construction). 

This schedule provides additional benefits.

Benefits to frequencies and journey times

Service from Worcester doubles to half-hour headways. Additionally, coming from Worcester the travel times are equal (or slightly better) to today’s Worcester expresses, at about 1h21m (compared to today’s 1h23m). 

Service from Framingham becomes clock-facing with half-hour headways. There is a resulting trade-off: the current schedule offers hourly 43 min journeys in addition to hourly 56 min journeys (offset from each other by about 15 minutes); my proposed schedule sees consistent journey times of 50 min, which is a bit slower for commuters who are used to the current Worcester expresses. On the other hand, my proposal eliminates the 45 min gap between trains, significantly improving commute flexibility. 

(And, as I’ll discuss below, it may be possible to run two H2H trains, which would provide an additional express option for Framingham commuters.)

Journey times either remain constant (within 3 minutes) or improve from most stations. Ashland and West Natick see a similar tradeoff to Framingham – journey times increase by 6-7 minutes; in West Natick’s case, that is off-set by a doubling of frequency.

Benefits to rolling stock efficiency

Finally, this schedule requires no additional trainsets, and may in fact require fewer trains than the current schedule. By my reckoning, the current schedule requires about 8 or 9 trains, possibly with one or two intermingled with other lines. My schedule requires 8 trains, which can be reduced to 7 if most reverse services make limited stops (which would be commensurate with the reverse peak demand, which, at least in 2018, was focused on commutes from Boston to Framingham and to Worcester, and to a lesser extent, Natick.)

If even one trainset is freed up, this opens the door to several possibilities.

Additional “Heart-to-Hub” service

First, the newly available sets can be repurposed to provide additional service on the Framingham/Worcester Line. For example, one of those extra sets could be used to add an additional “Heart-to-Hub” express service from Worcester:

potential skip-stop schedule with an additional H2H service

(In the not-too-distant future, I would love to see a second H2H slot instead filled by a MassDOT service from Springfield, ideally using rolling stock that has been sourced externally.)

30-min headways on the Fairmount Line

Possibly most importantly, even just freeing up a single extra set would allow the Fairmount Line to increase from 45-minute headways to clockfacing 30-min headways, which would be a big step forward in getting the Fairmount Line closer and closer to rapid transit service. 

half-hourly Fairmount service, requiring only one additional trainset

Higher frequencies to the Newtons

Finally, while it would definitely require at least one additional trainset relative to today, I sketched out a schedule that would add a third stopping pattern, originating at Framingham, expressing to Auburndale and making all stops thereafter, providing 3 tph to Framingham, and providing clockfacing 20-minute headways to the Newtons. This schedule would (I believe) require 8 sets operating from Worcester, and two additional sets operating from Framingham.

schedule concept for service to the Newtons every 20 min

(The schedule generator I built requires trips to “originate” in Worcester, so I’ve included hypothetical departure times from Worcester in italics – trains with the N service pattern would in reality originate at Framingham.)

Overall, I would use the extra trainset(s) to reduce Fairmount headways to 30 minutes as a first priority, and add a second H2H service as a second priority. I don’t see an urgent need to provide 20 minute headways to the Newtons – I offer it more as a fun bit of imagination. 

Conclusion

To review, I believe using a skip-stop service pattern originating from Worcester will:

  • Provide half-hourly service from Worcester at the same travel time as today
  • Provide half-hourly service in the peak direction to the three stations in Newton
  • Provide near clock-facing service from Framingham at a consistent journey time comparable to today
  • Maintain existing frequencies for all other stations
  • Maintain equal or faster journey times for most stations
  • Require no additional rolling stock
  • Potentially free up existing rolling stock to raise frequencies on the Fairmount Line to 30 min

To me, that sounds like a palpable improvement in service — and something I believe would be well worth the MBTA’s consideration.