2 ms·
As a year-round cyclist commuter, the situation outlined is a bit more complicated than just two choices. C) Sometimes method "A" is best, because there's too
by ArlenBales 10y ago
As a year-round cyclist commuter, the situation outlined is a bit more complicated than just two choices.
C) Sometimes method "A" is best, because there's too much car traffic or too unsafe car traffic for the cyclist to take the lane (method "B"). In this case, it works wonderfully if the car yields to the cyclist (and any pedestrians). When cars don't yield to the cyclist/pedestrians going straight, and they should ALWAYS yield, you have problems.
D) Method "B" is ideal, except when the intersection sucks and doesn't detect the cyclist. There is an intersection I pass through everyday that is like this. If it's empty and I take the lane, it doesn't detect me. If it's completely empty (no cars in sight from any direction), I usually ride through even on a red. If there's cars, I ride to the curb, dismount, hit the crosswalk button, re-mount, and wait for green. The problem arises when after I do this, cars show up behind me to make a right turn and putting me in situation "A". Normally situation "C" plays out if the driver yields to me, but even so I always make eye contact with the right turners to make sure they're aware of me.
The best situation is B) if a car is already in the lane turning right or going straight as I approach the intersection. I can sit in the lane going straight and the light will go green because it detects the car.
tl;dr I wish intersection lanes detected bicyclists better. So much aged infrastructure.