Hacker News new | past | comments | ask | show | jobs | submit login

> The problem is that putting cyclists moving at 10 to 15 mph (14 to 22 feet per second) at the pedestrian position results in situations where neither the cyclist or the motorist see each other until the last second and that results in a collision

This is why I specified correctly designed: what you're saying is an artifact of a poorly-designed intersection which does not have good visibility or clear traffic flows.




> This is why I specified correctly designed

Even the NACTO (National Association of City Transportation Officials) design guide states:

>> Driveways and minor street crossings are a unique challenge to cycle track design. A review of crossing facilities and design practice has shown that the following guidance may improve safety at crossings of driveways and minor intersections:

>>

>> * If the cycle track is parking protected, parking should be prohibited near the intersection to improve visibility. The desirable no parking area is 30 feet from each side of the crossing. >>

>> * For motor vehicles attempting to cross the cycle track from the side street or driveway, street and sidewalk furnishings and/or other features should accommodate a sight triangle of 20 feet to the cycle track from the minor street crossings and 10 feet from driveway crossing.

The distances quoted should make it evident that, at least in the US, even the guidelines aren't going to lead to "correctly designed" intersections.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: