RFT-CDR-09 CorridorThis is the parking-specific case of Parking-Lane Reallocation, applied to bike facilities. A common configuration keeps some parking but moves it away from the curb, using the parked cars themselves as part of the physical buffer protecting the bike lane between the parking lane and the sidewalk.
Bike Highway / Greenway (COL-BHG-04), Default (Standard Collector) (COL-DEF-01) with Protected Bike Lane / Cycle Track (ELM-PBL-37)
Most applicable where on-street parking demand analysis shows capacity to reduce or relocate parking without materially harming adjacent businesses or residents, and where lane width or count changes alone don't recover sufficient space.
AASHTO identifies reconfiguring or reducing on-street parking as one of three established retrofit approaches for adding bike facilities without widening the road.1 Removing parking near intersections specifically has documented safety benefits beyond the bike facility itself, improving sightlines between drivers and other road users.2
Can move through the construction spectrum starting with temporary channelizers and paint at the pilot stage, since testing community and business response to the parking change before committing to permanent curb reconstruction is common and often politically necessary. See Construction Methodology & The Build Spectrum.
Usually a city public works or planning department decision, though parking removal frequently requires more direct business and resident engagement than lane-width or lane-count retrofits, and may need city council involvement where removal is contested. See Legal & Planning Mechanisms.
Protected bike lane retrofit via lane-width reallocation (RFT-CDR-07), Protected bike lane retrofit via lane removal (RFT-CDR-08) (the other two approaches to the same underlying goal, distinguished by where the recovered width comes from); Parking-lane reallocation (RFT-CDR-05) (the general-purpose version of this same mechanism)