Laserfiche WebLink
Why We Need to <br />Update Our Current <br />Land Development <br />Regulations <br />Ease of Use <br />Every Elk River resident, business owner, or developer <br />should be able to navigate and understand the Code <br />of Ordinances without the assistance of an attorney or <br />member of city staff. One significant factor that detracts <br />from the user -friendliness of Elk River's land develop- <br />ment regulations is its organization. Land development <br />regulations should be organized in a manner that makes <br />it straightforward to use and administer. User-friendly <br />regulations use tables and graphics when appropriate, and <br />order sections based on how frequently they are used and <br />referenced. <br />Elk River's current land development regulations are not <br />structured to allow developers or members of the public <br />to find relevant information rapidly. For instance, Division <br />2 - Administration and Enforcement, which defines the <br />city's permit procedures and requirements, and Division <br />5 - Supplemental Regulations, which includes regulations <br />for specific uses such as accessory buildings and personal <br />solar panels, are at the beginning of Article VI - Zoning. <br />Meanwhile, Divisions 6, 7, and 8, which list the allowable <br />uses, setbacks, and lot sizes for different districts, come <br />toward the end of Article VI - Zoning. Most code users seek <br />to know the permitted uses and dimensional standards for <br />their site of interest before understanding detailed proce- <br />dures on permitting processes or regulations for specific <br />uses, and so the city's existing format requires most code <br />users to sift through the first several articles before finding <br />the information they need to get started. The organiza- <br />tion and user -friendliness of Article VI - Zoning could be <br />improved if the permitted use and dimensional regulations <br />in each district were presented together in a tabular format <br />at the article's beginning. <br />Further, the structure of information within the Divisions <br />of Article VI - Zoning is not intuitive and may require <br />many code users to look back and forth between different <br />subsections to locate relevant information. For instance, <br />a site plan review and permit process for applications in <br />the Downtown District is defined in Section 30-1026 (g), <br />while the procedure is not clearly enumerated in Division <br />2 - Administration and Enforcement, which contains <br />the submittal requirements and procedures for condi- <br />tional use permits and variances. Further, the application <br />requirements for site plans in the Downtown District are <br />not clearly and objectively listed, while the information <br />is defined for conditional use permits in Division 2. The <br />code's user -friendliness would be strengthened if the <br />permit procedures were organized together within one <br />division and if application requirements and procedures <br />were clearly and consistently listed. <br />Development Standards and <br />Use Specific Provisions <br />Development standards and use specific provisions are <br />scattered throughout Article VI - Zoning. The structure of <br />the development standards and use specific provisions <br />should be reorganized to reduce excessive cross refer- <br />encing, improve readability, and be more user friendly. In <br />addition to restructuring these sections, the city should <br />enhance and modernize existing standards and estab- <br />lish additional standards in order to align with the vision, <br />goals, and recommendations of this plan and to reflect <br />current best practices. For example, Division 5 lists parking <br />minimums for permitted uses, however, the section does <br />not enumerate tools such as shared parking, an essential <br />tool in realizing the outlot development detailed in the <br />Economic Development Plan. <br />Another barrier to realizing outlot development is the <br />city's minimum parking requirements. For example, the <br />minimum amount of parking required for a retail store <br />is 1 space for every 200 square feet of floor area. The <br />national average minimum requirement, based on the <br />Institute of Transportation Engineers, is 1 space for every <br />250 square feet of floor area. Although this difference <br />may seem marginal, when extrapolated out to a potential <br />development, it could have big impacts on the develop- <br />ment potential of a piece of property. For example, a typical <br />grocery store has around 40,000 square feet of floor area <br />and would therefore require 200 parking spaces based on <br />Elk River's existing minimum requirement. The industry <br />standard however would require only 160 parking spaces. <br />Elk River requires that parking spaces be nine feet wide <br />and 20 feet long, or 180 square feet. Therefore, Elk River <br />would require the typical grocery store to dedicate 36,000 <br />square feet of land area to parking while the industry <br />standard would require only 27,360, an 8,640 square foot <br />difference. Not only does this excessive requirement limit <br />the development potential of a property, it also negatively <br />impacts stormwater absorption and can lead to urban heat <br />island issues. <br />128 <br />I97MITI ad907C1OWN I AVE9101Wo <br />Implementation Plan • Elk River Comprehensive Plan <br />