Service Analysis

by

TTC Service Changes Effective January 3, 2016 (Updated)

Updated December 8, 2015 at 12:30 pm: I checked with the TTC about the termination of both the 509 Harbourfront and 511 Bathurst routes at Fleet Loop rather than simply running one route between Bathurst and Union Stations. Here is the reply from TTC Service Planning:

We considered running a 511 (Bathurst Stn-Union Stn) service but ruled it out for two main reasons. Firstly, stop usage on Fleet west of Bathurst has greatly increased in the last year, and serving these stops only with the shuttle bus would introduce a transfer or longer walk for too many people. Secondly, because of the road configuration and traffic patterns, it is not possible to have a northbound stop for through 511 cars on Bathurst at Lake Shore. The nearest stop would be the existing 509 stop on Bathurst farside of Queens Quay. This adds to the walking distance for customers heading to Fleet Street, and requires customers to cross an inhospitable intersection.

The original article follows below:

The new year brings changes to some routes, mainly on the streetcar system, to deal with the shortage of new Flexitys and a construction project while improving service on 501 Queen, 502 Downtowner and 503 Kingston Road to better reflect actual conditions.

2016.01.03 Service Changes

Continue reading →

by

A “Reset” For Waterfront Transit Plans? (Updated)

Updated October 15, 2015 at 10:20 am:

Because the options for the Waterfront West line are not fully explained or explored in the City report, I have added the drawings of the options from the Environmental Assessment to the end of this article.

A few weeks ago, I reported on a presentation at the TTC Board meeting by Deputy City Manager John Livey on the status of various rapid transit plans and studies. This was by way of a preview of reports that were expected at the City’s Executive Committee meeting on October 20, 2015.

One of these reports has now surfaced on the subject of Waterfront Transit, while another on SmartTrack is still in preparation. (Reports on the Relief Line and Scarborough Subway studies are not expected until the new year pending results from the UofT’s new demand model.)

The new report proposes a “reset” in the status of the many waterfront studies and proposals given that many of them are incomplete or out of date. The area of study will be south of Queensway/Queen from Long Branch to Woodbine, although there is passing mention of Scarborough which has its own collection of transit problems in the Kingston Road corridor.

The fundamental problem along the waterfront and areas immediately to the north is that population and plans for development continue with no end in sight, while transit planning, such as it exists at all, looked much further afield for signature projects. Moreover, origins and destinations in the present and future waterfront are not conveniently located along a single line where one scheme will magically solve every problem. Transit “downtown” is not simply a matter of getting to King and Bay. There is a mix of short haul and long haul trips, and a line designed to serve the first group well almost certainly will not attract riders from the second.

There has been significant growth in many precincts along the waterfront, including South Etobicoke, Liberty Village, Fort York, King/Spadina, City Place, South Core, and King/Parliament.  Further, significant growth is planned for emerging precincts, including Lower Yonge, East Bayfront, West Don Lands, North Keating, Port Lands and the First Gulf site.  There is currently a latent demand for transit south of Front Street as witnessed by transit loading on the King and Harbourfront streetcar services.  King Street, for example, represents the most southerly continuous east/west transit line and is regularly experiencing near or at-capacity conditions through much of the weekday peak periods.  The extent of latent and anticipated future demand creates an imperative for defining a long-term transit solution as soon as possible. [pp 1-2]

Better transit on King and Queen, whatever form it might be, will address demand from redevelopment of the “old” city north of the rail corridor, but it cannot touch the “new” city south to the lake. Service on the rail corridors (Lake Shore and Weston) can address some longer trips, but with constraints on both line capacity and service frequency. Despite politically-motivated claims, the GO corridors will not be “surface subways” with service like the Bloor-Danforth line, and GO service is constrained to operate through some areas that are not well placed relative to the local transit system.

Continue reading →

by

The Evolution of Service on Queens Quay

The new, improved transit right-of-way on Queens Quay has been in operation for a few months, and it has had its share, and then some, of problems. These included confused motorists, pedestrians and cyclists who could not figure out the new lane arrangement and signals, more than a few autos stuck in the tunnel entrance at Bay Street, and a streetcar collision thanks to an open switch at the Spadina/Queens Quay Loop.

When the design for the new road was still on the drawing boards, a red flag went up for transit watchers with the number of traffic signals, some fairly closely spaced. The “old” Queens Quay’s signals had their problems, and just to get a semblance of “priority” the detectors for approaching streetcars were moved further and further away from the signals in the hope that they would be able to cycle to a transit green before the streetcar actually arrived.

The streetcars returned, but the signals were, at first, on a standard program with no provision for detecting transit vehicles, although this changed in mid-June with the installation of the new, permanent traffic controllers.

Has there been an improvement? This article reviews current and past operations of the 509 Harbourfront and 510 Spadina cars running on Queens Quay.

Continue reading →

by

Blue Night Service Expansion: Fall 2015

The overnight “Blue Night” network will see many changes and additions this fall. These will be rolled out in two waves: first with the September/October schedules on Labour Day weekend, and the remainder with the October/November schedules at Thanksgiving.

This is part of a more extensive expansion of service beginning in September that relates to the Ten Minute Network, All Day Every Day service, and improved crowding standards on routes with frequent service. Those and other changes will be described in a separate article.

Here are maps of the network as it exists now, and with the two stages of additions:

BlueNightMap_201507

BlueNightMap_201509_Delta

BlueNightMap_201510_Delta

Several of the routes will be renumbered so that the night services match the daytime routes except for the using “300” series. In the case of the King and Spadina night services, they will run, at least initially, with the daytime route numbers because there are no roll signs for “304 King” or “317 Spadina” in the CLRV/ALRV fleet. This problem will vanish as the routes convert to Flexity cars with programmable signs.

All services will operate on 30 minute headways.

This implementation is a work-in-progress, and Service Planning does not expect to turn to the question of timing points until the routes are in place. This is a vital piece of work for a network with wide headways where TTC performance stats show that headway (and, by implication, schedule) adherence is very weak. Riders of these routes should be able to depend on vehicles appearing at expected times and connections to work in a predictable way. This is as important a part of the new service as simply putting the buses and streetcars on the road. If service is not predictable in the middle of the night, riders cannot be expected to use it especially for trips that are time-sensitive such as early morning work shifts.

Continue reading →

by

Service Analysis of 502/503 Downtowner/Kingston Road Tripper: 2013 to 2015

Recent articles on this site looked in great detail at the 501 Queen car and the problems with its service. Often, when people talk about Queen, they miss the streetcar routes that are, in effect, branch operations of the Queen line serving Kingston Road in The Beach:

  • 502 Downtowner (formerly Kingston Road) operates between Bingham Loop (at Victoria Park & Kingston Road) and McCaul Loop sharing trackage with 501 Queen west of Woodbine Loop (which is actually at Kingston Road, and is named for the old racetrack, which itself became “Greenwood” when “New Woodbine” opened in northern Etobicoke). This route operates weekdays until the end of the PM peak. Evening and weekend service is provided by the 22a Coxwell bus.
  • 503 Kingston Road Tripper operates rush hours only between Bingham Loop and York Street running into the core via King from the Don Bridge, and looping downtown via Church, Wellington and York.

This service design has been in place, with only a few changes, since 1948:

  • 1954: Streetcar service cut back from Birchmount Loop to Bingham Loop.
  • 1966: Coxwell bus replaced Coxwell streetcar and evening/weekend service on Kingston Rd./Coxwell (same as the 22A today).

The route name “Downtowner” arose from an ill-advised proposal to provide “relief” to the downtown subway by extending Kingston Road cars from McCaul Loop west and north to Bathurst Station in 1973. This didn’t last long. A year later the extended service became a peak-only operation, and that remained, on paper at least, until 1984. We have the name as a memento of that extension now 30-years in the past. The basic problem was that very little of the service actually reached Bathurst Station with many cars short turning either at Wolseley Loop (Queen & Bathurst) or at McCaul Loop.

The situation is not unlike what we see today because the 502 Downtowner schedule does not provide enough running time, and short turning is a chronic problem. This is particularly troubling because the short turns defeat the purpose of the route’s existence:

  • A short turn eastbound at Woodbine Loop removes service from the street which the route is intended to serve.
  • A short turn westbound at Church (looping via Richmond and Victoria) sends a car east without serving the major stops downtown from Yonge to University.
  • A short turn westbound at Parliament (looping via Dundas and Broadview) removes a car even more from downtown, and not even a clever rider walking a block east from Yonge (an “illegal” move with a regular transfer) can take advantage of the service.

This is compounded by extremely erratic headways that are far worse than I have seen on any other route I have analyzed. According to TTC route performance stats, the 502 is “on time” (that is to say, within ±3 minutes of the scheduled headway) 30% of the time. As we will see later, even that claim is a stretch.

As for the 503 Kingston Road Tripper, service on that route is supposed to be blended with the 502, and during AM peaks it can work out, sort of, there is a vaguely reliable headway of alternating 502/503 cars on Kingston Road. But it’s a hit-and-miss situation, and very large gaps in 503 service are quite common.

Anyone attempting to use transit on or to Kingston Road is well advised to get on the first thing that shows up and be prepared to transfer. This appalling situation is a mockery of what the TTC claims is its “customer service”.

Service on Kingston Road was substantially better in past decades, and it is no wonder that ridership and scheduled service levels have fallen given the unpredictable nature of these routes. Recently, there has been some improvement. In April 2013, off-peak headways of 502 Downtowner improved from 20 to 16 minutes, and in June 2015, from 16 to 10 minutes. However, the fundamental problem of headway reliability undoes much semblance of “improvement”.

Continue reading →

by

Service Analysis of 501 Queen 2013 to 2015: Part 2, Running Times

In the first article of this series, I reviewed the headways (time between vehicles) on route 501 Queen from August 2013 to May 2015. A pattern there is that headways on the outer parts of the route are consistently, at times extremely so, worse than the advertised frequencies. Even in the central part of the route, average headways are close to scheduled values, but the regularity of vehicle spacing is not – cars commonly run in pairs on a much wider combined headway than the schedule calls for.

With this route listed among those that will be part of the TTC’s “Ten Minute Network”, actually achieving that goal will be as important as the inevitable hype that will accompany the announcement. This is also a route destined for better service thanks to new loading off-peak loading standards.

This article turns to the question of running times – the period required for a typical vehicle to get from point “A” to “B” on a route. These are important for a variety of reasons:

  • If the scheduled time is commonly less than the actual time needed, then vehicles will always be late, and there will be a strong incentive for cars to short turn.
  • If the scheduled time is commonly more than what is needed, then vehicles will either dawdle along their routes, or take extended siestas at terminals.
  • “Congestion” is a routinely cited reason for the TTC’s inability to operate reliable service, but it is not a consistent phenomenon across the route, by time of day or by day of the week. Some of the worst disruptions arise not from chronic congestion, but from events such as construction projects or diversions around festivals. The location of the delays is not confined to the core area.

There is a lot of material here, and I don’t expect that most readers will go into all of the detail. The first part looks at the route overall, and then I turn to individual segments. If there is any overall message, it is this: the operation of a long, busy route like Queen is affected by many factors. Some are institutional (schedules, procedures). Some are chronic (predictable congestion). Some are transient (accidents, illness). Some of the worst are from relatively short-lived events such as construction work or event diversions where the resulting service leaves much to be desired. There is no one “magic solution” that will fix all of them with minimal pain for either for the TTC or for other road users.

Continue reading →

by

TTC Board Meeting July 29, 2015 (Updated August 3, 2015)

The TTC Board will meet on July 29, 2015, and various items of interest are on the agenda. These include:

  • The monthly CEO’s Report (Updated August 2, 2015)
  • A presentation by Toronto’s Chief Planner Jennifer Keesmaat (Updated August 3, 2015)
  • Faregates for PRESTO implementation
  • Purchase of new buses and implications for service growth (Updated August 1, 2015)
  • Improved service standards for off peak service on “frequent” routes
  • Proposed split operation of 504 King during TIFF opening weekend (Updated August 2, 2015)
  • An update on Leslie Barns
  • Excluding Bombardier from eligibility for future contracts (Deferred to September Board meeting)
  • Council requests related to Lake Shore West streetcar service (Referred to TTC Budget Committee)

Continue reading →

by

Service Analysis of 501 Queen 2013 to 2015: Part 1, Headways

Of the TTC’s many routes, 501 Queen is the longest and the subject of ongoing complaints about service quality and reliability. Two standard explanations are offered to the long-suffering riders: we cannot operate a reliable service thanks to traffic congestion, and we have no equipment with which to operate more service.

I have published detailed reviews of individual months of operation in past articles, but an accumulation of data for various periods and conditions now makes a retrospective look at the route’s behaviour possible.

The data used in this analysis come from the TTC’s vehicle monitoring system which collects GPS information on the fleet every 20 seconds. The raw data are transformed by several programs I have developed over the years so that they can be presented in a consolidated format. Interested readers should see Methodology For Analysis of TTC’s Vehicle Tracking Data for details of this process. The data were provided by the TTC, but the analysis and interpretation are entirely my own.

Service History

The last significant change to 501 Queen schedules occurred in Spring 2013 when weekday services were adjusted to address overcrowding. Since then, there have been only two basic schedules used on the route:

  • The standard schedule provides service between Neville Loop in the east and Long Branch Loop at the city’s western edge. Half of the cars are scheduled to short-turn at Humber Loop, and except for overnight service, from that point westward the scheduled service is half the level of that east of Humber.
  • On some occasions, construction has required that the line operate in two segments. One is from Neville to Humber, and the other (using buses) is from Humber to Long Branch. Service east of Humber is similar to that on the standard schedule. To the west, scheduled bus service is more frequent to allow for the capacity of low floor buses versus the two-section streetcars (ALRVs) used on 501 Queen. (A variation on this includes a shuttle service from Humber Loop to the condos east of Park Lawn, but it does not alter the service provided on the main part of the route east or west of Humber. This shuttle is not part of the service analysis.)

501_ServiceHistory

This table shows the two service designs for 501 Queen including the headways (scheduled time between vehicles), numbers of vehicles, end-to-end trip times and “recovery” time.

This last item deserves comment because it is not, as the name implies, intended to give operators on this extremely long route a break after their journeys. Instead, its primary function is to make the schedule work out so that the round trip time is a multiple of the headway. Because of the difference in trip times on the two branches of the route, this can produce long recovery times at periods in the day when they are not badly needed simply to make the schedule work out properly. I will turn to trip times and reliability in the second part of this series.

This article covers the following periods of operation on 501 Queen:

  • August-October 2013 (service split at Humber Loop after Thanksgiving weekend)
  • January-April 2014 (service split at Humber Loop for April)
  • September-October 2014 (service split at Humber Loop)
  • March-May 2015

As a general observation, service on much of the Queen route is very unreliable and, in some cases, to the point where it exists more in theory than in practice. Bunching is commonplace, and there is no evidence of any attempt to keep cars spaced apart from each other even long before they enter the most congested section of the route. If there is an operating discipline, its aim is to keep operators on time, with service to riders coming as an afterthought. In principle, if all of the service is on time, then reliability will take care of itself. However, in practice, the service routinely operates well off of its scheduled headways. This cannot be put down entirely to “traffic congestion” given how pervasive a problem this is and has been on 501 Queen for years.

Service on this route, particularly on its outer portions, has been an issue for as long as I can remember, and the TTC always has an excuse. If only they would expend one tenth of the effort to manage headways on this major route as they do to tell us about their latest of clean subway stations and other “customer service initiatives”, there would be many happy riders, and an incentive to bring even more. The route is developing medium and high intensity buildings along its length, but the service levels are unchanged since 2013 (and with only minor changes before that).

The TTC plans to introduce new schedules on Queen later in 2015 (or possibly early 2016) to address some of the reliability problems. However, without the will to ensure that vehicles on this very  long route maintain proper spacing, the concept of reliability, let alone the “ten minute service” network of which Queen will be a part, will be meaningless.

Continue reading →

by

Coming Soon: July 2015

Since that blizzard of articles about TTC budgets and fares, it’s been rather quiet in here. Fear not! I actually have works in progress to tide us over the relatively quiet summer months until the political season heats up in the fall.

There will be a series of articles about the operation of the downtown streetcar lines looking at their behaviour over time, and reviewing how changes that have been made (or are planned) affected them. These include:

  • 501 Queen (including the effect of split operation with a bus shuttle on Lake Shore to Long Branch)
  • 502/503 Downtowner & Kingston Road (including the recent move to a 10-minute off-peak headway on 502)
  • 504 King (including the effect of additional running time on service levels and terminal operations)
  • 505 Dundas
  • 506 Carlton (including a look at the effects of the College/Spadina construction diversion)
  • 509 Harbourfront (including a review of the changes on Queens Quay)
  • 510 Spadina

The TTC plans additional meetings of its Budget Committee and these will, no doubt, produce more details about plans and options for 2016 and beyond. I will cover this material as it becomes available.

by

Toronto To Propose Peak-Hour Extensions on Queen, Dundas, Carlton/College

The City of Toronto will hold three public meetings regarding proposed changes in rush hour traffic restrictions on Queen, Dundas and Carlton/College between Parliament and Roncesvalles.

  • Wed. June 17 at 6:30 pm: Mary McCormick Community Centre, 66 Sheridan Avenue
  • Thurs. June 25 at 6:00 pm: Scadding Court Community Centre, 707 Dundas Street West
  • Mon. June 29 at 6:00 pm: City Hall, Committee Room 2

Work underway by City Transportation Services and the TTC includes:

The project team is currently:

  • Analyzing GPS-based data for the streetcar routes along Dundas Street, College/Carlton Streets, and Queen Street West
  • Looking at how existing peak-hour restrictions function along the routes
  • Finding opportunities to improve streetcar travel times and reliability. For example, where streetcar travel times increase sharply after current restrictions end (e.g. 6pm), the project team is considering extending the peak period by a half-hour or hour on each end to improve the flow of transit, general traffic, and cyclists
  • In a few cases, where no clear benefit is observed from an existing extension, peak hours are being reduced

Additional measures to improve transit operations, in various stages of implementation, include:

  • Re-timing signals to give more green time to the priority direction
  • Active Transit Signal Priority (extended green or shortened red when transit vehicles are detected and meet certain requirements)
  • All-door boarding / Proof of Payment (POP)
  • Greater enforcement of restrictions

[From the “Overview” tab]

Disclosure: I have acted as a consultant to this project in the analysis of TTC vehicle tracking data.