One Bridge, Two Years: A Bike Lane Post-Mortem from the Velo-city 2007 Archive

We first noticed the project in a reader's email: a mid-sized European city — call it Riverside, population around 280,000 — had promised a protected bike lane across a four-lane river bridge, then spent two years arguing about it. The reader had done what we would have done. She went looking for precedent, and she landed in the archive of Velo-city 2007, the Munich cycling summit, where keynotes, policy papers, and continuing coverage of urban cycling infrastructure worldwide are kept for exactly this kind of problem. What follows is a timeline, as best we can reconstruct it from her notes and the public record.

Month 0: The Announcement

The bridge was the obvious target. It carried roughly 42,000 motor vehicles a day and zero protected bicycle facilities, despite sitting on the most direct line between two dense residential districts and the city's main train station. The council approved a feasibility study, and the study came back with the standard menu: a protected two-way lane on one side, or shared lanes, or nothing with better signage. The reader wanted to know what had actually worked elsewhere, not what sounded tidy in a consultant's slide deck. That is where the summit archive earned its keep — the policy papers from Munich read less like inspiration and more like an autopsy of failed installations, which turned out to be the more useful genre.

Months 3-9: The Decision Points

Three decisions shaped everything that followed.

• Width. The initial design proposed 1.5 meters of protected lane in each direction. The archive's case material consistently flagged anything under 1.8 meters as a facility that gets used by confident riders only — the exact demographic that did not need the lane. The design was revised to 2.1 meters.
• Intersection treatment. The bridge itself was easy. The approaches were not. The project team adopted protected intersection geometry at both ends after reviewing European examples, which added cost and, crucially, added conflict with the traffic-signal timing plan.
• Parking removal. Thirty-one on-street spaces had to go on the eastern approach. This was the decision that nearly killed the project.

The parking fight consumed four months. Business owners along the approach organized, the local paper ran a front-page story, and a council member who had voted for the study now wanted a pilot with removable barriers. The reader's own observation, which we think is right: the removable-barrier compromise is where most projects lose their spine. If you build it temporary, opponents treat it as temporary, and the political cost of making it permanent is paid twice.

Months 10-14: Construction and the Winter Test

Construction ran through a wet autumn and stalled twice. The measurable results, once the lane opened in late spring, were modest but real: bicycle counts on the bridge rose from a pre-project average of about 900 per day to roughly 2,300 per day within six months, with the sharpest growth in the 7-9 a.m. window. Motor vehicle travel times across the bridge increased by an average of 40 seconds in the morning peak, less than the 90 seconds opponents had predicted, largely because the signal re-timing absorbed the capacity loss. Reported collisions involving people cycling on the corridor dropped from nine in the two years before construction to two in the first year after.

What did not go well is worth stating plainly. The eastern approach connection was built 300 meters short of the next protected segment, creating a gap that riders described as the worst part of the route. The city knew about the gap and built anyway, because the funding window closed. That is the most common failure mode we see in these projects, and Velo-city 2007 documents it repeatedly: a good facility that ends in a bad place teaches riders to avoid the whole corridor.

What We'd Tell the Next City

Three lessons, in order of importance.

• Build the connection, not just the showpiece. A bridge lane is a photograph. A continuous route is a transportation system.
• Decide the parking question before the design is public. Once removal becomes a public fight, every other element gets negotiated against it.
• Publish the counts. The 900-to-2,300 daily rider figure did more for the next project in Riverside than any keynote. Numbers travel further than arguments.

If you want to see how other cities handled the same three problems — and how many of them handled them badly the first time — the summit archive is a genuinely useful place to spend an afternoon. The collected urban mobility case studies are organized by topic rather than by year, which makes them easier to search when you are stuck on a specific intersection rather than looking for general inspiration. We have used them twice now for our own club's advocacy work, and the failure cases have been more instructive than the success stories.

Riverside's lane is now permanent, by the way. The removable barriers came out in year two, and the council vote was 9-4. The gap on the eastern approach is still there. Somebody will fix it eventually, and when they do, we hope they write it down.