job: Ridership Data Technician in Baltimore

Here's an opportunity perfect for someone who is interested in transit data and monitoring. 

Via Baltimore MTA, the region's transit agency:

If you or someone you know likes data collection and analysis on a large scale and wants to put those skills to use in public transit, then there’s a new opportunity in the MTA’s Office of Service Development – The Ridership Data Technician (or RDT).

Full details and to apply: http://tinyurl.com/kg7nop3

MTA’s use of Automated Passenger Counters (APCs) continues to grow. We are just really getting started and are looking for an innovative and tech- and data-savvy person to join our team to take our APC program to the next level – allowing better planning, analysis, scheduling, and reporting for stakeholders inside and outside the agency.

If you’re interested, apply using the link above. Or, feel free to forward to someone you know that might be a good fit.

It sounds like a great position for someone who is familiar with APCs and current methods, and who has ideas about exciting new places to take this type of data. If that's you, or someone you know, it could be worth a look!

How do I find a hotel near good transit? Not (yet) via google!

A recent post discussed Jeff Howard's hotels near transit maps suggested looking at Google Hotel Finder, a utility tucked away within Google Maps that purports to help you find a hotel based on travel time from some location. A user plops a pin on the map, and the tool draws isochrones based on drive, transit, and walk times, which supposedly show you the area of the city where hotels are within that travel time of your destination.

Screen Shot 2015-03-02 at 11.35.06 AM

So far, so good – I put a pin in downtown Portland, and Hotel Finder shows me a big blob in the center of the city that I can get to by transit within 15 minutes. It looks like there will be lots of hotels I can choose where I can quickly take transit into downtown. However, when we look a bit more closely, we can see a big problem with Google's approach.

Screen Shot 2015-03-02 at 11.34.53 AM

In this image, I have moved the pin to a corner near Reed College in Southeast Portland. This is a residential area bordering a low-density industrial district and the campus and fields of a small, exclusive liberal arts college. It is served by just one bus route, the 10-Harold, every 30 minutes. Yet according to Google, from this location, I'm just a short 15-minute trip from outer East Portland, or the inner Eastside Industrial District.

The problem here is that Google is providing an isochrone of transit access that does not consider frequency, i.e waiting time.  They assume that the bus shows up right when you need it..  

Once I'm on the Harold bus, it's true that I might be able to take it from 28th far out into the east side in just 15 minutes. But depending upon when I arrived at the stop, I could wind up spending up to 45 minutes making the trip. If we assume an average wait of 15 minutes, or half the headway, the area shown by Google as within 15 minutes of the pin is actually more like 30 minutes!

Imagine you are a person who is coming to a city for business, and you picked a hotel expecting to be able to travel to your meeting by transit in just 15 minutes. Yet when you walk out to the stop, or check a trip planing app, you find that you will wait longer than that just to catch the next bus! You might be late to your meeting, and the tool you used to pick the hotel would have failed to direct you to accommodations that met your desire to be a short transit trip from work.

A more useful version of Hotel Finder would add waiting time. This would alter the isochrone in response to frequency, and more accurately show the area (and hotels) within a short transit trip of the desired location. 

We are surprised to see this kind of misleading info from the crack team at Google Transit.  In presenting transit travel times that don't consider waiting, they are talking about transit as though it worked just like cars, doing a disservice to everyone who wants to consider transit when the choose a location.

London and Dublin: open to ideas

Just as literature graduate students never admit that there are books they haven't read, we urbanist pundits aren't supposed to admit that there are cities we've never been to.  In fact, we're so up to date in our lived experience that there are no great cities we've never been to recently.

Tip: We're all faking it, mostly with Google Earth.

So, to keep up my outsiderish reputation, I'd like to announce that I haven't been to London for 19 years, and I've never been to Dublin at all.  Fortunately, that's changing this month.  I'll be in London March 14-16 and Dublin for a week following that.

What does a transit consultant with North American and Australasian experience do with just a couple of days in London, or with a full week in Dublin?  With whom should he meet?  What experiences must he have?  I have my own ideas, but I love the fact that so many of you know these cities better than I do.  Have at it in the comments!

How do I find a hotel near good transit?

Map_of_hotels_near_washington_dc_metroHere's news you can use, or at least news I can use as an absurdly frequent flyer.  

All of the standard travel shopping sites make it very hard to assess the transit options from a hotel's location.  At most they have distances and sometimes car travel times.  So I often spend too long doing research, and pay too much for a hotel close to my destination when I might easily have stayed further away more cheaply if I knew good transit was there.

This, therefore, is a really good tool.  In the case of Washington DC, it helps you see all the hotels that are close (objectively close, not hotel-marketing-close) to a subway station.  It's the work of Jeff Howard, and he's also done one for Atlanta's MARTA subway.

You can get hints of similar output from Google, very crudely, by pointing Google Maps at a city and then specifying, say, "hotels near a DC Metro station," but Google is easily confused by excessively clear requests, and to Google, "near" means car-near, not transit-near.  Someday, maybe Google will understand "hotel within 400m of a frequent transit stop," or even "hotel within 30 min frequent transit travel time from ___".  But that's clearly a way off, and Google often seems more interested in interpreting vague search requests than replying to clearly stated ones.

In any case, even a competent search engine wouldn't produce Jeff Howard's very useful feedback about hotels.  Click on a station and there's a writeup about each station area, including a map showing the hotel's exact relationship to the station, and links to the hotels themselves, including a reservation widget.  Nice work, Jeff!

 

My interview on National Public Radio

Last week I was a guest on Here & Now, a nationally syndicated radio program produced by WBUR in Boston, talking with the show's Jeremy Hobson about the recently approved Houston METRO Transit System Reimagining, and how its lessons apply to other American cities.  The segment aired today, and is a nice summary of the project, quickly covering much of the material discussed here, here and here. Take a listen via the embed above, or head over to the Here & Now site to check it out.

Houston’s reimagined network: don’t let us make it look easy!

AnimatedFrequentNetwork

It's great to see the national press about the Houston METRO System Reimagining, a transformative bus network redesign that will newly connect a million people to a million jobs with service running every 15 minutes all day, with almost no increase in operating cost.  Last week, when the Houston METRO Board finally adopted the plan for implementation this August, I was in New Zealand advising Auckland Transport executives on how to roll out a similar plan there, one that MRCagney and I sketched for them back in 2012.  Advising on these kinds of transformations, and often facilitating the design process, is now one of the core parts of my practice.

And here is my most important piece of advice:  Don't let anyone tell you this is easy.

Much of the press about the project is picking up the idea, from my previous post on the subject, that we redesigned Houston's network to create vastly more mobility without increasing operating cost — "without spending a dime," as Matt Yglesias's Vox piece today says.   An unfortunate subtext of this headline could be:  "Sheesh, if it's that easy, why didn't they do it years ago, and why isn't everyone doing it?"

Some cities, like Portland and Vancouver, "did it" long ago.  But for those cities that haven't, the other answer is this:  

Money isn't the only currency.   Pain is another.  These no-new-resources restructurings always involve cutting some low-ridership services to add higher-ridership ones, and these can be incredibly painful decisions for boards, civic leaders, and transit managements.  Civic officials can come out looking better at the ends of these processes, because the result is a transit system that spends resources efficiently in a way that reflects the community's values.   But during the process they have every reason to be horrified at the hostility and negative media they face.

If you're on a transit board, here's what these transformations mean:  Beautiful, sympathetic, earnest people — and large crowds of their friends and associates — are going to stand before you in public meetings and tell you that you are destroying their lives.  Some of them will be exaggerating, but some of them will be right.  So do you retain low-ridership services in response to their stories, and if so, where does that stop?  I'm glad I only have to ask these questions in my work, not answer them.

For a decade now I've been helping transit agencies think through how much of their service they want to devote to the goal of ridership and how much they want to devote to a competing goal that I call coverage.  Ridership service should be judged on its ridership, but coverage service exists to be available.  Coverage service is justified partly by the political need for everyone (every council district, member city or whatever) to have a little service, because "they pay taxes too," even if their ridership is poor.  But it's also justified as a lifeline, by the severity with which small numbers of people need it.  

In the early stages of the Reimagining project, I facilitated a series of METRO Board and stakeholder conversations about the question:  How much of your operating budget do you want to spend pursuing ridership?  I estimated that only about 55-60% of existing service was where it would be if ridership were the only goal, so it wasn't surprising that the agency's ridership was stagnant.  I explained that the way you increase ridership is to increase the percentage of your budget that's aimed at that goal.  And if you're not expanding the total budget, that means cutting coverage service — low ridership service, but service that's absolutely essential to some people's lives.  

In response to a series of scenarios, the Board told us to design a scenario where 80% of the budget would be devoted to ridership.  That meant, of course, that in a plan with no new resources, we'd have to cut low-ridership coverage service by around 50%.  Mostly we did that not by abandoning people but certainly by inconveniencing some of them.  But there was no getting around the fact that some areas — areas that are just geometrically unsuited to high-ridership transit — were going to be losers.

We didn't sugarcoat that.  I always emphasize, from the start of each project, how politically painful coverage cuts will be.  The stakeholder committee for the project actually had to do an exercise that quantified the shift of resources from low-ridership areas to high-ridership ones — which was also a matter of shifting from depopulating neighborhoods to growing ones.  They and the Board could see on the map exactly where the impacted people were.

And exactly as everyone predicted, when the plan went public, those people were furious.  Beyond furious.  There really isn't a word for some of the feelings that came out.

Houston had it much worse than most cities, for some local reasons.  Along the northeast edge of inner Houston, for example, are some neighborhoods where the population has been shrinking for years.   They aren't like the typical abandoned American inner cities of the late 20th century, where at least there is still a good street grid that can be rebuilt upon.  In the northeast we were looking at essentially rural infrastructure, with no sidewalks and often not even a safe place to walk or stand by the road.  Many homes are isolated in maze-like subdivisions that take a long time for a bus, or pedestrian, to get into and out of.  And as the population is falling, the area is becoming more rural every year.

I feel the rage of anyone who is trapped in these inaccessible places without a car.   I also share their desire to love where they live, and hope my description hasn't offended them.  But I can't change the geometric facts that make high-ridership transit impossible there, nor can I change the reality of their declining population.  And that means I can't protect civic leaders, elected officials, and transit managements from the consequences of any decision to increase the focus on ridership.  Increasing your transit agency's focus on ridership, without growing your budget, means facing rage from people in low-ridership areas, who will continue to be part of your community.

Houston's situation is worse than most; less sprawling cities can generally prevent any part of the city from depopulating in the context of overall growth.  But in any city there are going to be less fortunate areas, and the disastrous trend called the "suburbanization of poverty" means that increasing numbers of vulnerable people are forced to live in places that are geometrically hostile to high-ridership transit, and thus demand low-ridership coverage service.

So don't let anyone say this was easy.  What's more, in Houston it was easier for me than for anyone else involved, which is why I'm uncomfortable when Twitterers give me too much credit.  I flew in from afar, facilitated key workshops for the Board and stakeholders, led the core network design process, and got to go home.   It was the the Board, the management, the key stakeholders and the local consultants led by TEI who had to face the anger and try to find ways to ease the hurting.  

Was it worthwhile?  I was very touched by what METRO's head of planning, Kurt Luhrsen, wrote after the Board's decision.

I am overjoyed for the citizens of Houston.  Particularly those who are dependent upon the bus and have been riding METRO for years.  Their trips to the grocery store, the doctor’s offices, work, school, church, etc. take way too long and are usually way more complicated than they need to be.  

Today, with this Board vote, Houston took a giant step toward making these citizens’ lives better.  That simple fact, making people’s lives better, is why I love my job in transit.  It is where I draw my inspiration and today definitely recharged my batteries a bit.  I am also very proud of our Board, METRO employees, our consultants, our regional stakeholders and many others who worked tirelessly to make this action today possible.  These types of projects are difficult, that’s why so few transit agencies really want to do them.  But today we did it.  This plan will improve people’s lives, and I am so thankful that I got to play even a small role in it.     

I, too, am thankful for my small role in guiding the policy and design phases of the process.  I listed, here, some of the key people who really drove the process, all of whom worked much harder than I, and who faced much more ferocious public feedback than I did, to bring the plan to success. 

Transit in Houston is about to become a completely different thing, vastly more useful to vastly more people's lives.  But don't let anyone imply this was easy.  It was brutally hard, especially for the Board and staff.  Nobody would have done it if it didn't have to be done.

Houston METRO’s Transit System Reimagining Plan approved

Over the past two years, our firm has worked as a member of a diversely skilled team to help Houston METRO comprehensively redesign the city's transit system (look back to this post for the backstory). Houston is a dynamic, fast-growing city, where despite a reputation as a place where one must own a car to live, many areas have developed land-use characteristics indicating a large, untapped market for quality transit. This project has sought to design a transit network which can deliver the type of mobility outcomes current growth patterns demand, through a extensive Frequent Network grid. 

Today, we are proud to share the news of the unanimous passage of the final plan by METRO's Board of Directors, with implementation on track for August 2015. In the history of transit in North America, top-to-bottom transit network redesigns are very rare, particularly for a city of the Houston's size and national importance. This is a great day for Houston, and will be a fascinating case study for transit in North America.

The final approved map (click here for the detailed pdf):

Reimagined Network Plan Feb Revision

basics: should I vote for a transit tax?

Note:  This popular post is being continuously updated with useful links and comments.  Come back and it may be improved!

In the United States, but occasionally in Canada too, voters are sometimes asked to decide whether to raise taxes to fund transit improvements.  I’m often asked whether I support these things.  I don’t like telling people how to vote, but I can point out some predictable patterns in the arguments, and some universal facts about transit that you need to keep in mind.   Continue Reading →

can we get the slides from your presentation?

[Updated August 1, 2019]

This is the second most common question I receive, second only to “What do you think of ___ transit technology?” but a little ahead of “How do I become a transit planner?

While it’s usually the client’s decision, my preferred answer is a compassionate no.

In my presentations, most of the content and tone arises from what I say, not what’s on the slides, so releasing the slide deck without my voice attached carries a high risk of misunderstanding.   Slides by their nature do not convey nuance, tone, or feel.  If I prepared slides that were easy to understand without the benefit of what I’m saying, they might be fine for professional contexts but they’d be way too boring to use in a public event.
For example, I will sometimes just put up a picture and a few words that prompt me to tell a story, but I’m not going to put the three-paragraph story on a slide, and even if I wrote out the story in the notes (and even if, more implausibly, the people reviewing the slide read the notes) it wouldn’t convey the effect of me telling the story.
This may be one of those few moments when my past life as a theater director affects me.  I’m very attuned to the difference between a performance and a script or score.  If scripts accurately reflected what happens in a live performance, we wouldn’t need live theatre or live music.  PowerPoint slides are part of the script; they are not the show.
In resisting releasing my slides, I am also cognizant of Edward Tufte’s groundbreaking work on visual presentation, notably The Cognitive Style of PowerPoint, in which, among other things, he blames the lazy thinking encouraged by PowerPoint for the Columbia space shuttle disaster.
The other obvious reason, which is that my slides are our intellectual property, is the least important to me, though I obviously dislike seeing my work show up without acknowledgment in things that other people produce.
So when I get this request, my response is:
  • If you are interested in a particular thing I said, there’s probably a quotable article here about that.
  • There may also be a video of my presentation.  You may be able to find it on the event sponsor’s website, and the best of my presentations are also collected here. While it has its own limitations, a good video can capture most of what actually happens in an event.
I hope that helps.