Redesign the Urban Ring

I like the extension of the Mattapan line to Roslindale
Just out of curiosity, why? The MBTA's Route 30 bus, which currently links the two neighborhoods, carries only 2,000 passengers per day on a route serving relatively congestion free streets. Would a 4 mile trolley ride to Ashmont and the Red Line become the preferred path of travel to downtown for Roslindale residents over the current 1 mile bus ride to Forest Hills and Orange Line? Or do you think there is some untapped demand in travel between the two neighborhoods that would be willing to ride a trolley but not existing bus service?
 
As suggested by @TheRatmeister, we're reviving this thread for transit pitches related to Urban Ring, instead of dumping them in the general Crazy Transit Pitches (or occasionally the Green Line Reconfiguration thread).

To kickstart some discussions, I'll start by posting this map showing some southwest quadrant alignments, originally written as a reply to @BlazingZack :
1000028183.png


Copying over some notes I said over there:

Almost any combination of lines here can give you an Urban Ring, and/or an alternative D-E connector that serves LMA more directly than the Huntington Ave stations.

Your choice depends on too many variables, which I detailed in the original comment.

If anything, it's Exhibit A of how much of the "divisiveness" really depends on your level of optimism. The "bore baby bore" Reddit folks will think very differently from someone like F-Line who questions just about any C&C subway with utility relocation, not to mention TBMs.
 
So just to restart this thread of urban ring thoughts, I figure a good place to start would be listing some generally agreed upon conclusions.

Essentially mandatory nodes:
  • LMA
  • Nubian
Highly desirable nodes:
  • Somewhere in Cambridge, either Kendall, Central, or Harvard
  • Ruggles or Roxbury Crossing
  • Sullivan
  • Logan Airport, preferably the terminals
  • West Station
  • Kenmore/Fenway Park
Lower priority, primarily residential areas:
  • Southie
  • Assembly
  • Seaport
  • Allston/Lower Allston
  • Brighton
  • Union Sq
  • Charlestown
  • Chelsea
  • Revere
  • Everett
  • UMass/Columbia Point
  • Wonderland
  • Widett Circle
  • Suffolk Downs
  • Cambridgeport
Mode choice:
Either GL compatible light rail or a separate subway line, not BRT.

Method of construction:
Surface/elevated whenever possible, C&C tunnel when it's not, TBM for the toughest sections.

The rest of this will be some of my random personal opinions:
  • The rebuilding of the Tobin Bridge in the near-but-not-too-near future is a good opportunity, and would provide an excellent link to/between areas currently underserved by transit (Charlestown/Chelsea)
  • Focusing on areas with strong potential for redevelopment provides an opportunity to fund the scheme. This includes areas such as Andrew, Widett Circle, Lower Allston, Inner Belt, that polluted industrial hellscape part of Everett, and Wonderland.
  • Good corridors for C&C subway construction include Dorchester St/E Broadway (The Southie One), Broadway (The Chelsea/Revere one), Broadway (The Everett one, c'mon lets be more creative), Melina Cass Blvd (Although Elevated might be even better here)
And now my spicy takes:
  • Automated Light Metro (à la Copenhagen or Vancouver) is the best mode choice. Smaller trains with very low headways are well suited for a route where many people will take short journeys involving transfers, and can decrease construction cost with smaller stations.
  • An APM connecting to the BL would be the better solution for Logan Airport, allowing UR service to serve large, dense areas in Everett, Chelsea and Revere while also facilitating redevelopment of Wonderland and the Everett Hellscape™.
  • While Kendall is a better node than Harvard, serving Kendall would likely mean sacrificing service to some combination of Lower Allston/Harvard/Central/Union Sq, which, IMO, tips the balance away from Kendall and towards Harvard or Central.
  • The GJ would be better suited to a more local service, such as a light rail line/busway with frequent stops connecting to West Station/Sullivan. Urban ring service should find another ROW.
  • The urban ring doesn't have to be a ring, a U-shape could be better.
So, with that said, here's my preferred Urban Ring:
Screenshot 2024-02-10 at 22.46.08.png
 
To bring over a few pieces that I contributed in the other thread:
Here is a broader overview of my take on [the question of getting from BU Bridge to Longwood], with the obligatory Pretty Map:

1707613847318.png


...

One question I think that would impact this: what kind of service are you running south of Fenway station? Is it surface-running in a dedicated ROW? In transit lanes? Is it grade separated? How far does it run -- LMA, Ruggles, Nubian? I think those would inform what kinds of investments and tradeoffs are reasonable between BU and Fenway.
To the points that @Teban54 raised in the previous thread:
Almost any combination of lines here can give you an Urban Ring, and/or an alternative D-E connector that serves LMA more directly than the Huntington Ave stations.

Your choice depends on too many variables:
  • a) How fast do you want trains to traverse through this quadrant?
    • At-grade LRT with mixed street running (most likely on Park Dr and Mountfort St)?
    • At-grade LRT with all 13 grade crossings, but with dedicated lanes only?
    • Grade separate as much as possible, with maybe 1-2 grade crossings?
    • Fully grade separated?
On this point, I've favored going with two answers instead of one. I argue that a service coming from Kendall + Sullivan (if not farther) needs to prioritize being fast (which is why I send it down the Fenway Branch to Brookline Village), while there is a niche for a second service that runs more slowly over a shorter distance. My Transportation Dreams map depicted this as a Harvard <> Ruggles service, but I think you could also do a Kenmore <> Ruggles service.
  • b) Related to (a): How much demand is there for through-LMA rides and to-LMA rides from the north? This determines how many people benefit from a faster ride.
    • Example O-D pairs: Cambridge-LMA, OL North-LMA, Riverside-Kendall/Harvard, OL South-Kendall/Harvard, Nubian-Kendall/Harvard, many non-commute trips and trips involving B branch
My general theory here is that farther destinations (e.g. Orange Line North) will be biased toward to-LMA journeys, while closer destinations such as Harvard and Cambridgeport will be more biased toward through-LMA journeys. I think the "squished" nature of the Urban Ring corridor also impacts this, as does the continued high-speed of the Red Line -- no Orange Line rider is going to transfer at Ruggles for Harvard, in my opinion.
  • c) How much detour do you want to make to the southwest at LMA?
    • Which east-west road through LMA to use: Fenway-the-road, Longwood Ave, or Francis St?
    • Related to (b) in terms of how many riders will need to wind through the LMA detour
    • Also related to cost (financial and political), as Longwood Ave and Francis St will be more expensive
    • Note that street-running on Fenway-the-road may result in speed restrictions that offset advantages in travel time
In my opinion, an infill at Aspinwall ("Kent Square") on the Fenway Branch provides pretty good coverage to the southwestern LMA.
  • d) How much detour do you want to make to the northeast at Kenmore?
    • Several alignments too: Park-Mountfort, D-Pike, and "Kenmore/Lansdowne" (D-Lansdowne-Brookline Ave-B)
    • Again, see earlier note on travel times for street-running sections
  • e) Related to (d): How important do you think Kenmore is?
    • Compare through-Kenmore and to-Kenmore demands
    • Hitting every GL branch may be as good as hitting Kenmore? IMO, its function as a bus transfer hub is overrated: the only Kenmore bus that doesn't go to LMA is the 57
    • Kenmore/Lansdowne does offer transfer to commuter rail, but some designs allow you to do it at West Station
    • 2015-17 passenger survey data: 42% of Kenmore riders start their trip from there, 27% transfer from buses, 31% transfer from another GL branch
      • 2022 passenger survey data is available, but sadly it drops the "Previous Mode" field and the raw number of passengers (only shows percentages), so not nearly as useful for this purpose
I don't see Kenmore itself as a particular priority, though see (h) below.
  • (f) How important do you think getting to the core of LMA is?
    • Current D and E stations require average walk of 10 minutes to most hospitals, while a more central station can do much better
      • @Riverside has a more detailed table that he may want to post?
    • But LMA has higher transit mode share than most other employment centers, suggesting the 10-min walk may not be deterring too many people from using transit?
Yup, I need to update that table and post it. Relative to expense, I'm not convinced a core LMA station is necessarily worth it.
  • (g) How important is a convenient transfer to the B branch?
I would give this some weight, in part because we're also talking about a convenient transfer to the 57 bus; between those two, that's a lot of Allston Brighton that could have an easy 2SR to LMA. (There's also a related question about providing a link between West Station and LMA.)
  • (h) Do you even want a continuous service at all?
    • One alternative is to simply terminate two legs of LRT services both at Brookline Village, avoiding the engineering challenges of cross-LMA altogether
    • Another is to have the northern half be LRT that ends at Brookline Village, and the southern half be BRT that goes through LMA surface roads, ending at Kenmore
    • Splitting the two services at Kenmore is also an option (if you can somehow short-turn Comm Ave trains)
    • Whether that's actually desirable depends on (b) and (e)
I think continuous service can be a good long term goal, but that there are plenty of discontinuous alternatives that are very viable. I'll also point out that the "squished" nature of the Urban Ring corridor means that journeys around the Ring through LMA are going to be less competitive against, e.g. the 1 bus, depending on your destination. So, there are some limits to the benefit of a continuous route.

In particular, I think that a "first gen build" that terminates multiple services at Kenmore could be a useful way to break this project into smaller chunks.
  • (i) Of course: What's your budget?
Well that's the question of course. I think it might be more feasible and/or productive to frame this question as "where would these projects fall in your priority list?". Where do they fall in my priority list? Good question, stay tuned.
 
This comment is inspired by the very first post in this thread by Van, and is a continuation of my comment in the Green Line Reconfiguration (GLR) thread. I decided to move here once I realized what I'm about to say have significantly more to do with Urban Ring (UR) and less to do with GLR. While my previous comment in the GLR thread was largely feedback on Van's and Riverside's points, this comment ended up incorporating much more of my personal opinions.

High-level philosophy of an Urban Ring

While Van's comment is technically more about GLR than Urban Ring, because it was branded as an Urban Ring proposal, a lot of the underlying motivations are more applicable to UR than GLR. In particular:
The purpose of this is two fold; the first being to take pressure off of the 4 major downtown transfer points (Park, State, Gov't Center, and DTX), and second to connect large job centers, primarily Kendall Sq and the Longwood Medical Area.
These are points I really want to stress, especially the first point about reducing transfers downtown. The same argument was conveyed by @JeffDowntown much more recently:
Simplistic reply on the goal of an Urban Ring, but it really is about total network capacity and efficiency. And a big barrier today is the transfer capacity at the four main downtown transfer stations.

So a primary goal of the Urban Ring needs to be to out-compete the downtown transfer stations for some significant portion of total system transfer load, hence freeing up capacity in the downtown transfer stations.

As an example, a rider needs to see it as logical to go from Northeastern to Harvard by way of the Urban Ring rather than via Park or Downtown Crossing downtown transfers.
Therefore, I think the #1 goal of an Urban Ring is for circumferential trips to be faster than, or at least equally as fast as, trips that use a downtown transfer.

What about the other objectives?

Two of the most commonly considered objectives are:
  • #2: Enhance connectivity to key nodes outside of downtown core (employment centers, recreational centers, etc)
  • #3: Fill (mostly residential) transit deserts between existing lines
My opinion: Both of them should take lower priority than #1 when in direct conflict; However, they feed into #1 by virtue of being part of what makes a trip faster, especially #2. This is primarily due to the difference between two-seat rides (2SRs) and three-seat rides (3SRs).

Suppose I live in Malden and work at Harvard, but the Urban Ring route goes from Sullivan to Central. My choices are:
  • (a) Malden - DTX - Harvard
  • (b) Malden - Sullivan - Central - Harvard
Even though (b) covers a shorter geographical distance, it requires an additional transfer. This can already discourage some riders prioritizing comfort from using it, but more tangibly, it incurs a time penalty due to transfers (going through transfer walkways and waiting for a train).

A possible solution is: Make the Urban Ring go directly to Harvard! Now (b) becomes just a 2SR (Malden - Sullivan - Harvard), while still having a shorter distance. As long as the Urban Ring travels fast enough and is not too roundabout -- which itself is not a guarantee -- I will almost always choose (b). This frees up space at Downtown Crossing for other riders working downtown.

The problem is, Harvard is not the only job destination. Suppose my two roommates Mary and Tom both work in Kendall. (Commuters to Kendall are similar in number to (Central+Harvard) combined, and twice as much as each of them individually.) Now their choices are:
  • (c) Malden - DTX - Kendall
  • (d) Malden - Sullivan - Harvard - Kendall
(d) obviously loses: it covers a longer distance, meaning it would still have been slower even if transfers were instant. This is a problem that I call "backtracking". A similar problem exists on the residential end: even if the Urban Ring went to Malden, now my friend Bob who drives to Wellington needs to backtrack, and for my friend Christina who lives in Melrose, in a future with OLX to Reading, Urban Ring will not turn her trip from a 3SR into a 2SR.

I propose several high-level principles, many of which are illustrated by this thought exercise above:
  • Connecting an Urban Ring directly to key nodes outside downtown (#2) is a great way to cut down travel time (#1), by turning 3SRs into 2SRs. Not everyone will get these "lucky" 2SRs, so it's best to maximize the number of people that can get them.
    • This also applies to bus hubs. Allowing people to hop from a bus to the ring route directly, avoiding the radial route at all, is very useful.
  • There's value for a ring that's not too far from downtown. Anyone inside the ring will experience backtracking, which significantly degrades the experience, and their effects are much greater than anyone outside the ring. Thus, the "outer branches" need to carry enough ridership before a ring can be placed. (This applies to both origins/neighborhoods and destinations/jobs.)
  • The ring needs to travel fast enough. This can mostly be achieved in two ways: Taking a more direct route between points; and achieving a higher speed, by having fewer stations, grade separation, etc.
  • The ring needs to have convenient transfers to radial routes. Inconvenient ones will increase travel time and passenger experience; or worse, intersecting a radial route without a transfer station completely undermines the ring's functionality.
  • In some cases, the ring itself can serve as a demand generator for future TOD. (Here's an example from Madrid.) However, how much this applies to Boston (and US cities in general) is another question.
In fact, several successful ring routes serve CBDs, and can often be a pseudo-radial line for these key nodes: Seoul's Line 2 (another explanation), Beijing's Line 10, Singapore's Circle Line, and Tokyo's legendary Yamanote Line.

However, these principles then introduce several tradeoffs:
  • Ring radius: Do you place your ring closer to downtown to hit key nodes, gather higher ridership on outer branches, and reduce cost? Or do you place your ring further away from downtown, for greater distance savings (and possibly higher TOD potential)?
    • When two radial lines form an acute angle, the bigger your circle is, the shorter the distance. However, this also makes more people need to backtrack.
  • Route choice: Do you take a more roundabout route to hit a key node X? Or do you take a straighter route that bypasses them, to help other passengers traveling on the same quadrant but not to X?
    • I often call this "to-X" vs. "through-X". The answer depends on the comparative demand for these two patterns, which in turns is depends on prominence of X itself.
    • This also manifests in where you place the station in X: a central location or a peripheral one?
  • Stop spacing: Do you make more stops in X, to reduce travel times for the to-X crowd to reach the stations? Or do you fly through X with fewer stops, so that other passengers get a faster trip?
    • Again, this often depends on to-X vs. through-X.
  • Target for competition, and "close calls": Sometimes, two radial routes form a ~120° angle, such that a circle can't achieve much distance savings. Does your ring try to cater to this crowd and achieve at least equal travel time, such that at least some riders will take it, freeing up some capacity downtown? Or do you just give them up and let them transfer downtown, in order to serve other riders (between two other radial routes) better?
    • Practical scenarios in Boston: OL North - LMA; OL South and Huntington - Kendall; Nubian - Seaport - Chelsea
  • Perhaps the most important -- Budget: Do you go for an expensive build with a more ideal route and grade separation? Or do you settle for a cheaper route with drawbacks, so that you at least have something to ride in your lifetime?
    • This affects all tradeoffs above.
(I largely avoided the question of how "key nodes" should be defined: Employment centers? Recreational centers? Neighborhoods? Right now, I lean towards the first option, but not extremely strongly. I welcome attempts at changing my mind, which include future analyses I plan to do myself to answer this question.)
 
Last edited:
Extended readings on circumferential lines
Here are some articles I found with a quick Google query (lol). I've read some of them, but not all, so I'll read the rest together with you guys.

Blogposts
  1. Moscow: Questioning the Circle Line (from Human Transit blog)
  2. Mixing Circumferential and Radial Transit (from Alon Levy's Pedestrian Observations blog)
  3. Mixing Circumferential and Radial Transit in the Other Direction (also from Alon Levy)
Even though #2 and #3 do not directly address purely circumferential lines, all three posts (and the comments!!!) provide very valuable insights. This particular comment under #1 elegantly explains why connecting to key nodes is important.

Academic papers
On Boston's Urban Ring in particular:
  • "Analyzing the role of circumferential transit in relieving core congestion" (2002): I can't access this paper, but from the abstract, it specifically "explore the role and ability of circumferential transit to relieve core congestion in the central subway system of Boston", but also consider other systems.
  • "Coming Around" (2003): This one does have open access, and is a very detailed paper that discusses MBTA's Urban Ring proposal from that era. But I haven't read the paper in detail to see if they're explaining the T's plans or discussing/proposing their own.

On non-Boston systems in general:
 
Last edited:
I wanted to come back to this thread with a discussion of the Copenhagen Metro and why I think it's extremely relevant to an urban ring service.

Overview
The Copenhagen Metro is a relatively small system. It has 4 lines, with 2 radial lines, 1 loop line, and 1 radial line that runs along part of the loop. (There is also the S-Train network which is cool but I'm going to skip over that for right now.)
1713189269709.png

The network features a combination of underground, elevated, and at-grade stations, although the majority of the system is underground.

The Trains
This is where it starts to get interesting. The Metro uses the Hitachi Rail Italy Driverless Metro system, which means the trains are small, only 128ft long. (For reference, Red Line trains are around 420ft long.) And yet, the M3 of the Copenhagen metro can carry more passengers daily than the Red Line did in 2019. It does this through very high frequencies. M3 and M4 trains come every 2-3 minutes, and so headways on the combined section can be as low as 80-90 seconds during peak times.
1713189571781.png

The Stations
When you use the metro one of the first things you notice is that all the (underground) stations are very similar. They are (almost) all built in a 20m by 60m box, which makes the construction process fairly straightforward. Anywhere you can dig a 20x60m hole you can build a station, which means that you can easily site a station under just about any moderately wide street. They have no fare gates, operating on a proof-of-payment system, and are about as simple as you could build them.
1713189625731.png

The Money
The Copenhagen Metro is fundamentally tied to real-estate development. M1 and M2 stimulated huge new developments on the island of Amager, while the dirt excavated from the M3 tunnels was used to make new land in the harbor to be built upon and developed. M4 is designed to connect these new areas in the north as well as more areas currently under redevelopment in the south. Proceeds from land sales and development is how these projects have been funded.

Why is this relevant?
So why is this related to the Urban Ring? The urban ring is a service designed to make connections with other lines, and be used for many short journeys rather than a few end-to-end journeys. This high turnover rate and high number of journeys involve a connection mean that a system with smaller trains is not a problem, since there is not one busy section where the trains fill up and slowly empty out, and the high frequencies make connections shorter by reducing the amount of time spent waiting. The small stations in a 20x60m hole design makes stations easier as they can be sited under small, relatively narrow strips of land like on the SW corridor next to Ruggles, at Bellingham Sq in Chelsea, or under the Oscar Tugo Circle at LMA. and the funding model is also extremely relevant, as a design like the one I sketched up previously links a huge number of areas with massive sites awaiting development. Wonderland, Bell Circle, the Everett Hellscape™, Sullivan, Community College, the Inner Belt, Lower Allston/West Station, Widett Circle, and Andrew are all stations adjacent to huge sites that are either actively being redeveloped or are open to redevelopment that could be used to (At least partially) fund the project.

Screenshot 2024-04-15 at 16.41.06.png

So how much complexity could the "Small station box" eliminate? Of the stations on my fantasy diagram, only the following could likely not be built using the station box method:
  • MassArt/Wentworth if the extended Huntington Ave subway is built first
  • Harvard
  • Union Sq
  • At-grade would likely be preferred for Community College, Sullivan, and Assembly
  • Charlestown, Admirals Hill (Elevated as part of a Tobin Bridge replacement)
  • Cheslea Creek, a stacked design would likely be required here
All the other stations are located on streets or adjacent to open spaces where a 20x60m space could be excavated.
 
Last edited:
I wanted to come back to this thread with a discussion of the Copenhagen Metro and why I think it's extremely relevant to an urban ring service.

Overview
The Copenhagen Metro is a relatively small system. It has 4 lines, with 2 radial lines, 1 loop line, and 1 radial line that runs along part of the loop. (There is also the S-Train network which is cool but I'm going to skip over that for right now.)
View attachment 49609
The network features a combination of underground, elevated, and at-grade stations, although the majority of the system is underground.

The Trains
This is where it starts to get interesting. The Metro uses the Hitachi Rail Italy Driverless Metro system, which means the trains are small, only 128ft long. (For reference, Red Line trains are around 420ft long.) And yet, the M3 of the Copenhagen metro can carry more passengers daily than the Red Line did in 2019. It does this through very high frequencies. M3 and M4 trains come every 2-3 minutes, and so headways on the combined section can be as low as 80-90 seconds during peak times.
View attachment 49610
The Stations
When you use the metro one of the first things you notice is that all the (underground) stations are very similar. They are (almost) all built in a 20m by 60m box, which makes the construction process fairly straightforward. Anywhere you can dig a 20x60m hole you can build a station, which means that you can easily site a station under just about any moderately wide street. They have no fare gates, operating on a proof-of-payment system, and are about as simple as you could build them.
View attachment 49611
The Money
The Copenhagen Metro is fundamentally tied to real-estate development. M1 and M2 stimulated huge new developments on the island of Amager, while the dirt excavated from the M3 tunnels was used to make new land in the harbor to be built upon and developed. M4 is designed to connect these new areas in the north as well as more areas currently under redevelopment in the south. Proceeds from land sales and development is how these projects have been funded.

Why is this relevant?
So why is this related to the Urban Ring? The urban ring is a service designed to make connections with other lines, and be used for many short journeys rather than a few end-to-end journeys. This high turnover rate and high number of journeys involve a connection mean that a system with smaller trains is not a problem, since there is not one busy section where the trains fill up and slowly empty out, and the high frequencies make connections shorter by reducing the amount of time spent waiting. The small stations in a 20x60m hole design makes stations easier as they can be sited under small, relatively narrow strips of land like on the SW corridor next to Ruggles, at Bellingham Sq in Chelsea, or under the Oscar Tugo Circle at LMA. and the funding model is also extremely relevant, as a design like the one I sketched up previously links a huge number of areas with massive sites awaiting development. Wonderland, Bell Circle, the Everett Hellscape™, Sullivan, Community College, the Inner Belt, Lower Allston/West Station, Widett Circle, and Andrew are all stations adjacent to huge sites that are either actively being redeveloped or are open to redevelopment that could be used to (At least partially) fund the project.

View attachment 49614
So how much complexity could the "Small station box" eliminate? Of the stations on my fantasy diagram, only the following could likely not be built using the station box method:
  • MassArt/Wentworth if the extended Huntington Ave subway is built first
  • Harvard
  • Union Sq
  • At-grade would likely be preferred for Community College, Sullivan, and Assembly
  • Charlestown, Admirals Hill (Elevated as part of a Tobin Bridge replacement)
  • Cheslea Creek, a stacked design would likely be required here
All the other stations are located on streets or adjacent to open spaces where a 20x60m space could be excavated.
One big drawback of the Copenhagen station design is only one elevator per station -- and even there they are frequently out of service.
 
One big drawback of the Copenhagen station design is only one elevator per station -- and even there they are frequently out of service.
I believe this is only true for the older M1/M2 stations, the M3 Cityringen stations generally have 2 parallel elevators at the end of the platform to provide redundancy. Regardless of how common it is, it's definitely possible to have redundant elevators with the Copenhagen station design.
 
I wanted to come back to this thread with a discussion of the Copenhagen Metro and why I think it's extremely relevant to an urban ring service.

Overview
The Copenhagen Metro is a relatively small system. It has 4 lines, with 2 radial lines, 1 loop line, and 1 radial line that runs along part of the loop. (There is also the S-Train network which is cool but I'm going to skip over that for right now.)
View attachment 49609
The network features a combination of underground, elevated, and at-grade stations, although the majority of the system is underground.

The Trains
This is where it starts to get interesting. The Metro uses the Hitachi Rail Italy Driverless Metro system, which means the trains are small, only 128ft long. (For reference, Red Line trains are around 420ft long.) And yet, the M3 of the Copenhagen metro can carry more passengers daily than the Red Line did in 2019. It does this through very high frequencies. M3 and M4 trains come every 2-3 minutes, and so headways on the combined section can be as low as 80-90 seconds during peak times.
View attachment 49610
The Stations
When you use the metro one of the first things you notice is that all the (underground) stations are very similar. They are (almost) all built in a 20m by 60m box, which makes the construction process fairly straightforward. Anywhere you can dig a 20x60m hole you can build a station, which means that you can easily site a station under just about any moderately wide street. They have no fare gates, operating on a proof-of-payment system, and are about as simple as you could build them.
View attachment 49611
The Money
The Copenhagen Metro is fundamentally tied to real-estate development. M1 and M2 stimulated huge new developments on the island of Amager, while the dirt excavated from the M3 tunnels was used to make new land in the harbor to be built upon and developed. M4 is designed to connect these new areas in the north as well as more areas currently under redevelopment in the south. Proceeds from land sales and development is how these projects have been funded.

Why is this relevant?
So why is this related to the Urban Ring? The urban ring is a service designed to make connections with other lines, and be used for many short journeys rather than a few end-to-end journeys. This high turnover rate and high number of journeys involve a connection mean that a system with smaller trains is not a problem, since there is not one busy section where the trains fill up and slowly empty out, and the high frequencies make connections shorter by reducing the amount of time spent waiting. The small stations in a 20x60m hole design makes stations easier as they can be sited under small, relatively narrow strips of land like on the SW corridor next to Ruggles, at Bellingham Sq in Chelsea, or under the Oscar Tugo Circle at LMA. and the funding model is also extremely relevant, as a design like the one I sketched up previously links a huge number of areas with massive sites awaiting development. Wonderland, Bell Circle, the Everett Hellscape™, Sullivan, Community College, the Inner Belt, Lower Allston/West Station, Widett Circle, and Andrew are all stations adjacent to huge sites that are either actively being redeveloped or are open to redevelopment that could be used to (At least partially) fund the project.

View attachment 49614
So how much complexity could the "Small station box" eliminate? Of the stations on my fantasy diagram, only the following could likely not be built using the station box method:
  • MassArt/Wentworth if the extended Huntington Ave subway is built first
  • Harvard
  • Union Sq
  • At-grade would likely be preferred for Community College, Sullivan, and Assembly
  • Charlestown, Admirals Hill (Elevated as part of a Tobin Bridge replacement)
  • Cheslea Creek, a stacked design would likely be required here
All the other stations are located on streets or adjacent to open spaces where a 20x60m space could be excavated.
I figured I'd elaborate on what alternative sites could or likely couldn't also work well with the "small box" design:
  • Kenmore is probably a no due to the GL tunnels
  • A combined Fenway/St Marys could work. The walk to the latter would be a bit on the longer side but not too bad.
  • BU could work quite well, Comm Ave is wide enough that you could potentially not even need to touch the B branch tracks
  • The Grand Junction could work fairly well. A Waverly St stop could be at grade, Pacific St appears to have just enough room, Mass Ave has a big parking lot, Gallileo Gallilei has the GJ park and is also just really wide by itself, and there's a wide open space behind Memorial Way if a station is desired there. (This then gets into the Harvard vs Kendall debate but that can be saved for another time.)
  • Seaport could get difficult with all the tunnels already there, but you might be able to find a big enough space.
  • The Chelsea Greenway/SL3 busway is generally wide enough, although the location isn't optimal.
  • The only place you could make this method work at Logan appears to be where the Terminal E parking is currently, but that's not very central. Better than the current BL stop though.
  • There is no shortage of space at Newmarket
  • Maybe you could get something under 93 at JFK/UMass? Failing that you could dig up part of the busway
 
I believe this is only true for the older M1/M2 stations, the M3 Cityringen stations generally have 2 parallel elevators at the end of the platform to provide redundancy. Regardless of how common it is, it's definitely possible to have redundant elevators with the Copenhagen station design.
Agreed. More just pointing out that you can get too simple in the station design. There is a limit to how cheap you can go and still maintain functionality. But even a redundant elevator version is still a very efficient design (which we would find some way to muck up, I am sure).

The problem with a standardized design is it take out a lot of the opportunity for Project Consultants managing the Design Consultants, managing the Construction Consultants to pad their bills.
 

Back
Top