Orange County NC Website
115 <br />Annotated Outline <br />DEVELOPMENT STANDARDS <br />General Commentary: This chapter contains all of the development standards in the newA~D ie 5aYeDeVelOPyment Standards <br />development with the exception of the subdivision standards, which are found in <br />Article 6, Subdivisions. The proposed contents of Article 5, Development Standards, 5.1 Off Street Parking and Loading <br />are listed in the sidebar and are discussed below. Examples of standards to be <br />incorporated into this article include: ' - <br />5.2 Landscaping Standards <br />Off-street parking and loading standards as described in the diagnosis; <br />Revised landscaping standards that emphasize new standards for vehicle 5.3 Tree Protection <br />accommodation areas, performance-based buffers, and street trees; <br />e New Vee protedion standards for retention of exisfing tree canopy, <br />specimen trees, and tree protection during construction; <br />Open space set-aside standards; earance and limiting <br />fence and walls standards that focus on fence app <br />fence heights; <br />Exterior lightingstandards; <br />Trafficimpadstandards; <br />New community form standards; <br />Commercial design standards that address the design and orientation of <br />retail establishments; <br />Multi-family design standards focusing on multi-family strudure <br />appearance; and <br />Carrying forward the existing signage standards with no substantive <br />revisions. <br />5.4 Open Space Set-Aside <br />5.5 Fences and Walls <br />5.fi Exterior Lighting <br />5,7 TrafficlmpactAnalysis <br />5,g Community Form Standards <br />5.9 Commercial Design Standards <br />5.10 'Multi-Family Design-Standards <br />OFF-STREET PARKING AND LOADING <br />This sedion includes quantitative off-street parking requirements for uses 5:11 signage ~ - <br />matching the revised use table for consistency and ease of use. The <br />d'fferentiated bytdi trid and type of development will be set forth and <br />Incentives will be used to allow developers [o provide fewer than the minimum number of required parking spaces to <br />referred development types, such as verucally-integrated <br />exchange for providing public or green space, or developing p <br />mixed nal off sVeetospaces'provided n'excess of therm n mum requtrements (for allruses)Ibe onnperviouslor semir-''pervious <br />add <br />surfaces. <br />Flexibility will be built into the provisions by allowing applicantr to propose alternative strategies, such as off-site par ing, <br />shared parking, valet parking, or (in appropriate settings} credit for on-street parking spaces. Deferrevd~ ~ nldgareavforofuture <br />included that allow a developer to construd 80 percent of the minimum required amount of parking and then monitor <br />parking demand during initial operation of the development (for perhaps a year or 16 months), <br />parking held in reserve until monitoring proves that the built parking is either adequate or is inadequate and needs to e <br />rovisions are added requiring pedesuian amenities and bicycle parking facilities. <br />expanded into the reserved area. Finally, p <br />The parking lot landscaping provisions are relocated to the new landscaping section. <br />LANDSCAPING STANDARDS rester flexibility in <br />The current landscaping requirements will be upgraded and the general planting requirements increased. To improve c arty, <br />graphics will be used, as appropriate, to explain the requirements for fandscapmg. Provisions allowing g <br />' meeting landscaping standards (such as aggCeg~ a of lanrds p g may bePequir0edl[o be native otrldroughdt tolerant courage <br />creative design. In addition, a minimum p g <br />In additon to the general requirements for all landscaping, we suggest adding more specific standards for site landscaping for <br />nonresidential and multi-family uses. We recommend upgrades to the parking lot landscaping provisions such as the <br />Page 13 <br />Hillsborough, North Carolina <br />Unified Development Ordinance I DraftAnnotated Outline <br />November, 2009 <br />