Early in 2007 when I started looking at the TTC’s vehicle monitoring (CIS) data, I thought to be finished with it long ago, to have blazed through many routes and written wonderful commentaries on all of them. Things didn’t quite work out as I had planned, and I got bogged down with competing issues and other calls on my time. Also, the programs that digest, massage, and otherwise render presentable the TTC’s data needed some housecleaning both to make them more robust and to reduce a lot of the manual work that went into the early analyses on 504 King.
Things are much simpler now, although the challenges of interpreting the data remain with each route offering its own peculiarities. Now I turn to the Dufferin Bus, a frequent route for which the TTC receives many complaints about service. How will it compare to routes we have seen already?
The route is 13.56km from Dufferin Loop to Wilson Station, although half of the scheduled peak service runs only to Tycos Drive about 3/4 of the way to the north end of the line. This is in the same range as the Carlton and King cars, although they spend much more time in “downtown” conditions. It is shorter than the 16.65km Queen-Humber route, and of course much shorter than the 24.43km Queen-Long Branch route.
The scheduled service is generally more frequent than on the streetcar lines, although with smaller vehicles so that headways are better for any level of demand scaled to capacity.
As I have done on previous routes, I will look first at the data for Christmas Day 2006 as this shows the route in its simplest state without any effects from traffic congestion, weather or heavy passenger loads.
29 Dufferin Service Chart December 25, 2006
29 Dufferin Northbound Headways December 25, 2006
29 Dufferin Southbound Headways December 25, 2006
29 Dufferin Northbound Link Times December 25, 2006
29 Dufferin Southbound Link Times December 25, 2006
The service chart is in the familiar pattern, although there are peculiarities that show up on all of the charts for Dufferin. Note the sawtooth patterns at about 500 (Lawrence Ave.), 340 (Rogers Rd.), 200 (Bloor St.) and 100 (Queen St.). These are all CIS signpost locations, and quite commonly the position calculated from a vehicle’s odometer must be reset when it reaches these points. The buses have not actually moved backwards, only the position used by CIS.
At the top of the chart, you will occasionally see small “tails” extending above the 640 line (Wilson Stn.). These are buses that reported a location to or from Wilson Garage.
Between Dufferin Loop (50) and King St. (80), some vehicles appear to move very slowly. Looking at this closely, it is often the same vehicle on repeated trips, and this may indicate that certain vehicles don’t reliably report their departure from Dufferin Loop. The data gives the impression that they leave much earlier than they actually do. By King Street, however, everything is back in sequence.
What is quite visible on this chart is the same sort of bunching that we see on other routes with vehicles running in pairs. This is particularly evident in the evening causing wide gaps in service.
The headway charts show the same behaviour we saw earlier on the King and Queen lines. Buses leave Dufferin Loop (first page of the northbound charts) on widely varying headways even when the average (and scheduled) headway is under 4 minutes. The plus-or-minus three minute rule clearly does not apply here and headways over 9 minutes are common. Many headways are at one minute or less showing that buses leave the terminal together.
The timepoints I have chosen for Dufferin were selected to avoid areas where it is difficult to resolve the location of the buses due to correction effects. The timepoints are:
- Dufferin Loop
- King Street (useful for calculating round trip times to Dufferin Loop and, hence, layover times)
- Dundas Street (south of the congested area around Dufferin Mall)
- Dupont Street (north of the subway connection and the end of a congested area on the route)
- Eglinton Avenue
- South of Lawrence (chosen because data at Lawrence itself is unreliable)
- Wilson Avenue & Dufferin Street
- Wilson Station
The irregular headways persist over the length of the route, although they do not open up into wider gaps as we move from one end of the line to the other as they do on King. Note that headways in the evening when the schedule is 8 to 9 minutes continue to be erratic, but the swings (even those within the TTC’s three-minute target) produce wide gaps in service.
Link times are consistent over the route as one would expect on a holiday. The spikes in the northbound (up) trips from Dufferin to King are caused by the problem mentioned above where the departure time from the loop is not reported, and the last known time for a bus at the loop is much earlier than it really was. A similar problem happens southbound from Wilson Station.
In the next installment, I will look at overall headway and link times for the month to see the general pattern of operations before turning to a few specific days as examples.
Bunching is horrible along Dufferin- usually 3 or 4 vehicles, especially at Dufferin Loop. I would be curious as to the reliability of available bike racks.
I’ve ridden 29 Duffern only once — a weekday heading home from the CNE (to Wilson Stn). Even with the extra service, I could easily see service was erratic at best.
At numerous points on the route, I could see larger crowds at some stops, indicating that buses had not been by in a while. Some buses had large gaps between them, and usually the bus behind such a gap was crushloaded, often with 2 or 3 buses right behind also crushloaded. Funnily enough, there was a large crowd of buses filling Dufferin Loop (most would go to Dufferin service, some on 193). My bus was passed by Queen by another bus, which turned back at Dufferin Stn (and no, there were hardly any pickups south of Queen to delay us).
Some people have blammed this bunching on the high-floor Orion Vs that provide service, and say that it should be converted into a low-floor route since many strollers/wheelchairs use the route, and a low-floor ramp is easier and quicker to deploy than a high-floor lift.
Another dealing with 29: One day while I was on Tycos Dr., I saw 4 buses pass by in about an hour to 1.5 hour span. This was on a Saturday.
The problem with the 29 route is that, there is no offical station for a bus to stop and pick up. Since Dufferin station is a “stop” on a bus route, there is 1 bus for two routes. For example if there was a Southbound route from Nloor to the Dufferin Loop and a northbound route from Bloor to Wilson station, then it would be much easier to organize route times, and it will be similiar to the Victoria Park 24 and the 12 line.
In the summer, I went to the CNE grounds in july for a visit. It was a day with no special events. I took the 29 at around 3 pm. I saw 3 29 buses at this loop doing nothing but just parked there and the drivers just chatting. Now I know they could be on their break, but this is unacceptable.
Hey, Steve I want to say that your site is amazing, but maybe we could have a message board. It will create more discussion on these important topics. There are two other routes in the TTC line I think is also very poor. The Bellamy 9 (only 1 bus on the route on weekends and on week days 15-20min just if you’re lucky) and the 102 Markham.. there are always 2 or 3 bunched together and if you miss that you have to wait 10 min.. Now I don’t expect you to include this in this thread I just wanted you to know that and your own personal opinion.
Steve: The bus routes for which I have data, in addition to Dufferin, are Bathurst, Finch West and East, Don Mills and Victoria Park. I also have data for all the streetcar lines although I have not yet presented analyses of Spadina/Harbourfront, Bathurst, Dundas, Carlton or St. Clair.
I run this site in my spare time, and there are times it sort of takes over my life when an important issue breaks. I’m not planning to allow any additional features because then I would have to monitor them, and I want to keep the overall quality high and the focus on topics that interest me. Even if readers don’t always agree, the discussion is interesting and forces me to think about my own positions.
I really appreciate the route analysis and the zig-zag time/location charts are a fantastic way of presenting the data. But if you would consider it, I have one request. Could you produce different charts for UP trips and DOWN trips? During the peak periods those charts become a mess of lines and I find them unintelligible. Separate charts for UP and DOWN would make it far easier to interpret headways and travel speeds. A million thank-yous if this is possible.
Steve: It is possible with a bit of programming, although an alternative is to change the data display in either of two ways.
Shorten the time span for one page to spread out the data.
Change the paper type from letter to legal to give more horizontal space.
The main reason I show both directions on one chart is that it clarifies which trips go together. This reveals situations where the same vehicle consistently runs immediately behind another one, and clarifies behaviour at short turns.