Small CaBi Reality Check

Capital Bikeshare has, by most any reasonable measure, been a rousing success. And there’s a ton of great anecdotes out there as to how it is bringing about a sea-change in bicycling (my favorite bike convert story leads this post). But with slightly less than two years in service, there’s not a whole lot of evidence out there on the impact CaBi is having on bicycling in general in the DC area. The most basic question is, “how much has bicycling grown with the introduction of CaBi?”

The real answer to that question will come through household travel survey data releases that incorporate CaBi’s lifespan (in other words, data from calendar year 2011 and onward). But in the meantime, we can easily figure out a benchmark number to frame our expectations.  Back-of-the-envelope time!

It is pretty easy to find out what proportion of trips are by bicycle, via national and regional household travel surveys. What I had a devil of a time finding what was finding out the actual number of trips. Which I never did. So, here’s my imperfect best guess (save your receipts for a full refund):

  • About 215,000 people live in Arlington County, VA.  About 615,000 live in Washington, DC.
  • According to the MWCOG’s ’07-08 household travel survey, Arlingtonians took 0.8% of all their trips by bicycle, and District residents took 1.5% by bike. (Why this survey? It measures all trips, vs. the US Census only measuring commute trips. Thus, apples-to-applesauce with CaBi ridership data)
  • While people in other surrounding counties also ride CaBi, we’re going to assume that it’s in much smaller numbers than the two core jursidictions, and we are going to ignore them, lest it skews this slipshod analysis. Sorry, Marylanders.
  • People in the survey averaged about 4 trips per person per day.
  • Based on that, we can estimate (people x trips x bike rates = total trips) that somewhere around 44,000 combined trips are taken by Arlington and District residents by bike every day.

According to the latest CaBi Dashboard ridership data, CaBi averaged 4,715 rides per day over the past year. That, assuming that 100% CaBi trips are additive, is just under an 11% bump in bicycle ridership directly attributable to CaBi. We do not know bicycle ridership for 2009 or 2010 (the year CaBi rolled out), though we can assume that it followed recent trends in ridership and population growth, and rose further beyond the 44K trip level.

For somebody who is an unabashed lover of bikesharing, an 11% bump does not seem to reflect the dramatic change that CaBi has anecdotally brought to bicycling in the region. To reach the levels of bicycle modeshare in Europe, we need to multiply by whole numbers.

From Pucher & Buehler 2012 (pdf)

Even comparing to other US cities puts an 11%(ish) gain in perspective.

From Buehler and Pucher 2012 (pdf)

So, if we all accept that resting on our CaBi laurels is insufficient, what’s next?  Well, we’ve already taken a look at a couple of ways to squeeze more ridership out of the existing CaBi system.  I’ll throw out some other crackpot ideas in the weeks to come.

This entry was posted in Uncategorized. Bookmark the permalink.

6 Responses to Small CaBi Reality Check

  1. Pingback: Measuring bikeshare performance — defining “success” | bikepedantic

  2. Pingback: Bikeshare is to bike lanes, as Peyton is to the Colts | bikepedantic

  3. Pingback: Improving Bikeshare Operations, Marketing, and Ridership – Heartwarming Graduation Edition | bikepedantic

  4. Pingback: Burke, BHAGs, and Bikeshare | bikepedantic

  5. Pingback: Biking Natitude | bikepedantic

  6. Pingback: Changes in Natitude, Changes in Rackitude | bikepedantic

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s