5 ms·
> eliminating maze-like cul-de-sac-heavy street layouts You can actually do the opposite. You make suburbs heavily maze like to slow traffic down. Instead, you
by BlackFly 5y ago
> eliminating maze-like cul-de-sac-heavy street layouts
You can actually do the opposite. You make suburbs heavily maze like to slow traffic down. Instead, you build plenty of shortcuts for bikes and pedestrians: the direct routes. That is: the incentives to bike or walk (short direct route to nearby locations) should outweigh the incentive to drive (twisted path that might be kilometers winding around a crow's flight of 100m).
Actually building separate paths for pedestrians and cyclists is a required ingredient in that recipe though.
- jabl 5y agoYes, I'm not convinced that cul-de-sacs are necessarily bad, they prevent residential streets from becoming throughfares. What you propose with shortcuts for foot or bicycle traffic could be a good compromise.
- herbst 5y agoI was raised in a city that has one river that splits the city. Around this river is where all the biking centralises and cars are forbidden. The city is old and narrow too. Thing is you are nearly everywhere faster by bike. And so the far majority of people has and uses one. People whine about their traffic there, not realizing how lucky they are.
- atrettel 5y agoI have seen it argued that heavily-curved suburban streets are safer because drivers have to slow down to see around the bends, etc. Highly-curved suburban streets also tend to avoid 4-way intersections and prefer T intersections. In theory both of these should make the streets safer, but in practice the streets tend to be built to highway-like standards, making many people drive over 30 miles an hour anyway. I encounter that on a daily basis. I would instead prefer for designers to make the streets narrower and to provide prominent sidewalks and bike paths, since that sends a much clearer signal that drivers should slow down. Moreover, there is a second problem with these suburban street layouts. They tend to follow a hierarchical design. Each area is a separate "pod" that is disconnected from adjacent areas. To get to another area, you have to go through a limited number of "choke points" that feed you into a larger road or an even larger road or highway (traverse up the tree and then back down). This design choice inevitably leads to traffic at the choke points, since many drivers cannot possibly avoid these paths. A street grid avoids that since it operates in parallel; there are many equivalent routes. This is literally the same as running a program in serial versus parallel. So even drivers have good reasons to dislike typical suburban streets, since they do inevitably lead to traffic by design.
- BlackFly 5y agoAh, so I was more getting at a style seen in the Netherlands. The residential neighbourhoods have short sections of roads with frequent choke points (sometimes featuring speed bumps, but sometimes just narrowing of the road to a single lane), together with frequent one way sections and blocked routes for cars but continuations for lighter vehicles. From the perspective of a vehicle, the neighbourhood is precisely a pod: disconnected from a neibouring region until they filter from the residential streets onto a more main road and then back into the neigbouring residential area. However, to pedestrians and bicycles, there is no real delineation. Mazelike to vehicles, multiply connected and convenient to pedestrians and bicycles. Edit: so pedestrians and bicycles will typically avoid the choke points since more direct routes are available to them. On the main roads where vehicles become congested (and faster) clear separation of the traffic types becomes increasingly necessary compared to lazy back streets where bicycles and vehicles can intermix (these people will typically be neighbours anyways).