I sold my car

Today we sold our family’s second car. Since taking a new job last year, my car mostly sat in the driveway. I can get to work really easy on the bus or on a bike (and the same for my wife, to a slightly lesser degree) and parking costs made me think twice when I considered driving to work.

The sale was an emotional experience. I loved driving the car, and I’ve always liked driving. I got my learners permit when I was fourteen (Iowa let ‘em drive early) and as with most teenagers (at least back then) , the car signaled freedom to me. My feelings about driving have moderated some since, but I’ve retained much of the original nostalgia and excitement, especially when starting a road trip. I’ve learned a lot about the impacts on our cities and climate reliance on the car creates since that initial love affair, but in the end, the strongest reason we had to ditch the second car was cost.  Hundreds of dollars a week is a strong motivator.

But this wasn’t a simple matter of deciding to ride the bus more. A large number of factors has to converge to make it possible for a family of three with two jobs outside the home to make do with one (private) vehicle.

  • Working in the hub of a hub-and-spoke transit network. We have lots of bus routes that are fairly competitive with a car because my wife and I both work in or near downtown. This wouldn’t be the case if we worked in the suburbs, inner ring or outer.
  • We found a great daycare nine blocks from our house.  You can walk there easily in most weather from our house or take the bus/bike.  The location and density of daycare centers should not be overlooked if your goal is to encourage alternative modes.
  • Minneapolis is walkable and fairly bikeable.  The city does a pretty good job making it feel safe and easy to walk and bike places.  Destination density (stores, food, etc) is tolerably high in some neighborhoods, although it could definitely be better.
  • New technologies.  We feel better with one car knowing their is a car-sharing service that parks a car a few blocks from our house.
  • We have the resources to rent a car when we need it.  Even if we do this once a month for a week, we still save a lot versus owning.

We really depend on automobiles a lot.  If we want to change that for whatever reason, or if we want to be sensitive to the needs of those who can’t afford a car, then it’s about way more than providing transit.

David Alpert on driverless cars

I’ve been meaning to write a “how this urbanist stopped worrying and learned to love the driverless car” post for a while, but I’ve finally been spurred into action by this piece in the Atlantic Cities by Greater Greater Washington founder David Alpert.  Right up front I want to say I still have a lot of concerns about how we plan and incorporate robot cars, but on this issue of competing road users, I take a different view.

Alpert’s contention is that in our society’s haste to adopt driverless cars, we will “intensify current tensions” between drivers (more accurately called passengers in a robot car-filled world of the future) and non-auto users, such as pedestrians and cyclists, who are trying to use the same right of way.  I think this case is overstated for a number of reasons.

The author’s main evidence for the idea that tensions will be increased is reference to an animation done by some computer scientists that showed how to optimize an intersection when most of the cars are driverless, thus increasing flow.  According to the article,

[H]uman-driven cars would have to wait for a signal that would be optimized based on what everyone else is doing. And the same would be true of pedestrians and bike riders.

And to that Alpert reacts:

That certainly sounds like all other users of the road will have to act at the convenience of the driverless cars, under constraints designed to maximize vehicle movement instead of balancing the needs of various users…

The video even depicts an intersection with a whopping 12 lanes for each roadway, at a time when most transportation professionals have come to believe that grids of smaller roads, not mega-arterials, are the best approach to mobility in metropolitan areas.

Driverless cars, therefore, are poised to trigger a whole new round of pressure to further redesign intersections for the throughput of vehicles above all else.

I’m not sure how this one animation demonstrates why driverless cars would trigger a gush of road-building or elimination of non-auto facilities.  Setting aside the fact that I’m sure this animation was developed as a proof-of-concept (I can hear the research team now: “If we use 12 lanes in each direction, it will look even more impressive!”), this leads me to my first objection to the premise that driverless cars will increase tensions.

Driverless cars don’t make bad roads, people make bad roads

As Alpert himself states, “Already, cities host ongoing and raucous debates over the role of cars versus people on their streets. For over 50 years, traffic engineers with the same dreams about optimizing whizzing cars have designed and redesigned intersections to move more and more vehicles.”  Yes, and we’ll continue to have this debate into the future whether robot cars are adopted or not.  Given that gradual adoption of this technology is the most likely scenario (more on that later), I don’t see auto users getting more vocal (than they already are) about road capacity because there car has a few more widgets.

Building a balanced transportation system that looks at the full picture of quality of life rather than just mobility and speed will continue to be a challenge, although we seem to be making some progress in that direction.  Issues of public health, environmental impact and land use impacts will probably always take some extra effort to incorporate into transportation decision-making, an effort organizations like Greater Greater Washington should continue to make.  I view this as an institutional problem, failing to bring full information about transportation systems impacts to the design table, and it should be addressed in our decision-making processes.

12-lane at-grade intersections would make any cityscape pretty awful, but that leads me to my second objection:

Driverless cars can do more with less

Maybe the computer scientists at UT Austin should have showed a 2-lane 4-way intersection with driverless cars instead of a 12-lane intersection.  They also should have showed a comparison with a present day intersection.  One of the potential benefits of driverless cars is squeezing more flow or capacity out of the road systems we already have.  Cars can drive closer together, and yes, maybe intersections can look more India-like.  Potentially, we’ll get more from our existing concrete without having to widen or reduce non-auto infrastructure.

There is also this nagging funding issue.  In Minnesota for example, we already can’t pay for all the roads we want.  So 1) a huge explosion of more road-building probably isn’t likely and 2) driverless cars give us kind of another way out: if we’re intent on adding more capacity, maybe we can make our vehicles smarter rather than our roads wider.

And finally:

Driverless cars are safer

The first forays into “driverless cars” are about collision detection and avoidance (see a long list of existing implementation here).  Google’s driverless car has driven 200,000 miles and been involved in two accidents (both while being driven by a human).  Before any cars are driving themselves around, their computer brains will just be allowed to stop us from having accidents.  This is good for auto users and others alike.   And their adoption will happen gradually (they’ll be pretty expensive at first).

It seems obvious that driverless cars will be programmed to not hit pedestrians and cyclists.  Driverless cars will never (or very rarely) drive in a bike lane or right-hook a cyclist.  And for the next fifty years, they’ll probably be operating on roadways that look very similar to what we have today, pedestrian cross-walks and all.  The dys/utopian future where we have streets with tightly-spaced driverless cars traveling 200 mph is quite a ways off, and when that happens, why shouldn’t they be limited access and/or grade separated?  Wouldn’t we require the same of high-speed rail?

Again, there are lots of other potential negative impacts we need to be aware of as driverless cars become common (see my summary here), but I think these can be addressed by human policy decisions.  We also need to take some drastic action on emissions from transportation that contribute to climate change, and robot cars will likely not have a measurable impact there for some time (it’s also possible our action, if we take any, may actually delay their deployment).

Robot cars could offer urbanists a myriad of benefits that Alpert doesn’t address (but which others have covered in detail, but that should probably wait for another post.

Using bikes for serious emissions reduction

Bicycles in a square

According to the European Cycling Federation, if the whole of the EU cycled like the Danes, they could achieve significant emissions cuts.

If the EU cycling rate was the same as it is in Denmark, where the average person cycles almost 600 miles (965km) each year, then the bloc would attain anything from 12% to 26% of its targeted transport emissions reduction, depending on what forms of transport the cycling replaced, according to the report by the Brussels-based European Cycling Federation (ECF).

This figure is likely to be a significant underestimate as it deliberately excludes the environmental impact of building road infrastructure and parking, or maintaining and disposing of cars.

These figures are for the EU’s 2050 emissions reduction target.  The figures are even greater for 2020 targets.

Bikes are not a new technology that would require long adoption periods and high initial capital costs.  Almost everyone knows how to use them, and they are cheap.  They also have myriad co-benefits, not least of which is increased physical activity.  To get serious about reducing greenhouse gas emissions, we should take a close look at the bike as a potential solution.

Using ECF’s study as a model and making some estimates, the Twin Cities metro could see some significant emissions reductions if we biked like the Danes, but getting there would be tough.  I’ll get to that, but first some initial thoughts on the Europeans. Continue reading

Not really Streetless in Seattle

A better movie

City Journal, a creation of the Manhattan Institute, has a profile of Mike McGinn, Seattle’s newest Mayor.  What really grabbed my attention was the reference to Seattle’s Bike Master Plan and what City Journal claims is it’s call for converting 3 percent of Seattle’s car lanes into bike lanes.  This little tidbit is getting this article a lot of play, at least in my planner-nerd circles.  However, I can’t find any evidence to back up this 3 percent figure.

City Journal is anti-McGinn, calling him “anti-car” and painting his transportation initiatives as misguided.

Sure enough, when McGinn became mayor, he began pursuing anti-car policies. He’d like to levy an $80 fee for registering a car in Seattle, and he has raised taxes on parking in privately owned garages. He now plans to raise parking-meter rates downtown to $4 an hour from $2.50, which would make it costlier to park in Seattle than in any other American city except Chicago. He also supports maintaining the so-called head tax, which docks businesses $25 annually for every employee who drives alone to work.

But McGinn’s road diet, which went into effect in July, is probably his most audacious idea. As the centerpiece of the city’s $240 million “Bicycle Master Plan,” which mandates the construction of 118 miles of bike lanes and 19 miles of trails by 2017, the diet will convert 3 percent of Seattle’s car lanes into bike lanes. Even major freight routes, including one that leads to Boeing Field, will see car and truck lanes converted to bike-only use.

Then there is this:

Factors both meteorological and topographical make Seattleites unlikely to forgo cars as their primary means of transportation. Rain falls more than 150 days a year in this famously gloomy city, rendering cycling both unpleasant and unsafe. And Seattle’s ubiquitous steep hills make San Francisco look like Des Moines. It’s hardly surprising that, according to the Seattle Department of Transportation, a mere 2,600 people—out of a total downtown workforce of 230,000—commuted downtown by bicycle in 2009.

They forget to mention that citywide, Seattle is now tied for second among the 70 largest cities in the US in terms of bicycle commuter mode share and that cycling to work has grown 93% since 2000 and 22% since 2009.  They also forget to mention that (auto) vehicle miles traveled has been basically flat in King County since 2005, and VMT per capita has been on the decline in the region since 1999.

What about that 3 percent figure?  That seems substantial if true.  It wouldn’t totally surprise me given the other press I’ve seen about McGinn and his opposition to new auto lanes or facilities (see Deep Bore Tunnel and 520 Bridge), but this is taking away lanes, not just not creating new ones.  However, on my  brief scan of the bike plan, I can’t find any explicit reference to converting car lanes.  Is City Journal taking liberties, or did I miss something?

Appendix F, “Guidance for Retrofitting Seattle Streets to Create Dedicated Bicycle Facilities“, which includes guidance for arterial (high-volume) roads, does say “Implementing some of these facilities will require a change to the existing roadway configuration.”  However, it goes on to lay out a process for analyzing existing roads to see how a bicycle facility could be accommodated.  The process includes considering how the changes in the street cross section will effect traffic volume, speed, heavy vehicle traffic and on-street parking demand, among other things.  This seems like pretty typical engineering stuff.  The plan says where generally the city would like a bike lane, and then the engineers look at the details to see what might be possible.  Sometimes, it might not be possible at all, and the plan admits this.

If analysis finds that the target bicycle facility type is feasible, the project can move forward to implementation. If there are constraints that would prevent the target facility from being achieved, alternatives should be developed with the goal of improving bicycle safety and access to the highest degree possible, given the constraints of the particular corridor.

The process of developing alternative designs should always be informed by the recommendations of the Bicycle Master Plan, which identifies a facility type for all segments of the proposed bicycle network. Other alternatives should be explored as well, again with the goal of improving bicycle safety and access, and providing the most suitable bicycle facility given operational and environmental constraints within the corridor. If the city decides not to proceed with implementing the Bicycle Master Plan recommendation on a particular roadway, it will document the reason for its decision to choose a different alternative. The burden is on the city to explain why it is not implementing a recommendation in the plan.

Later, the appendix actually says if the desired cross section can’t fit because of “operational or environmental” factors, roadway widening should be considered.  That part didn’t make it into the City Journal article.

Here’s my guess about the 3 percent figure.  City Journal writer Epstein looked at the total miles of planned on-street bike lanes yet to be built (118).  Then he found the total number of lane miles of Seattle surface streets (3,745).  Then he assumed that each mile of new bike lane equals one less lane mile for cars (there are a lot of things wrong here, the biggest being that the plan prefers reducing lane widths in order to add facilities, which wouldn’t reduce car lane miles at all).  Then he did some long division, and presto: 3.15%!  Remember, City Journal is “the nation’s premier urban-policy magazine“.  If anyone, including the editors of City Journal or writer Ethan Epstein would like to explain an alternative calculation, let me know and I’d be happy to post it.

St. Paul’s electric vehicle charging stations

St. Paul has a nice video introducing their electric vehicle charging infrastructure.  According to a presentation I saw at MNAPA, the City hopes to have 150 public stations available by 2015.  They also estimated that the cost for installation was anywhere between $850 in parking ramps to $6,000 in on-street spaces.

A generational shift in driving?

Sightline Daily looks at two data points from the National Household Transportation Survey:

Among older folks, driving didn’t change that much between the two studies. But among younger Americans, driving habits changed radically: folks between the ages of 20 and 40 drove far less in 2008 than their counterparts did in 2001.

This is perhaps the most compelling piece of evidence I’ve seen suggesting that there’s been a profound generational shift in America’s driving habits.

That doesn’t exhaust the analysis, of course. Some portion of this trend may be simple economics: the recession of 2008 may have hit younger folks a bit harder than the recession of 2001. (The fact that both surveys were taken in the midst of a recession was just pure dumb luck.) And there are still all sorts of questions about what’s at the root of this trend: is it young folks substituting life online for life behind the wheel?  Environmental concerns dampening their enthusiasm for cars? More young people choosing to live car-lite city lifestyles? I’m sure there are dozens of theories out there, and probably many that have a grain of truth.

And then there’s the anomaly of 50-54 year olds, who looked more like 30-somethings than 50 or 60 year olds. Is that just a data glitch, or a real trend?

Regardless, the evidence is pretty compelling for a broad generational shift:  on average, folks under 40 are driving less than their counterparts from previous years. And if that trend keeps up, it will mean less and less driving per capita, as today’s low-mileage 20- and 30-somethings hit their peak driving years.

I’d say the 2008 recession did hit young people harder, as youth employment is at an all-time low.  Minnesota may have hit “peak travel” in 2004.

TTI’s Urban Mobility Report Is Still Only About Mobility

Traffic

Evaluating land use and transportation policies in terms of accessibility rather than mobility is the goal of many planners and advocates, whether they know the terminology or not.  This new focus requires recognizing the interconnectedness of land use and transportation decisions.

Unfortunately, one of the most influential voices in transportation research and policy has not yet made these changes.  From Greater Greater Washington (via Market Urbanism):

The Texas Transportation Institute today released the final version of their report on congestion, which ranks the DC area tied for first with Chicago in hours wasted in traffic. Unfortunately, the report’s methodology completely misleads as to the seriousness of traffic, and TTI is pushing the wrong policy solutions.

The TTI report narrowly looks at only one factor: how fast traffic moves. Consider two hypothetical cities. In Denseopolis, people live within 2 miles of work on average, but the roads are fairly clogged and drivers can only go about 20 miles per hour. However, it only takes an average of 6 minutes to get to work, which isn’t bad.

On the other hand, in Sprawlville, people live about 30 miles from work on average, but there are lots and lots of fast-moving freeways, so people can drive 60 mph. That means it takes 30 minutes to get to work.

Which city is more congested? By TTI’s methods, it’s Denseopolis. But it’s the people of Sprawlville who spend more time commuting, and thus have less time to be with their families and for recreation.

Sadly, despite CEOs for Cities pointing out these methodological problems last year, TTI went ahead and finalized its report without fixing them (PDFs). TTI ranks Portland as worse than Nashville, with a Travel Time Index (TTI) of 1.23 1.15 for Nashville and 1.151.23 for Portland. However, because of greater sprawl, Nashville commuters spend an average of 268 hours per year commuting, while the average Portland commuter spends 193 hours per year.

What does this mean for public policy and the Washington region? TTI’s data is often used to justify spending money on new freeway capacity, since congestion sounds bad. TTI even promotes this approach. Tim Lomax, a co-author of the report, told the Post’s Ashley Halsey III, “You can do little things like stagger work hours, fix traffic-light timing and clear wrecks faster, but in the end, there’s a need for more capacity.”

In some sense, we shouldn’t be surprised, since the report is titled the Urban Mobility Report.  However, the goal of commentators and the CEOs For Cities report is to call attention to the fact that mobility (or level of congestion) alone is not an adequate means of measuring the performance of our land use and transportation systems.

Road Trains Tested In The Real World

Road Train Test

Road trains (also called vehicle platooning) are convoys of semi-autonomous vehicles with a professional driver in the lead vehicle.  The Safe Roads and Trains for the Environment initiative (SARTRE) describes road trains as:

…a convoy of vehicles where a professional driver in a lead vehicle drives a line of other vehicles. Each car measures the distance, speed and direction and adjusts to the car in front. All vehicles are totally detached and can leave the procession at any time. But once in the platoon, drivers can relax and do other things while the platoon proceeds towards its long haul destination.

Road trains were actually tested in the real world by Volvo, who is part of the SARTRE team, in December.  They cite the benefits of road trains as numerous:

Platooning is designed to improve a number of things: Firstly road safety, since it minimises the human factor that is the cause of at least 80 percent of the road accidents. Secondly, it saves fuel consumption and thus CO2 emissions by up to 20 percent. It is also convenient for the driver because it frees up time for other matters than driving. And since the vehicles will travel at highway speed with only a few meters gap, platooning may also relieve traffic congestion.

There are some potential downsides to road trains as well, but ideally they can deliver many of the benefits of intra-city transit without some of the drawbacks.  Really road trains are just a stepping stone to fully autonomous cars, and caveats of same apply here as well.

MN DOT Discusses Tolls To Pay For New St. Croix River Bridge

From MPR News:

Minnesota Department of Transportation spokesman Brad Larsen says a MnDOT study shows a $1.50 toll each way would, over time, raise nearly half the cost of a new $642 million St. Croix River bridge.

Larsen says a tolling plan would need clearance at both the federal and state level.

I think it is encouraging that MN DOT is considering (or at least exploring) tolls to pay for this bridge.  I don’t think the bridge is necessary, but if it is built, tolls should pay for it.  A more glaring example of how the system subsidizes greenfield, exurban development is hard to find.

Note that as it stands, the bridge cannot be built because the National Park Service has determined the bridge would “fundamentally change the scenic qualities that existed when the St. Croix was designated a national wild and scenic river in 1972″ and would have “direct and adverse effects that cannot be avoided or eliminated.”

Peak Travel – Minnesota Edition

The industrialized world may have reached peak (auto) travel in the early 2000′s:

A study of eight industrialized countries, including the United States, shows that seemingly inexorable trends — ever more people, more cars and more driving — came to a halt in the early years of the 21st century, well before the recent escalation in fuel prices. It could be a sign, researchers said, that the demand for travel and the demand for car ownership in those countries has reached a saturation point.

According to the study, the US peak was about 8,100 miles per car per capita. How does Minnesota compare?  According to MNDOT statistics, VMT per capita in Minnesota stopped growing in 2004, just one year after what the study defines as the national peak.  Not only has VMT per capita stopped growing, but total VMT in Minnesota has been on the decline since 2007.

Although other countries have hit “peak travel” as well, the peak is not the same.  The peak for Japan, for instance, was 2,500 miles per car per capita.  So as the authors suggest, there must be other factors (gridlock, parking, gas prices) affecting demand.  Or perhaps, as one commenter noted, there is nowhere new to go:

What’s the use of travelling anywhere when everywhere is the same? Same strip malls, big box stores, culture, etc. You get in a car, endure onerous expense, congestion, parking problems to arrive at — surprise! — the place that you left.