Scarborough Subway Ridership and Development Charges

The Star’s Jennifer Pagliaro reports that City Council has approved a confidential settlement with BILD, the Building Industry and Land Development Association, to avoid an Ontario Municipal Board hearing that could lead to rejection of the Bylaw implementing the Development Charges intended to pay for the Scarborough Subway. The matter was before Council in confidential session on June 7, 2016.

Staff miscalculations on the ridership of the Scarborough subway will leave taxpayers on the hook for millions more, after city council voted to settle a dispute with developers.

According to a secret report before council on Tuesday, the contents of which were shared with the Star, the city’s lawyers advised councillors to accept a settlement with the group representing developers, the Building Industry and Land Development Association (BILD).

The settlement, which reduces the amount builders will have to pony up to help finance the subway, is expected to cost the city as much as $6 million in lost revenues.

If the settlement is for only $6 million, the City should consider itself lucky because the calculation underlying the DCs is based on flawed ridership estimates and an out of date network design. Moreover, the original authorization appears to double count subway revenue with both a special Scarborough Subway Tax and Development Charges to recover the same costs.

Recent news of a 50% reduction in expected Scarborough Subway ridership from 14,100 to 7,300 passengers in the AM peak hour reignited political debate on the viability of the subway scheme. However, these numbers are not just hypothetical indicators of how the line might perform, they are integral to the calculation of Development Charges (DCs) that would help to fund the City’s share of this project.

See also my previous articles:

The formula to calculate development charges is complex, but at its heart is one key measure: how much of a new transit project will benefit existing properties versus future development. If the primary role of a new subway is to improve the lot of current riders, then only a minority of its cost can be recouped by DCs (and thus from future purchasers of new properties).

Toronto allocates DCs on a city-wide basis rather than assigning each project only to the neighbourhoods it will directly serve. These charges already help pay for many projects as shown in the introduction to the study establishing the level of new charges for the SSE.

The Council of the City of Toronto passed a Development Charges (DC) By-law, By-law 1347-2013 in October 2013, for the recovery of capital costs associated with meeting the increased needs arising from development. The effective date of the Bylaw was November 1, 2013. The recovery of DCs is on a City-wide basis and relates to a wide range of eligible City services:

  • Spadina Subway Extension
  • Transit
  • Roads and Related
  • Water
  • Sanitary Sewer
  • Storm Water Management
  • Parks and Recreation
  • Library
  • Subsidized Housing
  • Police
  • Fire
  • Emergency Medical Services
  • Development-Related Studies
  • Civic Improvements
  • Child Care
  • Health
  • Pedestrian Infrastructure

For commercial property, there is some justification to this because increased mobility makes travel to jobs simpler well beyond the location of any one project. For example, the Scarborough Subway might be held out as a way to stimulate growth at the Town Centre, but it would also reduce commute times to other parts of Toronto, notably downtown.

For residential property, especially for the large proportion of new development downtown, this link is less clear, and DCs on new condos can wind up funding transit projects of little benefit to the new residents.

This split is part of the eternal battle between sharing the cost of public services across the city and charging them locally or by user group.

In the case of the Scarborough Subway Extension (SSE), the split between new and existing beneficiaries was determined by the change in ridership projected with the subway project. The benefit was allocated 61% to new development and 39% to existing riders. The ratio is high because, at the time of the calculation, the projected peak hour ridership for the SSE was estimated at 14,100 compared with a base value of 5,500. Both of these numbers are suspect.

The base value was factored up from actual SRT ridership of 4,000 per hour to 5,500 to represent the load the subway would have had were it to exist in 2015. That value of 4,000 is equivalent to a load of about 240 per train when the peak service was 17.14 trains/hour (3’30” headway) as in 2012. However, by 2013 service had been cut to 13.33 trains/hour (4’30” headway) to reduce equipment requirements on the aging line. That is the service operating today, although a further cut to 12 trains/hour (5’00” headway) is planned for June 20, 2016. Some of the demand that would be on the SRT travels via alternate routes, some is packed into fewer trains, and some has probably been lost to the TTC. What the ridership might be today were the RT not capacity constrained is hard to tell, but it should certainly be higher.

The high value for future subway ridership combines with the low value for presumed current demand to load much of the SSE’s cost onto new development.

The situation is complicated by two competing ridership estimates:

The contexts for the three estimates differ, and this goes some way to explaining why the numbers are so far apart:

  • A line to Sheppard will attract more ridership than one ending at the STC.
  • A subway station at Sheppard, in the absence of improvements to the GO corridor such as RER and SmartTrack, will attract ridership from Markham just as Finch Station does from the Yonge corridor north of Steeles.
  • Removal of the station at Lawrence East, coupled with new GO corridor services, will reduce demand on the subway.

There is no guarantee that the land use, job and population assumptions underlying the three estimates are the same, especially when the highest number was produced in the context of boosting the importance of STC as a growth centre.

What we are left with, however, is the likelihood that the level of DCs allocated for the Scarborough Subway project were based on the most optimistic scenario for new ridership, and a network configuration quite different from what will actually be built. If the calculation had been done on the basis of lower ridership numbers, the DC revenue available to fund the Scarborough Subway would have been considerably lower.

Continue reading

A Cat’s Cradle of Transit Plans (Updated)

Updated June 6, 2016 at 11:30 pm: The chart of the demand profile for the Eglinton East LRT has been updated by City Planning to correct an error in labelling where inbound and outblound values were reversed. The new chart has been placed into this post, and the link to the source pdf has been updated below.

Public consultation sessions are coming to an end on the “motherlode” of transit projects (as they were described earlier this year by Toronto’s Chief Planner, Jennifer Keesmaat). This process will soon bring a consolidated set of reports and recommendations for Council. So far, the presentations have been subdivided between various projects.

A major challenge for politicians, the media and the general public is to sort out all of these schemes and to understand how they all fit together. This is not just a question of how we will finance all of the projects, but of how each project and the choices made for it will affect everything else. Where typical studies in Toronto might have wrestled with whether a new line should go under street “A” or “B”, and where the stations might be located, today’s work requires understanding of how the network will evolve over time and how it will work as a whole in a few decades.

The process is complicated further by having municipal (City Planning & TTC) and provincial (Metrolinx) components, and the secretive nature of Metrolinx studies means that some vital information about its projects is not yet public. The Metrolinx reports are expected to appear on their Board’s agenda for June 28, and this implies public availability sometime in the preceding week.

The consolidated City reports should be available on June 21 when a briefing session is to occur at City Hall a week before the June 28 Executive Committee meeting.

Continue reading

A Boost for the Relief Line

This afternoon, June 1, there was a small miracle at the TTC’s Greenwood Yard. Assorted politicians and transit management gathered for an announcement of transit funding, of new transit funding, and for that perpetual orphan of Toronto’s political scene, the (Downtown) Relief Line.

Steven Del Duca, Ontario’s Minister of Transportation, announced that Metrolinx would be given “more than $150 million” to work with the City and the TTC on advancing planning and design for the Relief Subway Line to bring it to “shovel ready” status.

This is a substantial commitment of financial support, but more importantly of political support. Del Duca was joined by Mayor John Tory in singing the Relief Line’s praises as a necessary part of growing capacity on the transit network building out from earlier improvements through GO/RER and SmartTrack.

According to Chief Planner Jennifer Keesmaat (whose Twitter session is in progress as I write this), study of the RL will focus initially on Phase 1 (Danforth to downtown), but will then shift to the northern and western extensions. The northern extension is of particular importance because, according to Metrolinx demand projections, it will have a major effect in offloading demand from the Yonge Subway and the Bloor-Yonge interchange.

RLUpdateProjectedDemand_P31

[Source: Metrolinx Yonge Relief Network Study p. 31]

With both the Mayor and Queen’s Park supporting the RL, and with provincial funding of the design work, the Toronto City Council gridlock over transit priorities can be “relieved” for at least a few years. The RL will not have to compete with other schemes for City funding, and with Metrolinx holding the purse, Council will not be able to divert the money to pet “relief” lines for suburban Councillors. Indeed, the whole suburbs-vs-downtown argument, which is born in part by a desire to be at the front of the line, need not pollute the RL study.

The Metrolinx role is also important because the RL (aka the “Don Mills Subway” to many on this site) needs time to be presented for what it can do for suburban Toronto were it to run north at least to Sheppard & Don Mills via Thorncliffe Park. Many riders would have a completely new route to downtown comparable to the service now provided by the Spadina Subway, and this would be completely separate from the existing congested system. Capacity released on the Yonge line would be available to riders from the proposed Richmond Hill subway extension, and the reduction of transfer traffic at Bloor-Yonge could eliminate the need for an extremely expensive and complicated expansion of platform and circulation capacity there offsetting some of the Relief Line’s cost.

Del Duca acknowledged the considerable work already done by the City and TTC on this file. Indeed, had it not been for the TTC’s Andy Byford with support from City Planning raising the alarm about the need for a Relief Line, nothing would have happened.

Some comparatively short term improvements will provide “relief” on the Yonge line, but these will be backfilled by pent up demand over the next decade.

RLUpdateCapacityChart_P20

[Source: Metrolinx Yonge Relief Network Study p. 20]

Smart Track may shave another small amount off of this, but notwithstanding the Mayor’s enthusiasm, the City’s own demand projections published as part of the Scarborough studies show that SmartTrack has a very small effect at Bloor-Yonge.

Tory is still somewhat confused about just what Smart Track’s effect will be considering how much it has been scaled back since his election campaign. He was happy to talk about track work now in progress in Scarborough (on the Stouffville corridor) as being part of Smart Track, when in fact it is the double-tracking work for improved GO service that was in the works before he even ran for office. And he still talks of this as if it were an $8 billion project when a great deal has been lopped off of the project’s scope.

Finally, the TTC CEO Andy Byford is happy just to see money coming his way from all three governments on both the capital and operating sides (although, the latter more grudgingly from the City).

As for construction, that’s still some years off, and it will be important to think of the project in phases, not as one megaproject. It will take five to six years to get to “shovel ready” status, and the issue then is how quickly we want to build the line. A lot of transit capital planning lately has been hostage to constrained finances at both the City and at Queen’s Park. By the early 2020s, the Scarborough subway project should be winding down and spending can shift to the Relief Line.

Now in all this excitement, if only someone would treat other orphaned projects like the Waterfront and Sheppard LRTs seriously.

Why Are Subway Cars on Bloor-Danforth So Dirty?

As a regular traveller on the Bloor-Danforth subway (Line 2), I cannot help noticing how often a car will appear with a very grimy exterior. Although inside the cars look just fine, the exterior can leave much to be desired. The comparison is quite striking with the gleaming trains on Yonge-University-Spadina (Line 1).

It turns out that this problem is caused by a combination of factors including the fact that the BD trains (the T1 sets) are riveted aluminum, while the YUS trains (the newer TR sets) are welded stainless steel.

I asked the TTC about this issue, especially considering how important system cleanliness is in their attempt to present a good face to customers, and they replied:

You’re correct that some of the T1 cars are not as clean as we like.

There are a number of factors in play here.

Trains are not washed regularly through the winter when the ground temperature drops below a certain point. Every winter, it follows that the trains become less clean. We do wash trains mechanically but it is less effective.

Each summer we employ summer students to hand wash the trains using detergent and pressure washers. They can do a train or so a day. They look pretty good, but with the condition of the body and its design –  it takes time.

Chemicals used also make the aluminium more porous and so we have to be careful how much we use, or we potentially make the issue worse over time as the body will attract even more dirt.

The work is made more difficult due to the number of rivets used on the sides of the train. You can see more staining around the doors in general where the normal train wash (think of a car wash for trains) just doesn’t get into these nooks and crannies. On the TR we designed this dirt trap out by the smooth car body.

The students have started work and you’ll see a gradual improvement in the fleet. That said, progress will be slower this year as we are using them to clean also air filters on the trains’ heating system which whilst invisible to customers needs doing across the fleet and is a higher priority.

We will be targeting the worst units first, and working through the fleet on a priority basis.

[Email from Mike Palmer, Deputy Chief Operating Officer, TTC, April 19, 2016]

The T1s will be with us for many years as they are only about 15 years old. TTC has had aluminum bodied cars for decades, and I hope that they can maintain some semblance of cleanliness with this fleet.

Toronto Council Endorses Transit Plan, Seeks Background Details

At its meeting of March 31, 2016, Toronto Council passed several motions relating to the proposed rapid transit plan for the city.These evolved first as a set of staff recommendations, then amendments at the Executive Committee and finally amendments at Council. The changes along the way give a sense of how the attempt at a general approach taken in the new transit plan by staff can be warped into an emphasis on individual projects while losing sight of the overall purpose. This is not new in Toronto’s political theatre, but the city and region are at a crucial time when the “big picture” of the transportation network is essential. The challenge for those who would lead this process is to find a responsible balance between wider priorities and local concerns without making every decision only on political merits.

Many of these motions involve requests for additional reports, and at one point there was some concern about whether city staff could actually handle the workload. One might ask whether the city should be making such important decisions if staff are unable to produce sufficient background material and simply want approval trusting their recommendations. While studying issues to death is a well-known delay tactic, rushing decisions without all the details is a classic method of railroading through decisions the city might regret later. There is certainly nothing wrong with asking for a more thorough study of items that have been omitted, provided that the same requests do not surface over and over again.

If anything, Council has been woefully underinformed on transit options, priorities and tradeoffs, and such an environment “debate” often has little to do with the real world. Will every Councillor read every page of every study? No, but at least the material will be there to answer questions, support the good ideas and counter the dubious schemes. We hear a lot about “evidence based planning”, but this can be a double-edged sword where “evidence” might not support fondly-held proposals.

This article groups Council’s motions by topic so that readers do not have to sort through the relationship of recommendations and amendments.

Continue reading

TTC Board Meeting Follow-Up: March 23, 2016

The TTC Board met on March 23. In earlier articles, I have already reviewed the agenda, and discussed ridership statistics.

Arising from the debate on ridership, the Board passed a motion to revisit the whole issue of actively pursuing ridership growth. The motion by Commissioner Shelley Carroll reads:

That TTC staff report back to the Commission by the third quarter of 2016 with a development plan for a comprehensive multi-year strategy to address current ridership stagnation and to achieve a steady rate of ridership growth annually thereafter.

This is particularly important going into the 2017 budget year when there will be pressure to accommodate both the start of new expenses for the Spadina subway extension (TYSSE) and strong growth in the Wheel-Trans budget. Debates and decisions about which options might be pursued to improve transit and attract riders need to have more background than the annual need for politicians to have something to announce. At the very least, changes should be thought out with specific benefits beyond the photo ops.

Continue reading

A Few Questions About “Emerging Transit Plans”

At the February TTC Board meeting, Chief Planner Jennifer Keesmaat took the Board through the road show presentation she and her staff have been taking around Toronto with the proposed new Toronto transit plan. This issue was held over to the March Board meeting because, for procedural reasons, there were limited questions in February.

One major issue here is that the body actually charged with setting transit policy, the TTC Board, was being briefed on a plan they had not seen before, and to which they had given no input or direction. This is only partly explainable by the fact that any long-term transportation plan would form part of the city’s Official Plan, and the Planning Department “owns” that document. However, one would hope that members of the TTC Board would have at least a passing familiarity with what was in the works. This situation is complicated by the presence of “citizen” members who are not also Councillors and are not part of the information flow, such as it is, at City Hall.

The plan and supporting reports will go to City Council a week after the TTC meeting.

A major problem, of course, is that “planning” in Toronto consists of catering to the whims of the Mayor, influential Councillors, the Minister of Transportation (and his government), and senior members of the government caucus. To describe planning in this context as unbiased and purely “evidence based” is something of a stretch.

That said, the situation is better today than in recent years because, at least, all of the proposals are on the table at once, and it is more difficult to dress up a bad proposal when it must compete for attention and analysis with many others at the same time. This does not prevent Councillors from making the attempt at advancing their pet projects, but some degree of comparative evaluation might keep them in check.

Continue reading

TTC Board Meeting Review: February 25, 2016

The TTC Board met on February 25, 2016. This article is a review of some of the reports and discussions at that meeting. For the full list, please refer to the agenda.

In this article:

As part of an update on cycling initiatives, the Board passed a motion asking staff to work together with the City on improved parking facilities for bicycles at subway stations. An article on this appeared on Torontoist’s website.

Continue reading

There’s A New Subway On The Way (7)

February 25, 1966, saw the ceremonial first train operate over the Bloor-Danforth line, but it was also the last day of service on many streetcar routes.

The fans, of which I was a very junior member in those days, were out in force trying to ride as many “last cars” as possible. This took some careful planning, and it was not physically possible to be everywhere.

The Bathurst service to Adelaide and the St. Clair service to Weston Road were rush-hours only, and so these were the first to be visited. It was a very dim late February afternoon as people photographed the last car to Avon Loop at Rogers Road. The destination signs said “Northland”, the name of a loop further south that had been replaced by Avon years earlier (before I was born), but the roll signs were never changed.

Next to go was the Parliament car, a route that operated until just after midnight. It was a short shuttle from Bloor at Viaduct Loop to King at Parliament Loop, but it was an important line it its day. The trackage was also used at times to route some King cars to Broadview & Danforth avoiding the congestion of streetcars at eastbound Queen & Broadview that could back up from the intersection to the Don Bridge on a bad day.

That Parliament car on its trip in to Danforth Carhouse conveniently crossed Pape & Danforth just before the last westbound Harbord car whose operator faced an unexpected surprise waiting at his first stop. Harbord wandered through the city in a vaguely U-shaped route from Pape & Danforth (see description below) to Davenport & Lansdowne. The running in trip down Lansdowne to the carhouse brought us to Bloor Street where it was time for a 3 am snack and a wait for what would be one of the two “last” Bloor cars.

The Bloor trip took us to both Jane and Luttrell Loops, and the car became so crowded as the night wore on that we started to leave passengers at stops. It was not quite dawn when the car pulled in to Lansdowne Carhouse, and everyone walked down the street to the brand new subway entrance where the Bloor night car transfer got us on to complete the night’s entertainment.

Many routes were affected by the subway’s opening.

The Bloor and Danforth routes vanished except for shuttles on the outer ends that would operate until the first of the BD extensions opened in 1968.

Jane Loop has been replaced by a new office building and parking lot, although the TTC history is still visible from the old traction pole sporting a Canadian flag on Google Street View. Bedford Loop, a terminus for peak-only services on Bloor-Danforth has vanished under the OISE building and a parkette. Hillingdon Loop (a peak-only short turn at Danforth Carhouse) now hosts a branch of the Toronto Public Library. Luttrell Loop is now occupied by housing that is newer than its surroundings, but the role as a TTC loop is clear from the road layout and the still-present traction pole.

The Parliament car was replaced by the 65 Parliament bus operating to Castle Frank Station at its north end. Viaduct Loop was abandoned and is now a parkette. Parliament Loop at King was for many years the terminus of the bus until it was extended south and west to serve the St. Lawrence district. The loop is now a parking lot for a Porsche dealership.

This was part of a complicated land swap some years ago between the TTC, the dealership and the Toronto Parking Authority. The TTC had plans to build a new streetcar loop on Broadview north of Queen where there is now a parking lot, the City wanted the land south of Front once occupied by the dealership as part of the “First Parliament” site, and the TPA wanted replacement parking if the TTC built on its lot. The dealership moved to the TTC lands, the City got the land south of Front, and the TTC bought a vacant lot on Broadview for a new TPA lot to replace the capacity that would be lost when the loop went in. The loop has never been built.

Much of the track used by the Coxwell car (daytime route, just like 22 Coxwell today) and Kingston Road-Coxwell (weekends and evenings, again just like the bus) remains in place from Coxwell & Gerrard south, east via Queen, and northeast via Kingston Road to Bingham Loop. Coxwell cars used a very small loop on the southeast corner at Danforth now occupied by a commercial building, and Coxwell-Queen Loop which still exists. The track north of Gerrard remained operational for some months after the subway opening and Carlton cars preferentially used it to loop at Danforth Carhouse rather than Coxwell-Queen when short-turning. Eventually, the power was cut and overhead removed. The carhouse remained active as a storage site for PCCs that were rotated into the pool used by Russell Carhouse, but the link was via Danforth, not Coxwell.

The Harbord car, whose route I described earlier, ran from Pape and Danforth at Lipton Loop (replaced during station construction by Gertrude Loop) to St. Clarens Loop at Lansdowne and Davenport. The route meandered a lot running south to Riverdale & Pape, a block west to Carlaw (jogging around the railway), then south to Gerrard (at the corner now home to the “Real Jerk” restaurant), west along Gerrard to Broadview, south to Dundas, west to Spadina, north to Harbord (finally on the street from which the route took its name), west on Harbord to Ossington, north to Bloor, west to Dovercourt, north to Davenport and west to Lansdowne. There had been track on Pape north of Lipton Loop for a proposed extension into the Leaside industrial district south of Eglinton, but this was never built due to the recession.

The Dundas car operated from Runnymede Loop to City Hall and service further east was handled by Harbord. With the subway opening, the routes were consolidated, and Dundas was extended east to Broadview Station. Various chunks of Harbord became other routes including the 72 Pape bus, 94 Wellesley, 77 Spadina (now 510 Spadina). Service on Dovercourt and Davenport was abandoned not to be replaced by bus routes until decades later.

The Carlton car, the only “zone 1” streetcar route in 1966 to retain the red ink from the days of multicoloured transfers, still operates over its old route much as the King car does although loops at Vincent and Erindale were replaced by Dundas West and Broadview Stations respectively.

The St. Clair and Earlscourt services were reorganized (this would happen a few times over the years until the “Earlscourt” route simply became a short-turn variant of St. Clair), and service to Weston Road was dropped. The 89 Weston trolley coach extension south from Annette to Keele Station provided a direct subway link for riders on Weston.

Bathurst and Fort were consolidated into a single route from Bathurst Station to Exhibition Loop which, in those days, was located where the Trade Centre (whose name changes with its sponsorship) is today. Service between St. Clair and Bloor was taken over by 7 Bathurst and 90 Vaughan which formerly shared Vaughan Loop at St. Clair with the streetcars. Service on Adelaide to Church (returning westbound via King to Bathurst) was abandoned. Active track remains on Adelaide today only from Spadina to Charlotte, and from Victoria to Church.

Where Should A Relief Line (East) Go? (Updated)

Updated February 24, 2016 at 10:40 pm: A map showing the various options for a Pape-Queen routing to downtown has been added at the end of this article.

The City of Toronto Planning Division has released the detailed technical scoring for evaluation of six possible routes for a Relief Line linking the core area to the Danforth subway.

The possible routes that survived a preliminary cull were:

  • A: Broadview to Queen crossing the Don River at Queen
  • B1: Pape to Queen crossing the Don River at Queen
  • B2: Pape to Queen, dodging south to serve the Unilever site before crossing the Don and swinging back to Queen Street
  • C: Broadview to King crossing the Don River at Queen
  • D1: Pape to King crossing the Don River at Queen
  • D2: Pape to King crossing the Don River at the Unilever site

Of these, the two Broadview options don’t fare very well, and the real debate is between the four remaining Pape options.

The scoring extends through many categories and pages, but to simplify things and understand just how each factor was ranked, I have consolidated the scores into a spreadsheet. (For the detailed evaluation, refer to the scoring document linked above.)

ReliefLineAlignmentScoringSummary

In place of the scoring system used in the city summary, I have converted each of the symbols to a numeric value:

  • Full moon = 4 points
  • 3/4 moon = 3 points
  • Half moon = 2 points
  • 1/4 moon = 1 point
  • New moon = 0 points

Within each major grouping of scores, the values were totalled and then normalized to the range of zero to one. For example, if a group contained 4 topics, then the maximum possible score is 16, and each alignment’s score is divided 16 to get a normalized value. This allows the scores from each group to be compared with each other.

At the end, the scores can either be summer individually (each topic counts equally), or the group averages can be totalled (each group count equally regardless of how many topics it contains) and normalized.

On a grand total basis, both the city’s technical evaluation and public feedback came to the same conclusion: even though there are variations between the four alignments, they all average out to a 3/4 score.

The point scores also come out close to the same with higher values on one item balancing lower values on others for, overall, an even ranking.

Quite simply, all other things being equal, the four alignments are more or less equivalent using this scoring system. However, the City opted for alignment B1 because, among other things, is is claimed to be cheaper and simpler to build.

The costs estimates in the City’s evaluation [at p.19] are:

  • $3.7-billion for either of the Pape via Queen options regardless of whether they follow Queen or King to the core
  • $4.0-billion for the Pape-Unilever-King option
  • $4.1-billion for the Pape-Unilever-Queen option

The ridership estimates are generally higher for the via King options, and higher still for the routes serving the Unilever site. In all cases, off-peak riding tends to be low compared to the rest of the network with roughly 2/3 of all boardings on the Relief Line being during the AM or PM peak. The effect is even more striking for configuration where frequent SmartTrack service at 12 trains/hour competes with the Relief Line for customers. This demonstrates the problem of a line aimed at primarily peak period “relief”. As and when we see projections for longer versions of the RL (to Eglinton or Sheppard), the balance of off-peak travel may change because the route will serve new subway territory, not simply provide an alternate route for existing trips.

Despite the even scoring overall, the preferred corridor was selected based on giving some criteria additional weight as shown in the table below.

201602_ReliefLineB1Selection

This evaluation, like so much other recent work, depends very much on the presumed presence of frequent SmartTrack service in the rail corridor. If that is found to be impractical, then the relative importance of the RL changes along with its appropriate alignment to serve the core. This is particularly critical at the Unilever site which would have only SmartTrack serving it if the RL stays on Queen Street.

One point above misrepresents the technical evaluation: both of the Queen Street crossing routes have the same cost estimate regardless of which route they take to the core area (Queen or King) and they share the same river crossing characteristics.

In summary, the choice “makes sense” in the limited context that a frequent SmartTrack service will actually be feasible and will be built. If SmartTrack cannot be provided on a five minute headway with a low fare, then the entire planning process will require a major rethink.

Updated February 24, 2016: The following map shows possible alignments for a route from Pape & Danforth to the core area. Notes on the map talk of a track connection at Danforth to provide access to Greenwood Yard. The technical scoring paper also mentions a southerly route under the rail corridor from Gerrard & Pape eastward. While this is longer, it would avoid the complexity of adding linking curves at Danforth.

201602_ReliefLinePapeOptions