Calculating the experience of riding a bike
Don’t tell anyone, but I’m a bit of a math geek. The math I use day to day is pretty simple, rarely more interesting than divvying the bill and adding tips at restaurants, but it’s more complex math that makes me swoon.
I’m smitten with mathematical equations that eloquently express universal truths about the natural world. About man-made designs. And most of all, about human nature. They’re kind of magical.
Knowing this, imagine the quickening of my pulse and the slight dilation of my pupils last Monday when I cracked opened my 205 page “Bicycle Facility Design” workbook and spotted:
My friends, THIS translates the human experience of riding a bike on a street into engineerese. It’s a formula that asks the same questions you do when thinking about which street to ride on.
- What’s the condition of the pavement? PC5
- How many vehicles are there? Vol15
- How many of those are really big? HV
- How fast are they traveling? SPt
- How much road space do cars and bikes have to share? We
Finally, like most great math formulas, there’s a natural logarithm and a constant thrown in and (voilà!) you have a numerical expression for riding a bike.
What does it mean?
An answer close to 1.5 indicates most people feel pretty safe riding a bike along that stretch of road. If the answer tips 4.5, it’s probably not where you would ride unless you absolutely had to. And 5.5? Don’t go there.
This was one of many formulas introduced at the Bicycle Facility Design Workshop in Carbondale, hosted by the Colorado Department of Transportation. With 23 transportation planners and engineers from across Colorado, I spent nine hours delving into the technicalities of how to design roads safely.
As someone with no previous transportation engineering experience, I was amazed—if not surprised—by the complexity of designing bike facilities.
What problem are we solving?
Shortly after lunch, while calculating stopping sight distance [fusion_builder_container hundred_percent=”yes” overflow=”visible”][fusion_builder_row][fusion_builder_column type=”1_1″ background_position=”left top” background_color=”” border_size=”” border_color=”” border_style=”solid” spacing=”yes” background_image=”” background_repeat=”no-repeat” padding=”” margin_top=”0px” margin_bottom=”0px” class=”” id=”” animation_type=”” animation_speed=”0.3″ animation_direction=”left” hide_on_mobile=”no” center_content=”no” min_height=”none”][S=(V2/(30(f+G)))+3.67V], I realized the equations, engineering standards and detailed schematics in our book all answer the question: “How?”
There are no proven formulas for “why,” “when,” “where” or “who.” Yet, these are the questions that we need to answer to get to the “how.”
Questions like: Why do we need safe spaces for people to ride bikes? When must a city, county or state build roads safe for folks who ride for transportation or recreation? Where aren’t people riding because they feel unsafe? Who will benefit from more opportunities to ride a bike?
This is where math fails us, but we don’t need a formula to know that our streets must be improved to be safer for all. If we don’t set the expectation that streets should be safe for everyone, all we get are well-designed bike facilities in places people already ride.
Across the country, we are in a process of changing the problem we’re solving from: “How do we move more cars quickly?” to “How do we move more people safely?”
Bicycle Colorado and the Colorado Pedals Project are partnering with organizations such as CDOT to make Colorado the most bicycle-friendly state in the nation. We’re grateful the math is in place to support good design, but we also need communities to elevate the value of cycling by asking the right questions (why, when, where and who) and saying “yes!” to cycling infrastructure.