Updated October 21, 2015 at 9:30 am:
The Executive Committee spent a few hours discussing this report. As the morning wore on, it was clear that Mayor Tory was becoming unhappy with questions about his scheme. By the end of the debate when he spoke, he said:
I think a number of the questions raised by members of council today are perfectly legitimate questions which I’m sure our staff have taken note of and if they weren’t already being asked and answered, those questions, they will now be. I just hope and I sense a generally positive sort of sense around here but I hope that we don’t get into being either sort of Douglas or Debbie Downer about these things. [Adapted from a quotation in the Toronto Sun]
Tory went on to say that he had “a mandate” from voters to build SmartTrack in a manner distressingly reminiscent of Rob Ford’s “mandate” to tear up Transit City. The problem with both claims is that voters did not elect Tory or Ford for those specific purposes, but in a reaction against the previous administrations, particularly in Tory’s case. Moreover, that “mandate” does not mean that the platform necessarily made sense as proposed, only that it was an attraction to voters that a candidate had concrete ambitions. We have already seen Tory backtrack on his claims that Toronto did not need more bus service (responding to Olivia Chow’s half-hearted support for transit), and there is no reason for SmartTrack to be treated as a divine plan on stone tablets.
As answers from staff to various questions made abundantly clear, there is a lot of work to do between now and first quarter 2016 when all of the details are supposed to return to Council. Staff went out of their way to avoid giving any indication of the way preliminary work might be headed lest they be drawn into a debate about “conclusions” before the supporting studies are in place.
The Executive Committee made a few amendments to the report’s recommendations:
1. Requested the City Manager to forward the report (October 15, 2015) from the City Manager for information to the Toronto Transit Commission, the Ministry of Transportation, Metrolinx, the City of Mississauga and York Region.
2. Requested the Chief Planner and Executive Director, City Planning to report to the Planning and Growth Management Committee on the results of the public consultations arising from the Preliminary Assessments of the Smart Track Stations, as set out in Appendix 2 to the report (October 15, 2015) from the City Manager, particularly with respect to the development potential of new stations.
3. Requested the City Manager to work with Toronto Transit Commission, Metrolinx, and GO Transit, to develop a One Map Strategy where by major intersections and/routes of these transit operators are shown on future hard copy and electronic local and regional transit maps, once SmartTrack routes and stations are established.
The first recommendation is the original staff proposal simply to transmit the update report to other agencies. The second arose from a concern by Councillor Shiner, chair of the Planning & Growth Management Committee, that implications of and potential for redevelopment around SmartTrack stations be understood as soon as possible. During debate, he spoke about the success of development a long the Sheppard line, an ironic stance considering how strongly he had opposed development around Bayview Station when it was at the design stage.
The third recommendation arose from Councillor Pasternak, who never tires of advocating the “North York Relief Line” (otherwise known as the Sheppard West extension to Downsview). His desire is that maps show all of the projects that are in the pipeline during studies, not just the one that happens to be the subject of debate.
A notable absence in the staff presentation was any reference to the Scarborough Subway Extension as an alternative route for travel to downtown. That presentation covered substantially the same information as the background reports, but it included a few new charts about comparative travel times with SmartTrack in place.
The important difference between this map [at p23] and the Tory SmartTracker website (which shows comparative travel times) is that the TTC includes the access and wait times for SmartTrack in its calculations. This reduces the proportionate saving over a trip. Another issue, of course, is that many riders do not work at Union Station, and taking SmartTrack there would be an out-of-the-way trip. This is not to downplay what SmartTrack might do, but to point out that if ST is to be part of a “network”, then advocacy for it must look at how it benefits all of the trips originating in some part of the city (say northeast Scarborough), not just those that conveniently lie on its route. This will be an issue in comparative ridership projections for ST and the Scarborough Subway Extension because those who are bound for midtown will almost certainly have a shorter trip simply by taking the subway rather than ST.
The original article follows below:
The City of Toronto’s Executive Committee will have as the first item on its agenda, October 20, 2015, an update on studies of Mayor Tory’s SmartTrack scheme. There is a lot of material in this update organized in a main report and several appendixes (linked below).
When SmartTrack surfaced as a major plank in Tory’s election campaign, it consisted of little more than a few background reports and a host of assumptions that could charitably be described as “amateur”. After spending five decades in the company of railfans who love to draw fantasy maps and rhapsodize about the old days, I can say that politicians and their supporters have the “let’s draw a map” bug on a scale the fans can only dream of. SmartTrack has the momentum of a political machine, but is riddled with problems, not the least of which is a willful blindness to the plan’s shortcomings.
In a separate article, I will turn to a pop-up website that purports to be from an independent group promoting SmartTrack although its members have close connections to the Mayor.
In a previous article, I reported on a presentation by Deputy City Manager John Livey at the TTC giving an overview of the state of various transit studies, including SmartTrack. The report to Executive is a much more extensive treatment of the project. It fills in some technical details, but leaves many, many questions still to be answered. SmartTrack boosters take the release of these interim studies as a good sign, although Mayor Tory has already made a claim about SmartTrack’s ability to relieve subway congestion that is not in the report because the demand studies have not yet been completed and published. Either he has an advance copy of those studies (in which case why don’t we see them too), or he is blowing smoke about his pet project.
As proposed in Tory’s campaign, SmartTrack would run from Unionville to the Airport Corporate Centre (the solid black route in the map above). Of this, the Eglinton West leg is the most problematic, and recent work has focused at Council’s direction on alternative routes entering the airport lands from the north (dotted line above).
A major problem for SmartTrack is that it shares corridors with GO Transit, and more importantly with GO’s proposes Regional Express Rail network that will feature much more frequent service than GO has provided historically. In effect, two competing schemes to improve regional transportation surfaced at roughly the same time, and each has its political support base. The difference for SmartTrack is that it is supposed to be a more local service with frequent stops and TTC fares, but that is easier said than done.
A fundamental question about SmartTrack is the matter of service levels. This has been described as a “surface subway”, but Torontonians are used to the idea that a “subway” shows up at least every five minutes, and this level of service was certainly implied throughout the election campaign. This has now been tempered to a 15 minute frequency of SmartTrack trains mixed in with the RER service. In the diagrams below, the RER service levels are taken from current Metrolinx plans. These maps show what is being modelled in the demand study.
This service design gives an RER or ST train every 7’30”, a considerably more aggressive level than Metrolinx discussed in June 2015. At that time, they confirmed that their planned infrastructure for the corridor would only support a 15′ headway of combined services. More trains require a more advanced signal system, not to mention more track, something that is becoming clear in the technical studies. A further problem is that much of this route is shared with other services such as the Lake Shore GO/RER trains, the UPX shuttle and VIA, not to mention the ever-present scheme to operate High Speed Rail from Toronto to London via the “north” route which leaves Toronto via the Weston corridor. It is easy to draw yet more lines on a map saying “the corridor is there”, but much harder to fit all of those services together in the same space.
Of course, “regional” or “commuter” or “overground” railways can run at subway-like frequencies. After all, the technologies of a subway train and a electric multiple unit (EMU) GO train differ mainly in design speed and crash strength, but the rest is cosmetic. The issue here is not to say that frequent service is impossible, but that the current Metrolinx plan for corridor infrastructure is nowhere near that aggressive because this would greatly exceed their own perceived needs. Moreover, there are constraints related to continued operation by freight railways over some GO lines.
The covering report to Executive conflicts with the service plan by claiming:
SmartTrack includes enhanced service levels (better than 15-minute frequencies) in both directions, additional stations, service and fare integration with the Toronto Transit Commission (TTC) network, and a new heavy rail corridor connecting to the Mississauga Airport Corporate Centre (MACC)/Pearson Airport. By leveraging the provincial commitment to improve the GO network, SmartTrack seeks to address the immediate need for greater access to rapid transit service in Toronto; provide relief to the overcrowded Yonge subway line; encourage development opportunities across the city; and create connections between major employment centres within the city and region. [p 1]
There is a big difference between “every 15 minutes” and “better than 15-minute” service especially in the implications for infrastructure design. If the target is 15+15 (a combined service of 7’30” on RER and ST), this produces very different infrastructure than 15+10 or even 15+6. Very frequent services (6′ headway or 10 trains/hour) cannot easily share infrastructure without careful design to minimize points of conflict and an operating strategy to eliminate delays at these points. The technical studies on infrastructure requirements are not out yet, but an essential point within them will be the target frequency for service. This includes not just isolated segments such as the Stouffville corridor, but also the shared trackage on the Lake Shore, Union Station and Weston corridors.
It is worth noting that the Western Corridor substudy (Appendix 3) is based on a 15-minute headway:
The service concept feasibility is examining the interaction of different services sharing the GO rail corridors, terminal station requirements and the integration of other transit services with SmartTrack. The Consultant has been asked to comment on:
- Any additional infrastructure that may be required in the Kitchener Corridor from Union Station to the point at which the SmartTrack corridor connects, to accommodate 15 minute SmartTrack service in addition to the other GO RER and UP Express services in the Kitchener Corridor; and
- The potential impacts to GO RER and UP Express services as a result of adding 15 minute SmartTrack service in the Kitchener Corridor without additional infrastructure. [Appendix 3, p 2]
There appears to be some confusion about the exact nature of the target service design even though this will have a very large effect on the infrastructure needs.
In turn, service frequency directly translates to capacity and attractiveness to potential riders. Four trains per hour carry a lot fewer riders than twelve, and the transfer between feeder services and the trunk line is relatively more of a time burden. Claims made during the Tory campaign for very high SmartTrack ridership presumed very frequent service, but that is not what’s on the table.
A further problem lies in the confusion between SmartTrack and RER. At times, they are presented as an integrated service, but at other times they are quite separate. RER and its infrastructure are definitely a base on which ST can build, but RER infrastructure is not, by itself, enough to permit ST operations even at a 15+15 level of service, let alone SmartTrack at 5 minute headways, the lower bound now under study. Claims by SmartTrack advocates that ST doesn’t need much new infrastructure because it will run on existing GO tracks are, to be kind, misleading.
The covering report is more circumspect on the issue of shared infrastructure:
SmartTrack could potentially be integrated with GO RER and/or coexist within the same corridors, utilizing common infrastructure elements (tracks, stations, rolling stock, crossings). The degree to which GO RER and SmartTrack are integrated, and how the services are operated and governed is subject to future discussion between the Province and the City once the service concept and infrastructure planning work has been further advanced. [p 9]
Several SmartTrack components were not included in the funded GO RER program. For instance, service frequency options better than every 15 minutes, fare integration, 11 new stations, and continuous service between Kitchener and Stouffville/Lakeshore East corridors at Union Station. The new western heavy rail spur connecting Mount Dennis to the MACC/Pearson Airport is also outside the scope of GO RER. [p 9]
An actual service plan and infrastructure proposal will not come forward until the first quarter of 2016.
Another major issue that has been completely ignored by SmartTrack advocates is that two major employment and development centres to be served by this line lie outside of the City of Toronto: the Mississauga Airport Corporate Centre and developments in and near Unionville. There has been no suggestion to date that the 905 regions who would benefit from this line actually pay toward the cost of its implementation or operation. Certainly, they will make an indirect contribution through provincial taxes to the base RER system, but the added upgrades needed to support ST are another matter. By contrast, the subway extension to Vaughan has York Region money in its capital budget, and the proposed extension to Richmond Hill has been discussed on a similar basis.
Fares are another delicate subject because of the Metrolinx Fare Integration study now underway. John Tory’s campaign proposed “TTC” fares on SmartTrack as if this line would be just like a new subway line within the TTC network. If the will exists to fund this operation, then of course ST will be far more attractive than the separate, discriminatory GO fares now charged within the 416. However, campaign claims that the line would be self-financing presume ridership levels and considerable net new revenue (as opposed to existing trips and fares diverted from other lines in the TTC network). This has yet to be validated by demand studies, and claims of “self-financing from day one” are nothing more than a self-serving attempt to dodge the question. (We already know that the TTC expects net operating costs to rise by about $31-million over the 2017-18 implementation of the Spadina extension.)
Table 4 in the main report is vital reading as it shows the magnitude of work still to be done for combined RER and SmartTrack planning. The list is long [pp 28-30] and the issues it raises are not trivial. Clearly, even the early 2016 update will not be able to address all of these topics in detail, but at some point, the largest, reddest flags have to pop up to avoid unsolvable problems further into the project. In particular, infrastructure, operational and cost considerations of very frequent service must be understood so that we don’t commit to a capability we cannot deliver.
For the balance of this article, I will work through the report’s appendices which each address different aspects of the project.
For the benefit of those who have not been following the GO/RER plans, this appendix provides a consolidated view of current intentions. Notably there will be large service increases in peak and especially off-peak operations, and these will trigger the need for major shifts in infrastructure including electrification of much of the GO network.
The portions of the GO network that will receive “RER” service are almost entirely those completely under GO’s control and ownership. When this service is in place, the network will be transformed from one whose primary mission is to deliver commuters to King and Bay to one that is truly “regional” and provides good bi-directional, all-day service. A big challenge for GO will remain that the network, based on existing rail corridors, is radial, and there will remain demands for trips that do not lie along the spokes radiating from Union. BRT routes can help, but at some point, the debate over allocation of road space will move from downtown Toronto out into the suburbs.
Electrification is essential to GO’s plans because it will allow trains to operate with better acceleration profiles needed both for closely spaced stations and frequent service.
As with the RER service plan, the electrification is limited to corridors that GO controls, with the exception of the Richmond Hill line (owned by the Province from Union north to the crossing with the CN York Subdivision north of Steeles).
The Metrolinx/GO RER program represents a substantial capital investment ($13.5-billion 2014$) and an implied commitment to future operating subsidies. When SmartTrack was announced, the position taken by Queen’s Park was that the provincial “1/3 share” would consist of its investment in RER as the base system. The actual dollar value attributable to SmartTrack is unclear, but it is fairly evident that there will be no additional provincial funding for SmartTrack beyond the GO/RER commitments.
GO draws its ridership primarily from outside of Toronto with only 12% of the total 197k daily trips being within the city. This is partly a function of the competing TTC system, the service levels at and locations of GO stations, and the fare structure which discriminates strongly against short-haul riding, particularly when the added cost of a TTC fare just to access a GO service is considered. As yet unknown is the degree to which, if at all, there will be a joint GO-TTC fare as part of “regional integration” that will make the GO network more attractive for inside-Toronto travel. This will be complicated by the presence of a “TTC fare” SmartTrack service on two of the corridors while riders on other parts of the “GO” network pay GO-level fares.
The vision of the GTHA Fare Integration Strategy is to increase customer mobility and transit ridership while maintaining the financial sustainability of GTHA’s transit services. This strategy will remove barriers and enable transit to be perceived and experienced as one network composed of multiple systems/service providers. [p 11]
The infrastructure for RER is already in place in the Weston (Kitchener) corridor, but much work remains on the Stouffville corridor including double tracking, improved stations and grade separations. SmartTrack improvements would be required over and above work already planned by GO.
Integration of RER and ST services poses various “challenges” according to the report. None of these is surprising, but at least they have moved from the realm of “amateur” comment by critics (like me and many others) to a professional realm where they are harder to ignore. These include:
Metrolinx is currently undertaking a comprehensive study of Union Station to ensure that sufficient capacity exists on the tracks, on the platforms, and also on the approach tracks throughout the Union Station Rail Corridor, to accommodate the planned GO RER service levels to 2031. Adding service beyond what is already planned for GO RER will be challenging within Union Station.
On the Kitchener corridor, the GO RER service concept calls for diesel and electrified GO service with express and local stops; VIA and UP Express trips add further pressure to corridor capacity. Running continuous service from Eglinton through to the Kitchener corridor, as proposed in the SmartTrack service concept, would put pressure on track capacity because it introduces a different type of service with a different speed and stopping pattern into an already complex environment. On the Stouffville corridor, the current GO RER service concept calls for seven trains in the peak hour, including three trains from Lincolnville and an additional four trains from Unionville.
Adding service beyond what is planned for GO RER may require additional tracks on the Kitchener and Stouffville corridors. [p 12, emphasis added]
SmartTrack Stations: Preliminary Assessment and Station Profiles
In all there are 26 proposed stations in the SmartTrack scheme including the alternative western corridor through Etobicoke North. City Planning reviewed them under a variety of criteria including:
- Choice: How well does the station connect to the transit network and serve a substantial potential market of riders?
- Experience: Are there key destinations nearby by which ST improves transit access?
- Social Equity: Is the station near Neighbourhood Improvement Areas and their affected population?
- Shaping the City: Is the station located in an area of existing and planned population growth?
- Healthy Neighbourhoods: Does the station integrate well with neighbourhoods by, for example, occupying currently vacant land?
- Public Health & Environment: Does the station conflict with natural or cultural features?
- Affordability: What is the station’s cost and the availability of a site?
- Supports Growth: Is the station located in an area of existing and planned employment growth?
This framework is common to all of the planning studies now underway and is used deliberately to permit comparison between various evalations.
A more detailed evaluation of proposed SmartTrack stations is ongoing and will be updated as more information becomes available. Further evaluation can include, for example, more in depth analysis of planning and development issues and opportunities (e.g. soft sites analysis), environmental considerations, ridership analysis, and technical considerations related to the corridors and rail operations. [p 5]
At this point, the evaluation looks at stations from a planning perspective, not a technical one, although the latter will be important in areas where physically adding a station may present challenges for train operation and surrounding infrastructure. Some of this is mentioned in the Station Profiles.
Metrolinx has its own new station evaluation underway as part of a network-wide review. That study began with a very long list of potential locations, and has only recently moved into the short-listing process. The Metrolinx analysis includes technical factors that are not in the City Planning list.
This list is intriguing because it begs the question of whether SmartTrack should have 26 stations at all, or if it can be an effective service with far fewer. A reduction in station count would have major effects on the integration of TTC service. For example, only the stations at Steeles (Milliken) and Eglinton (Kennedy) on the Scarborough leg rank highly, while Finch East, Agincourt (Sheppard) and Scarborough (Danforth) have a low rank.
It is important to remember that even existing GO station locations are dictated by the rail corridors which tend to be in old industrial areas that are not necessarily well-related to city planning goals for growth or to existing residential or employment concentrations.
Completely ignored in the discussion (and in the related TTC Integration paper) is the effect that Scarborough Subway stations would have on some of the proposed SmartTrack stations notably by intercepting passengers further east on a more frequent service and one that will more likely remain part of the TTC fare network.
Equally important are political considerations. SmartTrack is, among other things, pitched as yet another way to give Scarborough better access to downtown. If stations were dropped from the plan, how would this be perceived? Will ST gain many stations on a “chicken in every pot” basis and be built more like a “traditional” subway line with stations even in locations that might not be able to support them?
Stations that are close to the core are cited as potential locations where the streetcar network could be offloaded. However, this ignores the fact that physically transferring from a streetcar line to ST would involve getting off cars, possibly after they are well-loaded, accessing the ST station, and waiting for a train by which time the streetcar, for all its problems, would already be downtown. Having two lines cross on a map does not mean that this would be a convenient, well-used transfer point, especially for trips that are not bound for Union Station.
This is a point where the station study must interface with demand modelling. How much will each station actually contribute to SmartTrack demand, and how would the network behave if selected stations were dropped from the plan.
Western Corridor Feasibility Review
The Western Corridor is a very challenging part of the SmartTrack plan, and one for which it was severely criticized (by me among others) for the superficial and incompetent way in which it was reviewed as part of Tory’s campaign. The “consultants” behind this plan were unfamiliar with the area and the technical problems involved in a through route from the Weston corridor onto Eglinton Avenue, not to mention the basic challenge that the presumed right-of-way, the Richview Expressway corridor, had been sold off by Build Toronto.
Various alternative schemes have been considered, but they share various common factors:
- Surface operation along Eglinton, claimed as part of the original SmartTrack, is simply not feasible with the type of trains that will be used.
- The link from the Weston corridor to Eglinton will be complicated with both elevated and underground construction, and is likely to disrupt neighbourhoods through which it will pass.
- Additional track capacity will be required in the Weston corridor to accommodate all of the planned services, and this may conflict with some potential station locations.
The Eglinton LRT remains in the mix as a “base case” and indeed it was preferred at public meetings. Work to refine the LRT option continues:
Metrolinx is reviewing the approved LRT plan to consider alternative LRT concepts that would improve travel time compared to the approved LRT concept, address local concerns and at the same time improve strategic connections. [p 5]
The “Corridor 1” family of options deal with various ways to link the Weston corridor to Eglinton West. Three of the four maintain a link to the Mount Dennis Crosstown station, while the simplest (and the one proposed in the election literature) does not. None of them is a simple connection both for their interaction with railway infrastructure and with neighbourhoods.
The “Corridor 2” family of options take the SmartTrack route further northwest on the GO corridor and turn south into or beside the airport lands. These options have their own problems including potential conflicts with the airport itself, and suitability of station locations. Moreover, the link to the Mississauga Corporate Centre would be somewhat roundabout. A further problem with this group is that it would require capability for combined ST, RER and UPX operation to exist as far as the airport rather than only to Eglinton.
“Corridor 3” was a proposal for a stand-alone line on Eglinton from Mount Dennis to the Corporate Centre. This makes no sense at all as it would be an orphan line at considerably greater expense than the surface LRT alternative. It did not survive the technical screening.
Cost estimates for these options are not yet available.
A commentary on the capacity of the Kitchener corridor is worth repeating here in full:
While detailed analysis related to the full length of the Kitchener corridor is beyond the scope of this feasibility review, the review provides some insights pointing to areas requiring further analysis. The technical analysis indicates that without significant signalling upgrades, improvements to train control systems, or modifications to GO RER, SmartTrack or Union Pearson Express service concepts, two additional parallel tracks “are highly likely” to be required in the Kitchener corridor between Union Station and Mount Dennis or Woodbine Racetrack to make the connection to the new SmartTrack heavy rail corridor from Mount Dennis to the MACC.
Two new tracks for SmartTrack service would require a widening of the Kitchener corridor between Mount Dennis or Woodbine Racetrack and Union Station and associated property acquisition for all heavy rail options to the MACC.
The service concept in the feasibility study assumes two additional tracks all the way to Union Station to allow SmartTrack to run alongside GO RER, UP Express and VIA Rail services on the Kitchener corridor. The services to be accommodated in this corridor include:
- 15 minute GO RER service from Union Station to Bramalea
- 15 minute peak GO RER express and local service from Union Station to Mount Pleasant
- 15 minute Union-Pearson Express service
- 15 minute SmartTrack service from Union Station to the MACC
- VIA service
All of these services have different operating patterns that make management of operations on the corridor complex. This assumption of two additional tracks could possibly be adjusted if there were to be some form of integration of GO RER, SmartTrack and/or Union Pearson Express services and/or adjustments to service frequencies. Further analysis is required to test assumptions with respect to such integration.
Adding more tracks to the Kitchener corridor raises some technical challenges:
- a SmartTrack station at St. Clair Avenue may not be possible if additional tracks are required;
- this may also have potential impacts to the City’s current St. Clair Avenue West Traffic Congestion Environmental Assessment Study which is examining ways to improve east-west connections across the Kitchener Corridor;
- adding tracks to the Kitchener corridor could require significant modifications to recent rail improvements in the Weston and Junction Areas; and
- existing development adjacent to the Kitchener corridor may also limit corridor expansion in some sections.
These potential challenges would require further examination as plans for SmartTrack as a whole are developed. [pp 14-15]
Note that the design target is a 15 minute headway, not “better than 15” as cited elsewhere in the reports. Moreover, the issues raised here were known a year ago, and should have been clear to SmartTrack proponents, but they were “experts” who chose to ignore the critics. Sorting all of this out is not a job for a few months’ work between now and early 2016 unless a lot of options fall off of the table fairly quickly. What remains is unlikely to please those for whom the project was little more than a line drawn on an out-of-date Google Earth map.
The TTC has reviewed its surface network to determine how it might act as a feeder/distributor for SmartTrack. The analysis assumes that all of the currently proposed ST stations are implemented.
Notable on this map is that in Scarborough, the dense knot of routes feeding into the SRT at Scarborough Town Centre has mostly disappeared, but this is replaced by a comparable arrangement at Mount Dennis. Obviously this design only works if SmartTrack really is a TTC fare line just like the subways because much of the incentive to switch to it will depend on cost. A related problem will be service frequency and the availability of competing routes to downtown (the Scarborough Subway to the east, and the Eglinton Crosstown + Spadina Subway to the west).
The TTC describes a process for evaluation of service changes that considers the degree to which passengers overall will be “convenienced” by any change that might be implemented. This evaluation is not included in the report on a route-by-route basis.
TTC staff have identified a list of TTC services which, on an unweighted, pre-evaluation basis, would appear to provide customer-benefitting connections with SmartTrack. This list includes TTC routes making seventy-five (75) transfer connections at 21 proposed SmartTrack stations. The preliminary connecting routes are shown in the map attached as Figure 1. The list includes nine (9) TTC routes that could make connections at SmartTrack stations, but fall in the category of an off-route diversion. Off-route diversions are generally implemented by the TTC on an exception basis and are determined through the weighted evaluation process described above. This list of candidate routes will change as SmartTrack stations become finalized and after a full evaluation of the effects of these connections on all customers. [p 2]
This process will feed into both the demand modelling and the station analysis. This is particularly important where “off-route diversion” is required for a bus to reach a SmartTrack station. If few riders would make use of such a connection, the diversion simply adds travel time and annoyance for most riders who are making through trips.
Public consultation to date has included a number of meetings carried out as part of the overall transit project study review (SmartTrack, Relief Line, Scarborough Subway and GO/RER). Highlights of the feedback on SmartTrack include:
- Some residents asked questions on the distinctions and similarities between RER and SmartTrack.
- There was positive feedback for SmartTrack related to TTC fare integration, additional stations, electrification and greater frequency of service.
- Other comments were concerned that SmartTrack was redundant with RER, and that it would add further pressure to existing crowding at Union Station.
- A few comments were concerned with the potential impacts of SmartTrack stations on local communities and surrounding land uses.
- There were also concerns related to the coordination and prioritization of Toronto’s transit projects. There was concern expressed by some that SmartTrack has priority status over the other projects concurrently under way (including Scarborough Subway Extension and Relief Line project assessments).
With respect to the Eglinton West Corridor:
- Some comments indicated that land-use compatibility was a concern, particularly for communities and areas that would be impacted.
- Some comments related to the service concept, looking to gain a better understanding of how SmartTrack would impact other transportation services.
- Other comments related to technical analysis and asked if building heavy rail along the Eglinton corridor is feasible from engineering and operational standpoints.
- A majority of people preferred the Base Reference Case LRT, indicating support for the proposed LRT station stops and LRT technology as most appropriate for the Eglinton corridor.
- Other comments on the Base Reference Case LRT proposed improvements to the LRT including grade separations and removing some station stops to increase speed and travel times.
No consultation has occurred yet for the portion of SmartTrack outside of Toronto. This will be coordinated with the affected municipalities.
What is striking about this feedback is that people like the idea of SmartTrack, but have reservations about how it fits into a larger picture and its effect on local neighbourhoods.
Before diving into the specifics of SmartTrack, this report repeats a point often made and just as often ignored in transit debates: transit exists to support travel.
Transit must facilitate the types of trips that people want to take – ranging from local to regional – and carry the number of passengers that want to take those trips. Figure 4 illustrates how different existing and planned transit technologies can be used to provide various types of transit service. Together, all services provide an efficient network that moves people around the city region. [p 5]
It is worth noting here that the 504 King Streetcar is capacity constrained by the size of the streetcar fleet and the level of service provided in that corridor.
Also, the high capacities shown for GO/RER and SmartTrack, overlapping with subway demand, depend on a much higher level of service than is currently operated or is planned for these routes. For example, if either of these runs with 2,000 passenger GO trains every 15 minutes, then the capacity is limited to 8,000/hour, very, very much less than the subway lines.
City Planning undertook a study of rapid transit priorities that identified the top-ranked projects based on three principles: serving people, strengthening places and supporting prosperity. (A much more fine-grained set of criteria was also applied.) At the time, SmartTrack and RER were not in the mix, and Planning is revisiting the process. The outcome will be interesting because of a political context in which a low ranking for either of these schemes will not fit well with the accepted political wisdom.
For reference, the original set of top-ranked projects is still available on City Planning’s website. Note that these projects do not align well with SmartTrack, or putting it another way, SmartTrack does not align well with lines that had been flagged as the most important. To what extent the new map will reflect actual transit rider needs versus a gerrymandered political scheme remains to be seen.
There is a long section of this report that simply covers the process by which a transit proposal is developed and evaluated, and I will skip over that. Next comes a review of how SmartTrack fits with the city goals. This begins with general comments about how ST fits with city-building objectives:
SmartTrack and GO RER would both make better use of the currently under-utilized GO Rail corridors in the off-peak periods, a development which is called for in the Official Plan and is supported by Provincial Policy Statement Policy 1.6.3. SmartTrack proposes further enhancing GO RER services to provide more local rapid transit within Toronto.
With the current network configuration, the single biggest constraint to meeting the demands on the City’s rapid transit network is the capacity of the Yonge Subway, particularly the transfer at Bloor Station. SmartTrack is being designed to relieve this congestion, and would expand rapid transit to new parts of the City.
Depending upon the final station locations selected, the line has the potential to serve key development nodes like the Unilever site and Liberty Village. It would also serve the fast growing Distillery District and West Don Lands areas as well as several other large underdeveloped sites and many Employment Areas, improving their development potential. Some of the area through which this line would pass has recently experienced very rapid growth. Road-based transit services in the area face congested conditions and crowded vehicles.
SmartTrack would add additional transit capacity to support further growth of these areas and enhance their connection to the Downtown. It would also pass through or near many different Neighbourhood Improvement Areas, with the potential to improve transit accessibility in these areas. As currently proposed, the western heavy rail alignment options to MACC do not provide local transit service so separate local transit services on Eglinton would still be required. [pp 10-11]
Although the report talks about subway relief, it is important to note the statement that SmartTrack “is being designed to relieve this congestion” is not the same as “it will provide relief”. After all, the demand modelling has not yet been done, and we know from the June 2015 Metrolinx update that the actual effect of ST on subway congestion is minuscule compared with what a Don Mills Relife Line to Sheppard would provide. The degree to which ST can actually achieve the potential implied above depends a great deal on station siting, access, service levels and fares.
The report goes on to evaluate SmartTrack against the criteria listed in the Station Evaluation section. Here, the comments are more circumspect in particular where they relate to the output of the demand modelling. Notable points include:
- Social Equity:
- Approximately 12 Neighbourhood Improvement Areas (NIAs) are within walking distance of SmartTrack stations, depending upon final station locations. SmartTrack does not pass through significant areas of population not already served by high frequency and high capacity rapid transit.
- The stations proposed in the SmartTrack concept will provide an increase in the area of the City within walking distance of rapid transit stations. This increase occurs mostly in Etobicoke and northern Scarborough. [p 12]
These bullets make the important point that SmartTrack would serve new areas that do not now have good rapid transit service. However, this comes back to issues such as which stations would actually be built, along with the service pattern and fare structure.
- SmartTrack does not serve many areas planned for residential growth which are not already served by rapid transit. The percentage of land served by SmartTrack that is planned for residential growth is slightly above the average of the projects evaluated.
- The projected population growth around some SmartTrack stations in the City of Toronto is limited. Many of the areas that have projected population growth are already served by rapid transit.
- Many of the areas of higher density which will be served by SmartTrack are already served by rapid transit services (e.g. Weston, Bloor, Liberty Village, Danforth, Kennedy). [p 12]
These observations are a bit confused (and the double negatives don’t help one bit). Effectively, the report says that few growth areas without rapid transit are on the SmartTrack line, and that growth potential for some stations is limited (as noted in the Station Analysis). However, this misses two key points:
- Just because there is transit service somewhere today does not mean that the area is “served” by it especially if there are capacity and other service quality problems.
- A station with little growth potential immediately nearby might still serve a higher population via surface feeder routes. The relative locations are often constrained by existing rail corridor locations and land uses.
Neighbourhood impacts are low except in the Eglinton Corridor. This is easy to understand given that SmartTrack spends its time in largely industrial rail corridors. Eglinton is quite another matter.
As for Employment Growth, the situation is mixed:
- The stations in the City of Toronto proposed in the SmartTrack concept serve significant areas of employment growth. The percentage of land served by SmartTrack which is planned for employment growth is moderately above the average of the other 25 projects evaluated. The Woodbine (Northern Extension) corridor for the western alignment performs better than the Eglinton Ave corridor as the former has a largely residential catchment.
- Despite SmartTrack serving large areas of land targeted for employment growth, the projected employment density in the vicinity of proposed SmartTrack stations is low. Under some employment projection scenarios, there are stations which serve areas of significant planned employment growth and density (e.g. Unilever). Some of the other areas of high projected employment growth are already served by rapid transit.
- The existing employment density around SmartTrack stations in the City of Toronto is low. Many of the areas of higher density which will be served by SmartTrack are already served by rapid transit services (e.g. Union).
An important issue that is missing in these observations (both for residential and employment densities) is a sense of scale. How much growth are we talking about in each case, and to what extent will SmartTrack provide useful access as part of the transit network? How likely is growth in the designated areas particularly considering how long some of them have been underused?
The report peters out with updates on:
- The Relief Line: This is still focused on the narrow Danforth to Downtown segment which reflects the TTC’s long-standing bias against the RL in general and anything beyond a connection to Danforth in particular.
- The Scarborough Subway whose co-existence with SmartTrack remains a question for the demand model.
- Brief descriptions of the LRT projects in various stages: Waterfront, Eglinton, Finch and Sheppard.
Population and Employment Projections
The projection of population and employment is an essential pre-requisite to the Demand Modelling. For this purpose, the zonal system used in past projections had to be updated to be more finely-grained reflecting the spacing of SmartTrack and other rapid transit stations within the study area.
Population growth was modelled both for the basic data from past studies and the 2011 census, as well as on an enhanced basis presuming the existence of SmartTrack. This latter scheme is dubious because it presumes ST is sufficiently important that it would change regional growth at a measurable level as distinct from other city and transit network changes that might occur. Once again, the effect of ST will vary substantially with the service level actually operated. At four trains/hour, this is little more than an improved GO service, not a new equivalent-to-subway line. Moreover, the RER and other rapid transit projects will also contribute to growth. This smells of an attempt to goose projections on the ground that SmartTrack is uniquely able to stimulate growth beyond what might otherwise occur and even considering that it does not serve most of the GTA.
Even if we accept the premise, the delta for the SmartTrack versions out to 2041 is only about 6% which is small enough that it could well be within the margin of error for such predictions.
For the employment model, there is a similar table, but the difference between the basic projections and the SmartTrack versions is even smaller than for population growth, only 2-3% generally.
The report continues with its meandering examination, but it contains an important point: office space projections are provided by a sub-consultant, SRRA, who were responsible for the SmartTrack scheme in the first place. Of particular importance, this is the same consultant who in another study claimed that office growth downtown (and in many older areas of the city) was dead, and that all the new growth would come in the suburbs in areas (surprise!) that SmartTrack would serve.
This begs the question of whether the figures actually reflects trends that have been evident with a shift in both population and employment to more urban areas. There is supposed to be a separate report on future office development from SRRA at a later date.
This really is a report for the serious planning nerds, and yet the work it represents will have a considerable effect on the outcome of demand modelling. The figures presented here are aggregated to the City of Toronto and “Rest of GTA” level, and we have no idea of the distribution within each of these areas.
This section describes in great detail the capabilities of trip modelling in the University of Toronto’s new “GTAModel V4” which the City of Toronto will use for its planning. This is a much more sophisticated model than the one used in previous transit studies because it handles trips at a much more finely grained basis and deals with all-day flows through the network including counter-peak movements. It also models the effect of network congestion, capacity limits and fare levels on the route choice made for the modeled travel.
The model is in the final stages of calibration, essentially determining that for recent known traffic data it will produce the observed behaviour from known population, employment and other demands placed on the network.
As mentioned above, the service design that will be modeled is based on a 15-minute headway of SmartTrack trains overlain on GO’s planned service level for RER in the same corridors. Three connections from Mount Dennis to the airport will be modeled: the Eglinton SmartTrack route, the North Etobicoke SmartTrack route, and the LRT extension as the base case.
Also to be examined are the effects of stations, fares and service levels. This work is expected to report out in first quarter 2016.
Finally, we come to the money.
This report starts off with a little tutorial to distinguish between “funding” and “financing”, terms that are frequently confused, especially by politicians.
Financing refers to the financial mechanisms or tools used to raise the initial funds to pay for the construction of the project. Financing is usually required when there are differences in timing between project expenditure cash flows (often required upfront) and project revenues, which may not occur until much later. Debt, bonds, equity, and capital lease arrangements are typical financing tools to raise the initial funds for the project, but there are many other tools and structures that can be used depending on circumstances and level of participation and risk allocation between the public and private sector. The use of financing creates a future obligation to repay the money back with a return on capital investment.
Funding refers to the sources of project revenue, including future revenue streams that the project owner will use or pledge to repay the financing of the project over time.
In brief, “financing” is the mortgage you take out to buy a condo, and “funding” is the money you will earn to pay it off. For transit projects, very large amounts are involved, and on the “funding” side of things, there is much competition for scarce resources. This is further complicated in the “financing” side of things because too much borrowing pushes up future costs, just like maxing out your credit cards and having no money left for food. It’s a balancing act between many factors and competing priorities for public investment.
On the funding side, Queen’s Park is looking for $5.2-billion from Toronto and Ottawa based on the premise of a roughly $8-billion SmartTrack budget with the province putting in one third via “in kind” spending on its GO network. The Feds committed to $2.6b from their new Public Transit Fund, although the exact status of that is up in the air pending the election on October 19. The Liberals, likely inheritors of the government, have also pledged to support SmartTrack. The problem with this, of course, is that the support is more for political reasons (supporting Mayor Tory, and the “me too” phenomenon we saw with Scarborough Subway Champions), than for planning ones given that much work remains to be done on costing and on establishing the exact role and worth of the SmartTrack project. The NDP, for what it’s worth, instead pledged funding without attaching it to a specific project.
In any event, while it is nice to have promises of support, this comes from a barrel that is not bottomless, and we have yet to debate whether the first $8-billion collectively to be spent by three governments should regard SmartTrack as the top priority in Toronto.
The City, for its part, is about to launch into its annual Capital Budget review which includes the discussion of debt levels and potential alternate revenue sources. Recent remarks by City Manager Peter Wallace suggest that he is open both to changes in the City’s self-imposed debt ceiling as well as other sources of revenue, but these each bring problems. A higher ceiling allows more debt service charges (and hence more debt) relative to tax income, but according to Wallace, even that won’t deliver the kind of money needed to finance the many big projects facing the City, and more debt has implications for future budgets. New revenue streams inevitably spark political opposition from Councillors who could not agree on using any of the revenue tools actually available to them, let alone asking for something new like a sales tax.
The report talks of three potential funding sources: Tax Increment Financing (TIF), development charges, and sale of development rights.
The first and obvious question is “where will development occur”. This brings us back to SRRA who, as mentioned above, had previously held that much development would lie outside of Toronto. They have been commissioned to produce projections of what might occur.
Strategic Regional Research Alliance (SRRA) has been commissioned to prepare population and employment forecasts under scenarios that include and exclude SmartTrack. SRRA has expertise of the local real estate market. Using their population and employment forecasts, they will identify specific areas within the City where increased development is projected to occur. SRRA’s forecasts will also consider scenarios under current planning constraints and relaxed planning constraints.
SRRA’s analysis of development potential has not yet been completed. SRRA’s methodology and assumptions will be independently verified through a peer review by Cushman & Wakefield. It is anticipated that the peer reviewed development forecasts will be available in Q4 2015. [p 3]
There are two big problems with this. First, development outside of Toronto in Mississauga or Markham is beyond Toronto’s taxing authority. If any value is to be captured from it, regardless of the mechanism, it will benefit municipalities who are not contributing to funding of the SmartTrack project. Second, the development market in the core area is very strong, and much will occur whether SmartTrack is in place or not and its incremental effect could be small (see also Population and Employment projections above).
The premise behind TIF is that investment in an area will produce development that would not have occurred otherwise. The efforts of Waterfront Toronto are a perfect example in that much land would still be post-industrial wasteland but for the infrastructure installed to support a new, very large population. SmartTrack does not fall into the same category except for specific areas such as the Great Gulf (Unilever) site that require substantial new transit investment. It is not clear how much development will actually be due to ST and how long Toronto would have to wait for this to occur and TIF revenues to pay off the debt.
This chart is “magical” in that it makes the incremental TIF revenue look like a pile of new money. However, much depends on what lies in the “TIF Zone” and how much growth within it can be tied to a project. For example, one could not make all of the core area a TIF zone because, self-evidently, it is doing very well without SmartTrack. If the zone gets smaller, and the tax revenues (base and incremental) are reduced correspondingly, then there is not as much actually available as the chart might suggest. Moreover, the further off actual development lies, the greater the risk that it might not ever occur, or even worse, that accommodating pols will “relieve” future, hard-pressed developers of this burden.
Another source of revenue is “tax uplift”. For example, if the value of your house goes up by 10% because there is a new transit line (even better a new station) nearby, then that increase is available in theory as a transit funding source. The problem is that many factors affect property values, and house prices are rising strongly in Toronto even without transit spending. This also begs the question of whether, for example, residents of Brimley Road would be hit with new taxes on the presumed uplift in property values thanks to their new subway.
The determination of tax increment from new development is relatively straightforward and does not require any special legislation or tools. Once a TIF zone has been determined, new development taking place in that zone will be physically observable, and the new taxes generated directly measurable from its current value assessment.
The allocation of new taxes being attributable solely to SmartTrack is somewhat more subjective. The allocation would be accomplished by comparing a forecast of new development in the absence of SmartTrack with the forecast of new development with SmartTrack being built. SRRA is preparing these new development forecasts. [p 5]
The operative word here is “subjective”. The further one looks into the future, the less one can attribute a development to a specific past transit project unless there is a very close linkage between that project (a station location, for example) and the development. Moreover, any new development brings costs other than transit service that must be paid for from tax revenues, and the base level may not be adequate for this purpose.
With respect to residential values, the City did observe an increase of 3-5% in the Sheppard East corridor relative to city-wide values, but this is not solely attributable to the subway line.
Development Charges operate under a provincially-mandated formula that looks at all of the capital projects intended to support growth of the city, and the degree to which these specifically serve new development as opposed to providing improved service for the existing population and businesses. For example, a new subway line may carry many riders, but it represents better service for a large number of them and only the net new ridership can be claimed as “development related”. This trims a great deal of the city’s capital costs out of the pool on which DCs are based because they are not growth-related.
Once again, the question is whether SmartTrack will provide mainly much improved service for an existing demand and population, or if it can be linked specifically to new growth and to what degree. Services that are improved for the existing population must be funded through general taxes and DCs are only available for growth-related changes.
Development rights on city land come up from time to time as another magical source of revenue, but the many of the city-owned lands along the SmartTrack corridor are either unsuitable for sale as development parcels, are the site of functions that would have to be relocated, possibly with difficulty given that their current location is industrial, or are lands that have already been handed over to Build Toronto for sale (the Eglinton West properties are a prime example). Unlike the oft-cited Hong Kong, the City of Toronto does not own all land and is not in a position to profit from sale or long-term lease as a transit funding mechanism. Yes, there are potential locations where the city and local landowners could co-operate on intensification, but the available revenues would not come close to paying for a multi-billion dollar project.
At this point, the City staff are reviewing their options and will get back to Council in the new year. By then, the actual cost and scope of SmartTrack may be better understood, along with actual funding commitments from Ottawa.
If you have read this far, many thanks. Digesting all of these reports takes time, and yet this is one of Toronto’s most important issues probably in this decade. We wring our hands about the backlog of transit spending, but given a chance we focus on one project that was born of an election tactic and now has the force of a signature Mayoral project.
There is much more to transit in Toronto and the GTHA than SmartTrack, but we must understand what SmartTrack really is to properly set it in place among competing demands of which transit is only one.
Thanks for this. Of course, I already took a swing at FAST’s website and the lobby campaign in general at my site, but I would have never have had the time or the patience to go through what you just did above.
That map of potential transit connections to SmartTrack is very interesting. It assumes both an Eglinton-McCowan alignment for the Scarborough Subway Extension, a project that hasn’t even completed the EA process, and the Eglinton West spur for SmartTrack. The necessity of an express bus on Kennedy with SmartTrack right next door doesn’t make a lot of sense; it’s also quite interesting to see the return of the 18 Caledonia bus (from Yorkdale to a SmartTrack stop at Bloor) when I expect that a lot of the north-south travel, especially south of Eglinton, is headed to the Bloor Subway.
GO’s RER map always bothers me when I see both off-peak service and electrification extend only as far as Bramalea, a spot convenient for GO’s operations, but terrible for most of Brampton’s population. If we can shoehorn a heavy rail operation on Eglinton West through Etobicoke (and I’m not saying we should); there ought to be a way to get frequent trains into Downtown Brampton.
If SmartTrack has to be; I’d much rather see it use the UPX infrastructure to the airport, or operate to Bramalea or to a terminal near Woodbine Racetrack, where there are opportunities for Mississauga, Brampton, York Region and TTC buses and the Finch LRT to connect.
Yes, but what portion of this would come from simply extending the Eglinton LRT as originally planned – all the way to the airport grounds, and the Renforth Gateway? I think the billions supposed for ST should be really be focused where they would likely have a real impact, extending back to the full scope of TransitCity, and building a DRL. Given that Jane is unlikely to be buildable, reverting to a Kipling LRT might still be a viable option, providing north south linkage in the west. Regionally Hurontario LRT, Kipling, along with the existing subway lines, and DRL + Don Mills LRT should provide capacity boost north south, both at and away from the core. Viva next BRT, Finch LRT extended all the way to Yonge, and Sheppard subway/LRT east to Morningside, the Eglinton LRT + Malvern + Mississauga Transitway, and the BDL subway the capacity east west. Link these to GO properly, and ST is not only misguided – but pointless.
If we have the money for SSE, and ST, we should be able to do DRL and at least the Scarborough TransitCity and East Bayfront LRT. I think we should let GO be GO, and just make sure it is properly connected at the stations that are there now – LRT to Agincourt, Guildwood, Mt Dennis, Malton…Better to build a network of smaller projects (other than DRL- which is perforce big) that serve local demand, where we want it. Need to start building continuously, need to be careful to build in the right order, but get moving. Solving the regions transit problems needs to start by ensuring there is capacity into, through and around Toronto, and not just through the core. TransitCity was conceived around the origins and destinations that exist, and the ones that we want to develop, not the industrial lands that needed heavy rail freight access.
This RER proposal to have trains like GO or UPX travel along Eglinton Avenue is NUTS! Trains with their constant bell ringing every few minutes all day all night will drive people crazy. Just ask the poor people along the UPX line now. They can’t sleep. Anybody with half a brain would extend the Eglinton LRT farther west like it was intended to. Unfortunately, some BDM’s (Brain Dead Morons) at Silly Hall sold off the exclusive right-of-way reserved for the Richview Expressway for decades and never built. Now, it will be incredibly disruptive and very expensive to do whatever is built.
LikeLiked by 1 person
No, they do not. The signal system used on GO’s network can support five minute headways (or less) if the signals are sufficiently close together together. What would be needed on the Stouffville line is not be a more advanced signal system, just more signals.
Steve: Yes and no. If the headways get down to a level where some form of automatic train control or management is required as an extra layer, or if corridor constraints require, say, a three track section with trains moving back and forth to an express passing track, then the signalling system becomes more complex. It’s not just a question of a five minute headway and signals that give Spadina Avenue competition for close spacing.
I can’t believe the careless ramblings of a random university professor have derailed decades of transit planning and will cost us billions of dollars. The next time someone like Andre Sorensen has a transit proposal, instead of being polite and deferring to their expertise as a “professor,” we should just treat them like any other transit crank. We should kill bad ideas in the bud instead of letting them fester around. It was an unworkable and impractical idea in 2013, and it’s an unworkable and impractical idea in 2015. Now, despite the fact that the majority of Torontonians voted against SmartTrack and for a downtown relief line, it’s looking really hard to kill. Unless the planning department is willing to die on its own sword by coming out strongly against it or by discovering that it will actually cost $15bn, I don’t think there’s any way to stop it. I really thought Tory was a wily politician who could say one thing on the campaign trail and then do “the right thing” when in power. But he’s being oddly persistent with this SmartTrack thing.
Steve: Actually, I don’t think Andre Sorensen had anything to do with SmartTrack. It was Eric Miller who went on Metro Morning and shilled for Tory’s “A+” transit plan.
LikeLiked by 1 person
Once again, this is excellent work. I couldn’t even begin to address the points you have raised so I’ve just a few thoughts.
1. The offered benefit of Smart Track is the fast connection between employment centres and the core. Frequency and capacity appear to be more variable in their value to potential customers. This is definitely “line on map” planning at its … not worst but definitely most politically driven.
2. By politically driven, I mean that the project seems to have moved ahead (and ahead of the pack) with the displayed assumption that Smart Track *could* be built as proposed. Clearly that wouldn’t be possible without significant costs but we were forced to spend taxpayer money to go through that process anyways by studying the Eglinton West corridor almost before studying Smart Track.
3. If the route via the airport is chosen I do wonder if Smart Track could just stop at the airport, with an express shuttle bus running in between the Airport and the Airport Corporate Centre for all the business travelers while *plans* are made to extend the line to the Airport Corporate Centre.
There has so far been nothing that suggests that a 2 leg trip to the Airport Corporate Centre (via UPEx/Smart Track plus Pearson Shuttle bus, or UPEx/Smart Track + Eglinton Crosstown Phase 2, or for that matter via subway and an Airport Corporate Centre Rocket … or hell, a fare integrated trip using a MiExpress bus) is that much better (or more desirable) than the direct trip that Smart Track. Have you seen any study or comments to this effect?
4. The role of Smart Track in relation to UPEx is going to have to be considered and hard decisions made over the next 2 year. As you said, Smart Track and RER (and in some ways, UPEx) represent the same concept but approached in different ways by different champions (the mayor, the province). It wouldn’t be unreasonable to say that they are … if not two sides of the same coin, then two differently sized mixing bowls that nest together … but with two different chefs arguing over a very similar recipe.
5. It seems that the service plan for Smart Track has become more aggressive and ambitious. This raises obvious questions about corridor capacity, and not just in the Union station corridor. I’m not sure if Metrolinx has abandoned their plan to build a satellite station at Spadina and Front (North Bathurst yard), but it seems clear that if we are going to have a combined service frequency of less than 7 minutes for these downtown rail corridors, tunneling is going to be warranted.
This raises the obvious question of which tunnels and where. Could we be moving to a future with 3 east west tunnels (USRC for the Lakeshore Line, Wellington for Smart Track and Queen or Richmond for the Relief Line?
6. On the Relief Line itself, I think there is far greater opportunity for redevelopment and enhanced development along the RL corridor (both east and west branches and the Long RL option) than the Smart Track corridor. Think of the Studio lands, South Leaside, South Don Mills. I’m wondering why the proponents of Smart Track are so avidly promoting a project that connects to employment centres outside of Toronto (that will increase tax revenue for neighbouring municipalities) while ignoring/delaying a project that could bring significant revenue to Toronto.
7. On a related note … have there been any comparisons of the costs+benefits of Smart Track vs the cost+benefits of extending the Bloor-Danforth line to Renforth and Eglinton (MACC) and building phase 2 of the Crosstown LRT? I have that costs would be comparable (if using the $8-billion estimate for Smart Track) but I feel there would be far more significant benefits from investing in subway+LRT. As a MiWay user, I know that 17 MiWay routes (including branches) make trips to and from Islington every day and there are 10 TTC routes operating out of Kipling. If, say, 24 of those 27 routes (including branches) could be split up among stations at Dundas/427, Burnhamthorpe/427 and Renforth/Eglinton there would be significant reductions in bus traffic and car traffic along Dundas (including through the village of Islington) and more opportunities for development of lands in and along that extended subway corridor. Again, this would be with far greater development and potential than the oft talked about extension to Sherway Gardens, and in Toronto rather than in Mississauga.
Finally may I presume that you will be at Executive Committee on Tuesday?
Steve: You want to actually compare cost/benefit numbers for SmartTrack? What are you, some kind of wild-eyed radical? It is our manifest destiny! The greatest plan in the universe! It will solve poverty, hunger, unemployment and we won’t have to build anything else, anywhere. No, nobody has looked at a BD line to Renforth. There has not been any such line in the plans since the LRT line that was to run from Kipling Station to the airport, a western equivalent of the Scarborough LRT.
Yes I will be at Executive, if only to see just how deeply the BS piles up on the floor.
I’m also a little worried about this “GTAModel V4” simulation too. As a computer scientist, I think it sounds really cool. But at the same time, the fact that it works at a fine-grained level and requires “calibration” suggests that there might be too many assumptions and tuning parameters for the simulation, and the results will be too unstable to be accurate. I’m worried that politicians will assume that because the model is more complex that it will be better, when in actuality, it means there’s more room to “fudge” the parameters to get it to say whatever you want. Based on the papers describing the simulation, it seems that the civil engineering definition of “validating a computer simulation” seems much weaker than the computer science definition of “validating a computer simulation.”
Steve: I too do not entirely trust the new model, although there was plenty of room to screw around with the old one too — that’s how we got very high projected demand for the Sheppard Subway. If it’s any consolation, there is supposed to be a peer review of the model which I’m sure will work out well. The idea that we are finally building a model for more than core oriented AM peak flows, and that has a granularity that should work for transit, not just for expressways, is long overdue.
The challenge lies in assumptions about future growth and where it will occur. As I said in the article, having this work done by a company whose principal member claimed that downtown development was dead and designed SmartTrack to serve the presumed suburban growth, leads to the possibility of an invalid land-use, population and employment model going into the simulations. Garbage in, garbage out.
SmartTrack’s station profile for Unilever Station says:
During the campaign Tory said
Considering that ST is supposedly relying on that development to fund the city’s share of the line, dropping (potential, eventual) job numbers are not helpful.
Steve: The plans for the Unilever site did call for 50-70k jobs eventually on a 30 year buildout, but it is unlikely we would see that all in one go as the market has to absorb this and a lot of competing development closer to the core.
If the signals get closer together, like on the subway, then the system has to be able to provide multiple block protection in front of the train rather than 2 block protection in case a 12,000 foot freight needs to detour over the route. That requires a more advanced system. What, you say a 12,000 foot freight will never operate on the Stouffville line, true, but it could operate on the Lakeshore under trackage rights retained by CN and I believe by CP on the west end. Your mistake is that you are thinking like a logical rational human being. Transport Canada rules do not fall into this category when it comes to operating a commuter service on rail lines.
Union Station does not have the platform capacity for that many trains. With double berthing, stopping 2 trains on each platform and turning them back from where they came they can accommodate 4 trains per hour per platform in each direction. I am not sure of the number of platforms for GO but if it is 10 then they can run 40 trains per hour to the east and to the west. There are 4 lines to the west so in theory you could run 10 trains per hour per line or a 6 minute headway in each direction. The problem is that the throat trackage to the west cannot handle that number of trains and the platforms cannot handle that number of passengers.
A train every 6 minutes does not sound like a lot but when you try to operate it for a full rush hour using railway rules you are going to need a much more robust signalling and switching system that probably entails automatic train control. It would be no problem if it were 4 rapid transit lines running on their own right of way but it is, unfortunately, using railway rules; don’t forget that hypothetical 12,000 foot freight train that might, someday, need to be accommodated.
Nice work Steve, amazing the amount of work you have put into it.
Steve: Thank you! This is an important issue, and full understanding is essential to an informed debate.
LikeLiked by 1 person
Is there a detailed estimate of how much any of the SmartTrack options would cost anywhere in the report?
Steve: No. This is subject to more detailed work on these options, supposedly due early in 2016. The preliminary $8-billion estimate is a very back-of-the-envelope calculation done by the campaign advisors.
The infeasible Eglinton heavy rail option must be prohibitively expensive, given the need to accommodate 12-car GO trains. The option 2B which goes to the airport and Airport Corporate Centre (presumably replacing the UP Express though the report won’t admit this) is expensive but probably feasible. This would probably be comparable in cost to the spur that the Heathrow Express uses. The Eglinton LRT is by far the cheapest option.
A lot of the cost is the electrification of the Kitchener and Stouffville lines, which the province is paying for anyway.
Steve: Actually, there are probably substantial costs to provide additional capacity on the line (trackage, etc), not just the electrification.
A superb and very damning review! In any city where transit planning was carried out by grown-ups, this new report would be the death knell for SmartTrack, but of course, this is Toronto, and we do things differently here.
I see Mayor Tory is off to London shortly to take a peek at Crossrail 1. This bears about as much resemblance to Smart Track as the Wright Brothers biplane bears to the Space Station, but he may learn one or two things even so: first, big transit projects take a lot of time; and second, they cost a lot of money. SmartTrack as proposed is wildly underestimating both.
With signals you also gotta worry about real 100 mph VIA trains more then that hypothetical 12,000 foot freight train that might show up .
I think that 100 mph (160 km/h) VIA trains are, unfortunately, more hypothetical that the 12,000 foot freights. There have bee longer freights out west and I think one was on CP. Because of retained trackage rights all the lines that Metrolinx bought need to be able to handle them. The Weston Sub (Kitchener line east of Bramalea still sees a couple of freight trains a day. I would love to see fast VIA trains but I doubt I will ever see one again.
What is that Robert something like 155 cars and 5 -7 locomotives? I know I regularly see trains in the 100 car(+) range. I have been at crossings waiting for a train go by that took quite a while at 20-50 km, and 12000 feet is only about 3.6km, trains of at least 1600 metres would not be rare.
VIA cracks 100mph at a couple points on the Windsor trains via Brantford. Mainly in the GTA, and near Dundas (the town).
The number of cars depends on car length. It is 135 89′ cars or 300 40′ cars. Long trains usually have distributed power. I have seen long CP freights west of Thunder bay with 2 engines on the head end, 2 in the train and sometimes one at the rear.
I live on the Kitchener line where VIA is lucky to hit 60 mph. I don’t think Metrolinx will need to build a signal system for 100 mph trains where they are trying to run a 5 minute service. They do, however, need to accommodate those hypothetical freights because they do exist.
There can easily be 10 GO trains in one rush hour in one direction between Scarborough station and Union on the Kingston sub . That’s an average of 6 mins between GO trains and VIA trains do go 100 mph on the Kingston sub at that location . A 10 coach VIA train with a loco at each end at 100 mph is alot of kenetic energy . With no ATC the signals better have long advance warning and passenger trains should have strong buff strength .
What’s the likelihood they will just do the sane/obvious thing and deal with Eglinton West simply by extending the LRT at-grade for a fraction of the cost?
Steve: I think that is where Metrolinx has been quietly heading for some time, but who knows what political machinations will intervene.
According to GO’s schedules there are a maximum of 6 Lakeshore trains and 2 Stouffville train on the line at one time and it uses TWO tracks in the peak direction. There are NO VIA trains in the a.m. rush hour, 7:00 to 9:00 a.m. and one in the p.m. at 17:00. I will have to check into the speed of VIA at Scarborough station. If there are 10 trains it is because the service is screwed up again.
You are right, a 10 car train with 2 locomotives does have a lot of kinetic energy, which is why I find it hard to believe it would travel that fast through a station area but it might.
I mistakenly said:
I should have said:
According to GO’s schedules there are a maximum of 6 Lakeshore trains and 2 Stouffville train on the line IN THE PEAK HOUR and THEY use TWO tracks in the peak direction. There are NO VIA trains in the a.m. rush hour, 7:00 to 9:00 a.m. and one in the p.m. at 17:00.
@383 on the tree
VIA doesn’t run 10 coach trains in the corridor. Longest you’ll see is 8 cars, Sunday nights on the Brantford section of Toronto-Windsor. There are sometimes 8 car trains on the Kitchener section on holidays. Most corridor trains are 4 cars long, occasionally 5.
Rule 107 doesn’t apply at GO stations since passengers are (ostensibly) prevented from accessing a track not adjacent to their platform with a physical barrier and tunnels or bridges are provided so that passengers can change platforms. So yes they can speed through. They do so at many Lakeshore West stations as well, as do GO expresses and dead heading trains.
Steve, are there any stats out on how many of those $60 stickers they’ve sold that lets Metropass users travel on GO between Exhibition and Danforth stations? This would give insight into both the attractiveness of this kind of mode transfer, as well as what sort of success an integrated fare system with premium pricing for fast services (as discussed in your fare integration review post) would have with actual riders.
Steve: Sales have been extremely low. There was a report on this in July, and I have heard nothing to suggest things have improved since then.
I believe that this was the rule that required all trains to slow down in stations where there was more than 1 track and passengers could walk across one track to get to the outer track. I believe this still happens in Brantford and other stations but I haven’t checked lately. Rule 107 does not apply because GO put up the low fences between tracks and the underpasses to get around this so trains can pass through at speed. My question is do they do 100 mph or are they restricted to 79?
So back to the original statement of 383onthetree:
When and where does GO run 10 trains in a one hour period in one direction along with any VIA trains let alone ones doing 100 mph? Check the schedule and tell me when are there 10 GO trains between Scarborough and Union in the same rush hour with out adding the Richmond Hill stations which come in for the last bit. If I make the area long enough I can have 10 trains in one hour per directions but the more telling metric is how many trains past a point per hour per track? It is nowhere near 10. If VIA trains are actually doing 100 mph along this section it is not in the rush hour because there are not any.
Since there are actually only 8 trains in the peak hour and since they are usually using two tracks inbound that is 15 minutes between trains per track on average. There are times when GO trains are only 6 minutes apart but that is usually only for a short period of time as the front one will usually run express or take a different track. It is easy to make statements; it requires some work to check on their accuracy before making them. I checked the published GO and VIA schedules to determine the information that I published. Does GO ever run 10 trains in a hour? It probably happens when there is a problem but I doubt that it is planned that way.
I’m not sure. My estimates come from the time it takes to go between certain concession lines ~1 mile apart.
I should bring a GPS on board to check
That is a very rough method of estimating speed. At 100 mph a mile goes by in 36 sec, at 95 it takes about 38 sec at 90 it takes 40 sec. Any error in time or distance will make a major error in calculated speed. Railway crews used to have a table that gave the times to complete a mile and/or a 1/4 mile so they could time the mileposts and verify the speed of the speedometers. If they were speeding because the speedometer was wrong that was their fault. There were 40 telegraph poles per mile or 10 per 1/4 mile, 132′ apart. Unfortunately most of the poles are history but they still have the mile posts. Accurately measure the time to cover a mile in seconds and divide the number into 3600 to get the speed in mph, or take a GPS along, but that is so high tech when a stop watch will do.
I’d like to see Smart Track abandoned, after it is recognized that the good parts of it are already part of RER.
I’d like to see the Queen’s Quay East streetcar built. What if it didn’t terminate at Parliament, what if it went all the way to the Unilever site?
Would a dedicated streetcar, from Union to Unilever provide enough capacity for all the new riders going to and from that site? Would it be faster for them than taking a King streetcar or Queen streetcar?
Steve: Getting to Unilever/Great Gulf requires road realignment east of Parliament that is part of the next phase of waterfront work, particularly on the Don Mouth reconfiguration. However, we should not wait for that, but at least get the Union-to-Parliament leg (including the most complex piece, the work at Union) underway. As for Unilever, there are several proposed services recognizing that people will come there from many locations: Broadview Avenue extension including streetcars (making a connection to the Danforth subway), SmartTrack and/or GO/RER service on the rail corridor, possibly the east leg of the DRL depending on its alignment. The streetcars cannot handle this site all on their own, but are a necessary part of the eastern waterfront network.
There is a curtain of view blocking condos planned along the south side of Queens Quay. Three roads are planned for the condos, each with a stop light, that will slow down the streetcars. I think I mentioned this before. It seems to me that, with only a little bit more work, the developers could have been told they had to share entrance and exit ramps to their underground garages, and that they had to place their ramps north of the streetcar right of way, so that they only needed one road crossing the streetcar tracks.
The developers have begun excavating the underground garage for the first of these condos. It seems to me that underground access to the underground garages wouldn’t be much more work. Given that they are tearing up the whole block they could use cut and cover. That would make for just four stop lights between Union and Unilever, The Don Roadway, Cherry, Parliament, and the new service road for the condos.
I figured the extra precision of a stopwatch wouldn’t really help since the concession lines in Mississauga, Oakville and Burlington have wandered a little over the years, surveyors make mistakes and at such speeds its tough to get the exact time that you pass over the road centre line.
If you or anyone else are going to make the claim that trains are travelling at 100 mph when I know they aren’t or that there are “easily 10 GO trains per hour” (not you) when I know they aren’t, then be prepared to have your claims received with a lot of doubt. There are still mile posts if you know where to look and hand held GPSs are common and some of the new tablets have them built in. Before anyone makes these claims please check the facts and schedules. A 2 second error is the difference between 95 and 100 mph.
If we are going to have a reasoned debate then we need to deal with facts and not suppositions.
Steve: I might add that people really need to stay in one measurement system. Mileposts are called that for a reason. It is easy to slip between 100 “kph” and “mph” without noticing, and there’s a huge difference.
Here’s my attempt to wiggle out of being in the wrong. Despite being wrong (all estimates are wrong) saying that the Via goes 100 is nonetheless useful. In the preliminary stages of designing are you going to fuss over 95 vs 100? Those details will be worked out later in the game by someone with more information than me, but they will not be shopping around for an 80mph setup. Seeing as this blog is very much concerned with projects in their nascent stage, I thought it was a useful reminder that VIA’s equipment does speed through the GTA west.
Now here comes the admission of guilt: I asked the conductor (service manager, whatever) on my train today and he says the fastest he’s seen the train go is 93…
This is a very good article. Thanks for writing this.
FWIW, I’ve been writing a series of GO articles for local consumption:
Major GO Construction For Hamilton (talks about RER; the topic matter of your article)
All-Day Weekend GO Service Possible 2016 (via Niagara seasonal GO trains stopping at West Harbour)
I have a GPS speedometer app on my iPhone and have confirmed moments of consistent 143kph (90mph) for a 1-locomotive 12-car bilevel express train that was running late. The railroad speed limit is 90mph. So they definitely CAN go that fast. Also, vegata_skyline on urbantoronto forums is a GO driver, who has some very interesting data.
Also, there was a PanAm West Harbour Express GO train that left half an hour late but made it to West Harbour GO in only about 45 minutes. It zoomed past Burlington GO only 30 minutes after leaving Union. I watched this train on gotracker.ca in real-time. This may have very well broke the record for a 1-locomotive 12-car bilevel diesel GO train Union-to-Hamilton in just 47 minutes.
See Urban Toronto: here, here and here.
There was a different thread where a GO train driver posted maximum speeds he was able to pass a GO station (in express mode). Also, GO trains typically are able to enter a station at 70kph+ and brake to a full stop in one train length by the end of the platform. He said the record was ~103kph (for an empty train that braked well on some slight incline).
There is an /absurd/ amount of padding in GO schedules, to make sure they are reliably on time.
It is helpful to say that the system should be designed for 100 mph or even 160 but it is not useful to say the current signal system will handle the speed and capacity stated when the clearly don’t. A good system should be able to handle short periods of overload but to design schedules for that overloaded state removes the ability of the system to be able to make up time when needed.
Remember that kinetic energy varies as the square of the speed. The square of 90 is 8100 while the square of 100 is 10,000. That is almost 24% more energy required along with more time to accelerate and stop. I hope that the people who want to put all those stops on existing GO lines to serve the 416 will limit the top speed and greatly increase travel time.
There are two reasons for the padding in the schedule:
1) to get a schedule that is regular, always at the number of minutes after the hour.
2) to get the trains back on schedule after a delay. It is not as easy to short turn a GO train as it is a bus or streetcar.
When I read this, I originally thought of a cute & glib answer – just move the Toronto boundary to include these areas. Problem solved!
Then I started thinking, maybe this really is the answer.
After all, the City of Toronto has been expanding its boundaries for over a hundred years. A century ago, the city merged in a host of towns and villages on its border. Within my living memory, Toronto has had two sets of amalgamations of the boroughs within Metro Toronto plus the inclusion of the Rouge-Port Union area from Pickering. As well, Mississauga, Caledon and today’s Brampton were created from villages and townships in the 1970’s to make Peel Region. Likewise York Region, Durham Region, and Halton Region.
That Pearson Toronto International Airport lies outside Toronto proper is a geographical anomaly, mitigated only by the fact that Mississauga is considered to be part of the Greater Toronto Area.
In the Malton area, I would incorporate into Toronto that triangular area which lies east of Airport Road, west of Hwy 427, and south of Hwy. 407. (407 is a real physical barrier, which lies just north of Steeles Avenue.) The “M” in MACC would henceforth represent Malton, not Mississauga.
Similarly, in the east, move the Toronto boundary to Hwy. 407.
I am sure that the property owners within these two areas will not object when they see their municipal taxes go down!
I am only suggesting this IF, and this is a long shot, IF SmartTrack really does get built out into these 905 enclaves.
In the case of the MACC (Malton Airport Corporate Centre), the “surface subway” heavy rail line along Eglinton Avenue is unlikely for reasons obvious to most people, but alternative routes are shaky, too.
UPX has taken up rail corridor capacity, and rejigging UPX is also a difficult proposition. An Eglinton West LRT extension or a Finch West LRT at TTC fares to serve MACC makes the most sense. My opinion.
For clarification as well, those stopping distance also increase – based on energy. So a truck from 60mph can be expected to stop in 180 feet, from 70mph 245 feet or 36% increase in distance for a 17% increase in speed. Train stopping distances being much longer. So if you are looking at adding a lot of stops, and trying to increase speed, you are basically massively increasing the wear on trains, as they will essentially be spending much, much longer in either braking or acceleration phases.
Also to get significant benefit from this, requires there to be a substantial increase in the number of people who would benefit from the stops – ie available capacity. How about we work out where we can run the trains to, add the tracks, and serve the existing stops with greater frequency first. Heavy rail is a question way of supporting local demand, and this really should be served with a transit not subject to TC regulations for heavy rail.
Steve: You also reach a point where the stops are so close together that getting up to a higher theoretical top speed is of no benefit to local service.
Wait a second, that map from page 23 of the presentation is not Sheppard/Neilson to Union Station but instead Finch/Neilson to Union Station. The route map there is actually the 39 Finch East. Whoever made that map should be shamed.
Steve: Ah yes! The map is wrong, but the running time cited from Sheppard to STC is correct, and so at least the trip time comparison is not askew.
West of Renforth, the north side of Eglinton is part of Mississauga while the south side (out to Etobicoke Creek) is part of Toronto. It will be interesting to see the City of Mississauga wiggle out of any calls for them to contribute to Smart Track by pointing out that the Mississauga Airport Corporate Centre (I notice that John Tory only started adding the ‘M’ last week or a bit earlier) by pointing out that a significant majority (2/3 to 3/4) of the Renforth Gateway station catchment area is in Toronto.
Steve: There is, however, the small matter of Markham.
Combine the GO route scheduals of the Uxbridge line and Kingston line including that many trains don’t stop at Scarborough and it adds up to a lot of trains towards Union at rush hour . There are 3 main tracks and trains traveling the opposite direction too . Add service delays or bunched up trains and you may see trains running closer . A time card a few years old did show at least a 90 mph track speed . Of course if every trains gets more restricted signals at that time none SHOULD be traveling that fast . A VIA train can in fact sometimes hit 110 mph even if it is speeding , that fact that it can .
The point tho is that the buff strength has to be strong enough for a worse case scenario even tho most GO trains are slugs most of the time. A train running a Stop signal at crossovers, rear ending, head on or deraling . VIA trains travel the opposite direction on the next track over at 90 mph at morning rush . So just removing freight trains should NOT relieve passenger trains from not meeting FRA buff strength . TTC subways never reach these high speeds nor level crossings or risk hitting a 90+ mph VIA (or GO) train .
The railways use miles for distance and speed , not km so no mistake there .
LikeLiked by 1 person
The VIA schedule has a train eastbound out of Union at 6:40 with the next one at 9:20. The first inbound VIA train arrives at 8:25 which is after most of the rush hour trains have finished. It leaves Guildwood at 7:59 which means the GO locals are 20 minutes before or 12 minutes after it. As VIA takes 26 minutes express and GO takes 29 minutes making all stops I doubt that it is getting anywhere near 90 let alone 110 mph. There are 6 Lakeshore and 3 Stouffville trains arriving in the peak hour with 1 VIA train for a total of 10 trains on 2 tracks inbound and 1 outbound.
I fail to understand the point of your post: There is only one VIA train, not trains, in the morning rush and since its time is only slightly better than the GO locals it is probably not travelling near 90 mph. Especially since it is only 12.3 miles so the average speed is under 30 mph. Yes buff loading strengths are high; they can be found here. This is a US document but US and Canadian spec are similar. See section 238.203 Static end strength.
Are you saying that we won’t get rid of the TC buff loading requirements? I can agree with that. If you want to know the speed, ride the rain and look for the signs along the right of way. They can be many shapes. If there is only 1 number it is the speed, in mph, for all trains. If there are two numbers the top is passenger and the bottom is freight. If there are 3 then the top is LRC passenger, the middle the rest of the passengers and the bottoms is the freight speed. Note that these are maximum speeds and the trains may operate at lower speeds, especially if they stop a lot. Most locomotives have an overspeed trip that varies by the type of service and gearing of the train. It is not as easy to by-pass these as it was with older engines so I doubt, but don’t know for sure, if VIA’s trains can hit 110 mph. Though I was on a CN transcontinental in 1967 going west into Winnipeg 23 hours late clipping off mile posts in 33 seconds.