Laserfiche WebLink
<br />----...-............,.............:..>...............~.~'""--.-'-~--.---.......-.;...:..-.___~__~.:.__~.'lIi---.:.,,---------:..:........,:---:.....~_________'--".....;.........:....:~~.~_...:....:-. <br /> <br />typically on weekends, so that residents could <br />understand the full range of issues being <br />addres~ed and provide input into the different <br />regulatory approaches. The village used visual <br />preference surveys to gain a better under- <br />standing of what residents did and did riot <br />like. After th e new cod es were drafted, <br />Riverside operied up all ordinance review <br />meetings to the public to allow for continued <br />input. For the residential revisions alone, more <br />than 20 public meetings were held with the <br />plan commission before the public hearing on <br />the final ordinance. <br /> <br />what is encouraged. The second task is to <br />determine how specific or broad each stan- <br />dard should be. <br />It is often easierto tell an CiPplicantthat <br />he or she mtlst do something, rather than <br />attempt to persuade an applicant that adding <br />a certain design element is recommended. <br />The benefit of a requirement-a "mtist"-is <br />that the expected form is more predictable <br />and less review time is needed because it is <br />an issue of compliance, rather than negotia- <br />tion. The downside is that a requirement may <br />be met with resistance from property owners, <br /> <br />is expected and no cohesive look to the result- <br />ing development. This negates the purpose of <br />form-based controls. <br />Finally, it is important for a community to <br />remember the type of development it is plan- <br />ning for and to ensure t~at regulations do not <br />exclude specific development types that may <br />be desired, even .if ~hey are not the predomi- <br />nant form. If traditional residential develop- <br />ment includes tall homes in the Victorian <br />style, the code can be tailored to specifically <br />address these architectural forms as excep- <br />tions without setting a height limitthat leads <br />to out-of-scale modem development that tow- <br />ers over its neighbors. <br />In order to preserve the historic develop- <br />ment pattern within the village, Riverside <br />established strict setback controls for both the <br />CBD and the residential districts. In the CBD, <br />the village created parcel-by-parcel setbacks <br />for each zoning lot, Including a combination of <br />minirilUm setbacks, maximum setbacks, and <br />build-to lines, coLipled with buffer yard requirec <br />ments where lots abutted residential uses. In <br />residential districts, in order to maintain the <br />historic variability of the front setback, thecbn- <br />.~epf of a street yard was created. Prior to the <br />ordinance update, the village used an averag- <br />ing provision. The dimension of the street <br />yard-whether a front yard or corner side yard <br />in more ;traditional .zoning terms-is deter- <br />mined by the closest dimension indicated on <br />. the Works Progress Administration (WPA) <br />House Setback Survey. The WPA undertook a <br />House Setback Survey in Riverside between <br />1936 and 1953 to document building place- <br />ment on Riverside's lots, The information con- <br />tained in this survey, available from the Village <br />building department, is used to determine the <br />street yard dimension. Because Riverside his- <br />torically has a Varied front setback, using the <br />map allows the village to maintain the historic <br />development pattern and front yard variability. <br />Some districts were also more amenable <br />to strict controls than others. Within the CBD, <br />there are veiy specific design standards for new <br />construction, including permitted building mate- <br />rials and standards for scale, massing, and fen- <br />estration; including an illustrative guide of con- <br />textual architecture. Because the CBD is a <br />concentrated area with a dearly established his- <br />toric character, the majority of regulations are <br />"musts." However, within the reSidential dis- <br />tricts, the village drafted design standards to <br />address only the specific elements that were <br />identified as the mostvulnerable.to permitting <br />out-of-character construction, such as building, 09 <br /> <br />ZONING PRACTICE 5.08 <br /> <br /> <br />With any design-oriented process, the <br />use of illustrations and photos is necessary to <br />communicate design concepts and policy ram- <br />ifications. Openhousesprovide an important <br />opportunity to illustrate what is currently per- <br />mitted under existing regulations and to solicit <br />input on proposed changes; For example, in <br />Riverside, the controversy centered around the <br />maximum building height for the CBD. Many <br />residents believed that the proposed three- <br />story height was too tall. Only after the village <br />illustrated how that height matched existing <br />development with.in the CBD was the issue <br />resolved. <br /> <br />Step 4: Balance the Regulations <br />Once the various elements ofth.e desired <br />form are identified, specific regulations can <br />be drafted. First, planners need to balance <br />what must (a requirement) be done versus <br /> <br />@ 4' ornamental fence along <br />surface parking lots <br />. @ 2' min. width. for groundcover <br /> <br />@4'widemin. Low Hedge row <br /> <br />@Large Deciduous Trees 25' <br />O.C. along surface parking lots <br />@ Parking Structures <br /> <br />@ Decorative paving pattern <br /> <br />. @ 2' high min. Raised Planter with <br />4' wide min. Low Hedge row and <br />2' min. Width for groundoover <br /> <br />@ Builciing .access points <br /> <br />@$mallornamental Trees at <br />Plaza Area entrance . <br /> <br />developers, architects, and others during the <br />code-drafting process, and may lead to <br />in~reased variance applications after code <br />adoption. When design elements are simply <br />encouraged, the code provides more flexibility <br />and tends to"calm the nerves of those who <br />fear the "architecture police," but if too many <br />eleme1)ts are only encouraged, communities <br />have no way to guarantee the desired end <br />product. <br />The specificity of the controls, whether <br />required or encouraged, is another difficult sit- <br />uation for any community to navigate. If the <br />contr~ls are very specific, the developer <br />knowsexaWy what is expected and can plan <br />accordingly. But if the standards are too spe- <br />cific, with limited alternatives, the outcome <br />can produce cookie-cutter development. On <br />the other hand, if the standards are left too <br />broad, then there can be confusion over what <br />