News   GLOBAL  |  Apr 02, 2020
 10K     0 
News   GLOBAL  |  Apr 01, 2020
 42K     0 
News   GLOBAL  |  Apr 01, 2020
 5.9K     0 

I think this examples misses the fact that this is not how New Yorkers interact with the subway system. A subway station here isn’t thought of as a destination but as a point on a network—like an intersection on the road network. Stations don’t really have names in the same way they do in Canadian systems; the “name,” such as it is, is merely a description of where the station is. You’d never get confused about which 125th street station to go to because you’d be thinking of it in the context of the line you were on. Just as it wouldn’t be confusing to, say, direct someone to take the 501 streetcar to Yonge, it isn’t confusing to tell someone to take the A train to 125th street.

I’d much prefer we followed a similar approach in Toronto vs coming up with unique “destination” station names every time a potential conflict arises. If I’m travelling along Eglinton and I come to a Bathurst Station there should be no confusion—I’m at Bathurst and Eglinton.
Bathurst and Eglinton? You're at the Forest Hill Station. Named after the Village of Forest Hill. The former Reeve of Forest Hill from 1938 to 49, was Frederick Goldwin Gardiner (who became the first chairman of Metropolitan Toronto, from 1953 to 1961). They named an expressway after him.

1746363574728.png
 
I'm really not a fan of the idea of using neighbourhood or historical names to differentiate between stations. I agree with the approach outlined by @IsaacKhouzam that thinking of station names like surface route stop names would be the most ideal approach. There is nothing special about RT lines that means that their passengers would somehow not be able to understand multiple Yonge stations, but on bus and streetcar routes it's fine. At most I'd be OK with every station being in the style of Bloor-Yonge, Sheppard-Yonge, though I don't think of it is a priority. But artificially creating unique station names by dredging up the names of obscure neighbourhoods or historical settlements is something I find incredibly offputting.
 
I'm really not a fan of the idea of using neighbourhood or historical names to differentiate between stations. I agree with the approach outlined by @IsaacKhouzam that thinking of station names like surface route stop names would be the most ideal approach. There is nothing special about RT lines that means that their passengers would somehow not be able to understand multiple Yonge stations, but on bus and streetcar routes it's fine. At most I'd be OK with every station being in the style of Bloor-Yonge, Sheppard-Yonge, though I don't think of it is a priority. But artificially creating unique station names by dredging up the names of obscure neighbourhoods or historical settlements is something I find incredibly offputting.
The St. Andrew's and St. Patrick's wards in Toronto were named after their respective patron saints, reflecting the city's diverse religious and ethnic background. St. Andrew's was named for the patron saint of Scotland, and St. Patrick's for the patron saint of Ireland. So they named the stations on the University section of Line 1 after ancient city wards.

The actual named churches...
1746367466426.png
1746367500445.png
 
Is the plan to wait until there's a firm opening date to formally announce the name change from Eglinton West to Cedarvale on Line 1? For how much signage they've installed early in preparation for Line 5 (bus stops, wayfinding in stations, etc.) it feels like there should've been more noise about this by now.
 
But artificially creating unique station names by dredging up the names of obscure neighbourhoods or historical settlements is something I find incredibly offputting.
I agree that place names should not be aritificially contrived - but there is lot of room for grey here. Transit place names should have relevance to the districts, communities (and their heritage) of the city and not simply be a technocratic grid... otherwise, we might as well just give them gps or map coordinates.

Certainly, past communities that had "official" municipal status deserve recognition and can be meaningful - Mount Dennis, Fairbank, Forest Hill, Swansea, Leaside, Weston, were actual municipalities with councils and post offices and fire brigades. There is value in keeping that heritage alive, and integrating transit names with community is good for the promotion of the city generally. Other points that had distinct identity or longterm use as a landmark (Cedarvale, Donlands, Six Points, Thistletown come to mind) may also merit retention. This will be subjective, as not everybody remembers or knows every bit of city history or was present when that name was used for a place. (Sometimes, where a place or a bit of history has crept into the naming of roads, there's a convenient convergence.)

We need to show much more respect for the original indigenous place names, as well. Transit should not exclude itself from this.

(My grandparents used to refer to a particular place as "The Village" because when they built their house in the 1930s, it was indeed a village with the surrounding area being countryside. Everyone in my family still uses that term, whereas most current day Torontonians would offer a blank stare if it were used. How many people know why we have Downsview? Runnymede? Scarlett Heights?....aviators will likely still think of Humber Bay as "Whiskey Point", because there was once a collection of large buildings forming a distillery that were used as a visual reference for one of the Pearson flight paths )

Longevity is not the only thing. Science Center has turned out to be unfortunate (well, scandalous, but that's not a transit issue). Hakimi is regrettable, but if someone proposed renaming NYCC as "Rush Commons" or "Lee-Leifson Corners", I would be delighted.

It's subjective, but that's OK.

Kip District remains a trigger. Ugh.

- Paul
 
Last edited:
I'm really not a fan of the idea of using neighbourhood or historical names to differentiate between stations. I agree with the approach outlined by @IsaacKhouzam that thinking of station names like surface route stop names would be the most ideal approach. There is nothing special about RT lines that means that their passengers would somehow not be able to understand multiple Yonge stations, but on bus and streetcar routes it's fine. At most I'd be OK with every station being in the style of Bloor-Yonge, Sheppard-Yonge, though I don't think of it is a priority. But artificially creating unique station names by dredging up the names of obscure neighbourhoods or historical settlements is something I find incredibly offputting.
Idk man, you go on Google Maps and it says "Forest Hill" in big bold letters. In fact, of all neighbourhoods in Toronto, I feel like Forest Hill is one of the more well known neighbourhoods for various reasons.
1746371612995.png


Besides that, naming stations after historic names or neighbourhoods is quite literally what most major metro systems around the world use. Go to any major city, whether its Paris, London, or Moscow, and almost all of the stations are named either after the neighbourhood, a local landmark, and if all else fails the local street.
 
The St. Andrew's and St. Patrick's wards in Toronto were named after their respective patron saints, reflecting the city's diverse religious and ethnic background. St. Andrew's was named for the patron saint of Scotland, and St. Patrick's for the patron saint of Ireland. So they named the stations on the University section of Line 1 after ancient city wards.

The actual named churches...
View attachment 648434View attachment 648435

IMHO, landmark-based station names are good for downtown. Residents of the whole city tend to know the downtown based landmarks and neighbourhoods. St. Andrew and St. Patrick are perfect station names.

But when dealing with stations outside the downtown core, such names are confusing for riders who don't happen to be local residents. If you just want to find # 1234 on Abcde Street, then names based on intersections make for easier wayfinding.
 
dk man, you go on Google Maps and it says "Forest Hill" in big bold letters. In fact, of all neighbourhoods in Toronto, I feel like Forest Hill is one of the more well known neighbourhoods for various reasons.
Forest Hill is one of the better known ones, along with the Annex. But for every such neighbourhood that is well known, there are mountains of neighbourhoods that are obscure, to say nothing of the fact that which area belongs to which neighbourhood appears to be highly flexible and subject to interpretation.

For example, if we go by Google Maps, Eglinton-Scarlett is situated in an area called Westmount, Islington and Royal York form the boundaries of Royal York Gardens to the north of Eglinton. Islington and Kipling form Richmond Gardens to the north, but this is also overlapped by an area called Willowridge-Martin Grove-Ridgeview, which encapsulates, also, Richmond Gardens and Royal York Gardens. Conversely, Scarlett, Royal York, and Islington, with Eglinton as the north boundary, also belong to Edenbridge-Humber Valley, while the area along Kipling is also known as Princess-Rosethorn and Princess Anne Manor. And many of the neighbourhoods that are shown on Google Maps are contrary to the city of Toronto's official neighbourhood database, too.

Is this really useful to wayfinding? Surely this would cause much more confusion than Eglinton-Islington, Eglinton-Kipling, etc. Neighbourhood names only work when the places are well known, especially if the idea with this is catering to out of towners. If a person shows up at Dundas Station thinking it's going to be Dundas West, well, that sucks, but at some point the idea of personal responsibility has to kick in, especially in the age of apps which can guide you step by step through the entire process of travelling.

Or what about circumstances where two stations are in the same neighbourhood? Mount Dennis station is in Mount Dennis, but so is the future Jane-Eglinton (Eglinton Flats can't be, because it runs afoul of the same trouble that Dundas and Dundas West co-existing do). Every neighbourhood I mentioned in my above paragraphs also encapsulates at least two major concession roads as well. Which one gets priority for the neighbourhood name?

I agree that place names should not be aritificially contrived - but there is lot of room for grey here. Transit place names should have relevance to the districts, communities (and their heritage) of the city and not simply be a technocratic grid... otherwise, we might as well just give them gps or map coordinates.

Certainly, past communities that had "official" municipal status deserve recognition and can be meaningful - Mount Dennis, Fairbank, Forest Hill, Swansea, Leaside, Weston, were actual municipalities with councils and post offices and fire brigades. There is value in keeping that heritage alive, and integrating transit names with community is good for the promotion of the city generally. Other points that had distinct identity or longterm use as a landmark (Cedarvale, Donlands, Six Points, Thistletown come to mind) may also merit retention. This will be subjective, as not everybody remembers or knows every bit of city history or was present when that name was used for a place. (Sometimes, where a place or a bit of history has crept into the naming of roads, there's a convenient convergence.)

We need to show much more respect for the original indigenous place names, as well. Transit should not exclude itself from this.

(My grandparents used to refer to a particular place as "The Village" because when they built their house in the 1930s, it was indeed a village with the surrounding area being countryside. Everyone in my family still uses that term, whereas most current day Torontonians would offer a blank stare if it were used. How many people know why we have Downsview? Runnymede? Scarlett Heights?....aviators will likely still think of Humber Bay as "Whiskey Point", because there was once a collection of large buildings forming a distillery that were used as a visual reference for one of the Pearson flight paths )

Longevity is not the only thing. Science Center has turned out to be unfortunate (well, scandalous, but that's not a transit issue). Hakimi is regrettable, but if someone proposed renaming NYCC as "Rush Commons" or "Lee-Leifson Corners", I would be delighted.

It's subjective, but that's OK.

Kip District remains a trigger. Ugh.

- Paul
I am one of the most historically inclined people on the forum - in fact, I'm not at all a modernist or promoter of the future - and I'm all for reminding people of the past as much as possible, but in the case of station names I really don't see that it is at all helpful. Station names are supposed to give you quick information about where you are, and any name that is not current, likely only to be remembered by old folks reminiscing, or history nerds poring over old maps, run contrary to that. Otherwise you might as well rename Dundas Station to Crookshank, and St. Patrick to Anderson.
 
Last edited:
For example, if we go by Google Maps, Eglinton-Scarlett is situated in an area called Westmount, Islington and Royal York form the boundaries of Royal York Gardens to the north of Eglinton. Islington and Kipling form Richmond Gardens to the north, but this is also overlapped by an area called Willowridge-Martin Grove-Ridgeview, which encapsulates, also, Richmond Gardens and Royal York Gardens. Conversely, Scarlett, Royal York, and Islington, with Eglinton as the north boundary, also belong to Edenbridge-Humber Valley, while the area along Kipling is also known as Princess-Rosethorn and Princess Anne Manor. And many of the neighbourhoods that are shown on Google Maps are contrary to the city of Toronto's official neighbourhood database, too.

Is this really useful to wayfinding?

Unfortunately, mapmakers don't want to leave any area unlablled.... so yeah, they drag in a lot of terms that are obscure or contrived. Anybody in Etobicoke knows Princess Margaret and the Kingsway, but without really knowing the boundaries. Differentiating Richmond Gardens or Richview is an endless and futile debate.

Realtors love to extend these boundaries or add new terms rather than deal with reality..... Stonegate has bad connotations as low status rental, so they call my hood Kingsway South, Sunnylea East, etc.

I agree that transit naming has to be discerning, and not build on the less substantive side of place naming, but nothing wrong with bringing a few forgotten terms back to life to add identity to key destinations. Corktown was a forgotten term until recent development, The Distillery District never existed until it was redeveloped.... before that it was just Cabbagetown.... a name which once applied to most of the then-scuzzy territory east of Jarvis and south of Wellesley, but has shrunk as parts gentrified and the name became more exclusive. Lots of places in the burbs do meet this standard. Jane-Finch for instance is now a cultural term and not a street grid reference.

But used appropriately, place names are quite useful for wayfinding and are richer than a grid reference.

- Paul
 
I think this examples misses the fact that this is not how New Yorkers interact with the subway system. A subway station here isn’t thought of as a destination but as a point on a network—like an intersection on the road network. Stations don’t really have names in the same way they do in Canadian systems; the “name,” such as it is, is merely a description of where the station is. You’d never get confused about which 125th street station to go to because you’d be thinking of it in the context of the line you were on. Just as it wouldn’t be confusing to, say, direct someone to take the 501 streetcar to Yonge, it isn’t confusing to tell someone to take the A train to 125th street.

I’d much prefer we followed a similar approach in Toronto vs coming up with unique “destination” station names every time a potential conflict arises. If I’m travelling along Eglinton and I come to a Bathurst Station there should be no confusion—I’m at Bathurst and Eglinton.
Yes, I am aware of how the New York/Chicago naming scheme works, and of course a New Yorker who uses the subway will know as well. But will a suburbanite from New Jersey who uses the subway twice a year know how this works? Or an infrequent user who has a poor sense of direction and wants to blindly follow Google Maps? What about a tourist? Most of these people do not know exactly where the subway lines are located relative to the streets above or relative to the other subway lines and they do not know what the naming scheme for the stations is. Someone like this will just be confused when they see "125 St Station" show up three times on Google Maps.

Even if I type something like "125 St station 1 train" into Google Maps, it still gives me the wrong stations. So even someone who understands how the naming scheme works, but is unfamiliar with the area and wants to rely on Google Maps, could be led the wrong way. Apple Maps only ever shows one of the 125 St stations when searching. I can't even figure out how to get the correct one to show up if I wanted to navigate to a station instead of an intersection or address, and didn't want to find it on the map. And 125 St is not even the worst example - at least all of them are on the same 125 St. There are numerous examples where there are duplicates in different boroughs, or even duplicates on the same line - e.g. the R train serves a 36th St in Queens and a different 36th St in Brooklyn!
 
Forest Hill is one of the better known ones, along with the Annex. But for every such neighbourhood that is well known, there are mountains of neighbourhoods that are obscure, to say nothing of the fact that which area belongs to which neighbourhood appears to be highly flexible and subject to interpretation.

For example, if we go by Google Maps, Eglinton-Scarlett is situated in an area called Westmount, Islington and Royal York form the boundaries of Royal York Gardens to the north of Eglinton. Islington and Kipling form Richmond Gardens to the north, but this is also overlapped by an area called Willowridge-Martin Grove-Ridgeview, which encapsulates, also, Richmond Gardens and Royal York Gardens. Conversely, Scarlett, Royal York, and Islington, with Eglinton as the north boundary, also belong to Edenbridge-Humber Valley, while the area along Kipling is also known as Princess-Rosethorn and Princess Anne Manor. And many of the neighbourhoods that are shown on Google Maps are contrary to the city of Toronto's official neighbourhood database, too.

Is this really useful to wayfinding? Surely this would cause much more confusion than Eglinton-Islington, Eglinton-Kipling, etc. Neighbourhood names only work when the places are well known, especially if the idea with this is catering to out of towners.
I'm generally in the camp of using intersection names, but I don't have that much of an issue with the neighbourhood names.

Neighbourhood names are useful if they are used, and they are used if they are useful. Once Cedarvale and Fairbank (both names I had previously never heard of before ECLRT) are opened and start being printed onto every TTC map and announced on every Line 5 train, no doubt more people will start using these names for these areas. Simply by using the names, the neighbourhoods referred to by those names will become more specific, useful, and commonly used. Whether doing this good or not is I think a matter of personal preference.

This happened a lot in London for example - stations built in nondescript areas, or undeveloped areas were sometimes given very arbitrary or obscure names, and the neighbourhood became named after the station. Examples include Archway, named because there was an arch bridge nearby, Swiss Cottage, named after a pub, or Queensbury, which was just made up.

Or what about circumstances where two stations are in the same neighbourhood? Mount Dennis station is in Mount Dennis, but so is the future Jane-Eglinton (Eglinton Flats can't be, because it runs afoul of the same trouble that Dundas and Dundas West co-existing do). Every neighbourhood I mentioned in my above paragraphs also encapsulates at least two major concession roads as well. Which one gets priority for the neighbourhood name?
There's no need to come up with some kind of systematic way to prioritize, just pick one and use it, as long as there's no duplicates. Eglinton Flats is fine, as is Mount Dennis West, as is Jane-Eglinton. Even using public consultation to pick one would be fine - just ask people living in the area. This seems like a simple and easy way to make public consultation more meaningful.
 
If the name is unfamiliar to some, it will grow on people. In a century or so, they'd think it weird to be called anything else.

The city last updated neighbourhood names in 2022. Go to https://www.toronto.ca/city-government/data-research-maps/neighbourhoods-communities/neighbourhood-profiles/about-toronto-neighbourhoods/ for the current list.

One thing I noticed on that list is that Eglinton Avenue is a dividing line. Different neighbourhoods on each side.
The city's "naming" is hardly consistent with common usage. It never was. I wouldn't take that too seriously.


It’s not opening this year.
I wouldn't make such absolute statements without a supporting reference. There's no evidence of this.
 

Back
Top