Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/kfarr/near-term-protected-bike

🚲Near-Term Protected Bike Network
https://github.com/kfarr/near-term-protected-bike

Last synced: 7 days ago
JSON representation

🚲Near-Term Protected Bike Network

Awesome Lists containing this project

README 

        
# 🚲 2019 SF Near-Term Protected Bike Network

An open source working sheet attempting to prioritize bicycle facility improvements in San Francisco in order to focus community and City efforts on quickly delivering small projects of a few blocks at a time.



## Forced rank top 10 "routes" (April 27):

1. Valencia

2. 2nd

3. Howard

4. Folsom

5. Polk

6. Embarcadero

7. 5th

8. Golden Gate Park

9. 8th

10. Townsend



Last updated April 27 based on [informal twitter survey](https://twitter.com/kfarr/status/1113189980275245056) and rubric defined below. [Source data.](https://docs.google.com/spreadsheets/d/1DU1aKr5Ow7ywOJoXCLVYoEESQD2hKLyPETXL0_bvVk0/edit)



## Forced rank top 10 "routes" interlaced with "projects" (April 27):

1. Valencia

- a. Valencia (19th to Cesar Chavez)

- b. Valencia (15th to 19th)

2. 2nd

- a. 2nd (Townsend to Market)

3. Howard

- a. [Howard (2nd to 5th)](https://github.com/kfarr/bike-lane-priorities/tree/master/howard-2nd-to-5th)

- b. Howard (2nd to Embarcadero)

4. Folsom

- a. Folsom (4th to 2nd)

- b. Folsom (2nd / Essex to Embarcadero)

- c. Folsom (13th to Cesar Chavez)

5. Polk

6. Embarcadero

7. 5th

- a. 5th Street (Townsend to Market)

8. Golden Gate Park

9. 8th

10. Townsend

- a. Townsend (5th to 2nd)

- b. Townsend (7th to 8th)

- c. Townsend (2nd to Embarcadero)



Suggested projects arbitrarily created by Kieran as a strawman used for community feedback, however the intention is purposefully small segments that can be quickly designed and implemented in the near-term.



## What is this list?

This is an attempt to force rank which bicycle infrastructure improvements should be implemented in San Francisco.



## Why this list?

There are many supporters of bike infrastructure improvement but not all align on which specific projects are important relative to each other.



This misalignment can impact infrastructure building in a few ways:

- Leads to "squeaky wheel syndrome" where a loud minority get attention

- Improvements are often reactionary related to specific high-profile incidents instead of proactive

- General low productivity as efforts are splintered on different projects by each city agency, advocacy organization and even the general public.



Further, there is no forum for stakeholders outside of City agencies to see technical details of projects and a "source of truth" of current and proposed conditions.



Instead, this approach attempts to use a simple rubric to prioritize projects which is open and can change based on community discussion. This approach also attempts to be a central repository for all persons (whether or not affiliated with the City) to update factual information of various projects based on current conditions and proposed new projects.



## Project Prioritization Rubric:

* Feasibility - Level of effort for (protected) relative to current conditions (Includes: removal of parking, thru lanes, physical constraints, road width, utilities, transit lanes and tracks, overhead wires.) Projects may rank more favoribly as being feasible if they are in progress or otherwise have a quick path to completion. 

* Data - Injury (collision, fatality), ridership, ratio (ie low ridership::high injury), user surveys or votes, modeling (estimating future ridership)

* Closing the Gaps - Network Connection (System Utility)



## How do you think bike lane projects should be prioritized in San Francisco?

Open a new issue: https://github.com/kfarr/bike-lane-priorities/issues



## What is done? What allows an item to be removed from the list?

It must be a useable fully protected bike path. This is most likely satisfied with a sufficiently wide bike lane buffered by parking, continuous safe-hit style delineators, or otherwise permanent physical barriers such as concrete or planters.



Projects that are in progress but incomplete remain on the list. It is not done until there are no cars parked on the lane and it provides a continuous safe travel path for people on bicycles on the duration of the project scope.



## Terms as used in this document

route - an entire street

project - a subset of a route defined as the space between 2 blocks (for example: 3rd street between howard and folsom)



## Other project contenders

- 11th (Market to Division)

- [Harrison (2nd to 5th)](https://github.com/kfarr/bike-lane-priorities/tree/master/harrison-2nd-to-5th)

- Harrison (5th to 11th)

- Harrison (11th to 16th)

- Townsend (2nd to Embarcadero)

- "Hairball"

- Cesar Chavez (Guerrero to 101)

- Broadway (Polk to Columbus)

- Broadway (Columbus to Embarcadero)

- 3rd (Market to Terry Francois)

- Embarcadero - which segments?

- Columbus - which segments?

- Sansome (Which segments?)

- Battery (which segments?)

- Kearny (Market to Columbus)

- Stockton (Broadway to Market)

- Polk (which segments?)

- City Hall

- Bryant (which segments?)



Add your own: suggest a change through github, open an issue or contact me @kfarr on twitter



## For more reading

For an example of a high quality bike plan, check out [Oakland's 2019 Bike Plan](https://www.letsbikeoakland.com/draft-plan/#/)!