Tag Archives: Toronto

WMATA Infill Stations: Oklahoma Ave and River Terrace

Because of the challenges in adding underground infill stations, most candidates are going to be at grade or above ground. Almost by definition, that means fewer opportunities for infill stations around the core of the system, and therefore within Washington’s city limits.

The existing system features a huge gap as the Orange/Blue/Silver lines cross the Anacostia River. The east of the river stations (Minnesota Ave and Benning Road) are both two miles from Stadium-Armory.

Filling this gap is not a new idea – early WMATA plans called for stations at both locations. Oklahoma Ave was on the books long enough for renderings to be drawn up.

WMATA Adopted Regional System, 1968

WMATA originally considered the area next to the Benning Road Power Plant for a rail yard (the “S&I” oval on the map above, for service and inspection). The adjacent Kenilworth Ave station eventually moved east and became Minnesota Ave.

These two sites are unique in that they do not parallel any existing railroad services, where future regional rail might offer faster, longer-distance service, allowing Metro to focus on shorter distance travel markets. Part of the argument for more infill stations, particularly in the suburbs, is the promise of regional rail. However, these two locations do not need that promise to fulfill their roles – they offer compelling visions on their own.

Oklahoma Ave

Metro planners envisioned Oklahoma Ave as a park and ride station, taking advantage of the extensive surface parking for nearby RFK Stadium on non-event days. The nearby Kingman Park community vociferously opposed a parking-focused station, and WMATA eventually dropped the station in 1977.

1970 Rendering of elevated Oklahoma Ave. Station

Adding an infill station at Oklahoma Ave would likely follow the same concept from the 70s: two side platforms along the existing elevated guideway.

Connections: Potential transit connections from Oklahoma Ave are relatively weak. Almost all transit is located just north along Benning Road, including the DC Streetcar as well as extensive bus service. It wouldn’t be difficult to extend those lines to connect with the station, but the expense (and ongoing time penalty for bus riders) for doing so would depend on the broader plan – if Oklahoma Ave were built together with a River Terrace station, the latter could offer superior transit connections.

Land use: This is another challenge for the area. The immediate surroundings are the northern parking lots for now-vacant RFK Stadium. A large portion of those parking lots are now athletic fields. The parking lots were originally created by filling in the Anacostia’s tidal marshes. As a result, the entire area is within the floodplain, and unlikely to ever be developed as housing or office.

Redevelopment of the remainder of the RFK site outside of the floodplain is a contentious topic with complicated jurisdictional issues yet to be resolved. If the site were to return to a stadium/venue use, the ability to disperse crowds to multiple Metro stations would be a potential advantage.

Without an intense use at RFK, the rationale for Oklahoma Ave is less clear, particularly if River Terrace were built. However, if RFK Stadium were to be redeveloped as some sort of venue with large crowds, then the case for Oklahoma Ave is much stronger.

Ease of Construction: The biggest benefit at Oklahoma Ave is that construction ought to be easy – existing elevated track in the middle of a parking lot. The potential complications would involve any operational changes to the existing line, and determining any role for this location in future Metro expansion plans.

River Terrace

An infill station at River Terrace presents a tantalizing opportunity. The existing tracks are located at a key chokepoint and river crossing, served by one of the busiest bus lines in the city. The existing neighborhood to the south of Benning Road is isolated, separated from the rest of the city by the river to the west, DC-295 and the railroad tracks to the east, and the former Pepco site to the north.

Connections: Benning Road serves as a critical choke point for transit service, making it a great candidate for improved infrastructure. Lots of bus services cross the river here; the nearest crossing to the north (US-50) is along a freeway, and to the south (East Capitol Street) lacks good service. The DC streetcar terminates just to the west, with longstanding plans to extend it along this stretch of Benning Road.

In the future, the H/Benning corridor has long been targeted for Metrorail service. One of the longstanding concepts would be the “separated Blue line,” a new trunk line through the District to separate out existing Blue Line services from Orange and Silver services. Such a vision ought to include River Terrace as a four-track station enabling cross-platform transfers.

WMATA is currently in the midst of their ‘Blue/Orange/Silver’ study. The concepts released in 2021 did not include a new connection at River Terrace. These larger network designs will impact the kind of infill station design for River Terrace.

DC’s once-ambitious streetcar plans have been substantially curtailed. However, the one extension still officially on the books (though controversially) is the Benning Road extension, passing through the River Terrace site. One rationale for the extension is to connect the eastern end of the streetcar line to something, preferably a Metro station. However, because of the D&G junction, splitting Metro service along the Orange Line and Blue/Silver lines, connecting at Benning Road means losing the value of connections for Orange Line passengers.

Benning Road Streetcar Extension Plan – adding a Metro connection at River Terrace (34th St NE) improves connectivity for all users.

Land Use: Immediately adjacent to the station site is Pepco’s now-demolished Benning Road Power Plant site. The plant was demolished in 2012, and in later years was only used during peak periods of demand for a few days per year.

The plant was once the source of a huge amount of pollution, particularly in the Anacostia riverbed. Large-scale remediation and clean-up will be needed before redevelopment is feasible. Additionally, the site retains electrical distribution infrastructure and support for Pepco operations.

Despite all the challenges, it’s a 70+ acre site in the middle of the city with (potentially) excellent transit connections.

Ease of Construction: Compared to Oklahoma Ave, just adding platforms to the existing elevated section would be extremely complicated.

First, this section of track includes the notoriously unreliable D-route pocket track. The pocket track was originally slated to turn terminating Silver Line trains, but WMATA determined it was not suitable to serve that purpose reliably, and investigated alternative designs.

Second, the location of the pocket track (the straightest section) extends over the Anacostia River. Furthermore, the track itself is immediately adjacent to the Benning Road right of way, requiring some combination of road and bridge relocation or a station cantilevered over Benning Road.

Any design with side platforms ought to consider the possibility of a new Blue Line connecting through this location. The ideal design would allow for a future cross-platform transfer between the existing tracks and future Blue line services.

Third, Benning Road itself provides an opportunity for a creative and efficient passenger transfer from Metro to buses and streetcars. Doing so will involve extensive reconstruction in the area, meaning this won’t be a simple infill station – but the opportunity is too large to pass up.

There are lots of examples of efficient transfers between streetcars and rapid transit. Toronto is full of them, such as this one at Dundas West.

St. Clair West is another, featuring a fully-integrated streetcar and bus transfer loop built around (not just next to) the entrances to and from the subway. Passengers can transfer easily while protected from the elements and with minimal walking distance.

(side notes: Dundas West includes a small McDonalds, hitting on another minor obsession of mind, in-station retail. Also, do check out the excellent Station Fixation blog for a full visual tour of the entire Toronto system)

At River Terrace, this might involve diverting the streetcar tracks off of Benning Road itself to encircle a ground-level mezzanine for the Metro station, offering quick and direct transfers for passengers moving between modes.

Don’t rule out elevated rail in cities

Toronto is looking to Honolulu for transit inspiration – looking to tap into the potential for elevated rapid transit to improve the city’s transit expansion plans. However, key city officials are extremely concerned about the impacts of elevated transit to the city. Skepticism is good, any may be required to ensure that elevated rail is successfully integrated into an urban environment, but it shouldn’t be an automatic disqualifier for the kinds of improvements that make rapid transit possible. From the Toronto Star:

Toronto chief planner Jennifer Keesmaat cites the shadow that a structure like the [elevated Gardiner expressway] casts on the street below. She also brandishes one of the chief arguments for building Toronto’s LRTs in the first place.

“From a land use planning perspective, if our objective in integrating higher order transit into our city is to create great places for walking, for commerce, living,… elevated infrastructure doesn’t work so well for any of those objectives,” she said.

It’s true that making elevated rail work in urban areas is a challenge, but it shouldn’t be so easily dismissed. Of particular concern is the willingness to equate the visual impact of the six-lane Gardiner Expressway with a potential two-track elevated rail structure. The other key concern is the equivocation of grade-separated transit with at-grade light rail.

Toronto seems full of transit terminology confusion these days. Embattled Mayor Rob Ford has been pushing for subways as the only kind of transit that matters (SUBWAYS SUBWAYS SUBWAYS!) regardless of context or cost. Meanwhile, the transit agency is looking to implement a ‘light rail’ project that features full grade separation and an exclusive right of way – in other words, a subway. Ford opposes the light rail plan in favor of an actual, tunneled line with fewer stations and higher cost. Much of the rhetoric seems focused on equating light rail with Toronto’s legacy mixed-traffic streetcar network.

However, just as Ford’s dogmatic insistence of subways at any cost is irresponsible, Keesmaat’s suggestion that at-grade LRT can accomplish the same transit outcomes as grade-separated LRT can is equally misleading. Remember the differences between Class/Category A, B, and C right of way (from Vukan Vuchic, summarized here by Jarrett Walker), paraphrased here:

  • Category C – on-street in mixed traffic: buses, streetcars, trams, all operating in the same space as other street users.
  • Category B – partially separated tracks/lanes: exclusive right of way for transit, but not separate from cross-traffic. Vuchic dubs this “Semirapid Transit.” often seen with busways or light rail.
  • Category A – right of way exclusive to transit, separated from all cross traffic: This is required for rapid transit. Examples include subways/metro systems and some grade-separated busways.

Transit system types by class of right-of-way.

Transit system types by class of right-of-way. X-axis is system performance (speed, capacity, and reliability), Y-axis is the investment required.

The distinction matters because the quality of the transit service is substantially different. Service in Class A right of way will be faster and more reliable than Class B, at-grade LRT. Part of the planning challenge is matching the right level of investment (and ROW category) to the goals for the system. However, even with the need to balance transit goals with those for urban design, planners like Keesmaat shouldn’t categorically dismiss the possibility of building Class A transit facilities.

Part of the confusion might be from the technology. A catenary-powered rail vehicle can operate in Class A, B, or C right of way, and fill the role of streetcar, light rail, or metro – all with little change in technology. Consider San Francisco, where Muni trains operate in all three categories – in mixed traffic, in exclusive lanes, and in a full subway. The virtue of light rail technology is flexibility, but that flexibility can also confuse discussions about the kind of transit system we’re talking about. The vehicle technology isn’t as important as the kind of right-of-way. Indeed, many of the streetcar systems that survived the rise of buses precisely because they operated in Class A and B rights-of-way.

Keesmaat certainly appreciates the difference between the kind of regional rapid transit you’ll see in Honolulu and at-grade LRT:

“The Honolulu transit corridor project is really about connecting the city with the county…. It’s about connecting two urban areas. That’s very different from the context we imagine along Eglinton where we would like to see a significant amount of intensification along the corridor,” said Keesmaat.

At the same time, the kind of transit she’s describing and the kind of land use intensity aren’t mutually exclusive at all – quite the opposite.

densitytable2withcap

Subways are nice, but require a high level of density/land use intensity. Payton Chung put it succinctly: “no subways for you, rowhouse neighborhoods.” Payton cites Erick Guerra and Robert Cervero’s research on the cost/benefit break points for land use density around transit lines. This table to the right shows the kind of density needed to make transit cost-effective at various per-mile costs.

The door swings both ways. Rowhouse densities might not justify subways, but they could justify the same Class A transit if it were built at elevated rail construction costs. Finding ways to lower the high US construction costs would be one thing, but given the systemic increase of US construction costs, using elevated transit would be a good way to extend Class A rights-of-way to areas with less density.

Instead of categorically dismissing elevated rail, work to better integrate it into the urban environment. Consider the potential for the mode to transform suburban areas ripe for redevelopment. Wide rights-of-way along suburban arterials are readily available for elevated rail; redevelopment can not only turn these places into walkable station areas, but also help integrate elevated rail infrastructure into the new built environment.

Keesmaat’s concerns about elevated rail in Toronto stem from the impact on the street:

“The Catch22 with elevating any kind of infrastructure – a really good example of this is the subway in Chicago – not only is it ugly, it creates really dark spaces,” she said.

It’s not just the shadow but the noise of elevated transit lines that can be problematic, said TTC CEO Andy Byford. If you build above the street you’ve also got to contend with getting people there, that means elevators or escalators.

First, it’s not clear what Byford is talking about: accessing subway stations also requires elevators and escalators. The nature of grade separated rights-of-way is that they are separated from the grade of the street.

Keesmaat’s concerns about replicating Chicago’s century-old Els are likely misplaced. No one is building that kind of structure anymore – and a quick survey of newer elevated rail shows slimmer, less intrusive structures. Reducing the visual impact and integrating the transit into the cityscape is the real challenge, but the price advantage and the benefits of Class A right-of-way cannot be ignored. It’s not a surprise that the Star paraphrases UBC professor Larry Frank: “On balance… elevated transit should probably be considered more often.”

Fearing ‘hyperdensity’ in urban areas

Aerial view of Toronto. CC image from rene_beignet.

Aerial view of Toronto. CC image from rene_beignet.

One of the books I picked up through the rounds of exchanging holiday gifts is Vishaan Chakrabarti’s A Country of Cities: A Manifesto for an Urban America. I’ve read an excerpt of the book published in Design Observer and watched Chakrabarti’s accompanying lecture; I’m looking forward to reading the full book.

In my initial reaction to the book’s excerpt embraced the praise for dense, urban, transit-supportive cities, but expressed concern about the political and regulatory hurdles to achieving such a vision. In particular, the ‘hyperdensity’ terminology Chakrabarti used to describe levels of density that can support subway transit seemed like it could directly antagonize citizens skeptical of change – citizens that currently hold the upper hand in many of the procedural and regulatory battles over new development.

Consider some of the reactions in Toronto. This op-ed from Marcus Gee in the Globe and Mail echoes Chakrabarti’s praise for urban density, but also shows the risk of the ‘hyperdensity’ terminology:

A spectre is haunting Toronto – the spectre of hyperdensity. Jennifer Keesmaat, the city’s dynamic chief planner, worries about it. So does one of Toronto’s smartest local politicians, city councillor Adam Vaughan…

[T]he city’s Official Plan seeks to direct new development – office buildings, condo towers and so on – to key areas of the city, fostering the process known in planners’ jargon as intensification. The aim is to put new buildings on about a quarter of the city’s geographical area, keeping the three-quarters that is left – residential neighbourhoods, quiet, smaller streets – free from runaway growth.

As anyone can see from the thickets of development around nodes like Union Station or Yonge and Eglinton, it has been remarkably successful – too successful for some. “We have reached this exciting and terrifying tipping point where we are starting to question whether it could be there is something called too much density,” Ms. Keesmaat said. “There are some areas of the city where we are seeing too much density – hyperdensity – and there are other areas of the city where we are seeing no growth at all.”

Here, the warnings about hyperdensity echo San Francisco’s concerns about “Manhattanization” – long-standing skepticism about growth and urban development with serious impacts on the city and region’s affordability over the past decade plus.

It would seem that Toronto’s plan is working exactly as intended: growth is channeled to some areas while it isn’t allowed to happen in others. Seeing little to no growth in areas of the city planned for little or no growth would all be according to plan.

This isn’t to say that the plan is wise. Trying to focus all growth in a city with high demand into downtown and a handful of mid-rise corridors might be too much of a constraint. It’s a strategy tailor-made to minimize conflict with the single-family neighborhoods, not dissimilar from Arlington County’s focus on Metro station areas while preserving single family homes nearby. It’s also one that bears a great deal of similarity to DC’s current discussions about how, how high, and where to grow. As Payton Chung notes, even this modest bargain is no guarantee to avoid conflict:

Among large North American cities, only Toronto has joined DC in making a concerted effort to redirect growth into mid-rise buildings along streetcar lines — and only as an adjunct strategy in addition to hundreds of high-rises under construction. (The two metro regions are of surprisingly similar population today.) Yet there, just like around here, neighborhoods are up in arms at the very notion.

Nor does it guarantee the city can actually match supply to demand:

DC cannot put a lid on development everywhere — downtown, in the rowhouse neighborhoods, in the single-family neighborhoods, on the few infill sites we have left — and yet somehow also accommodate enough new jobs and residents to make our city reliably solvent, much less sustainable. The sum of remaining developable land in the city amounts to 4.9% of the city, which as OP demonstrates through its analysis, cannot accommodate projected growth under existing mandates.

Something will have to give.

Toronto’s plan took the lid off in downtown, yet now the resulting development is derided as ‘hyperdensity.’ Marcus Gee notes that hyperdensity’s impact on infrastructure also provides the means to upgrade those facilities; build more transit; expand parks and urban amenities:

If the hyperdensity tag catches on, it could become a useful tool for downtown councillors who want to appease their constituents by blocking new development or for suburban councillors who want to steer more development to their wards even if there is no call for it there. It could also help kill exciting projects like the Frank Gehry-designed proposal by David Mirvish for King Street West. Ms. Keesmaat’s planning staff oppose the plan for three towers of more than 80 storeys each – too tall, too dense – and city council backed her up in a vote on Dec. 18.

It is reasonable to worry that new development will cause overcrowding on transit or overtax other city infrastructure. But if that is the concern, let’s build better transit to keep up with the growth, not halt the growth for fear of the future. Central Toronto is still far less dense than it could or should be. Hyperdensity should be a goal, not a thing to fear.

Emphasis added. This is the crux of my concern. How we frame the issue matters, even if the eventual solution won’t be about convincing the public of the virtues of hyperdensity and embracing it as a goal. Rather, achieving that goal will require reforming the processes and procedures for making decisions about land use and development.

I hope Chakrabarti’s book will touch on this; I look forward to reading it.