Bicycling
Bike Score places DC 6th, shows big gaps in bikeability
Walk Score, which has been on a roll with new scores and rankings lately, created a new Bike Score reflecting a place's bikeability. DC has the 6th highest Bike Score among cities they rated, but the map shows stark differences within the city.
The score combines 4 factors: Bike lanes, hills, the distance to various amenities, and the percentage of people who bike commute. In DC, that concentrates the score heavily in the center. Already there is more in the center, and it's a lot flatter, which is the reason the city centers where it does.
It's important to recognize that this is just descriptive, not proscriptive prescriptive. In other words, places where few people bike get demoted in the rankings, which helps people understand and visualize where people don't bike today. But that doesn't mean that the places shaded closer to red couldn't become great places to bike, though there's nothing to do about the hills.
DC comes in behind Minneapolis, Portland, San Francisco, Boston, and Madison, but ahead of Seattle, Tucson, New York and Chicago. Do you think this is accurate?
Comments
- Latest Metro map drafts add Anacostia parks and other tweaks
- Bikeshare is a gateway to private biking, not competition
- DC Council makes major policy changes overnight
- Short-term Washingtonians deserve a voice, too
- Public land deals have both benefits and pitfalls
- Parklets give every block a little park
- Judge denies injunction against closing schools







by oboe on May 14, 2012 12:54 pm • link • report
by David R. on May 14, 2012 12:57 pm • link • report
It's worth clicking through to the detailed heat maps.
For example, Chicago and Seattle are polar opposites on the hilliness scale, as one would expect. Hills are just there, but bike lanes and bike commuters can change with policy.
Most cities seem to get a lot of their bike commuting from a few key places within the city. E.g. Boston is from the Brookline and Allston area. DC is from Ward 1 and Capitol Hill mostly.
by Ward 1 Guy on May 14, 2012 1:00 pm • link • report
It would be interesting to add in safety data as well (e.g. crashes).
by Gavin on May 14, 2012 1:07 pm • link • report
by MLD on May 14, 2012 1:29 pm • link • report
1) Living next to the Capital Crescent trail or Metropolitan Branch Trail doesn't mean that you can actually access said trails. Ditto for glossing over bridge elevation.
2) There doesn't seem to be much discussion about bicycle-friendly roads without dedicated lanes. Realistically, this describes most of DC. There are only a small number of roads that you really need to avoid.
3) On that note, there is no bicycle-eating vortex in Foggy Bottom. No idea how that got on the map. Is there really such a distinct gap in bicycle infrastructure over there?
4) Bikeshare and bike parking should weigh in. I spent the weekend in Boston, and let me tell you that CaBi is a much more useful system than Hubway thanks to the many locations, and....
5) Layout of the city. Boston's a notoriously difficult city to navigate. Doubly so on a bicycle. DC's bike routes are well-marked, pretty easy to figure out, and have some semblance of fitting together into a coherent network that follows the grid. Yeah, there are still some pretty big gaps, but it's a start.
by andrew on May 14, 2012 1:39 pm • link • report
by charlie on May 14, 2012 1:41 pm • link • report
2. Hills are a factor, but facilities/safety are a much bigger factor. From where I live to Clarendon I can basically go one of two ways. The more level route also has a lot more traffic while the calmer streets involve more up and down but I can handle that relative to the fact that cars aren't tearing through.
3. Bike paths (especially miniature ones used where two streets are close but not connected) always seem way steeper than if the road had been connected for cars. I'm sure cost is the main issue along with environmental impact of changing grades but it still sucks to use those. That is the exception to my first point where I'll deal with the street because at least then I can still pedal somewhere outside of my lowest gears.
by X on May 14, 2012 1:49 pm • link • report
by Tom Coumaris on May 14, 2012 1:53 pm • link • report
That being said, the topography makes biking over here challenging if you are going east to west within east of the river. The bridges are horrible connectors over the Anacostia River.
by Veronica O. Davis (Ms V) on May 14, 2012 1:55 pm • link • report
And this is the data that the House in its infinite wisdom decided was unconstitutional and will be cancelling?
by Michael Perkins on May 14, 2012 2:12 pm • link • report
by Jake S. on May 14, 2012 3:27 pm • link • report
by Ward 1 Guy on May 14, 2012 4:06 pm • link • report
So X, that's a big difference between Arlington and DC. We have parallel roads as alternatives. You don't for the main arterials in Arlington.
Another thing that makes biking easier in DC are the radial avenues, which provide "short cuts" along an otherwise orthogonal grid. E.g., with Kansas Ave., it's easy for me to get to many places, and to continue via Columbia Rd. and Florida Ave. to Georgetown or Arlington County.
WRT Jake S. -- I don't know if biking sucks in those places, but hills are definitely an issue. Going up the escarpment across the fall line, around Florida Avenue in the Adams-Morgan to Columbia Heights area, around Howard University on GA Ave. (but I don't like riding uphill from Upshur St. to Missouri Ave.), from Michigan Ave. to Taylor Street on N. Capitol, etc., does suck. People probably have their preferred hills. I don't mind 14th, Sherman, or Georgia, but 15th, 16th, 13th are terrible, and I hate the long incline up Michigan Ave. or on Ft. Totten Drive.
by Richard Layman on May 14, 2012 9:24 pm • link • report
by Ian Cooper on May 15, 2012 7:36 am • link • report
Also -- "descriptive, not proscriptive" -- I think the word you want is "prescriptive".
by Jack on May 15, 2012 9:50 am • link • report
Add a Comment