Detroit has started testing its new streetcars on Woodward Avenue. Quicken Loans bought the naming rights to the line, so it’s now officially called the QLINE. If you’re British, this name probably won’t instil feelings of rapidity.
Here’s a recent tweet from M1-Rail (click here if it doesn’t show up below):
The #QLINE is back on the road for testing today! Take a pic and tag @M1RAIL if you see the streetcar. #WeMoveDetroit pic.twitter.com/K42aHxebgG
— M-1 RAIL (@M1RAIL)
//platform.twitter.com/widgets.js
Note how the train is running curbside.
There’s lots of debate about the economic benefits of streetcar/LRT over other transit solutions such as BRT. But if you’re a regular reader of this blog, you’ll probably know that I am a supporter of light rail.
In the case of Detroit, I also think there’s symbolic importance to bringing back light rail to the core of the city. The last Detroit streetcar was shut down in 1956.
It’s also worth mentioning how the streetcar line was funded. Below is a breakdown of funding sources dated 2014.
There may have been some changes since then, but it’s positive to see the public and private sectors come together, alongside a large infusion of philanthropic money (The Kresge Foundation).
Many of the companies on the above list sponsored individual stations. The cost to do so was $3 million, which is why you see that number show up a few times. Compuware and JP Morgan Chase shared a station at $1.5 million each.
Is this a transit funding model worth replicating?
Blitz by Tristan O'Tierney on 500px
Back in 2011, the The Pembina Institute published a report called, Building transit where we need it. And in it they quite clearly outlined the population densities that are needed to make various types of transit investment cost effective.
For subway they specify a minimum population density of 115 people per hectare and for light rail (LRT) they specify a minimum population density of 70 people per hectare.
And the reason for this is because there’s a strong correlation between population density (i.e. land use) and transit ridership. The two go hand in hand and should not be decoupled. If population densities are too low (as they are, for example, along the Sheppard subway line here in Toronto), people don’t take transit. They drive.
Here’s a chart from the report showing the current and projected population densities for Toronto’s existing and proposed routes (keep in mind this is from 2011).
So what does this chart tell us?
Subways don’t make a lot of sense in many parts of the city. LRT will do just fine.
The Sheppard subway line is an under-utilized asset. Even by 2031 we’ll barely be reaching the requisite population densities.
The Bloor-Danforth corridor could use more intensification.
The Yonge-University-Spadina line is going to need to relief.
Unfortunately, transit decisions are often made based on politics instead of data. And that results in subways in places that don’t make a lot of sense. That’s unfortunate because it means less riders, less revenue, and more subsidies.
The other challenge with running subways through low density neighborhoods is that it then creates tension when the city and developers go to intensify those neighborhoods through transit-oriented development. (See #DensityCreep.)
But if we’re going to be fiscally irresponsible about where we deploy our transit capital, the least we could do is upzone the surrounding areas and impose minimum population densities.
In fact, here’s what I think we should do: Land use should be bundled with the transit decision.
Instead of asking where the subway station should go, we should be asking where the subway station should go and all the density needed to bring the area up to a certain minimum population density. And if that second criteria for whatever reason can’t be met, then we don’t build the line.
I wonder if we framed the question in this way if it would change where subway lines get approved. What do you think?
If you live in Toronto and only give serious thought to one thing today, it should be to this interactive transit map created by Metro.
The map shows all existing, planned, and proposed transit lines in the city, and then overlays population densities, commuting patterns, household income, and so on. It’s a super valuable map that I think reveals a lot about how we should be focusing our energies to get Toronto moving.
So what sorts of things does it tell us? I’ll give 2 examples.
If you look at commuting patterns across the Bloor-Danforth subway line, you’ll see that Runnymede station in the west is where people switch over from taking transit to driving. People west of that station tend to drive. Naturally, it also happens to coincide with where population densities start to fall off.
By contrast, if you look at the east side of the city along the Danforth and beyond, the entire stretch more or less relies on transit to get around. Part of this likely has to do with income levels, but it’s also because of the availability of the Gardiner Expressway. There’s no equivalent in the east end. Dylan Reid of Spacing Magazine believes this makes a case for some sort of road pricing along the Gardiner, and I would agree.
As a second example, look at the population densities along the proposed Downtown Relief Line, Finch LRT, and John Tory’s SmartTrack line. Outside of the core, the population densities are relatively low along the proposed SmartTrack line – which is never a good thing for rapid transit.
There’s also no Sherbourne station on the SmartTrack line, which happens to have the highest population density across the entire Relief Line – 22,131 people per square kilometre! That’s more than any other stop along the Yonge-University subway line except for Wellesley station.
I’ve written about this a lot before, but I think we need to do a better job of matching up transit investment with expected customer demand. Too often we let politics get in the way of rationale decision making. Maybe it’s time we did something like set minimum population densities. If you want a subway line in your area, you have to first bring the people.
What else does this map tell you?