« social media's influence on public transit (guest post) | Main | graphic artists! seeking ideas for book's cover »

07/11/2011

network design for high ridership, a dense city example

How do transit network designers go about their task? Surprisingly little has been written about this.  You can pick up books that appear to cover the "network planning" process and find examples of good and bad networks but rarely a description of how to do the design thinking itself.  EMBARQ's recent manual for network planners in India, for example, provides great detail about how to analyze demand and evaluate results, but show no awareness of the really challenging task of network design, which sits in between those tasks.

I'm thinking my next book will probably be a little e-book talking through the process in more minute detail. For now, let me talk through a quick example, just to capture the outlines of how a network designer might approach a problem. 

My example is the core of Halifax, Nova Scotia, a dense peninsula built out mostly before 1945 and therefore highly conducive to transit.  It isn't the only transit-conducive place in the metro region, but it's the largest, and its peninsular location helps us isolate it as a design problem, so I can discuss it in a brief example.

spacer

The peninsula's developed area is about 6 km (4 mi) long and 3 km (2 mi) wide at its widest point. 

First, we take stock of the strategic focal points, especially major destinations and chokepoints.

Major destinations are part of why you'd focus on the Halifax peninsula as the core of any effective regional transit strategy.  The strongest transit destinations are:

  • intense, in terms of number of people coming and going.
  • all-day, so capable of using relatively efficient two-way, all-day service instead of just the more expensive one-way peak commuter express service.

Those are usually places with lots of people coming and going, not just employees.  What kinds of places are those?  Large scale:

  • Government institutions
  • Universities
  • Medical facilities
  • Retail

They're all on the peninsula.  Provincial government, two universities, the major medical centers serving all of Atlantic Canada, and retail centers both downtown and on the west edge.

The other reason you focus on the peninsular core is that it's already dense and walkable, because most of it was built before 1945.  So much of Halifax is here, and is so amenable to transit, that a strategy trying to optimize transit mobility must take full advantage of these opportunities.  If you care about mobility to an outer suburban community, you must care about circulation within the peninsula, because many of your citizens are going there and they may need to move about within the peninsula while there.  What's more, peninsula residents who choose not to own cars (which for many could be a viable and liberating choice) will sometimes need to travel outward, and a transit-intensive peninsula will generate outward transit demand further supporting the radial services that outer suburbs need.

So what do we have on the peninsula? 

spacer

All access is via just six chokepoints (red circles), plus ferry lines east across the harbor.  These will be ideal locations for transit connection points (yellow rectangle with T) because many lines, offering travel to many origins and destinations, must converge there anyway.  So the transit agency has done a good job here.  Except for the northernmost bridge and the northernmost exit to the west, all the chokepoints have transit connection facilities nearby.

The whole peninsula is dense and there are tall buildings here and there throughout, but the big concentrations are in the areas I've shaded.  Downtown is the blue area on the waterfront, while the parallel blue box further west is the medical zone.  The magenta zones are the major universities.  The southern one, St. Marys, is a Catholic school with about 7000 students.  The northern one, Dalhousie, is a major public university (16,000 students) that spills eastward along the green axis toward downtown, mixing with major medical facilities, office buildings, and dense, often student-oriented housing.  This green area is the core of a potential sustainable-transport paradise, because all the elements that make Halifax in general such a strong market (listed above) are mixed especially closely here, while the dominance of the universities, medical facilities, and shopping guarantees all-day two-way flow, the best situation for highly efficient transit.

I hope you've followed all this even if you don't know Halifax, because the same kind of assessment needs to be made of any city.  This doesn't mean that you have to have all of Halifax's features, but you need to be looking for those features you do have, with particular focus on density patterns and chokepoints, becuase these are the best starting point in defining a strategic outline of the network, within which you can then develop local ideas in more detail.

Now we look at the network of major transit-operable streets:

spacer

The grid pattern means that some kind of high-frequency grid is almost certainly in order, so that people can get anywhere to anywhere on the peninsula with at most one connection.  Obviously, since all trips within the peninsula are short, connections are a bigger disincentive, so we'll try also to link major destinations with direct services.  However, if we made direct service everywhere to everywhere our primary goal, we'd end up with lots of overlapping lines and would struggle to afford enough frequency on them all.

Notice, however, the way the southwest edge of the peninsula runs on a diagonal compared to the street grid.  That's an invitation to draw L-shaped lines, an east-west grid element connected to a north-south grid element.  Like this:

  spacer

Grid lines that "bounce" off of diagonal edges, like this one, tie together more destinations without a connection while remaining complete grid lines (i.e. running all the way across the grid)  so as to maximize the number of other connections that can be made. 

But Oxford Street sort of peters out at the north end, so where do we go?  We "tie off" or "anchor" the line by going to a nearby major destination where many other connections will be available.  Fortunately, one is nearby.  The "T" just southwest of where Oxford ends is also a major shopping center. 

Meanwhile, at the other end, we notice that many connections throughout the east-of-harbour Dartmouth area are available at a "T" just over the bridge.  A single frequent line to that point, covering many of the major destinations of the peninsula, can plug into all of those connections, so that the whole catchment area has easy one-transfer access to most of these destinations.  So we have this:

spacer

And in fact, Halifax's Metro Transit has already had the same thought.  Their most frequent transit line, Line 1, looks like this:

spacer

It's on Spring Garden instead of South, but that's only about 400m difference.  The university and most medical facilities in the area are adequately served from either.  But Spring Garden is more of a continuous "mainstreet" through this area, although major institutions front on both. 

So what have we missed?  Well, the next big corridor is Robie, which (along with nearby parallel streets like South Park) is really the medical axis.  It would have been tempting to turn our first line north along Robie instead of Oxford, because while Oxford is perfectly fine lowrise density Robie has the highrise intensity of institutions.  At the south end, Robie bounces off the diagonal grid-edge as Inglis, which gets us to the smaller university, St. Mary's.  If we bounce again at the east end of Inglis we head north along Barrington into downtown.  Once we're past Spring Garden we're duplicating the first line, but we're virtually downtown by this point, so duplicative service on one street, adding up to very high frequencies, makes sense and can be useful for internal downtown demand.  (Remember, the shorter the trip, the higher the frequency you need to compete for it.)  So that suggests something like this:

spacer

This is not what existing service does.  Robie now has an overlay of several lines doing slightly different things, several of which end in a very odd one-way loop at the south end, like this one, rather than going downtown. 

spacer

Perhaps it's just trying to turn around.  One-way loops are a good idea at outer low-density ends of lines, but they introduce needless confusion and circuitousness in dense areas, where it should be possible to serve all markets two way.

Meanwhile, back in our ideal grid, our Robie-Inglis route encountes a perplexity at its northwest corner.  At Chebucto Road, Robie seems to branch into the continuation of Robie and the larger Windsor Road, which takes on a more car-oriented character as it heads for the chokepoint at the far northwest corner of the peninsula, near Clayton Park.

This situation is tricky, and I wouldn't make a recommendation at the high-level scale of this exercise; much deeper knowledge of existing travel patterns and land uses would be needed.  For now, let's assume that the smart thing to do is follow Windsor, because it completes the grid, serves a chokepoint, and thus is useful both as an internal corridor on the peninsula and a gateway path to the larger region.

spacer


Now, you can see how some east-west frequent lines would largely complete the grid.  To work best they'd have to aim for the chokepoints too, so that while offering intense local circulation within the city they'd also provide access to much of the peninsula from the surrounding suburbs.  Metro Transit has already drawn most of these lines, and they seem to work pretty well except that many aren't frequent enough to really function in a high-frequency grid, or even to compete for the very short east-west trips that they would serve within the dense peninsula.

spacer

The dark blue line, existing lines 2 and 4 combined, is already every 15 minutes, but the other two key grid lines here, orange Line 6 on Quinpool and and green Line 9 via the far north, are still every 30, not enough to really function as elements of a grid. Notice too how 6 and 9 bounce off edges of the grid, completing linear corridors before turning to find a major destination and connection point at which to terminate.  (Lines always want to terminate at big destinations, called anchors in the business, because otherwise they tend to empty out near the end, leaving permanent wasted capacity.)

Yes, there are still gaps, but we've hit all the major denstinations and most of the peninsula's density.  As we turn to those gaps, network design starts to get fun and subtle, as we have to dig into more detailed data to find the clues for how we should patch routes together.  And here I'll stop, as I've reached the end of what I can do in such a "high level" view.

But here's my point:  I'm almost certain that the lines drawn here, or something very, very like them, would be part of a successful network for Halifax, because they are big-picture responses to issues that are obvious at this big-picture scale.  Network designers sometimes fail to take this high-level sketch planning step, and instead wade too quickly into the million possibly interesting details.  If you focus on too much detailed data too soon, though, you end up wandering around inside the data, unable to get any big picture "structure" that you can hang onto while you consider the subtler questions. 

Also, while it's very important for many people to be able to follow this kind of thinking, designing optimized networks, especially in difficult geography, is a bit of an art.  Like any inductive thought, it involves deeply understanding the data but then being open to ideas that come in unpredictable bursts of inspiration, much the way scientific theories come about.  The "having ideas" part isn't in many manuals because it's not really teachable; it's to some extent an innate talent.

Consultants like me can help with the subtler thinking of network design, and of course many professional transit planners are adept at it.  But you don't have to have those skills, or want them, you can be a more effective advocate if you understand the kind of thinking I've been demonstrating here.  If you want to influence transit in your city, you have to understand the basics of the network design problem, as it arises from facts of geometry, facts of transit, and the unique geography of each city.  That way, even if you're not ready to do network design yourself, you can assess whether the designers of your own network have done a competent job, and make suggestions that they could actually use.

Posted at 14:38 in Basics, Frequent Networks, Halifax, Urban Structure | Permalink

| Digg This | Save to del.icio.us | |

TrackBack

TrackBack URL for this entry:
www.typepad.com/services/trackback/6a00d83454714d69e201538fcd1a8f970b

Listed below are links to weblogs that reference network design for high ridership, a dense city example:

Comments

spacer You can follow this conversation by subscribing to the comment feed for this post.

spacer

One-way loops are a good idea at outer low-density ends of lines,

Why is this true? It is because you can cover more ground?

Great post, btw. Especially the point about the details.

Posted by: Corey Burger | 07/11/2011 at 17:50

spacer

@Corey Yes, because in low-density areas all you can do is cover area to provide basic links to stronger transit services.  One way loops often do that well, though even there you can lose riders if the "long way around" the loop is too long.

Posted by: Jarrett at HumanTransit.org | 07/11/2011 at 17:58

spacer

This pretty much applies, almost verbatim, to Charleston, SC's geography and destination conditions. But if you want to see a system philosophy that appears to be "one-way loop" by default just take a gander at Charleston's bus route map. (www.ridecarta.com/shared/pdf/System_Wide_Map.pdf) Confusing as all get out!

Of course, here, there are special conditions that disadvantage a true high-frequency network. Narrow (slow) streets in a core that is largely touristic (horse buggies are your alternate transport), fewer chokepoints that discourage a dispersed network, and a much longer N-S peninsula market (demanding a more linear service trunk). But Charleston's core could be a good case of comparison with Halifax (I'd be interested to see how they compare at the region level too).

Posted by: Eric O | 07/11/2011 at 19:12

spacer

Looks mostly good. However, I don't like the fact that the dark blue line turns right to go into downtown, while the purple line is the one to go across the bridge. This creates a situation where traveling in a straight line leads to a forced transfer, in favor of a direct connection for an l-shaped trip to a preferred destination. This smells like a radial, rather than a gridded system.

Furthermore, it appears from the map that to get downtown from almost anywhere on the dark blue line, you could do it just as easily via the orange, purple, or light blue. The trip NE from downtown across the bridge, also seems a bit redundant with the ferry. And the walk from downtown to a straight-through blue line still looks to be under a mile, if I read the scale correctly.

So, perhaps this might be better if the dark blue ran straight through across the bridge, while the purple ended downtown, by the ferry dock.

Interestingly enough, as you constructed the network in stages, the purple going over the bridge looked perfectly fine when that was the only line shown. It was when the blue was added that things started to look a little bit strange.

Posted by: Eric | 07/11/2011 at 20:11

spacer

@Eric The question of whether to have a straight east-west line that misses downtown is, I suspect, something that can only be answered with data on ridership patterns. Or else you may end up with a blue bus that completely empties out at the transfer point with passengers who try to cram on to the already-full green buses, only to be filled again with passengers coming from downtown, which seems operationally suboptimal.

Posted by: anonymouse | 07/11/2011 at 20:47

spacer

Drawing transit routes based on data on ridership patterns has two problems:

1) There are lots of things that can cause ridership patterns to naturally change with time. For example, businesses can expand, go bankrupt, or relocate. Changes to zoning laws can increase or decrease the number of people that can live in a neighborhood. Professional sports teams can move into our out of a city. And changes in schools, crime, etc. can make a neighborhood a more or less desirable place to live.

Because of this, any system that has special kinks in the route to handle the demand optimally for the ridership now is likely to be suboptimal for the ridership ten years from now. While this can conceivably be addressed by redrawing the bus routes every few years, change leads to confusion about what routes go where. Plus, route changes can be politically very difficult to pull off, even if most people are better off because there will inevitably be someone who's worse off, who will complain loudly.

2) Using ridership data is inherently an incomplete picture, as it only includes the people who are riding the bus today, not all the trips that people are making. For example, ridership data may say most people riding the bus are headed downtown, but are most people, overall, really going downtown, or does it just appear that way because almost everyone that isn't going downtown has decided that the bus is too slow and is driving instead? If you want your mode share to grow, rather than merely cater to your existing customer base, these are important questions that need answering. Jarett has a good discussion on this.

What's nice about the grid pattern is you don't have to worry about things like "we have a bunch of people going from this point to this other point". You simply focus on connecting areas according to the geometry of the roads and let whatever travel patterns people want to have happen.

Ridership data can be important, for example, in deciding which size vehicles to use on a given trip. For example, if most people really are headed to downtown, you can use smaller buses on a straight-through dark-blue line, with bigger buses on the pink, light blue, and green, to handle the loads. If ridership patterns change in the future, reallocating which sized buses go on what routes, or adding extra buses on the busiest routes during the peak, is much less disruptive than redrawing the routes themselves. By contrast, trying to use ridership data to draw the routes themselves simply leads to a situation where you're enumerating a handful of trips that you're designing the bus for and, for everything else, people should just drive. This narrows the customer based to a few niche markets, rather than serve a broad base of the population.

Posted by: Eric | 07/11/2011 at 23:21

spacer

If ridership patterns change in 10 years, can't you just change the bus routes to more closely match demand? Isn't that one of the big benefits of the much-vaunted "flexibility" of buses?

And as far as grids go, they have their pluses and minuses, and one of the minuses is that cities are rarely isotropic, with demand evenly spread throughout the grid and trips evenly distributed in all directions. Very often, there will be a center, where more people want to go to, or maybe even a few such centers, and it can make sense to divert buses there.

And as far as serving niches, it can be a choice between providing decent service to a few, and winning just that small ridership market from the car, but decisively, or providing mediocre service to everyone, and not winning against the car at all. Which one you really want depends on the transit agency, its goals, its political environment, and what is physically and politically achievable in a given city.

Posted by: anonymouse | 07/12/2011 at 00:02

spacer

This reminds me of Madison, which is an isthmus where they've funneled many routes onto two streets through the isthmus - no need for cross-isthmus service when it is one mile wide: www.cityofmadison.com/metro/schedules/SystemMaps/WeekdayMap.pdf

Posted by: twitter.com/calwatch | 07/12/2011 at 00:27

spacer

As a professional planner and resident of Dartmouth across the harbour from Halifax, I found this really interesting and insightful. That #1 bus is indeed very successful in terms of ridership and convenience! As for "continuing the blue line across the bridge to Dartmouth", a few years ago such a route was in fact added - the #10 bus - and has also been very well received. It also extends in both directions to link our two largest business parks. Last but not least, an underused, grade-separated railway line follows the diagonal southwestern edge of the Halifax Peninsula, links four of the six choke points, and terminates at the southern edge of downtown and the eastern edge of the university corridor, opposite a new farmers' market and arts college campus. In the other direction it extends all the way out to Bedford, a major suburb and shopping destination. Let's "join the dots!"

Posted by: Marcus Garnet | 07/12/2011 at 08:02

spacer

@Marcus.  Thanks for your local perspective! 

As for the rail corridor, by all means preserve it, but meanwhile, build the market with buses.  Once you have the Line 80 bus to Bedford running every 15 minutes with healthy all-day loads, you're ready to think about light rail, but as I understand that needs some expensive duplication of track.

As for commuter rail, again, it needs to be more cost effective than buses (or ferries) in the corridor.  Because you can deploy three modes (rail, bus, ferry) between downtown and Bedford, you risk seeing all three developed separately, as different projects, stopping at different Bedford stations, and thus all competing with each other to achieve a poorer frequency than could be accomplished with a strong investment in one.  Note too the need to be clear about whether you want to serve a commute-only market or an all-day market.  A few commuter trains on your abandoned line might be possible at lowish cost, but of course only all day high frequency would be useful for intra-peninsula travel. 

Posted by: Jarrett at HumanTransit.org |

gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.