October 2009

Thou Shalt Review Ordinances...And Then What?

Using zoning code audits and ordinance reviews to better manage stormwater

Article Tools

Create a Link to this Article

Photo: Lisa Nisenson
Walking tours are good ways to examine the built environment from the receiving waterway’s point of view. A measuring wheel can be helpful to assess pavement widths, which are, in turn, a great measure of excess impervious cover.

Additional Article Content

By Lisa Nisenson, Clark Anderson

Comments

Communities covered under Phase II of the National Pollutant Discharge Elimination System (NPDES) are wrapping up activities under the first round of permits. If the first five-year permit cycle was about setting up programs, the second permit cycle will focus on program assessment and fine-tuning. EPA anticipated this evolution, including the following language: “In developing your program, you should consider assessing existing ordinances, policies, programs, and studies that address stormwater runoff quality.”

Ordinance and code reviews are an increasingly popular tool to identify and address the impact of land development standards and zoning codes. Similarly, communities are reviewing codes for barriers to low-impact development or overarching sustainability goals. This article provides information on conducting code reviews and some of the more surprising findings related to conventional zoning codes.

Preparation

The first step in preparation is to determine how the review results are to be used. At the most basic level, reviews can be revelatory, where the results are used primarily for education and outreach. Second, cities can perform code audits in concert with a local planning effort. The most consequential audits are launched as part of regulatory programming such as Phase II, combined sewer overflow control plans, and total maximum daily load implementation plans, where code changes are required in order to meet regulatory standards.

In addition to having someone from planning and zoning walk you through zoning codes, the following pre-code audit steps can help streamline the process:

  • Determine regulatory requirements for site design not presented in the zoning code. Ask the city or county engineer to bring stormwater performance standards; hillside development standards; and building, utility, and plumbing codes.
  • Find out if changes to zoning and planning are already underway to meet new rules on water conservation, “green streets,” hazard mitigation, and the like.
  • Chart out ahead of time whether adopting code changes can get you additional benefits—for example, points or priority funding for state infrastructure projects.
  • Prepare to exploit cross-program actions. For example, a code change to increase and track tree canopy for stormwater management may also meet climate initiative goals to reduce urban heat island effect.
  • Finally, because changes to legal code may be involved, make sure the legal department and elected official are involved and aware of possible changes needed.

Activities
In addition to the code review itself, there are several parallel activities to include in a code audit. Windshield surveys and walking tours are helpful in determining how codes and regulations are translated into actual projects. Second, the use of maps is important, because the relevance of a certain code category can hinge on how large an area the zone covers or on its location. Finally, interviews are needed to ascertain whether code language that appears to be a barrier or opportunity has any meaningful on-the-ground influence.

Photo: Lisa Nisenson
Shared parking relieves the landscape of additional pavement. Here, a parking space was “found” on existing impervious surface.

Methodology
The first generation of code reviews, by and large, tended to recommended changes within the existing code structure—for example, revised setbacks and parking ratios. These recommendations, while applicable, seemed incomplete, because Euclidian zoning codes are implicated in driving excess land development and consumption, as detailed below. Euclidean zoning refers to the practice of establishing codes for single-use districts—for example “R” and “C” zones for residential and commercial zones, respectively. These codes control uses, bulk and placement of buildings, and parking, among other things.

Moreover, many early code audits focused on a single objective—for example, reducing runoff on individual lots or rooting out excess parking from code. Communities today are tackling community design issues on several fronts, and reviews need to address multiple scales and multiple objectives simultaneously. One of the most effective methods for capturing multiple scales of development and impacts is, conveniently, from the watershed’s point of view.

Early versions of code reviews with the watershed in mind focused on impervious surface, with recommendations largely centered on reducing the percentage of impervious cover. However, one of the most direct methods of reducing the share of impervious cover is to grow lot sizes. Success at the lot level can thus become a wider disturbance at the watershed level. This same standard also penalizes compact development, where building blueprints intentionally maximize site coverage with the aim of reducing the overall development footprint. To overcome the site-versus-watershed tension, we asked the impervious cover question in two ways:

  • What drives excess impervious cover at the larger basin level?
  • What drives impervious cover at the site level?

As it turns out, these questions are really looking at efficient use of land, which is also at the core of code reviews to address walkability, economic development, transportation, and reductions in energy use.

Series of Questions
Investigating site-level impacts that arise from land development standards is challenging enough, but how does one assess impacts on a larger scale? This involves looking at what drives land development patterns. Table 1 shows examples of “pattern” elements within codes, and sample questions.

Advertisement

Findings
How does code affect open space?
On individual sites, bulk requirements such as setbacks and landscaping requirements begin to shape “open space” on a lot, while prescriptions for dedicated open space appear in language for larger residential subdivisions and office park–type projects.

One of the strongest actions related to open space is to weave open space and parks into a green infrastructure program, which begins to define the services rendered by conserved land. Quantified details can help support and defend stepped-up code language for land acquisition and restrictions on ecologically sensitive lands. Next Page >

What Do You Think?

Post a Comment

Be the first to tell us what you think!

Post a Comment

Not a subscriber? Sign Up
 
 
*  
 




 

Get Stormwater E-mail Updates!

Get weekly news and updates through our Stormwater e-mail newsletter!