My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 06/06/2013
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2013
>
Agenda - Planning Commission - 06/06/2013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:18:05 AM
Creation date
6/6/2013 9:18:37 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
06/06/2013
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
383
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Fortunately, this is changing as senior planning <br />staff members learn more about the best prac- <br />tices of form -based coding, schools begin to <br />teach more courses in smart growth planning <br />and form -based coding, and people continue <br />to educate themselves on these topics. <br />The form -based coding approach and <br />methodology presented in the articles men- <br />tioned above represent a paradigm shift in the <br />way we write zoning codes, not just an attempt <br />to add an additional layer of form -based regu- <br />lations on a use -based system. The intent of <br />this two-part series is to give communities the <br />knowledge to know what to ask for and what <br />to request of their consultants, and for con- <br />sultants to understand how to select the most <br />effective form -based code approach. These <br />two articles will address common form -based <br />coding misconceptions and highlight com- <br />mon mistakes to avoid based on up-to-date <br />best practice standards learned from the most <br />recent applications. They will also compare <br />different approaches for regulating urban form <br />and give them appropriate labels so they are <br />not confused or used interchangeably. <br />COMMON MISCONCEPTIONS <br />Even with the growing application of FBCs to <br />neighborhoods, cities, and regions across the <br />country, many communities remain hesitant <br />to embrace form -based coding. Undoubtedly, <br />some of this hesitation is rooted in common <br />misconceptions related to FBCs. <br />Form -Based Codes Are Relatively Untested <br />Contrary to popular belief, FBCs have been <br />tested in the marketplace. Here are statistics <br />from just two projects to summarize the poten- <br />tial economic benefits of an FBC. First, along <br />the Columbia Pike corridor in Arlington County, <br />Virginia, more than 1,30o units and almost <br />25o,000 square feet of nonresidential space <br />have been built in eight different projects with <br />complex infill conditions under the Columbia <br />Pike Form -Based Code since its adoption in <br />2004. Second, from 2005 to 2008, the taxable <br />value of properties subject to FBCs in Nashville, <br />Tennessee, increased in value by an average of <br />75 percent and one area, Ridgeview, showed <br />a z,000 percent increase in vlue. This was <br />compared to a 27 percent increase in value in <br />COMPONENTS OF A FORM -BASED CODE <br />Communities should analyze how effective the entire FBC system, not its individual compo- <br />nents, is for responding to planning trends and goals. FBCs are more than just mixed use zon- <br />ing districts. Here is an overview of standard and optional components: <br />• Building Form Standards: Building form standards are form -based zone standards that replace <br />the existing zone standards. They are the core component of an FBC and typically regulate the <br />configuration, features, and functions (uses) for buildings that define and shape the public <br />realm. To be the most effective, their content should be generated primarily by community <br />character documentation as opposed to the preexisting zone standards for each area. <br />4 Regulating Plan: A regulating plan is the map assigning the code's various standards to <br />physical locations, including the form -based zone standards. It replaces the zoning map <br />in a form -based code. In a citywide form -based code it is the same as the zoning map and <br />will have form -based and non -form -based zones on it. It is usually applied in a more fine- <br />grained manner than a zoning map, taking existing and intended form into account. <br />• Frontage Type Standards: Frontage type standards regulate the appropriate transition from <br />the private realm to the public realm. The ultimate intent of frontage standards is to ensure, <br />after a building is located correctly, that its interface with the public realm and the transition <br />between the two are detailed appropriately. <br />4 Public Space Standards: Public space standards are specifications for the elements within <br />the public realm, including thoroughfares and civic spaces. Thoroughfare standards incor- <br />porate detailed requirements for sidewalk, parking lane, and travel lane widths and street <br />tree locations. Civic space standards regulate parameters, such as maximum and minimum <br />size, and introduce a range of nonsuburban civic space types into a city or town. <br />• Building Type Standards: Many FBCs include building type standards that are supplemental <br />to the building form standards. They introduce an appropriate range of building types that <br />are allowed within each form -based zone and regulate form characteristics specific to each <br />type. To be effectively regulated, especially when applied at a larger scale, building type <br />standards should be tied back directly to zone standards. <br />ZONINGPRACTICE 5.13 <br />AMERICAN PLANNING ASSOCIATION I page 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.