"Stroad" seems to be a recently popularized by strongtowns. I'm curious if anyone has actually managed to measure this sort of thing? My suspicion is that it "stroads" are essentially to-wide streets, and it should be possible to find research indicating that streets should be narrower, because widening them causes people to drive too fast. I was only able to find the following, coverage, though:
They both seem to fundamentally go back to a single conference paper,
"Narrower Lanes, Safer Streets." I don't know those blogs, and a single conference paper is -- I mean the paper is probably good but, hard to build a case on just one paper.
What is up with this? Computer engineers produce reams and reams of papers. Where are the civ.Es hiding their secrets?
edit: changed slightly, original text seemed unintentionally dismissive.
It's definitely a word coined by Strong Towns. But, a "new" made up word? I guess it depends on your scale of "new."
The oldest reference to "Stroad" on strongtowns.org I've found is this[1] from January 2, 2012.
That makes the term nearly 10 years old. That being said, this term has been getting much more popular over the last couple years, especially due to Not Just Bikes.
the argument is that streets and roads serve fundamentally different purposes and thus have different design goals, and stroads do both and thus fail at both. Roads are for transit, getting cars a long distance between interest points, and streets are for navigating within a point of interest like a neighbourhood. Roads want to optimise for higher cruising speed and streets are to optimise for parking, mixed-use with pedestrians and cyclists, etc. You can't combine these things - it's not a measurement divide but a categorical one.
Traffic engineer here. Generally there is a hierarchy of roads called functional class. It goes local street - collector - minor arterial - major arterial - freeway. From local to freeway the speeds increase and the land access decreases. Good urban design should connect only roads one "step" apart, that is local roads should only connect to collectors and so forth. Reality is clearly different.
I would imagine everyone can think of a local road that is more convenient than another route therefore attracting high traffic volumes. These roads become problematic without improving the proper route. The other side of the coin is an arterial that is built but too many accesses are allowed to connect to it. In my home town this has happened when the city council caved to developers and allowed residential construction on a major arterial because nobody wanted to build commercial developments at the time. Jump ahead 10 years and there is now a strange neighborhood with driveways directly on the busiest street in town.
Changing roads is very tricky due to the funding sources. Usually local roads are only eligible for local funding where as arterials are eligible for federal funding. There are exceptions and it is much more nuanced than can be explained in one paragraph.
> Generally there is a hierarchy of roads called functional class. It goes local street - collector - minor arterial - major arterial - freeway.
This heirarchy seems to miss the importance distinction that Strong Towns makes between a "street" and a "road", in that "streets" are places where human life takes place, and "roads" are how vehicles move rapidly from place to place. It has only category with the word "street" literally present, and then moves immediately to other things whose relationship to the street/road distinction is unclear. This is a problem because streets include those that are purely residental as well as those with retail etc.
You are correct. The old way of thinking about roads/streets (synonyms in this case) is a place to move cars. The people centric view on transportation is new enough that there isn't much traction among the old guard at state DOTs. Changing something like functional class and what it means is very hard due to decades of history. As the saying goes, old dogs can't learn new tricks. This is especially true for government agencies. I have worked with cities that have a strong desire to make their transportation network people centric but the state won't help pay for it because the concepts don't move enough cars and to them, that is all that matters.
Exactly. Ideally, only the street should have real street functionality (houses and shops directly accessible from the street). Maybe the collector too; it's meant to have many streets connecting to it, so access to car parks for shops makes a lot of sense there too. But anything arterial should just be about getting people from one end to the other as smoothly as possible.
There's one more category that's often ignored in this list: the rural road. There, the functions can mix without any problems, but only because of its very low density and low use; very little traffic means you can still cross the road easily, and have time to turn into drive ways and things like that without hindering anyone.
I'll actually defend the stroad, they work fine so long as you don't allow parking, and you limit the driveways to 2-3 per "block" - anything more than that and they cease to function as an street or a road. Often the stroad is just a section with a bunch of businesses on an otherwise well designed arterial road.
The pictures they post of supposed stroads look like normal arterials to me.
The problem with 3 driveways per block is you've just made a really low density set of stores. This means that you massively increase the average distance someone has to travel to get to the store they want. One of the main reasons to separate streets and roads is that it encourages tightly packed small shops which (especially when combined with mixed zoning) create low average travel distances. Lower travel distances mean fewer cars on the road (cause more stuff is in walking/biking distance) and therefore lower traffic.
> The pictures they post of supposed stroads look like normal arterials to me.
That's because in America, most arterials are stroads. We've gotten used to bad infrastructure.
And yeah it works on some level, sure. American businesses still manage to function, people still manage to do things. But there are a number of major downsides still.
Where I live there's a diamond interchange between two state highways controlled only by stop-signs at the end of the off-ramps towards the smaller of the two.
Near that interchange there is a neighborhood. For whatever reason, both sides of the neighborhood have traffic lights, so when traffic is heavy, if you want to go from the larger to smaller highway (particularly if you want to turn left!), it's far more expedient to cut through the neighborhood.
>Changing roads is very tricky due to the funding sources. Usually local roads are only eligible for local funding where as arterials are eligible for federal funding. There are exceptions and it is much more nuanced than can be explained in one paragraph.
Don't get me started on all the perfectly functional things they screw up because some jerk central planner in DC wrote a spec based on national averages.
I get the idea, and I'm in favor of removing stroads. I think it would be more compelling if it was backed up by some data. Finding actual data on stroads is basically impossible because it is not a term-of-art as far as I can tell.
Try the terms "road diet" and "traffic calming", they will yeild more results. While not exactly the same concept, they are terms that have been in use within the industry for much longer.
Just yesterday was thinking about how much pavement is between me and my neighbors across the street. Standard suburbia single family home area, and I think we could have a car on each side of the street and still pass two cars through side by side, though thankfully cars never need to slow down out of fear of hitting things - one side is no parking. It's a ton of infrastructure and maintenance cost that is never fully utilized. Even at the peak of demand (Christmas or Thanksgiving probably) we're not all hosting at the same time, and most likely two very nearby neighbors will be traveling (not taking up street space, and probably fine with you parking in their driveway if you ask permission).
On top of the massive street, everyone has driveways that can hold 2-3 vehicles and typically 2 sometimes 3 garage stalls (though many are filled with "stuff", an entirely separate issue).
But this comes after the traffic and environmental and planning studies, so it's more of a "how" to build, after you've at least gone through some preliminary design and figured out "what" to build.
And yes, there is literally a table (for highways at least) that gives values for lane width vs the "natural speed" that drivers gravitate to.
> "Stroad" seems to be a new made-up word by strongtowns
Thank you! I clicked the link and then scrolled through several top-level comments thinking that either this was some sort of internet joke that I wasn't previously aware of or I somehow managed to not learn word that everyone else has always known.
It looks like they came up with it in 2013 actually, I've only recently bumped into it (and suddenly, multiple times). I think it might be in the process of becoming a thing for... I dunno, there's a particular group of people online who get really into very specific policy things and kind of meme about them, but also kind of try and make solid arguments for them.
https://usa.streetsblog.org/2015/05/27/compelling-evidence-t...
https://thecityfix.com/blog/bigger-isnt-always-better-narrow...
They both seem to fundamentally go back to a single conference paper, "Narrower Lanes, Safer Streets." I don't know those blogs, and a single conference paper is -- I mean the paper is probably good but, hard to build a case on just one paper.
What is up with this? Computer engineers produce reams and reams of papers. Where are the civ.Es hiding their secrets?
edit: changed slightly, original text seemed unintentionally dismissive.