Starting today and running until the end of March, the City of Toronto, the Toronto Transit Commission, and Metrolinx will be hosting several public meetings as they work towards planning out this city and region’s rapid transit network.
Below are a few of the key maps from their presentation.
Here is what Toronto’s rapid transit network looks like today (the hollow lines represent projects in construction):

Here is what will be built within the next 6 years:

And here is what they are recommending should be built within the next 15 years:

It’s hard not to get excited when you see maps like this. Of course, it’s a lot easier to draw lines on a map then it is to fund and execute on projects like this.
But I think it all starts with us acknowledging that these initiatives are critical to both our economic competitiveness as a city region and our quality of life as citizens of it. Because if this is something we really want, then we can absolutely make it happen.
Click here if you’d like to see the full presentation and also the public meeting dates/times.
At the beginning of this year I wrote a post about a mobile tracking app called Moves that I had heard about through my friend Sachin Monga. He had just published a beautiful set maps showing where he physically spent his time in both Toronto and San Francisco.
His post spurred me to download the app and at the end of my post I promised to share my own set of maps once I had collected enough data points. It’s only been about 3 weeks, but already my maps are starting to fill out, so I thought I would do a release.
The orange lines represent transport of some sort (car, subway, streetcar, and so on) and the green lines represent walking. I don’t cycle very often in the winter (I know, I’m a fair-weather cyclist), so you won’t see any of those lines just yet. However if I posted a map from the summer, I know it would look completely different.
Here’s a first one showing a regional scale:
Here’s a second one showing the city of Toronto:
And here’s a third one showing mostly downtown:
What’s interesting about these maps is how much you can tell about me and the way I move around the city.
For one, there’s a good chance I ski or snowboard given that I’m driving up to Collingwood, Ontario in the winter. You can also see how heavily dependent I am on the Yonge subway line, which is the thickest orange line in the middle of downtown. It’s also interesting to see how localized I am within my neighborhood (St. Lawrence Market). I walk to get groceries. I walk to the gym. I walk to coffee. And the list goes on.
This is fairly typical for people living in urban neighborhoods, but it would be interesting to see where it applies in the city and where it begins to fall apart. I would also imagine that there’s a correlation to the area’s Walk Score, although this (Moves) might actually be a better measure since it’s usage data.
Either way, imagine what cities could do if they had this sort of data for every resident. They would be able to see precise resident flows and then determine exactly where transit and infrastructure investments should be made instead of politicking to determine where they should be made.
That time is coming.
Starting today and running until the end of March, the City of Toronto, the Toronto Transit Commission, and Metrolinx will be hosting several public meetings as they work towards planning out this city and region’s rapid transit network.
Below are a few of the key maps from their presentation.
Here is what Toronto’s rapid transit network looks like today (the hollow lines represent projects in construction):

Here is what will be built within the next 6 years:

And here is what they are recommending should be built within the next 15 years:

It’s hard not to get excited when you see maps like this. Of course, it’s a lot easier to draw lines on a map then it is to fund and execute on projects like this.
But I think it all starts with us acknowledging that these initiatives are critical to both our economic competitiveness as a city region and our quality of life as citizens of it. Because if this is something we really want, then we can absolutely make it happen.
Click here if you’d like to see the full presentation and also the public meeting dates/times.
At the beginning of this year I wrote a post about a mobile tracking app called Moves that I had heard about through my friend Sachin Monga. He had just published a beautiful set maps showing where he physically spent his time in both Toronto and San Francisco.
His post spurred me to download the app and at the end of my post I promised to share my own set of maps once I had collected enough data points. It’s only been about 3 weeks, but already my maps are starting to fill out, so I thought I would do a release.
The orange lines represent transport of some sort (car, subway, streetcar, and so on) and the green lines represent walking. I don’t cycle very often in the winter (I know, I’m a fair-weather cyclist), so you won’t see any of those lines just yet. However if I posted a map from the summer, I know it would look completely different.
Here’s a first one showing a regional scale:
Here’s a second one showing the city of Toronto:
And here’s a third one showing mostly downtown:
What’s interesting about these maps is how much you can tell about me and the way I move around the city.
For one, there’s a good chance I ski or snowboard given that I’m driving up to Collingwood, Ontario in the winter. You can also see how heavily dependent I am on the Yonge subway line, which is the thickest orange line in the middle of downtown. It’s also interesting to see how localized I am within my neighborhood (St. Lawrence Market). I walk to get groceries. I walk to the gym. I walk to coffee. And the list goes on.
This is fairly typical for people living in urban neighborhoods, but it would be interesting to see where it applies in the city and where it begins to fall apart. I would also imagine that there’s a correlation to the area’s Walk Score, although this (Moves) might actually be a better measure since it’s usage data.
Either way, imagine what cities could do if they had this sort of data for every resident. They would be able to see precise resident flows and then determine exactly where transit and infrastructure investments should be made instead of politicking to determine where they should be made.
That time is coming.
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?
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?
Share Dialog
Share Dialog
Share Dialog
Share Dialog
Share Dialog
Share Dialog