Roncesvalles Construction Resumes

Completion of the Roncesvalles reconstruction will proceed over the next four months from mid-March to early July.

The City’s Construction Notice explains the staging of the remaining work between Queen and Dundas Streets.

  • March 21 to 30:  Housekeeping work on sidewalks left over from 2010.
  • March 28 to May 16:  Sidewalk work on the east side of Roncesvalles south from Fern to Queen, and on both sides between Dundas and Howard Park.
  • April 4 to 25:  Enbridge Gas will relocate a main between Geoffrey and Howard Park on the west side of Roncesvalles.
  • May 9 to June 13:  Sidewalk work on the west side of Roncesvalles south from Howard Park to Geoffrey.
  • June 20 to July 4:  Road reconstruction on the west side of Roncesvalles from Geoffrey to Howard Park.

From March 27 onward, the 504 King service will revert to the schedule used in fall 2010 with a bus shuttle running from Dundas West Station to Sunnyside Loop.  Southbound service will run via Lansdowne, and northbound service will run via Roncesvalles.  In early May, construction will reach the point where buses can operate southbound diverting via Howard Park, Parkside Drive and High Park Blvd.  Streetcar service will resume in July.

A related project, the reconstruction of track on King from Roncesvalles to Close, is scheduled to begin in late May and continue until mid August.

TTC Service Changes Effective March 27, 2011

The list of changes for the “March” (actually almost April) schedule period is rather short because the TTC deferred implementation of service cuts on lightly used routes to May 8.

One intriguing side-effect of that decision is that the amount of service operated will be “over budget” because the cuts were incorporated in budget plans in November 2010, long before there was any public discussion, and at a time when rumours of cuts were met with denials from the TTC.

In our wonderfully new “transparent” Toronto, how many other changes are lurking, unpublished, in the budget?

Changes in Hours of Service

53F Steeles East Staines Express: Two new morning trips will be added weekdays from Morningside at about 5:21 and 5:48 am.

Diversions

505 Dundas: With the resumption of watermain work on Dundas, streetcars will divert via Spadina and College until late June.  Headways at all times will not be changed, but one car will be added to the route to handle the longer round trip times.  There will not be any replacement bus service on Dundas.

504 King: Reconstruction of Roncesvalles Avenue will resume to allow work by Enbridge Gas as well as completion of the sidewalk reconstruction.  During this period, the same bus shuttle that operated in 2010 will run from Dundas West Station to Sunnyside Loop, and King cars will loop through Roncesvalles Carhouse.  The Jane night bus, which runs on Roncesvalles, will not be affected.

In May, work is expected to begin on track replacement and paving between Roncesvalles and Close on King Street.  This will complete the rebuilding of the King route to the new resilient track standards.  While this is in progress, King and Lake Shore cars will divert via Queen and Shaw.  The work is expected to be completed before the CNE (with associated traffic problems in Parkdale) opens in mid-August.

Unlike the period of watermain work on King West in 2010, there will not be any replacement bus service on King west of Shaw.  I can’t help wondering why the TTC doesn’t simply route the 504 to Dufferin Loop so that service would be maintained for riders from Shaw to Dufferin whose access to Queen is limited by the rail corridor.

If One Bus Is Good, Seven Must Be Better

Recently, I received a note from a reader about bunching on the 29 Dufferin bus.  This is one of two routes on which increased supervision has led, or so the TTC claims, to improved service (as discussed in my recent article about the Customer Service plan).

I’m wondering what TTC is doing to prevent bus bunching as this seems to be a big problem on many routes…

I wrote to TTC customer service but of course I didn’t hear back from them. I would be interested to know what measures are in place to space out the buses. It seems to me that buses are just rushing to get to the end of the line; they basically do not care if they have 2-3 buses traveling together or if the last buses have no passengers.

I took this video as an example, there are 7 buses passing Bloor stop in under 3 minutes … such a waste from TTC. Just imagine being the “lucky” one that just missed all 7 buses. How long they will need to wait for another bus?

The TTC talks a good line about service management, but a casual look at any of the routes where real-time monitoring is possible (through the open data interface to GPS vehicle data) routinely shows bunching even at 7am when there cannot possibly be “traffic congestion” effects.  Two basic questions about bunching emerge from all of the service reviews I have done:

  • Why are vehicles allowed to leave termini very close together rather than regularly spaced?
  • Why are vehicles entering service from yards or from short-turns not spaced between through runs so that even headways are provided?

This does not require millions in high technology to implement, only the will to manage the service, something the TTC once did regularly with no more than route Inspectors on the street.  With the tools now available for vehicle tracking, it should be much easier as all vehicle locations are available online.

I plan to review the Dufferin bus operations again in the Spring (my last review was published in January 2008) once the effects of winter weather are not a concern.

Short turns disrupt service near the ends of routes, and on Dufferin this can show up as poor service to Liberty Village thanks to turnbacks southbound at Dundas.  On King, short turns eastbound at Parliament and westbound at Roncesvalles deprive riders on Broadview and on Roncesvalles (which have demands to some degree independent of the route downtown) of service.

If the TTC is going to strive for having 99% of the service advertised actually on the street, it must also strive to have that service on the route, not sitting in a short turn, or running in a pack followed by a large gap.

The “Ooops” Factor in Planned Service Cuts (Updated)

Updated January 20, 2011 at 9:30 pm:

The table showing the route cuts linked in this article contained an error, and this has been corrected.  In the original table, I calculated the imputed cost/hour and cost/passenger of the services under review by dividing the annual vehicle hours saved and passengers affected into $7-million.  However, that saving would only have taken place over 9 months, and its annual value would have been about $9.33m.

Therefore, the imputed values, corrected for full-year savings, are $70.74 per vehicle hour and $7.16 per rider.  Some reports have claimed that the current subsidies are $30/rider, and this is not borne out by the TTC’s own numbers.  The actual values will vary from route to route and day to day, but the average is about 1/4 of this claimed value.  Indeed few of the services up for cancellation reach the $30/rider subsidy level as is evident on the updated and expanded spreadsheet.

The link to the table is reproduced here for convenience.

2011.03 Route Cuts Analyzed

In other news, I have now learned that the service improvements implemented in January 2011 are to be funded out of the savings from the late night cuts.  These improvements have an annual cost of about $4m, leaving only $3m for fall 2011.  However, about $1m will be lost to the delayed implementation of the cuts, leaving only about $2m for service additions in late 2011.

Updated January 13, 2011 at 3:05 pm:

Maps added:

Map of routes facing proposed cuts

Map of routes with proposed additional service (Fall 2011)

It is worth noting that some routes appear on both maps indicating that they have a proposed service cut in one period to pay for an improvement in another, although we don’t know exactly what that may be yet.

[The original article follows below.]

Continue reading

Analysis of 512 St. Clair Operations for July 2010 — Part III (Headways)

In two previous articles, I have reviewed the St. Clair car during its first month of operation on the new right-of-way over the complete route from Yonge to Keele.  Running times during busy periods are down compared with April 2007, when the only right-of-way was between Bathurst and Yonge Streets.  However, the situation with headways, an important factor in how riders perceive service quality, is quite another matter.

For the entire period of construction, the idea of regular, scheduled service was something of a fairy tale on St. Clair, and both the streetcars and buses made their way such as they could along the route.  One would commonly see vehicles taking long terminal layovers, and headways were not a big priority.

In analyses of other routes, there is a common factor that is independent of the route’s length, the time of the year, the weather, eclipses or any other phenomena:  vehicles do not leave terminals on a regular spacing.  They leave when they get around to it, a practice abetted by the TTC’s standard that ±3 minutes is considered to be “on time”.  Pairs of vehicles can travel together on routes with short headways and remain within this standard.

Continue reading

Analysis of 512 St. Clair Operations for July 2010 — Part II (Link Times) (Updated)

In the first article of this series, I gave an overview of the data for one day’s operation on the 512 St. Clair route in July 2010.  Here, I will review link times (the time taken to get from one location to another) on the route for the entire month, and compare this with data from April 2007 when the St. Clair car last ran over its full length from Yonge to Keele.

Updated December 29, 2010 at 9:50 am:

A set of charts has been added comparing the running times between Keele and Yonge for April 2007 and July 2010.  See the end of the article for links and commentary.

Continue reading

Analysis of 512 St. Clair Operations for July 2010 — Part I (Introduction)

Updated at 3:20 pm, December 27: The scale on the headway charts has been changed to 30 minutes with 3-minute gridlines, and on the link time charts to 18 minutes with 3-minute gridlines.  The intent is to spread out the data points to give a better view of the fine details.

[My apologies for the appearance of this series many months after the fact.  It took quite a while to get the GPS-f0rmat data from the TTC for reasons unknown.

I look forward to the plans for an Open Data access to data for all routes as a regular online service so that this type of analysis will not require special requests for data extracts.  Whether the “new” TTC goes ahead with providing this data remains to be seen, although “transparency” is supposed to be a watchword in the new administration.]

June 30, 2010, brought streetcar service to the full St. Clair route out to Gunn’s Loop for the first time since 2007.  In an earlier article, I reviewed the line’s operation in April 2007.  This was a “before” snapshot intended as a comparison to the “after” construction line behaviour for which we have waited so long.  Now we can look at the “new” St. Clair to see the benefits, such as they might be.

On two weekends, service did not operate over the entire line due to street festivals.  No sooner was streetcar service restored to Keele, but it vanished again on July 3-4, and again on July 17-18.

This article reviews the basic information available and some of the analysis I have done using a single weekday as an example. Continue reading

Parliament and Roncesvalles 2010 Track Work (Update 11)

Updated December 19, 2010: Streetcar service resumed today on Roncesvalles Avenue to Dundas West Station.  The construction is not yet finished and this has predictably upset the neighbourhood.

The TTC seemed unusually ineptly prepared for this changeover.  Electric switches at many locations had not been reactivated requiring operators to throw points at commonly used junctions by hand.  The Sunday Stops on Roncesvalles which were not supposed to be part of the new design remain in place both at stop poles and in onboard stop announcements.  Indeed, the location of some stops appears to be a leftover from the shuttle bus operation.

At least one errant auto, parked in the wrong direction and foul of the southbound track, was struck by a passing streetcar.  Permanent signs indicating where people can and cannot park don’t exist yet, although a number of temporary “emergency, no parking” signs have appeared.

Anyone interested in watching service reliability can do so via various monitoring sites.

Meanwhile, Parliament Street reopened to regular traffic recently, and this morning, both the King and Dundas cars diverted bothways via Gerrard and Parliament to bypass construction on Broadview.  No pointman was provided for the westbound manual switch at Parliament, although on previous occasions the TTC has spent a small fortune manning this location for diversions.  Why the switch isn’t electrified is a mystery considering how frequently this diversion is used.

Continue reading

Follow That Car! (Updated)

Updated November 30, 2010 at 4:00 pm:

  • NextBus links added
  • Information about the Open Data interface added

Original post below:

With the advent of an Open Data interface to vehicle tracking information, there are now two websites providing real-time information about TTC streetcar routes (and a few bus routes) in addition to the official, but not well publicised, NextBus site.

This post is intended as a repository for information on these applications.  If anyone develops a new one, please let me know, and I will update info here.

George Bell’s Site

George’s site began using historic tracking data for individual routes that was supplied to me by the TTC for my route analyses.  Originally, the site allowed you to play back an individual day’s operation on a route to watch how it actually behaved.  This function remains in place along with real time views of the data posted through the Open Data interface.

Currently, this includes all streetcar routes as well as the Bathurst and Dufferin buses.  By default, all routes are shown, but you can select an individual route.  There is no filtering in either the historic or real time views, and the odd vehicle can be found in the middle of Lake Ontario or the wilds of Caledon when its GPS gets confused.  As I write thi, bus 1401 appears to be moored just south of the international border in what would otherwise be Scarborough if that mighty burg had territorial ambitions.

There are many available controls and I leave it to readers to play with the site.  Note that it tends to be rather CPU and bandwidth heavy for those who might be contemplating access from a mobile device.

And, yes, the URL is really “borkbork.com” for fans of the Swedish Chef.

James Agnew’s “Where is my Streetcar

This site, developed with contributions from Mike Humphrey and Dennis Yip, consolidates mapping and arrival projection information from NextBus in one package.  You can pick specific stops as points of interest to see what service will arrive, but the site will remember your favourites and offer them as easy clicks to save on navigation.

The map displaying the route will adjust to display that part of the city where the route lies.  Agnew and Co. may only be “programmers, not artists”, but conveniences like this are what make a good app.

Visit their “About” page for background info.

NextBus

The official repository for TTC vehicle locations and predictions is NextBus.  This system, whose software shop is based in west downtown Toronto, provides the arrival predictions available by SMS message (using stop identifiers texted to a standard TTC number) and by web.

The TTC does not advertise the availability of vehicle predictions via web, and this is a really big shame because it is a very useful service that is not a big consumer of mobile bandwidth.

To access this function, you must visit nextbus.com and navigate through the list of locations down to the TTC.  If your browser supports cookies, NextBus will remember where you have been and will go directly to your recent query on your next visit.  Otherwise, bookmark the displays you will use commonly, and use any of them as a jumping off point for your next visit.

For example, I often transfer from the 501 to the 504 eastbound at Queen and Broadview.  Once I drilled down to the display for this service, I bookmarked it and can now quickly obtain next vehicle info.  The display refreshes, a nice touch for those cold winter nights when the King car is somewhere out of sight beyond the Don Bridge.

You can get from whatever display you are on to another direction, route and stop with a few clicks.

This site can also be used creatively to get a feel for the degree of bunching or location of gaps by jumping around a route and seeing what predictions look like at various locations.

Full route displays are available, but links to them are not provided.  Here is a link to the King car’s map.  A menu allows you to select multiple routes for display, handy for situations where service is provided by more than one route on the same street.

These two services — predictions and the maps — are not advertised by nor linked to by the TTC, but are easily the best part of the NextBus site.

While you’re there, you can watch the transit service in San Francisco, among other places.

Updated Nov 30, 2010:

A simplified interface to NextBus is available at their Webkit page.  There is also a barebones mobile interface.  The webkit page is better.

Toronto’s Open Data Initiative

The TTC’s Next Vehicle Arrival System data are available online from NextBus.  The data feeds include:

  • A list of supported transit agencies
  • A list of routes within an agency
  • A list of stops within a route
  • Predictions for service at one or more stops
  • A list of changes in vehicle locations

These interfaces are intended for application developers.

LRT For Toronto

Royson James has a pair of columns in the Toronto Star discussing the perennial LRT vs subway transit debates.

City needs a transit lesson (Nov. 17, 2010)

Commuters won’t fill LRTs, much less subways (Nov. 19, 2010)

James sets out the pros and cons without becoming mired in either side’s arguments.  As with any overview, there are points for or against either technology that are not made with the vigour that advocates would prefer.  The important issue, however, is not to choose one technology to the exclusion of the other, but to look at the appropriate one for each implementation.

One critical issue — regardless of which side one might be on — is the matter of land use and how the evolution of Toronto will affect demand on routes and the overall network.  There are two fundamentally different views of of future development — the Official Plan’s “Avenues” with major streets lined by mid-rise buildings and shops giving an active pedestrian environment at ground level, or the more traditional “tower in a park” design that has shaped much of Toronto’s growth since the 1960s.  A third variant has appeared over the past decade — both tall and dense, as exemplified by the railway lands, parts of Liberty Village and most recently the Queen West Triangle (Queen & Dovercourt).

Each of these produces transit demands which vary both due to the built form and to the neighbourhood in which development occurs.  A building located in an existing walkable neighbourhood with shops and transit will have very different transportation demands than the same building located on a suburban arterial where the nearest shop is the mall a short drive or a lonely, windy walk away.

The perennial myth about subways is that their high capacity will be consumed by redevelopment around stations.  This is utter hogwash.  The Yonge line is full well north of Eglinton not with Willowdale condo dwellers, but with traffic fed in on surface routes.  Developments along the line add to the demand, but the subway exists to serve a much wider catchment area.  Similarly, the BD subway depends on feeder services to many stations, and the decades-long absence of nearby development did not prevent the buildup of demand eastbound from Etobicoke or westbound from Scarborough.

LRT lies somewhere in between by serving both busy “local” corridors and, in some cases, acting almost like a subway in speed, if not capacity.  We must remember that the SRT would have been an LRT line (and to Malvern too, decades ago) but for Queen’s Park’s intervention with the ICTS technology.  Regardless of technology, it is a medium capacity line whose principal function is to feed the BD subway at Kennedy and, much more recently, to serve the high-density residential development at Scarborough Town Centre, developments that did not occur until decades after the SRT opened.

In many ways, LRT has always been a misunderstood, orphan technology in Toronto.  Some within the TTC have never accepted the retention of streetcars, much less the creation of an LRT alternative to full-blown subway construction.  At a time when LRT was coming back into favour around the world, Toronto pursued ICTS and lost the chance to show what real LRT could do.  At more than double the cost of the LRT proposal, ICTS “proved” that there was no cheap way to implement transit lines, and system expansion stalled.  The TTC did nothing to advance the LRT alternative.

Spadina, Harbourfront and St. Clair are really not LRT, but rather upgraded streetcar lines.  That statement brings me to a common question:  what’s the difference between streetcars, LRT and “Heavy Rapid Transit” (or HRT)?  Everyone knows what subways, streetcars and buses are, but things get mushy in the space between them.

The boundary between HRT and LRT is fairly straightforward:  if the technology cannot run at grade in medians or crossing streets and walkways, then it’s HRT regardless of what vehicle actually operates on the structure.  There can be “light” railways such as the SRT, or full-blown subways, but in either case the lines are confined to an exclusive right-of-way.  This imposes costs and complexities wherever they are built.

The boundary between LRT and streetcar is not as clear-cut.  How exclusive is the right-of-way?  How much mixed-traffic operation does a route have?  How aggressive is the traffic signal priority?  Do passengers board through all doors?  How far apart are the stations?  How long are the vehicles or trains?  All of these issues and more produce a range of answers, and there is no magic point at which a light blinks on “LRT”.  That’s the strength of the technology — LRT does not have to be the same thing all the time on every metre of a route or a network.  The challenge is to strike a balance between the “light” and “rapid” parts of the name — exclusivity and speed versus the footprint a line can have in a street and neighbourhood.

The term “LRT” has been oversold in Toronto.  We have never seen something in the style of other Canadian LRT implementations in Edmonton or Calgary.  We lost that chance when the Scarborough LRT became the “RT”.  It’s still dubious whether we will see that route incorporated into an LRT network, or swallowed by a subway extension.

Toronto’s “LRT” routes run through downtown areas with frequent cross-streets where traffic signals grudgingly give priority to transit (but just as often serve to delay it).  They have slow on-board fare collection with high-floor cars and low-floor platforms.  They suffer a planning context where transit must fight to be acknowledged.

There is only so much road space and money to go around.  Subways make for flashy announcements and lots of work for the construction industry, but endless waits by riders whose trips are not served by the most recent subway extension. LRT lines (and busways while we’re on the subject) take space that would otherwise be used by motorists.  On some arterials, this space is available, but on many it is not (even VIVA’s BRT network is constrained in places by a narrow right-of-way).

LRT advocates have an uphill battle because Toronto’s version of this technology pleases few.  St. Clair was a disaster for “LRT” (and for transit in general) — there were too many design tradeoffs and construction was appallingly mismanaged.  Operations have improved over “the old days”, but still depend on keen route supervisors who actually manage the service rather than letting cars roam back and forth in packs taking generous layovers at terminals.  We may be rid of traffic congestion, but not the infamous TTC culture.

The political climate may shift back to one where we make announcements to appear to be “doing something”, even if that won’t bear fruit for a decade or more.  Such plans will serve only small parts of the GTA when finished (if ever), we will have yet another “lost generation” of transit investment.  Decisions about how to build, where to build, what to build are difficult and need more than an endless supply of magic markers, maps and press kits.

We have seen how a proposed LRT network suffered from funding cutbacks.  Major new revenue streams (tolls, regional taxes) cannot be implemented in the current political climate without a huge fight and an expenditure of political capital nobody seems willing to make today.

“The Big Move” could turn out to be little more than a modest expansion of GO Transit, busways, and a few rail lines of indeterminate technology within Toronto.  That’s not a network, and certainly not a recipe for convincing people that transit can offer an alternative to driving.  The challenge is to find a plan, a network, a quality of transit service that people are willing to pay for, however the money is raised.

LRT has a role as do full-blown subways and busways with each fitting into the mix under the right circumstances.  Advocates would do well to focus on the strength of each technology rather than trying to justify a full network of one option.  The goal is to improve and expand transit, not to prove that my subway is better than your streetcar.

Footnote:

Within James’ second article, the TTC is quoted as saying that ridership on the King car is 1,800 per hour.  It’s worth noting that the AM peak service is 30 cars/hour of which 7 trips are served by ALRVs.  The TTC’s service design capacity is 74 for CLRVs and 108 for ALRVs, and this gives a total for the route of about 2,450.  Crush capacity is higher.  A common complaint from riders is that they cannot get on, and this suggests that the demand cited by the TTC is rather lower than the actual level.