You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 44.201.0.0/16 has been blocked (disabled) by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 23:54, 31 July 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪AntiCompositeNumber‬. The reason given is Open proxy/Webhost: Visit the FAQ if you are affected .
- Start of block: 13:55, 18 August 2022
- Expiry of block: 13:55, 18 April 2025
Your current IP address is 44.201.28.123. The blocked range is 44.201.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Short description|Urban planning restricting through traffic of automobiles))
((Multiple issues|
((Original research|date=October 2023|reason=Several paragraphs contain unsourced information on a niche subject.))
((more citations needed|date=July 2019))
))

[[File:Radburn Cellular Street Pattern.jpg|thumb|300px|right|The network structure of [[Radburn, New Jersey]] exemplifies the concept of street hierarchy of contemporary districts. (The shaded area was not built.)]]

The '''street hierarchy''' is an [[urban planning]] technique for laying out road networks that exclude automobile through-traffic from developed areas. It is conceived as a [[hierarchy of roads]] that embeds the link importance of each road type in the [[network topology]] (the connectivity of the nodes to each other). Street hierarchy restricts or eliminates direct connections between certain types of links, for example residential streets and [[arterial road]]s, and allows connections between similar order streets (e.g. arterial to arterial) or between street types that are separated by one level in the hierarchy (e.g. arterial to highway and collector to arterial). By contrast, in many regular, traditional [[grid plan]]s, as laid out, higher order roads (e.g. arterials) are connected by through streets of both lower order levels (e.g. local and collector). An ordering of roads and their classification can include several levels and finer distinctions as, for example, major and minor arterials or collectors.

At the lowest level of the hierarchy, [[cul-de-sac]] streets,<ref>[https://www.oregon.gov/lcd/Publications/NeighborhoodStreetDesign_2000.pdf] An Oregon Guide for Reducing Street Widths | Neighborhood Street Design Guidelines</ref> by definition non-connecting, link with the next order street, a primary or secondary "collector"—either a ring road that surrounds a neighbourhood, or a curvilinear "front-to-back" path—which in turn links with the arterial. Arterials then link with the intercity highways at strictly specified intervals at intersections that are either signalized or grade separated.

In places where grid networks were laid out in the pre-automotive 19th century, such as in the [[American Midwest]], larger subdivisions have adopted a partial hierarchy, with two to five entrances off one or two main roads (arterials) thus limiting the links between them and, consequently, traffic through the neighbourhood.

Since the 1960s, street hierarchy has been the dominant network configuration of [[suburb]]s and [[exurb]]s in the [[United States]], [[Canada]], [[Australia]], and the [[UK]]. It is less popular in [[Latin America]], [[Western Europe]], and [[China]].

Large subdivisions may have three- or even four-tiered hierarchies, feeding into one or two wide arterials, which can be as wide as the ten lane [[Champs-Élysées]] or [[Wilshire Boulevard]]. Arterials at this level of traffic volume generally require no fewer than four lanes in width; and in large contemporary suburbs, such as [[Naperville, Illinois]], or [[Irvine, California]], are often eight or ten lanes wide. Adjacent street hierarchies are rarely connected to one another.

==History==
[[File:MedinaTunisStreetNetwork.jpg|thumb|300px|Hierarchical street network in the [[Medina of Tunis]] includes culs-de-sac (green), local streets (yellow), collectors (orange), and arterials (red) linking the gates to the city centre.]]
In the pre-automotive era of cities, traces of the concept of a hierarchy of streets in a network appear in Greek and subsequent Roman town plans. The main feature of their classification is their size. In Roman cities, such as [[Pompeii]], major thoroughfares (e.g. the [[Decumanus Maximus|decumanus]]) had a width of 12.2 m, secondary streets (e.g. the [[cardo]]) 6 m and tertiary streets (e.g. vicinae) measured 4.5 meters. The first allowed for two way cart traffic, the second generally only one, while the third only loaded animals. Narrower streets that could only accommodate pedestrians were also present in both Greek and Roman cities. Thus the restriction on connections between major streets on particular modes (carts and chariots) was the effect of the width of the street itself and not the lack of linkage. This method is akin to the contemporary concept of [[permeability (spatial and transport planning)|filtered permeability]].

A clearer record of a stricter hierarchical order of streets appears in surviving and functioning Arabic-Islamic cities that originate in the late first millennium AD such as the [[Medina of Tunis]], [[Marrakesh]], [[Fes el Bali|Fez]], and [[Damascus]]. In these cases there are four classes of streets starting with the cul-de-sac type (1.84-2.00 m wide) and moving up to the local (third order connector), then a collector that usually surrounds a residential quarter (second order connector) and, finally, to the first order connector (arterial). The latter connector usually crossed the city through its centre and led to the city gates (see drawing). These arterials were decreed to be at least wide enough for two crossing loaded animals, 3.23 to 3.5 m.<ref>Besim Hakim 1986, Arabic-Islamic Cities – Building and Planning Principles KPI Ltd, London</ref> This tendency for hierarchical organization of streets was so pervasive in the Arab-Islamic tradition that even cities that were laid out on a uniform grid by Greeks or Romans, were transformed by their subsequent Islamic conquerors and residents, as in the case of Damascus.<ref>Nezar Alsayyad, 1991 Cities and Caliphs: on the Genesis of Arab Muslim Urbanism, Greenwood Press</ref>

In the automotive 20th century, the street hierarchy concept was first elaborated by [[Ludwig Hilberseimer]], in his ''City Plan'' of 1927. His major priorities were increasing the safety of [[primary school]]-age children [[walk to school campaign|walking to school]], and increasing the speed of traffic.

Planners also began to modify the grid into a [[city block#Superblock|superblock]] system, where high traffic generators such as shops and apartments were placed on arterial roads that formed the boundaries of the superblock. Schools, churches, and parks were located at the center, and houses filled the residential blocks. Within the superblock, ''T''-intersections, and [[cul-de-sac|culs-de-sac]] acted as [[traffic calming]] devices, slowing or preventing through traffic.

This model prevailed between roughly 1930 and 1955, in "instant cities" such as [[Lakewood, California]], and the Los Angeles district of [[Panorama City, Los Angeles, California|Panorama City]]. The street hierarchy has been the dominant model for network layout in new suburbs since [[Levittown|the Levittowns]].

In the 1960s, when [[operations research]] and [[rationalism|rational planning]] were the prevailing analytical tools, street hierarchy was seen as a major improvement over the regular, undifferentiated, "messy" grid system. It discouraged dangerous high-speed driving and [[street racing]] in residential areas. New master-planned suburbs often codified the street hierarchy into their [[zoning]] laws, restricting the use of grid layouts in residential districts.

Eventually, the street hierarchy was also adapted for [[industrial park]]s and commercial developments. Use of the street hierarchy is a nearly universal characteristic of the "[[edge city]]", a roughly post-1970 form of urban development exemplified by places such as [[Tysons Corner, Virginia]], and [[Schaumburg, Illinois]].

==Criticisms and discussion==
Social commentators and urban planners have often pointed out that the street hierarchy arrangement has serious limitations. These criticisms are generally part of a broader indictment of mid-20th-century urban planning, with critics charging that planners have only considered the needs of young children and their working-age parents in creating the spatial arrangement of the late 20th and early 21st centuries.

===Financial costs===
Some planners and economists consider the street hierarchy to be financially wasteful, since it requires more miles of street to be laid than a [[grid plan]] to serve a much smaller population.

While housing unit density and, consequently, population density affects the per capita cost of infrastructure, it is not inextricably linked to the street network pattern whether hierarchical or uniform. Theoretically and historically a [[city block]] can be built at high or low density, depending on the urban context and land value; central locations command much higher land prices than suburban. The costs for street infrastructure depend largely on four variables: street width (or Right of Way), street length, block width, and pavement width. These variables affect the total street length of a neighbourhood and the proportion of land area it consumes. Street length increases costs proportionately while street area represents an [[opportunity cost]] of land unavailable for development. Studies show that regular, undifferentiated grid patterns generally incur infrastructure costs about 20 to 30 percent higher than the discontinuous hierarchical street patterns, reflecting an analogous street length increase.((citation needed|reason= Referencing "studies" and making quantitative claims without citing anything|date=January 2016))

In suburban areas subject to [[property tax]] caps such as California's [[California Proposition 13 (1978)|Prop 13]], the enormous per-capita expenditures required to maintain streets mean that only houses costing over half a million dollars can provide enough property tax revenue to cover the cost of maintaining their street hierarchies. In areas with low developer [[impact fee]]s, cities often fail to provide adequate maintenance of internal and arterial roads serving newly constructed subdivisions.<ref>"Fresno May End Low-Fee Policy for Developers", ''Los Angeles Times'', 23 August 2005</ref>
Municipal records show that street maintenance represents a large portion of a municipal budget, particularly in Northern climates where snow removal is added to the regular lifecycle upkeep. Two planning strategies have been suggested to deal with these costs in new developments: reduction of street length or increase in household density, or a combination of the two. Of the two strategies, reducing street length is the most effective and permanent; densities can vary over time and cannot be effectively controlled.

===Pedestrian degradation===
[[New Urbanism|New Urbanists]] decry the street hierarchy's deleterious effects on pedestrian travel, which is made easy and pleasant within the subdivision but is virtually impossible outside it. Residential subdivisions usually have no pedestrian connections between themselves and adjacent commercial areas, and are often separated from them by high masonry walls intended to block noise. New Urbanist writers like [[Andres Duany]] and [[James Howard Kunstler]] often point out the absurd nature of car trips forced by the street hierarchy: while a grocery store may be less than a quarter-mile distant physically from a given home in a subdivision, the barriers to pedestrian travel presented by the street hierarchy mean that getting a gallon of milk requires a car trip of a mile or more in each direction. [[Jane Jacobs]], among other commentators, has gone so far as to say that modern suburban design—of which the street hierarchy is the key component—is a major factor in the sedentary lifestyle of today's children.<ref>((Cite web|url=http://www.forbes.com/2007/10/28/health-sedentary-cities-forbeslife-cx_rr_1029health.html|title=America's Most Sedentary Cities - Forbes|website=[[Forbes]]|date=June 3, 2016|archive-url=https://web.archive.org/web/20160603161424/http://www.forbes.com/2007/10/28/health-sedentary-cities-forbeslife-cx_rr_1029health.html|archive-date=2016-06-03))</ref> [[Mass transit]] advocates contend that the street hierarchy's denigration of pedestrian traffic also reduces the viability of public transportation in areas where it prevails, sharply curtailing the mobility of those who do not own cars or cannot drive them, such as disabled persons, teenagers, and the elderly.

===Traffic issues===
====Congestion causes and remedies====
Most [[traffic engineering (transportation)|traffic engineers]] consider the street hierarchy to be optimal, since it eliminates through traffic on all streets except arterials. However, some have contended that it actually exacerbates [[traffic congestion]], leading to [[air pollution]] and other undesirable outcomes.<ref>((Cite web|url=https://www.theatlantic.com/magazine/archive/2000/12/the-physics-of-gridlock/378457/|title=The Physics of Gridlock|first=Stephen|last=Budiansky|date=December 1, 2000|website=The Atlantic))</ref> An alternative to street hierarchy, [[Traditional Neighborhood Development]] (TND) networks, recommended by the Institute of Traffic Engineers, implies that a type of hierarchy is desirable nonetheless. It suggests that "While TND street networks do not follow the same rigid functional classification of conventional neighborhoods with local, collector, arterial and other streets, TND streets are hierarchical to facilitate necessary movements."<ref>((cite web |url=http://www.cues.fau.edu/cnu/docs/Traditional_Neighborhood_Development_Street_Design_Guidelines-ITE.pdf |title=Archived copy |access-date=2017-05-23 |url-status=dead |archive-url=https://web.archive.org/web/20110220174833/http://www.cues.fau.edu/cnu/docs/Traditional_Neighborhood_Development_Street_Design_Guidelines-ITE.pdf |archive-date=2011-02-20 |location=Washington, DC))</ref>

A more precise image of the prevalent thinking about structuring road networks can be found in the 2006 ITE/CNU recommended practice for the design of urban thoroughfares.<ref>[http://www.ite.org/bookstore/RP036.pdf Context Sensitive Solutions in Designing Major Urban Thoroughfares for Walkable Communities]</ref> In it, the functional, traffic-engineering classifications of roads are replaced by three basic road types: boulevard, avenue and street with the addition of a second type of boulevard – the multi-way. These road types reflect familiar names and images of roads and also real conditions in an urban environment, where each type normally performs multiple functions but only up to a hierarchical limit. For example, a boulevard can function as a principal and minor arterial but not as a collector or local access street; an avenue, as principal/minor arterial and a collector but not as a street; while a street can serve as minor arterial, a collector and a local (access road) but not as a principal arterial. These exclusions of functional roles derive from the design intention to put an emphasis either on mobility or access; both cannot be accommodated concurrently in every case.

These hierarchical distinctions of road types become clearer when considering the recommended design specifications for the number of through lanes, design speed, intersection spacing and driveway access. As the number of lanes increase from two to four and then six and, correspondingly, the operating speed from 40&nbsp;km/h to about 60&nbsp;km/h, the intersection spacing increases from a 90–200 m range to its double (200–400 m). Similarly, the restriction on driveway access becomes more stringent and, in effect, impossible in the case of a required raised median for boulevards and multi-way boulevards. Thus a multi-way and simple boulevard (corresponding to the functional definition of arterial) are deemed to perform their mobility function better when access to them is limited to intervals between 200 and 400 m, that is every three to five normal, 80-m-wide city blocks.

A common practice in conventional subdivision design is a road pattern that limits access to the arterials (or boulevards) to few points of entry and exit. These [[choke point]]s produce traffic congestion in large subdivisions at [[rush hour]] periods. Congestion also increases on the boulevard (regional arterial) if the access restrictions are not observed. Furthermore, congestion can be density-dependent in addition to being configuration-dependent. That is, the same geometric configuration ideally suited to improve traffic flow, [[roundabout]]s for example, fails to function adequately beyond a certain threshold of traffic volume. Increased traffic volume is a direct outcome of increased household density of a district.

These relationships of congestion to layout geometry and density have been tested in two studies using computer-based traffic modeling applied to large subdivisions. A 1990 study<ref>Traditional Neighborhood Development: Will the Traffic Work? Presentation by Walter Kulash at the 11th Annual Pedestrian Conference in Bellevue WA, October 1990</ref> compared the traffic performance in a 700-acre (2.8-km<sup>2</sup>) development that was laid out using two approaches, one with a hierarchical street layout that included cul-de-sac streets and the other a Traditional Neighborhood Design street layout. The study concluded that the non-hierarchical, traditional layout generally shows lower peak speed and shorter, more frequent intersection delays than the hierarchical pattern. The traditional pattern is not as friendly as the hierarchical to long trips but friendlier to short trips. Local trips in it are shorter in distance but about equivalent in time with the hierarchical layout.

A later more extensive comparative traffic study<ref>Taming the Flow—Better Traffic and Safer Neighbourhoods. Canada Mortgage and Housing Corporation, July 2008</ref> of an 830-acre (3.4-km<sup>2</sup>) subdivision tested three types of layouts: conventional, TND, and [[Fused Grid]]. It also tested the resilience of all three layouts to an increased traffic load generated by increased residential densities. The study concluded that all types of layouts perform adequately in most low to moderate population density scenarios up to a certain threshold of 62 persons per hectare (ppha). As densities increased beyond the threshold so did travel time. At a 50% density increase to 90 ppha, the conventional hierarchical pattern showed the highest increase in travel time (20%), followed by the TND (13%) and the fused grid (5%). When the density increased further to include one local job per two residents, delays increased respectively by 139%, 90% and 71% for the conventional, traditional, and fused grid. This confirms the density influence on congestion levels and that a hierarchical pattern can improve flow if laid out following the access restrictions proposed in the ITE/CNU practice guide.

In edge cities the number of cars exiting a large subdivision to an arterial that links to a highway can be extremely high, leading to miles-long queues to get on [[freeway]] ramps nearby. ''See [[Rat running]]''.

====Safety====
Transportation planners and traffic engineers have expressed concerns over the traffic safety drawbacks presented by the street hierarchy. Recent studies have found higher traffic fatality rates in outlying suburban areas than in central cities and inner suburbs with smaller blocks and more-connected street patterns.<ref>http://www.minority.unc.edu:9014/sph/minconf/2004/materials/ewing.etal.pdf 
 ((dead link|date=November 2020))</ref><ref>((cite web |url=http://www.virginia.edu/topnews/releases2002/lucy-april-30-2002.html |title=Archived copy |access-date=2006-09-03 |url-status=dead |archive-url=https://web.archive.org/web/20060903234004/http://www.virginia.edu/topnews/releases2002/lucy-april-30-2002.html |archive-date=2006-09-03 ))</ref> While some of this disparity is the result of distance from emergency medical facilities (hospitals are usually not built in a newly developed suburban area until a fairly late stage in its development), it is clear that the higher speeds engendered by the street hierarchy increase the severity of accidents occurring along arterial roads.

An earlier study<ref>Eran Ben-Joseph, Livability and Safety of Suburban Street Patterns: A Comparative Study (Berkeley, CA: Institute of Urban and Regional Development, University of California, Working Paper 641, 1995)</ref> found significant differences in recorded accidents between residential neighbourhoods that were laid out on an undifferentiated grid and those that included culs-de-sac and crescents in a hierarchical structure. The frequency of accidents was significantly higher in the grid neighbourhoods.

Two newer studies examined the frequency of collisions in two regional districts using the latest analytical tools. They investigated the potential correlation between street network patterns and frequency of collisions. In one study,<ref>Using Macrolevel Collision Prediction Models in Road SafetyPlanning Applications Gordon R. Lovegrove and Tarek Sayed Transportation Research Record: Journal of the Transportation Research Board, No. 1950, Transportation Research Board of the National Academies, Washington, D.C., 2006, pp. 73–82</ref> cul-de-sac hierarchical networks appeared to be much safer than the uniform grid networks, by nearly three to one.
A second study<ref>Sun, J. & Lovegrove, G. (2009). Research Study on Evaluating the Level of Safety of the Fused Grid Road Pattern, External Research Project for CMHC, Ottawa, Ontario</ref> found the grid plan to be the least safe by a significant margin with respect to all other street patterns.

A 2009 study <ref>Eric Dumbaugh and Robert Rae. Safe Urban Form: Revisiting the Relationship Between Community Design and Traffic Safety. Journal of the American Planning Association, Vol. 75, No. 3, Summer 2009</ref> suggests that land use patterns play a significant role in traffic safety and should be considered in conjunction with the network pattern. While all intersection types in general reduce the incidence of fatal crashes, four-way intersections, which occur regularly in a uniform grid, increase '''total and injurious crashes''' significantly. The study recommends hybrid street networks with dense concentrations of T-intersections and concludes that a return to the 19th century gridiron is undesirable.

===Banning on-street parking===
Banning on-street parking can provide social benefits if the car users and the general public pay for off-street parking.<ref>[https://trid.trb.org/view/1567244] Transportation Research Board | On-street versus off-street parking: an urban economic analysis | Created: Nov 12 2018</ref><ref>[https://safety.fhwa.dot.gov/saferjourney1/library/countermeasures/55.htm] Federal Highway Administration |On-Street Parking</ref><ref>[https://escholarship.org/content/qt3xj0q23z/qt3xj0q23z_noSplash_946f2e7b912e7cc9e71f98c81b3912d0.pdf] Shoup, Donald. "On-Street parking management v. Off-Street parking requirements." The access almanac 42 (2013): 38-40.</ref>

==Future prospects==
((more citations needed|section|date=November 2020))

===United States===
While street hierarchies remain the default mode of suburban design in the United States, its 21st century usefulness depends on the prevalence of low density developments. To the degree that developable land becomes scarce in coastal urban areas and in geographically constrained inland cities such as [[Tucson, Arizona|Tucson]], [[Las Vegas, Nevada|Las Vegas]], and [[Salt Lake City, Utah|Salt Lake City]], the street hierarchy's inability to handle any but the lowest population densities is a long-term liability. The street hierarchy is also unpopular in the coastal city of [[New Orleans, Louisiana|New Orleans]] because of its geographic barriers, and because like Philadelphia, New York, and Cleveland, New Orleans already had suburbs before the new design became popular. Grids were used in New Orleans to fit a population that had at one time reached over 700,000 into ((convert|180|sqmi|km2)) of land with over 20 percent of that number being dedicated to uninhabitable wetlands. There a street hierarchy took up too much space to be economical. Real estate developers in areas with high land prices, such as Southern California's [[Inland Empire]], are finding that the relatively high population density of contemporary subdivisions is leading to severe traffic congestion on arterial roads that were country lanes a decade earlier. The street hierarchy is also becoming less attractive as awareness increases of the environmental consequences of the urban planning paradigm of which it is an integral part. The "[[smart growth]]" movement calls for street patterns with a high degree of connectivity, and with it a more balanced provision for various travel modes, both vehicular and non-vehicular.

===Europe===
The [[Milton Keynes#Urban design|1967 design]] of [[Milton Keynes]], with its (national speed limit) grid roads at 1&nbsp;km intervals containing 'organic' road lay-out grid-squares, was strongly founded on the 'street hierarchy' principle. The 2006 [[expansion plans for Milton Keynes]] will abandon this model in favour of "mixed-use traditional British city streets".((citation needed|date=June 2017))

===Developing countries===
In countries such as India, where automobile ownership is increasing at double-digit annual rates, the street hierarchy is becoming increasingly popular as suburban development takes on forms strongly resembling those of American exurbs.
However, the suburban-like cities in China are the aftermath of excessive implementing hierarchical street-layout and rapid urban development. With high-rise residential towers, over-engineered roads and public transportation systems, they are distinctively different from American suburbs. The street hierarchy theory forms the center of the Chinese planning system which was adapted from ex-soviet in 60's. Today, Chinese planning schools are continuing to teach the theory unaware of its effects on the suburbanization, congestion and wasteful road-engineering.((citation needed|date=August 2015))

==See also==
*[[Complete streets]]
*[[Green transport hierarchy]]
*[[Road hierarchy]]
*[[Main Street]]
*((Annotated link|Pedestrian zone))
*((Annotated link|Permeability (spatial and transport planning)))
*[[Settlement hierarchy]]
*[[Side road]]
*[[Transit desert]]
*[[Transit mall]]
*[[Types of road]]

==References==
((Reflist|30em))

;General
*Handy, Susan, Kent Butler and Robert G. Paterson (2003). ''Planning for Street Connectivity (PAS 515)''. Chicago: American Planning Association. ((ISBN|1-884829-86-4)).
*Hise, Gregory (1997). ''Magnetic Los Angeles: Planning the Twentieth-Century Metropolis''. Baltimore: Johns Hopkins University Press. ((ISBN|0-8018-5543-8)).
*Kunstler, James Howard (1993). ''The Geography of Nowhere: The Rise and Decline of America's Man-Made Landscape''. New York: Simon and Schuster. ((ISBN|0-671-70774-4)).
*Nivola, Pietro (1999). ''Laws of the Landscape: How Policies Shape Cities in Europe and America''. Washington: Brookings Institution Press. ((ISBN|0-8157-6081-7)).

((Road types))

[[Category:Hierarchy]]
[[Category:Road transport]]
[[Category:Transportation planning]]
[[Category:Types of roads]]
[[Category:Urban planning]]

Pages transcluded onto the current version of this page (help):

Pedestrian zone (edit)
Permeability (spatial and transport planning) (edit)
Street hierarchy (edit)
Template:Ambox (view source) (template editor protected)
Template:Annotated link (view source) (template editor protected)
Template:Catalog lookup link (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite web (view source) (protected)
Template:Convert (view source) (template editor protected)
Template:Dead link (view source) (template editor protected)
Template:Delink (view source) (protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (protected)
Template:Hlist/styles.css (view source) (protected)
Template:ISBN (view source) (template editor protected)
Template:Longitem (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Nobold (view source) (template editor protected)
Template:Nobold/styles.css (view source) (template editor protected)
Template:Original research (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:Road types (edit)
Template:SDcat (view source) (protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Sp (view source) (template editor protected)
Template:Yesno (view source) (protected)
Template:Yesno-no (view source) (template editor protected)
Template:Yesno-yes (view source) (template editor protected)
Template:\ (view source) (template editor protected)
Module:Annotated link (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Catalog lookup link (view source) (template editor protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Check isxn (view source) (template editor protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Convert (view source) (template editor protected)
Module:Convert/data (view source) (template editor protected)
Module:Convert/text (view source) (template editor protected)
Module:Delink (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:GetShortDescription (view source) (template editor protected)
Module:Lang (view source) (template editor protected)
Module:Lang/ISO 639 synonyms (view source) (template editor protected)
Module:Lang/data (view source) (template editor protected)
Module:Language/data/iana languages (view source) (template editor protected)
Module:Language/data/iana regions (view source) (template editor protected)
Module:Language/data/iana scripts (view source) (template editor protected)
Module:Language/data/iana suppressed scripts (view source) (template editor protected)
Module:Language/data/iana variants (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:String (view source) (protected)
Module:Unicode data (view source) (template editor protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Street hierarchy.

Retrieved from "https://en.wikipedia.org/wiki/Street_hierarchy"