For other posts on the H Street Bikeway project, see category: H Street Bikeway. For the city webpage on the project, see H Street Bikeway to Sacramento Valley Station.

The 30% design for the 10th Street connection to the H Street Bikeway is shown below (these were also in the overview post H Street Bikeway: overview). The overall width of the roadway is 105.5 feet, and the ‘FOC face of curb’ width is 50 feet. The street narrows to 34 feet at the curb extensions at I Street and H Street.

---

I have created a StreetMix cross-section duplicating the design cross-section so that it can be compared to an alternative recommendation.

The design proposes a 7 foot bike lane northbound, with a 3 foot stripped buffer, and a parking lane to the right against the curb. Despite the cross-section showing a vertical delineator in the buffer, this is not possible with a parking lane to the right of the bike lane. The bike lane continues the separated, mostly parking-protected, bikeway from the south, which is a good thing. But a buffered bike lane is less safe than a separated bike lane, so detracts from the safety and low-stress goals of the project. The design encourages drivers, whether parking or drop-off/pick-up, to cross the bike lane, a poor practice.

Instead, the design should create a parking-protected separated bikeway. This reduces the utility for drop-off/pick-up, but an larger area could be set aside in the parking lane for this purpose, and the conflict zone crossing the bikeway can be clearly marked. Bikeways that swing into the curb past curb extension, and out again past curb extension, feel awkward for bicyclists, but they have been installed in several locations along the separated bikeway network, and don’t seem to engender safety issues.

The design also proposes sharrows within a southbound general purpose lane. You will have to look closely at the image to see the sharrows, but there are there. They are placed far to the right, in the door zone. This is a very poor design. New sharrows should not be installed, as they don’t decrease crash risk over unmarked routes. If they were there, they should be placed in the exact middle of the travel lane, and supplemented by ‘bicycles allowed use of full lane’ signing (MUTCD R9-20). to make is clear that drivers should not be passing bicyclists in this block. It is particularly likely that drivers will squeeze out bicyclists against the curb extension at I Street. An alternative is to stripe a narrow 5 foot bike lane, without buffer or protection, marked with green. Not ideal, but better than sharrows.

The design retains existing parking. Though it is not clear that removing parking would allow a better design, this should always be a consideration. There is ample and never-full parking in the city garage on the south side of I Street between 11th and 10th Streets. The curb extensions at I Street and H Street are critical features for the safety of walkers, but they do constrain design in this block.

My suggested design is below.

I do not have the time it would take to create an image of the street with the new design, but I think the cross-section will communicate clearly enough.

What is different? A southbound traditional bike lane (Class II) has been added. Both general purpose lanes have been reduced to 10 feet. There is no reason for over-wide lanes in this section. No buses, no delivery. The east side parking lane, an over-generous 9 feet, has been reduced to 7.5 feet. And the parking-protected separated bikeway is up against the curb, still with a 3 foot buffer from parked cars.