Laserfiche WebLink
<br />. <br /> <br />1'0 ensul"e succ.ess, all four elements must be incorpo- <br />rated into any effort, otherwise a co~munity will run <br />the risk oflosing support and derailihg the process. <br /> <br />1. Clear and Concise Standards <br /> <br />,,':;'The most difficult task in design-based code prepa- <br />,Y 'ration is crafting a standard that achieves a desired <br />,iffect or outcome without over-manipulating the <br />';Hesign process. Design standards should be tied to <br />'measurable purposes and outcomes. An example of <br />, an outcome is increasing pedestrian activity across <br />a building frontage (to reduce or prevent conges- <br />tion in the public streets) or ensuring infill building <br />compatibility (to facilitate the creation of a conven- <br />ient, attractive and harmonious community). This <br />draws the "essential nexus" or required connection <br />between the regulation and a valid public purpose. . <br /> <br />. <br /> <br />An example of this is the desire <br />to move residential buildings <br />doser to the str~et to encourage <br />'pedestrian activity while main- <br />'iaining a commensurate level of <br />'., 'privacy for occupant. To accom- <br />, ' ,,:p!ish this, residential buildings <br />, . '.historically have been elevated <br />, from the grade of the sidewalk, <br />usually approximately 11/2 to 2 <br />feet. This will allow the lower sill <br />height of the fronting windows <br />to be abov~ eye-level for most <br />passers,-by, ensuring that the <br />occuPants can monitor the activ- <br />ities of the street without sharing <br />their evening meal selections <br />with all of their neighbors. <br /> <br />Cl.I <I' <br />"Cl...... <br />;:j 0 <br />'U Cl.I <br />Cl.I fI) <br />,.1-< 2 <br />'0.. <br />C,,/<. Cl.I <br />to adhere to a rigid, contrived condition. In fa: 0/, ~ <br />the opposite is usually the case. Most design-b <br />codes, except for those written specifically for a his_ ", <br />toric area, are usually much more permissive in <br />style and detail. <br /> <br /> <br />:E " <br />c:: '~ <br />;:j ~ <br />S ~ <br />S .~ <br />o · <br />ul <br /> <br /> <br />To that end, design-based codes outside of a his- <br />toric district should refrain from specifically men- <br />tioning a particular architectural style. Most archi- <br />tectural styles found in the United States can fit <br />well within the context of an urban block. As a rule, <br />good urbanism can trump bad architecture. <br /> <br />Of course, there are some basic rules of pedestrian- <br />scaled design techniques such as the requirement <br />that all buildings have a definable base, middle, <br />and top in fa~de treatment as well as a requir.e- <br />ment for fenestration {doors and windows) at the <br />street level. <br /> <br /> <br />Facade detailing should prevail over all other <br />site elements including parking standards <br /> <br />Codes should also avoid loose, <br />highly subjective language such <br />as "the project should be inter- <br />esting" or "harmony in texture, <br />lines, and masses [is] encouraged." Particularly in <br />areas where the judiciary has not accepted aesthetic <br />zoning, communities would do well to avoid such <br />vagaries and consistently tie design standards to the <br />purpose statements found in their enabling legisla- <br />tion. <br /> <br />. <br /> <br />2. Style Neutral <br /> <br />Pundits of design-based codes often categorize <br />over-prescription as the encouragement of "Mickey <br />Mouse architecture" in that buildings are expected <br /> <br />A number of specific architectural <br />styles do not meet this definition in <br />the strict sense, particularly mod- <br />ernist styles such as th~jnternation- ' <br />al style and deconstructionist style. <br />This does not preclude these styles <br />from the urban environment, but <br />special attention would need to be <br />paid to ensure that such iconic <br />architecture does not visually. <br />impact the pedestrian realm. <br /> <br />3. Easy to Read Fonnat <br /> <br />The format of the document that <br />presents the design requirements is <br />nearly as important as the standards <br />themselves. <br /> <br />Standards should be clear in their <br />narrative as the legal standard will <br />be tested by the interpretation of <br />the text. Graphics, photos, and illustration should <br />be generously included, but should be used only to <br />supplement the text, not supplant it. <br /> <br />Other basic publishing rules should apply as well <br />including a readable typeface, consistent margins, <br />balanced white space, and a thorough index. <br /> <br />Communities must also consider the prevalenc.e of <br />codifying ordinances through the Municipal Code <br />Corporation (MCC) and similar web-based Code <br />clearinghouses. The format must not be so rigid as <br />