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

How Essential is the TTC?

In the past week, the TTC board and City Council have voted to ask the Ontario government to make the TTC an “essential service”.  During the debate, this action was opposed by both the TTC’s management and union on the grounds that this will only complicate labour negotiations.  Issues will go to arbitration that might otherwise be bargained between the parties, and costs will increase through the typically higher wage settlements granted to workers who do not have the right to strike.

Those who favoured essential service status argued that this is, de facto, the way things work anyhow.  When a transit strike occurs, it takes a few days, but the machinery of back-to-work legislation doesn’t take long to restore service.  Why, then, endure the upheaval of a short work stoppage if legislated arbitration will be the result?

This is an attractive argument, except when one looks at the context.  Toronto Council and the Mayor’s office has changed from the most pro-labour group any union could expect to see to an administration that makes little secret of its will to reduce the influence and effect of organized labour in Toronto.  Got a problem with garbage workers?  Privatize the service.  Got a problem with transit workers?  Make them “essential”.

Such actions may satisfy the urge to show the unions who is boss at City Hall, but they may not be the best policy for the city.

There is no question that the civic workers’ strike of 2009 was a turning point in Toronto politics.  Not only was it a lengthy strike, but one which saw contentious relations between union members and the very people — the voters — those members needed to gain political support for their position.  They failed miserably.  Much was written about who “won” the strike, and the union managed to convince everyone that they came out on top even though they conceded on the key issue of future sick benefit payouts.  The problem, at the end, was that voters endured a strike that seemed to have solved little (although the outgoing administration and city finance officials will tell you differently), and the voters were fed up.

Stir into this the wide perception that TTC workers are at odds with the people they serve.  The “sleeping collector” front page [RIP] was not the Toronto Sun’s finest moment, but the photo and the anti-union sentiment it provoked cut right across the city.  Relations between TTC staff and riders took on an “us vs them” feel that has reduced somewhat, but they remain less than ideal.  Some operators, a few, really are jerks.  Stories of buses held hostage while an operator claims harassment by a passenger still crop up.

Service on the street isn’t what it might be.  We can always use more buses and streetcars, but there are enough cases of operators fouling up service that this minority can easily be blamed for many service problems.

All that said, making the TTC an “essential service” won’t improve manners among the rotten apples, and won’t make the Queen car or the Dufferin bus run on time.  That takes an organizational will to provide service that’s as good as possible rather than always blaming problems on someone or something else.

The TTC and its new Chair, Councillor Karen Stintz, hopes to make Customer Service a top priority in the coming term.  The TTC must regard its customers as vital, its raison-d’être, not as pesky travellers who need to be taught how to behave properly on transit vehicles.  This is a question of attitude, not of labour negotiations.  Indeed, the organizational culture isn’t only on one side of the bargaining table.

Finally, the problem will land back in Council’s lap with the inevitable call for better transit funding, if only to keep up with inflation, system growth and the inevitable wage increases arbitration will bring.  How “essential” will transit be then?

The opportunity for a vindictive attack on transit workers and labour relations was probably the most “essential” part of this whole affair.  The new regime had a chance for chest-beating and a quick win that will probably do little, on balance, to improve transit.

In coming months, we will hear budget debates at the TTC and at Council.  Those who worship the holy grail of tax cuts will give long speeches about efficiency and belt-tightening, about how riders will have to make do with less service and higher fares, about how “the taxpayers” (as if they are not also transit users themselves) cannot be expected to bear a greater burden.

If transit really is essential to the economic health of Toronto, then Council must be prepared to spend and spend generously on this service as an investment in the city’s future.  We will see just how “essential” transit is to our new Council when the bills come due.

TTC Meeting Preview — December 2010 (Updated)

Updated Dec. 11, 2010 at 2:20 pm: The section on the site remediation report for the proposed Ashbridges Bay carhouse has been updated to reflect a June 2010 report on a possible alternative site near Broadview and Eastern.

Original article from Dec. 10, 2010:

The new Toronto Transit Commission dominated by political supporters of Mayor Ford will hold its first substantive meeting on December 15, 2010.  Among items of interest on the agenda are:

Continue reading

Did Toronto Council Ever Vote For Transit City? (Update 2)

Updated Dec. 8, 2010 at 7:45 am:  On Sept. 30, 2009, Council voted to fund continuing work on Environmental Assessments, and to enter into an agreement with Metrolinx for funding of the Sheppard, Eglinton, Finch and SRT projects.

Updated Dec. 7, 2010 at 10:30 pm:  This post has been updated with additional info supplied in a comment by a reader.  See the body of the article for the change which documents a vote in 2009 reaffirming Council support for Transit City.

In the brouhaha of Mayor Ford’s inauguration, his brief meeting with Premier McGuinty, and the question of whether Council will support ditching the LRT plan in favour of a subway network, a question comes up often:  did Council ever actually approve the Transit City plan, or was this just done by the TTC Commission itself?

Continue reading

Apologize, Now!

In a piece of political theatre utterly unworthy of Toronto, Mayor Elect Rob Ford invited Don Cherry, a loudmouth sports celebrity who is paid a small fortune to pontificate about hockey, to address the inaugural meeting of Council today.  Cherry proceeded to insult over half the population of Toronto, those who didn’t vote for Ford, those “left-wing kooks” and “pinkos”.

If I or any member of the public, let alone a member of Council, had made remarks like that, they would have been summarily silenced by the chair and possibly thrown out of the room.  This bozo was there as the Mayor’s guest, telling it like it is.

Mayor Ford allowed the important ceremony of his investment in office to be cheapened into a political slam against all those folks, the downtowners, the latté-sippers, the people who like streetcars, and who knows how many other groups who have yet to learn just how small-minded our Mayor really is.

The words may have been Don Cherry’s, but they were said with Mayor Ford’s blessing.

Cherry is an asshole who has no place in Council Chamber, a clown who cannot understand the difference between the entertainment of a break in a hockey game and the serious business of Canada’s largest municipal government.  He is no doubt thrilled to death with the exposure.

The Mayor has a duty to all of the people, and to the Council itself.  He ran on a campaign of respect for taxpayers.  That doesn’t mean just the ones who voted for him, but all of us.  I shouldn’t have to produce a photocopy of my ballot to get attention at Rob Ford’s City Hall.

The institution of Council has already been sideswiped by Ford’s one-man show on municipal policy, the attitude that his “mandate”, all 47% of of it with a 53% voter turnout, gives him the right to rule by edict, not by agreement.  Now, by inviting Cherry to speak and failing to censure what was said, Ford has insulted all of Council and the voters — all of them.

Mayor Ford:  Prove to us that you’re not the boneheaded idiot 53% of Toronto thought you would be when they voted against you.  Apologize, unreservedly, now.

Waiting at Sheppard & McCowan

On Monday, December 6, CBC’s Metro Morning included a piece by Mary Wiens about the problems of commuting through the suburbs, and the hopes of folks on Sheppard (and by implication many other places) for a subway network some day.

In reply to this, I sent a note to Mary talking about some of the issues and misunderstandings, and my sadness at the degree to which people who think they voted for subways have been misled.  Metro Morning liked the piece enough they asked me to record it, and it aired on December 7.  As I write this, the podcast version is not on the CBC’s website, and so I have placed a copy on my own site.  When the podcast goes up, I will switch the link to use the CBC’s version.

What About Transit, by Mary Wiens

Steve’s Letter, by Steve Munro

The Day The Big Move Died (Update 2)

Updated December 2, 2010 at 11:55 pm:

The Globe and Mail has a story by John Lorinc echoing the sentiments here with quotes from sundry people weightier than I am.

The Star reports on provincial reaction to Mayor Ford’s move.

Updated December 2, 2010 at 1:50 am: The Globe and Mail reports on a poll of Councillors regarding support for Transit City or subways.

  • Pro Transit City:  14
  • Transit City + Tweaks:  4
  • Subways:  11
  • Unknown:  15

Original article from December 1, 2010:

Toronto’s new Mayor Ford, acting with a haste uncharacteristic in Toronto affairs, and without even bothering to consult his new Council, has directed the TTC to stop work on Transit City.  The “war on the car” is over, and all new rapid transit will be underground.

The deafening silence from Queen’s Park shows us how much Metrolinx and its regional plan, The Big Move, depend on political agreement among GTA municipalities.  Removing the pols from the Metrolinx Board may have centralized important announcements at Queen’s Park, but it did nothing to blunt the effect any local Mayor or Council can have if they don’t play ball.

The Big Move has both a 15-year and a 25-year component, although the likelihood either of these would see substantial construction was compromised the moment Queen’s Park’s budget priorities trumped a scheme to build major transit improvements first as a prelude to new revenue tools.  Nobody wants to talk about taxes or tolls, but money for transit, whatever the technology, won’t come from the tooth fairy.  It won’t come from the private sector either, at least not without a guaranteed return on their investment.

Ford, whose aggressive tactics on Council are well known but whose character was carefully controlled during the election, has shown that he has a plan, and feels that his mandate gives him carte blanche to implement whatever he wants.  The voters have spoken.  Those who voted for 44 Councillors might beg to disagree, but that’s for Council to decide in weeks and months ahead.

The real problem is the lack of leadership on the transit file from Queen’s Park.  The Big Move was cobbled together from many local plans, including Transit City, and flawed though it might have been, there was general agreement about the shape of the plan.  Changing Toronto’s focus to subways unbalances the plan’s scale and benefits, not to mention the huge change in net cost.  Mayor Ford’s concern for taxpayers’ dollars appears to end when someone else is expected to pay the bill, and this could deprive Toronto of transit improvements while growth proceeds on smaller-scale projects in the 905.

If we can rip Transit City out of The Big Move with only the barest of response from Queen’s Park, how safe is the rest of the plan?  Will expansions in Mississauga, Hamilton, York Region and Durham be subject to the whims of whoever is in power, or will a semblance of regional planning remain?  Will provincial efforts dwindle to supporting GO Transit, an organization whose forced marriage with Metrolinx is still quite shaky.  The bride and groom are still arguing over decorations, and they almost certainly have separate bedrooms.

Readers who know me well will appreciate that today is not the brightest day in my history of transit advocacy.  It would be easy just to write a bitter rant against the incoming regime.  That would be a waste of time — they won’t read it anyhow, any more than they will listen to editorial boards at the Globe and Star.

That regime is not stupid, although many would paint Ford and his crew as a bunch of bumbling hicks.  They know what they want to achieve and they appear ready to push as hard as possible until, no, even if someone pushes back.  That’s the role of Council and of Queen’s Park if they really believe in Transit City.

There is a place for LRT and for subways in Toronto, and if we are to remake the transit plans, this process deserves more than the midnight YouTube announcement of Ford’s election campaign.  It also deserves a concerted effort by transit supporters everywhere to fight against slurs of downtown elitism, and to argue strongly for better, cost-effective transit.  We need to ensure that the “war on the car” is not replaced, stealthily, by a war on transit.

As for Metrolinx, I can’t help wondering what, exactly, its purpose is.  The Board rarely meets in public, and doesn’t discuss much of substance when it does.  Major announcements come from the Premier or the Minister, and many of these deal with GO plans that were in the pipeline before the Metrolinx amalgamation.  Now we see a Mayor can just tear up part of the plan, an ironic situation considering the grief David Miller endured for trying to get Toronto’s interests recognized at Queen’s Park.  If the Tories win the fall 2011 provincial election, Metrolinx and its hoard of consultants may find themselves out of work, and transit may be relegated to a desk at the back of the Ministry of Transportation offices in Downsview.

Meanwhile, my box of “Big Move” documents can join the many other plans in my archives.

LRT vs Subway — A TTC View

Before Mayor Ford took office, the TTC briefed his transition team on the comparison between LRT and Subway options for the Sheppard and SRT projects, as well as on the status of Transit City.

This article presents a condensed version of the information.

TTC Briefing Summary

The Briefing Summary contains three tables consolidating information scattered through many pages of the briefing documents.

The first page shows the committed and spent funding for the four projects:  Sheppard East, Eglinton, Crosstown and Scarborough.  An important note here is that the lion’s share of the money is in the period from 2015 to 2020.  Queen’s Park expects to raise this via whatever “Investment Strategy” Metrolinx comes up with, but the funding machinery is not yet in place.  Only the $3.1-billion for 2010 to 2015 is “money in the bank” for Toronto.

This is the first of several potential drags on any plan to revise or accelerate transit construction.  Queen’s Park has not planned to spend most of the money until after not just one, but two coming Provincial elections.  Moreover, they have not yet engaged voters and taxpayers with a debate over the exact source of funds be they tolls, taxes or the Tooth Fairy.

To the end of September 2010, just over $129-million has been spent, although there are commitments for considerably more.  At this point, we have no idea of the “break fees” involved in closing down these contracts.

The second table consolidates the status information on the four projects.  An important point here is that the extended construction period is determined by Provincial spending priorities and the desire to shift as much as possible into the “Investment Strategy”.  The original plans for both the Finch and Scarborough lines would have seen them completed years earlier.  The constraint is financial and political, not technical.

The third table shows the cost estimates for two variants on the Scarborough line as a subway (one ending at Scarborough Town Centre, the other at Sheppard), and for a Sheppard East line running to STC.  Schematic maps for each line are linked below.

TTC Scarborough Subway

TTC Sheppard Subway

It’s worth remembering how little of Sheppard Avenue in Scarborough would actually be served by the extended Sheppard Subway.

A critical point for the SRT is that in the subway scenario, it would have to remain in operation until 2022.  The TTC was concerned about making it last to the Pan Am Games in 2015, and a 2022 date is not credible given past TTC comments on the declining reliability of that line.

The presentation materials end on a summary page that concludes that the segment from Kennedy Station to STC is the “best candidate for a subway”.  This reiterates the TTC’s long-standing anti-LRT position for the Scarborough RT by comparing only the portion of the line from STC south.  The whole purpose of an LRT conversion was to reduce the cost of reaching Malvern, but with a subway plan that will never happen.

TTC staff is expected to produce some sort of subway plan in about six weeks, probably in time for the January 2011 Commission meeting.  We will see how much is a fair presentation of options, and how much is creative writing.

The big issue for me is that if we are going to have a subway-oriented plan, then it should be a plan that serves the emerging needs of the whole city.  Just building as much as you can with the money now earmarked for Transit City will give the impression of movement, but most of this will be to the benefit of the construction industry, not transit riders.  We need to know where demands are growing to the point where some form of rapid transit is needed, what form that would take, and how much it will cost.  Otherwise, voters will have a big surprise when they see how little they get for a substantial outlay.

Comments RSS

A link has been added to the comments area allowing readers to pick up the feed for comments on a specific article.

This option had been lost in a previous upgrade, and finally I got around to putting it back.

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.