Transit Network Analysis, SmartTrack and the Mysteries of Future Growth

Among the many reports (scroll down to the bottom of this document for links) coming to Toronto’s Executive Committee on March 9 is a short paper on Transit Network Analysis, three detailed demand projections and a paper about  Growth Assumptions. Although this has the neutral title Population and Employment Projections, it is in fact a review of the effect of SmartTrack on development in the Greater Toronto Area. The main report is titled Commercial & Multi-Residential Forecasts For The Review Of SmartTrack.

The paper is authored by the Strategic Regional Research Alliance, or SRRA, whose primary focus is real estate market tracking and projection. This organization (or its principals) were involved in the reports leading to the original SmartTrack plan in now-Mayor Tory’s campaign, specifically:

A fundamental premise running through all three papers, and perpetuated in the SmartTrack proposal, was that downtown Toronto was more or less fully built-out, and that future commercial growth would occur primarily in two major centres outside of the city, the large area around Pearson Airport and an equally large area around Markham. The potential for additional growth within Toronto itself was regarded as low, and therefore major expansion of the rapid transit network would focus on the two big suburban nodes.

At the Mayor’s direction, SRRA was retained as a consultant to the planning work now underway by the City of Toronto. This raised eyebrows both at Council for the crossover from a campaign support role to consultant, and also at Metrolinx where SRRA’s principal, Iain Dobson, had been appointed to the Board during the latter days of Glen Murray’s term as Ontario Minister of Transportation.

Although there is reason to take the new SRRA report with a grain of salt, the document makes interesting reading including a shift in some of SRRA’s outlook compared to their earlier work.

Which Land Use Model is Toronto Actually Using?

This report is supposed to be background to the overall planning study coming to Executive, but its focus is exclusively on the effects of SmartTrack. There is little mention of the development effects of other initiatives including the Scarborough Subway Extension (SSE), the Eglinton Crosstown LRT. Also, in part because ST and the GO/RER proposal cover the same territory and share stations, it is unclear how much change to development patterns occurs specifically due to SmartTrack and how much to the two services operating in one corridor.

Other background studies examine ridership effects of various combinations of SmartTrack, the SSE and the Relief Line, and these clearly must have an underlying land use, population and job location model. How this was developed or relates to the SRRA study is not clear.

That said, for the remainder of this article, I will concentrate on the SRRA text and its underlying assumptions.

Continue reading

GO Transit to Take Over UP Express

According to Oliver Moore in The Globe, the separate Metrolinx division responsible for the Union Pearson Express will be placed under GO Transit’s control. The fate of UPX President Kathy Haley is unclear.

UPX even managed to win awards from the Global AirRail Alliance for:

2015 Travelport Project of the Year – UP Express

2015 AccesRail Integrated Partnership of the Year – UP Express

2015 Personality of the Year – Kathy Haley, UP Express

2014 Air Rail Concept of the Year – UP Express: Strategic Partnerships, Toronto, Canada

2014 Travelport Project of the Year – UP Express: The Airport Connection

2013 Travelport Project of the Year – Union Pearson Express Project

One wonders who they were competing against, but the Alliance’s site does not list nominees, only winners. It is am impressive “project” that can rake in the hardware before ever carrying a passenger or proving its viability as a business. Such is the back-scratching nature of the industry, I must assume.

While it may be convenient to target Haley as the culprit here, the real question is how the structure and corporate attitude that led to UPX’ creation arose in the first place. From the beginning, this has been a project for which the word pretentious is almost inadequate. Despite the abandonment of this scheme by its original private sector proponent – for the simple reason that it was judged financially unsound – Ontario forged on with this as a signature project, part of the Bid Book for the Pan Am Games. We would show the world what Ontario could do.

Haley may take the fall for this fiasco, but she worked for a board who lapped up the praise, who bought into the flawed vision of what UPX would become. That board, and the government who set all of this in motion to begin with, owe us all an explanation.

When Is a GO Train not a GO Train? When It’s UPX!

Among the mysteries of the internal organization at Metrolinx is the presence of separate “divisions” for GO Transit (the commuter rail service), Presto (the fare card service) and UP Express (the premium fare airport shuttle service).  Rather than using the GO brand for the airport service and integrating its operation and fares, Metrolinx treats UPX as a completely separate entity, no doubt so that it could isolate the operation as a profit centre on the books. We now know that “profit” is the furthest thing from a UPX future where just finding riders now takes precedence.

Soon, fares on UPX will be much lower and this might encourage some to incorporate the UPX into their journeys. However, there are two glaring holes in the new arrangement.

UPX, being a separate operation, does not have fares integrated with connecting GO services at Union. Riders transferring between these services will pay separate fares for each leg of their journey. Presuming that UPX fares stay low, this should be corrected, at the latest, in the next annual review of GO’s tariff.

But the really bone-headed decision (or lack of decision) lies with the TTC. Although GO fares discourage “local” travel within the 416, there is a legal transfer move a rider can use called TTC Times Two. A trip can start on the TTC, transfer to GO, and then back onto the TTC again using the original TTC transfer.

With UPX moving to lower fares and the likelihood that it will attract commuter trade within the city, the question becomes “is TTC Times Two valid for UPX”? I asked the TTC’s Brad Ross and Chris Upfold this question at the recent TTC Board meeting. Their answer? “No” because (a) UPX is not a GO train and (b) a TTC policy change would be required.

The irony, of course, is that GO operates in the same corridor as UPX, and it would be impossible to distinguish whether a traveller with a transfer from the Lawrence 52 bus arrived at Union Station via GO or via UPX, except of course that GO service only runs in the peak period.

During the March 1 subway shutdown thanks to a power vault fire, TTC riders travelled on GO and UPX for no extra charge. The reverse courtesy has been extended to GO riders on occasion. This did not require a formal meeting and policy decision, simply the recognition that there is one transit network regardless of the logo on the train.

How riders get from one connection point to another should not matter. Between now and March 9 when the new UPX fares take effect, can someone at the TTC show a small spark of initiative and decide that a traveller on either a GO or UPX train can use TTC Times Two? Or will we continue to have an artificial distinction between two services provided on the same track by the same agency?

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

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

From time to time, the question of just what constitutes “subway demand” comes up in various threads on this site. As a matter of comparison, here is the TTC Scheduled Service Summary for April 7, 1964.

Headways on the Bloor-Danforth service itself were quite impressive. Two-car trains of PCCs, roughly the equivalent of the new Flexity cars, ran throughout the day until mid-evening, and the peak headways shown below are for trains.

                          AM Peak         PM Peak
                          Hdwy   Veh      Hdwy   Veh
Bloor route                      100             110
  Jane to Luttrell        2'30"           2'30"
  Jane to Bedford                         4'00"
Danforth route                    30              48
  Bedford to Hillingdon   3'20"
  Bedford to Luttrell                     3'00"
Combined                         130             158
  Bedford to Hillingdon   1'26"
  Jane to Bedford                         1'32"
  Bedford to Luttrell                     1'22"

Jane Loop was at Bloor & Jane.
Luttrell Loop was on Danforth between Main and Victoria Park at the old city boundary.
Bedford Loop was at St. George Station.
Hillingdon Loop was at the east side of Danforth Carhouse east of Coxwell.

The Bloor-Danforth streetcars could not carry all of the demand into downtown, and that work was shared with many parallel routes.

  • 2’00” Bathurst car from Vaughan Loop (at St. Clair) to Church & Adelaide
  • 1’30” Carlton car
  • 1’40” Dundas car from Runnymede & Dundas to City Hall
  • 2’30” Harbord car from Lansdowne & Davenport to Pape & Danforth via Dundas & Yonge
  • 1’20” King car
  • 2’00” Kingston Road car (now “Downtowner”)
  • 5’00” Kingston Road Tripper car (Victoria Park to Roncesvalles & Queen)

The streetcar system required 640 cars in the am peak, 684 in the pm peak.

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

The new subway would bring major changes in travel throughout the transit network.  The TTC produced a large poster, the size of a two-page foldout in newspapers of the day explaining many features of the line and its operation.

BDNews1

Probably the largest reorganization of routes in the TTC’s history accompanied the opening of the new subway including the change or removal of several streetcar lines. This was to be the beginning of a gradual dismantling of streetcar operation leading to the opening of a Queen Street subway in 1980.

BDNewsRoutesw

Lest passengers be confused about the destination of their trains with the integrated subway service, platform signs would indicate where the next train was headed. The signs remain on many platforms with their displays fixed to the now-standard destinations.

BDNewsDestSignsw

The two-zone fare system still existed, although its boundary would not be punctured by the subway until the extensions beyond the old City of Toronto opened. The fine boundary line is visible in the route map below.

BDNews2

Adult tickets were still a common method of fare payment, and the TTC exhorted travellers to switch to the mode used by “seasoned subway riders”, tokens, at the princely price of 6 for $1 in handy cardboard holders.

TokenHolder6

For the opening, a special commemorative token holder was issued.

TokenHolders1

The subway had its own pocket route map.

BDMap660226B

BDMap660226A

Six months later, this would change to the routes we know today.

BDMap660904B

BDMap660904A

Demand Projections for Relief Lines

The City of Toronto Planning Department has published a set of demand projections for various combinations of the (Downtown) Relief subway line, SmartTrack, and the proposed northern extension of the Yonge line to Richmond Hill.

This document makes interesting reading because it shows both the status of the evolving master transit plan that went into the modelling, and the vital point that additional capacity into the core area is essential to prevent complete gridlock on the subway system. Both SmartTrack and the Relief Line are essential to a future transit network.

That said, the report raises several issues in part by what it does not talk about, specifically some of the network configurations that have already been presented in various studies.

Alignment Options for the Relief Line, and Other Model Variations

This question of the Relief Line’s alignment is subdivided into two parts: what is the scope of the line, and which route will it take to link Danforth to the core area.

The big options include:

  • A “little J” route from Yonge Street to Danforth
  • A “big J” route from Yonge Street to at least Don Mills & Eglinton, possibly beyond
  • A “little U” from Danforth to Bloor West via downtown
  • A “big U” with northern extensions of one or both arms of the “little U”

Work has focussed on the “little J” because that is the scope for a Relief Line so long discussed, and approved for study by Council. Therefore the model numbers do not show any effect of taking the “little J” further north to intercept more traffic bound for the Yonge line. This has already been reported by Metrolinx as a very beneficial extension to the RL.

Within all of the options, there are permutations of a Danforth to Downtown route:

  • The north-south segment could lie on either Pape of Broadview.
  • The Don River crossing could be at Queen, or further south to allow the line to serve the Unilever site.
  • The route into the core could be via Queen or King.

A northern route via Queen makes for a simpler river crossing, but the southern route picks up a major new employment district. The King Street route into downtown also attracts more riders than a Queen route.

City Planning staff have erroneously talked of a King route as if it could only exist as part of the southerly Unilever site alignment, when their own study clearly shows the option of a route crossing the Don at Queen, and then veering into King Street. The more northerly crossing is preferred because it will be easier to build under the river at a narrower point.

RLAllCorridorsWeb

The following permutations were modelled to see how they would perform:

  • Broadview to Queen
  • Broadview to Queen to King
  • Pape to Queen
  • Pape to Queen via Unilever
  • Pape to Queen to King
  • Pape to King via Unilever

Of these, the two most promising were the Pape to Queen options with the only variation being whether the line ran to downtown via Queen or via King after crossing the Don at Queen Street. For this article, these are the only two whose demand projections I will discuss.

Further east, there is the question of the Scarborough Subway extension and SmartTrack. Model runs were performed with three variations:

  • No SmartTrack
  • SmartTrack on a 15 minute headway (4 trains/hour)
  • SmartTrack on a 5 minute headway (12 trains/hour)

The SmartTrack cases used a modified land use plan that assumed SmartTrack itself would cause growth that would not otherwise occur. This causes increases for the Relief Line’s projected demand when it is matched with a the lower level of SmartTrack service (4 trains/hour) because the latter does not attract as much riding as the Relief Line.

All model runs used a Scarborough Subway (SSE) with its original three stops, not the “optimized” version serving only Scarborough Town Centre. The disconnect between what is modelled and what is proposed indicates that some of the plan’s elements have changed very recently. The model is supposed to catch up to the plan in future iterations.

None of the SSE or ST figures are included in this report, and so we cannot see how the model divided up demand between them, albeit with the “wrong” station configuration.

Finally, the Richmond Hill extension was added to the model networks to see how it would affect demand on the critical downtown segment and Bloor Yonge Station.

All of these numbers must be taken with awareness of the limitations on what has been modelled, notably:

  • With the RL ending at Danforth, the potential benefit (and hence RL demand) of the “big J” is unknown.
  • The five-minute service on SmartTrack, identified in a previous study as essential to attract riders, may not be physically possible given constraints on sharing the network with GO.
  • It is unclear whether SmartTrack will actually operate at no fare premium above local TTC services, another essential component of making this service attractive to riders.
  • The effect of SmartTrack in the downtown segment, including the degree to which it would duplicate an RL at the Unilever site, depends on the ability to operate frequent ST service.
  • The relative roles of the Scarborough Subway and SmartTrack in attracting riders is unknown because the now-proposed station layout has not been modelled.

That is a long list of variables. Many of these will be addressed in updated model runs expected in coming weeks, but readers should be careful not to take the current model output as definitive.

Nonetheless, the report concludes that treating SmartTrack and the Relief Line as options is misguided because both will be required to accommodate future demand to 2031 and beyond. Addition of the Richmond Hill extension to the mix will exhaust the Yonge line’s capacity by 2041. This makes further study of the “big J” quite important.

The findings in this Summary Report make clear the importance of the Relief Line. It is apparent that both the Relief Line and SmartTrack will be required in the future to ensure the efficient operation of the existing and proposed future transit networks. Additional work is required to assess the potential benefits of extending the proposed Relief Line north of the Bloor-Danforth subway to Eglinton Avenue and potentially to Sheppard Avenue. [p 3]

Continue reading

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

February 1966 saw the opening of the Bloor-Danforth’s Keele-to-Woodbine stretch, and an extension to North York was already in the cards, albeit only to Sheppard Avenue. Like the BD extensions to Scarborough and Etobicoke, this segment would itself grow another two kilometres. The original plans called for the line to be built parallel to and west of Yonge Street just as the route south from Eglinton had been, but demolition of a swath of homes through North Toronto was not in the cards. The alignment eventually chosen lay directly under Yonge with a bored tunnel north to Sheppard. (The Finch extension would later be built cut-and-cover through the then much less-developed Willowdale.)

Progress Report 6 includes a few choice items including the coin changer at an automatic entrance (fares were 6/$1.00), the speed ramp linking the temporary Bloor streetcar shuttle platform at Keele Station to the eastbound platform, and a reference to Metro Toronto’s “balanced transportation system”. That was the standard buzzphrase used to sanitize a combination of subway and highway building in the 60s, and the Spadina Expressway project was very much in the foreground at the time.

The integrated service with trains running through the wye between the BD and YUS routes was now described as a six-month trial to be followed by a similar test period for separate routes.

The extensions were well underway, and the original balance of lengths east and west had been abandoned in favour of a more sensible Etobicoke terminal at Islington.