The BusGraphs Project

Ridership-based route productivity measurements—those which compare a route’s average number of riders to its cost of operation—are common within transit planning. Unproductive routes will be the first considered for elimination when funding is tight. Those that perform well may merit additional service when the budget supports expansion. I have previously argued that ridership-based measurements are, at best, incomplete for these purposes. There are factors beyond ridership that determine how much impact the elimination of, or investment in, a route will have. Transit routes have varying amounts of capability, regardless of how many people choose to take advantage of it. The transit agencies that I’m familiar with entirely neglect this factor, though, perhaps because they lack a way to quantify it. Measuring access offers a solution. While this style of analysis has become increasingly common at the network level, using it to compare the contributions of routes within a network has not.

I’ve recently improved my access analysis software to adjust walking speed based on change in elevation. The use of a constant walking speed, regardless of terrain, in previous analyses opened them to legitimate criticism, especially in hilly Seattle. A walking model can now be selected when computing an access analysis. At this time, there are two options: the original constant-speed model, and one that attempts to characterize how an average person navigates changes in elevation. Obviously, this is not a complete solution to the problem of accurately modeling how people get around. After all, walking speed is affected by elevation change in different ways for different people, and, for some, walking is not how they get around at all. Allowing for any variation is merely the first step on a path toward the ability to model the experience of any transit rider.

I’ve released the source code for the access analysis system that I have built to produce the maps and data in these posts. It resides in a collection of repositories, and basic setup instructions for deploying it onto Amazon Web Services are provided. All source is released under the GNU Public License v3.0.

Transit access is frequently depicted with isochrone maps. Given a starting point, time of day, and time budget, determine all the places that can be reached within that budget using transit and walking. These maps are not a new concept, with examples dating to the late 1800s. This site’s glossary depicts one of Melbourne, Australia from the 1910s as an example. Public transit consultant Jarrett Walker uses them aptly to explain the idea of access as a “wall around your life”. The bounds of the isochrone form this wall. Improvements to transit networks expand the area inside of it. It’s a compelling, understandable image.

This is a revised examination of a measurement of how individual transit routes contribute to overall access in Seattle. The first attempt was subject to a computational error that caused incorrect figures to be reported for certain routes. This iteration fixes that issue, and also uses updated schedules for King County Metro and Sound Transit that will take effect on September 14th.

The first version was presented in a series of parts. In each part, I chose a group of thematically similar routes and computed five measurements for them. I now find this approach to be somewhat clunky. These measurements don’t have clear “good” or “bad” values; they are only useful in comparison. Thus, it was difficult to meaningfully evaluate the routes chosen in the early part of the series. This revision presents all routes at once.

Twice a year, King County Metro revises its bus service. Most of the time, the revisions are small. Fluctuations in funding and the workforce may cause a few trips to be added or deleted, and construction projects may necessitate minor changes to routes. Often, the service revision is a non-event for riders, and the access implications are miniscule.

When Metro does make big changes, they’re typically in response to external factors. On September 14th, the agency will make its most substantial set of modifications in a few years. Sound Transit’s Lynnwood Link extension is opening at the end of August, and some Metro routes in North Seattle and Shoreline will change to connect to the new stations. Also, the construction of transit-priority features on Madison Street will be complete, enabling the launch of the RapidRide G Line. Some routes in that line’s vicinity will see changes as well. Amidst these additions and modifications are deletions of bus service from some corridors. This is a move that the agency has typically seemed loath to make. Often, cuts like this appear in early versions of a service revision, only to be rolled back when the agency receives complaints. While the deletions typically are intended to enhance service elsewhere, transit customers are loss-averse, and Metro is usually sensitive to negative feedback to a fault. In this case, some significant cuts survived several rounds of scrutiny.

Last week, Metro updated its GTFS schedules to incorporate the forthcoming service change. That allowed me to compute access measurements that reflect what riders in Seattle will experience when the new routes start running. If they are to be believed, riders are in for a mixed bag. For a service change that finally makes investments in new service after a pandemic and workforce shortages, that’s disappointing.

When the annual Fremont Solstice Parade celebrates the arrival of summer, King County Metro must reroute its buses around it. Routes 31, 32, 40, and 62 serve Fremont, and the parade forces them off their typical paths.

I was intrigued by the detours. The routes weren’t just avoiding the parade, they were bypassing the Fremont Bridge entirely. Mass transit has used the Fremont Bridge since its opening in 1917. It was built with two lanes of streetcar tracks on it. In spite of this precedent, I couldn’t help but wonder if Metro’s service could be better if no routes crossed it at all.

This is an updated proposal for transit service in Seattle that exceeds King County Metro’s definition of frequent service on all routes 24 hours per day, 7 days per week. Compared to its predecessor, it incorporates some changes to mitigate potential overcrowding, and, more importantly, uses a corrected budget of in-service transit hours. Correctly assessing, and holding to, this budget is critical for this proposal. In-service hours drive agency operating costs. As tempting as it is to imagine what a better-funded King County Metro could accomplish, I fear that not holding to a budget would push a proposal that is already ambitious and challenging into the realm of the totally impractical. As the budget of in-service hours is about 12% less than previously thought, the resultant route map looks sparser. Some bus routes that many people use daily would disappear, without direct replacement, under this proposal.

Removing existing routes is bound to be unpopular. Why consider it when running routes with uniform headways throughout the day and night is unheard of among transit agencies? I assert that their choice not to do so contributes to automobile dependence. I made this argument in more detail when I debuted the initial proposal. In short, if a person fears that relying on public transit will eventually leave them in a situation where they desperately need to make a trip, but can’t in a reasonable amount of time, they will prioritize purchasing a car. Once a person owns a car, the marginal cost of each use is low, compared to the fixed acquisition and maintenance expenditures. It will get used even for trips that could be reasonably made with transit. The increased congestion undermines transit that shares right-of-way with private vehicles. It can even hinder attempts at constructing dedicated right-of-way, since construction decisions will favor minimal traffic disruption over optimal station placement. As unusual as uniform frequency may seem to a transit planner, I believe that it is a necessary ingredient in a transportation system where fixed-route public transit is intended to largely supplant, not supplement, private vehicle use.

Due to a software error, the in-service time amounts computed for transit networks in previous posts are inaccurate. Posts where an access measurement is used on its own are not affected. When access is expressed in terms of the amount of in-service time—whether for the entire network or an individual route—this quantity may be incorrect. In specific, these posts are impacted:

• Seattle’s Transit Agencies Can Do Better
• How to Cut Service by 22% and Boost Access by 13%
• A Seattle Transit Restructure by the Numbers
• The Aftermath
• Seattle Could Have 24/7 Frequent Service; King County’s Priorities Seem to Lie Elsewhere
• The entire Route Productivity series

Due to a computational error, the data and conclusions in this post may not be accurate.

This installment of the access-based route productivity series focuses on four routes that serve Seattle’s Capitol Hill neighborhood, but are otherwise quite varied. Three of these routes skirt downtown, but one passes through Capitol Hill on its way there. Two meet Metro’s definition of frequent, one runs less frequently but all day, and one is the rare example of a peak-only route not oriented around downtown. The variation continues in the positions of routes 8, 9, 11, and 60 within Metro’s ridership-oriented route productivity measurements, and my access-based ones.