bigeman312
Senior Member
- Joined
- Jul 19, 2012
- Messages
- 2,358
- Reaction score
- 2,358
Exactly and it’s important to recognize which segments of the SW Corridor have higher and lower pedestrian compliance. Sections where the pedestrian path is a concrete sidewalk adjacent to traffic have much lower compliance than sections where pedestrians are presented with an asphalt path that’s more separated from traffic.The pedestrian and bike routes need to not only be separate, but the pedestrian path needs to be both more appealing and more obvious than the bike route. Most of the Southwest Corridor involves separated, parallel paths, but very few people use the pedestrian path, so the de facto result is the bike route as a shared use path. It's frustrating as somebody who mostly bikes the route, but I am sympathetic to the walkers and joggers, because the pedestrian path sucks much of the time (concrete instead of asphalt, closer to car traffic, etc.). Too often, paths for non-car ROW users are made inconvenient and physically taxing. As a bike rider, I'll accept less convenient, because the combination of speed and gear leverage makes it less of an issue. But when I'm walking, I don't want something that clearly tells me I have no business being there in the first place.
For example, the section between McBridge and Williams has higher compliance, as both pedestrians and cyclists are presented with pleasant asphalt paths through a park. When I bike on that section, I use the the bike path and when I run, I use the pedestrian path.
On the other hand, the section between Williams and Gordon has much lower compliance. The pedestrian path is a concrete sidewalk next to the street, while the cycling path is more pleasant, asphalt, and separated from traffic. Whether I bike or run on that section, I use the “bike” path, which is both lawful, more pleasant, and causes less stress on my joints than running on concrete.