Loading...
PZC Packet 030111Memorandum To The Planning and Zoning Commission Fr Sally Vecchio, Community Development Dir. Date February 24, 2011 RE Work Session 3: Overview of the Avon Development Code, Chapter 7.28 Development Standards This is the third PZC work session reviewing the recently adopted Avon Development Code (the Code). This meeting will focus on the Development Standards of the Code. Broken into nine (9) categories, this chapter of the Code provides specific criteria for design and development in the Town. Many of the standards from the Avon Design Guidelines were codified in this chapter, along with new standards intended to implement the Town's land use policies, including: a more pedestrian oriented community, protection of our natural resources, and attractive well-designed buildings. The standards apply to all development in the town. Staff will give a brief over review of each section of the Code, while identifying the new provisions. An outline of the nine development standards included in Chapter 7.28 is attached, and will be used to guide the discussion on Tuesday night. The Checklists The Checklists (attached) summarize each section and subsection of the Development Standards that will need to be addressed in a development plan application. There are 5 different checklists, depending on the proposed development (single-family/duplex, town homes/multifamily, mixed-use, natural resource, and alternative equivalent compliance). The Checklists are intended to be used by designers in preparing development plans, and by staff and PZC while reviewing applications to ensure compliance with town standards for transportation access and circulation, landscaping, parking, architectural design and areas subject to natural resources. PZC WORKSHOP 3 — AVON DEVELOPMENT CODE TOPIC: Chapter 7.28 - Development Standards §7.28.020 Parking and Loading Existing section with new additions designed to reduce impact of parking lots, and codifying the town's driveway requirements. • Standards and illustrations for parking stall dimensions (no change) • Off-street parking requirements (min changes from old code) • 125% increase in parking max (with minor exception by Director) • Mixed-use reduction (no change) • On street parking may be included in calculations (new) • Public Parking Districts (no change) • Bike Facilities for developments with > 25 parking spaces (new) • Design/Maintenance Requirements (new) o Includes snow storage requirements • Off -Street Loading (no change) § 7.28.030 Access Driveway requirements Existing standards and new standards codified • Mountain Terrain — new requirements, PZC approval for modifications • Court Driveways (new) • Drive-through Standards (new) §7.28.040 Mobility and Connectivity (AEC Available) New section implements planning policies supporting pedestrian connectivity, reducing dependency on vehicle, improving transit. • Bike and Pedestrian Paths • Vehicle Circulation — Internal Streets • External Streets and Sidewalks §7.28.050 Landscaping (AEC Available) Existing section with new standards for parking lots, buffering, maintenance and plant quantities. • Landscaped Area (no change) • Buffers between non-residential and residential uses (new) • Landscaped Units (new) o Based on average unit counts approved by PZC • Parking Lot Landscaping (from Design Guidelines) • Landscape Standards (new) • Plant List (no change) • Noxious Vegetation (no change, reference to title 8 AMC) • Irrigation and Watering Requirements (from Design Guidelines) • Revegation Requirements (from Design Guidelines) 21 Page §7.28.060 Screening (AEC Available) New section intended to screen certain uses from public view • Mechanical Equipment • Loading and Service Areas • Outdoor Storage Yards • Dumpsters • Materials and Design §7.28.070 Retaining Walls (AEC Available) New section intended to set limitation on size and material of retaining walls • Height and Material (from Design Guidelines) §7.28.080 Fences (AEC Available) Existing standards codified from the Design Guidelines §7.28.090 Design Standards (AEC Available) Existing standards from the Design Guidelines and new standards to implement Comprehensive Plan recommendations. 1. General Applicable Design Standards • Site disturbance envelopes (new) • Site design/ building orientation (new) • Materials and colors (no change) • Roof overhangs and materials • Weather protection for pedestrian areas 2. Generally Applicable Residential Standards 3. Design Standards for Wildridge (new) 4. SF and Duplex Standards in all other subdivision 5. Townhouse Design Standards 6. Multifamily Design Standards 7. Residential Parking Locations and Layout 8. SF and Duplex Garages 9. Mixed Use and Non -Residential Standards (most from Design Guidelines and District Plans) §7.28.100 Natural Resource Protection New section with standards codified from the Design Guidelines, and Comprehensive Plan. 1. Steep Slopes 2. Streams, River, Waterbodies, Wetlands 3. Grading, Erosion Preventions and Sedimentation Control 4. Flood Damage Prevention 5. Geological Hazard Areas 6. Scenic Views (reserved) 7. Alternative Energy Systems (solar and wind) 31 E' a g e DEVELOPMENT REVIEW CHECKLISTS — SINGLE-FAMILY & DUPLEX ZONE DISTRICT STANDARDS Date Zone District: Lot: Subdivision: This checklist is for the sole purpose of assisting the applicant in preparation of a development plan application. The applicant should refer to the Avon Development Code and Application Submittal Requirements to complete a development plan application. This checklist is not an official part of the Avon Development Code and should in no way be considered a replacement for the Code or instructions contained with the application. Code i Section 7.20 Code Requirement Minimum Lot Size Comply Not .Applicable Not Staff Comments 7.20 Minimum Lot Width adequate widths, sight lines and appropriate 7.20 Maximum Lot Coverage lighting. 7.20 Minimum Landscape Area Public sidewalks are located along perimeter § 7.20 Building Setbacks 7.28.040(e)(3) streets. § 7.20 Max Building Height 7.20 Max Number of Dwelling Units § 7.20.100 0 Deed Restricted Units 7.24 Use Permitted the princi al buildings entrances. MOBILITY AND CONNECTIVITY - Bicvcle and Pedestrian Paths Bicycle/pedestrian paths are designed with 7.28.040(e) adequate widths, sight lines and appropriate lighting. Public sidewalks are located along perimeter 7.28.040(e)(3) streets. There a continuous, internal pedestrian walkway 7.28.040(e)(4) provided from the perimeter public sidewalks to the princi al buildings entrances. 7.28.040(e)(5) Adeauate bike Darkina facilities are Drovided. 7.28.040(e)(6) Bicycle paths constructed in public right of way CODE SECTION•D • NOCOMMENTS The proposed new subdivision street circulation meet TOA Standards. 7.28.040(f)(2)(i) plan provides multiple connections to the 7.28.040(e)(7) Bicycle paths in private communities will be existing Town street network. maintained by the HOA. A cul de sac or dead-end street has been used Bicycle/pedestrian paths connect all adjacent 7.28.040(f)(2)(ii)(A) due constraints such as existing topo, natural 7.28.040(e)(8) developments, neighborhoods, and typical features or vehicle safety. destinations (schools, public trails, rec facilities, A cul-de sac is not proposed for etc . 7.28.040(f)(2)(ii)(A) commercial/industrial uses. 7.28.040(e)(9) Location of paths takes into consideration T All permanent dead end streets have been existing travel patterns. 7.28.040(f)(2)(ii)(B) 7.28.040(e)(10) Sidewalks are not located in areas prone to ice. MOBILITY AND CONNECTIVITY - Vehicle Circulation CODE SECTION•D • NOCOMMENTS The proposed new subdivision street circulation 7.28.040(f)(2)(i) plan provides multiple connections to the existing Town street network. A cul de sac or dead-end street has been used 7.28.040(f)(2)(ii)(A) due constraints such as existing topo, natural features or vehicle safety. A cul-de sac is not proposed for 7.28.040(f)(2)(ii)(A) commercial/industrial uses. T All permanent dead end streets have been 7.28.040(f)(2)(ii)(B) designed as -cul de -sacs and extend no further than 1000 linear feet. 7.28.040(f)(2)(ii)(C) Proposed cul-de-sac conforms to Fire Code and has been approved by Fire District. 7.28.040(f)(2)(ii)(D) No half streets are proposed. A pedestrian access easement has been 7.28.040(f)(2)(ii)(E) provided (10 ft wide), between the cul-de-sac LL and the closest adjacent street or sidewalk. The arrangement of streets in a development provide for the alignment and continuation of 7.28.040(f)(3)(i) existing of proposed streets. Traffic calming measures shall be integrated into the development to mitigate the impact of future "cut -through) traffic. LANDSCAPE STANDARDS CODE SECTION•. Street ROW shall extend to or along adjoining NOCOMMENTS 7.28.050(d) property boundaries so that a roadway 7.28.040(f)(3)(ii) connection of street stub shall be provided for ever 1,500 feet. 7.28.050(e) Street and sidewalk connections shall be made 7.28.040(f)(3)(iii) between neighborhood commercial and residential. LANDSCAPE STANDARDS CODE SECTION•. • NOCOMMENTS 7.28.050(d) If required does the landscape buffer meet code requirements. Does the application provide the necessary 7.28.050(e) Landscape Units at a minimum of 1 unit per 50 square feet of landscaped area. Is perimeter parking lot landscaping provided at 7.28.050(f)(1) a minimum width of 6 feet and 1.2 landscape units per lineal foot. Is an internal landscape strip provided for every 7.28.050(f)(2) other row of double row parking, when more than 50 spaces are provided. 7.28.050(f)(4) Does the internal landscaping island meet the code's design requirements. 7.28.050(f)(5) Does the internal landscaping strip meet the code's design requirements. Parking Lot Landscaping in TC District. 7.28.050(f)(6) Does the proposed landscaping meet the code requirements. 7.28.050(g) Does the landscape plan respond to minimum sight distance triangle requirements. 7.28.050(h)(1) Existing native vegetation and mature trees I I have been preserved. No trees or vegetation have been removed (except for noxious or non-native) outside 7.28.050(h)(1)(i) designated site disturbance areas on lots greater than '/2 acre in the RL, RD and RM zone districts. All native landscaping has been kept in its 7.28.050(h)(1)(iii) native state. 7.28.050(h)(1)(iv) Significant Trees and vegetation that have been • N/A AEC STAFF COMMENTS 7.28.060(b)(1) removed from the site has been replaced. 7.28.050(h)(1)(iv)(C) The location of Protective Construction Fencing has been identified on the plans. 7.28.050(h)(2) Proposed plant materials' have been specified on the plans 7.28.050(h)(3) Noxious Vegetation has been identified for properties removal Temporary installations of gas/oil tanks are 7.28.050(h)(4) Irrigation Plan is included on the Landscape 7.28.060(b)(4) screened from public ROW and/or neighboring Plan. properties. SCREENING STANDARDS CODE SECTION•. • N/A AEC STAFF COMMENTS 7.28.060(b)(1) All outdoor refuse and recycling receptacles are screened All antennas are screened from view from an 7.28.060(b)(2) public ROW or neighboring property Satellite dishes are screened from neighboring 7.28.060(b)(3) properties Temporary installations of gas/oil tanks are 7.28.060(b)(4) screened from public ROW and/or neighboring properties. Mechanical equipment is screened from public 7.28.060(d) ROW and/or neighboring properties by a parapet wall or similar feature that is an integral part of the building's architectural design. Load and service areas are in the rear, side or 7.28.060(e) inside of building, not visible from public ROW or adjacent residential uses. 7.28.060(f) Outdoor storage areas are screen with approved materials. 7.28.060(g) Shopping carts are stored inside the building. Shopping cart corrals are not plastic. Dumpsters are screened with 6 fit masonry wall 7.28.060(h) or wooden fence not visible for public ROW or nei hboring property. 7.28.060(i)(1) Plant materials are used to screen utility boxes 7.28.060(i)(2) No fence, wall or hedge is tall than 6 ft RETAINING WALLS CODE SECTION•. • NOCOMMENTS 7.28.070(b)(1) Retaining walls are utilized because finished Wildridge fence does not delineate the grades cannot meet Code standards property boundaries, is less than 4 ft in height, Walls over 4 ft high are designed with a series of split rail with no more than 2 rails, does not 7.28.070(b)(2) terracing. The width of terrace is at least 5 ft. delineate an area > 2,000 sf, and does not Retaining walls over 7 ft in height have been 7.28.080(b)(1) negatively affect wildlife migration. Multi -family 7.28.070(b)(3) approved by PZC fence is integrated into overall design of the 7.28.070(b)(4) Wall material is compatible with site and property. Duplex fence received approval from buildings on site adjoining property and fence is integrated into Walls over 4 ft high have been structurally overall design of the property. 7.28.070(b)(5) designed and certified by Colo licensed Walls and fences are architecturally compatible engineer and approved by Town Engineer. 7.28.080(b)(2)(i) with the style, materials, color of primary FENCES CODE SECTION•. •COMMENTS Wildridge fence does not delineate the property boundaries, is less than 4 ft in height, split rail with no more than 2 rails, does not delineate an area > 2,000 sf, and does not 7.28.080(b)(1) negatively affect wildlife migration. Multi -family fence is integrated into overall design of the property. Duplex fence received approval from adjoining property and fence is integrated into overall design of the property. Walls and fences are architecturally compatible 7.28.080(b)(2)(i) with the style, materials, color of primary building(s). Fences and walls are not greater than 50 ft in 7.28.080(b)(2)(i) solid, unbroken expanse length. 7.28.080(b)(2)(ii)(A) Fences material is compliant with Code 7.28.080(b)(2)(ii)(B) Fences in front yard is at least 50% open. Material has been approved by Director. 7.28.080(b)(2)(ii)(C) Solid fences have been designed to meet Building Code wind design criteria. 7.28.080(b)(2)(iii) Security fencing (razor , barbed wire or electric charge) are prohibited. 7.28.080(b)(2)(iv) Fence conforms to height limits. RESIDENTIAL DESIGN STANDARDS - Wildridge Subdivision CODE SECTION•D• NOCOMMENTS 7.28.090(e)(2) Roofs have 4:12 pitch or greater or have reduced building height to 30 ft. Building has street -facing architectural details 7.28.090(e)(3) and elements which provide human scale to the facade. RESIDENTIAL DESIGN STANDARDS -Single Family & Duplex Standards CODE SECTION•D• NOCOMMENTS — All Other Subdivisions 7.28.090(f)(1) Entry features and front doors to unit are CODE SECTION•. • NOCOMMENTS dominating elements facing the street. Duplex building relates to the surrounding area shall either recess behind the front fagade of 7.28.090(f)(2) by providing variations in height and massing, the dwelling portion of the structure or a front respecting scale/height of adjacent home and porch, or recess beneath a second floor bay. articulating front fagade. Side -loaded garages shall provide windows or RESIDENTIAL PARKING LOCATION AND LAYOUT - Single Family and Duplex CODE SECTION•. • NOCOMMENTS Front -loading (street -oriented) garage doors 7.28.090(i)(2)(i) shall either recess behind the front fagade of the dwelling portion of the structure or a front porch, or recess beneath a second floor bay. Side -loaded garages shall provide windows or other architectural details that are consistent 7.28.090(i)(2)(ii) with or complement the features of the living portion of the dwelling on the side of the garage facin the street. The use of alley or side -loaded garages, or the 7.28.090(i)(2)(iii) use of a combination of these garage orientations is required where feasible. 0 DEVELOPMENT REVIEW CHECKLISTS — MULTI -FAMILY RESIDENTIAL ZONE DISTRICT STANDARDS Date Zone District: Lot: Subdivision: This checklist is for the sole purpose of assisting the applicant in preparation of a development plan application. The applicant should refer to the Avon Development Code and Application Submittal Requirements to complete a development plan application. This checklist is not an official part of the Avon Development Code and should in no way be considered a replacement for the Code or instructions contained with the application. Code i Section 7.20 Code Requirement Minimum Lot Size Comply Not .Applicable Not Staff Comments 7.20 Minimum Lot Width NO NIA AEC STAFF COMMENTS 7.20 Maximum Lot Coverage Bicycle/pedestrian paths are designed with 7.20 Minimum Landscape Area 7.28.040(e) adequate widths, sight lines and appropriate § 7.20 Building Setbacks lighting. § 7.20 Max Building Height 7.20 Max Number of Dwelling Units 7.28.040(e)(3) § 7.20.100 0 Deed Restricted Units 7.24 Use Permitted MOBILITY AND CONNECTIVITY - Bicycle and Pedestrian Paths YES NO NIA AEC STAFF COMMENTS CODE SECTION•.REQUIREMENT Bicycle/pedestrian paths are designed with 7.28.040(e) adequate widths, sight lines and appropriate lighting. Public sidewalks are located along perimeter 7.28.040(e)(3) streets. There a continuous, internal pedestrian walkway 7.28.040(e)(4) provided from the perimeter public sidewalks to the princi al buildings entrances. 7.28.040(e)(5) Adequate bike parking facilities are provided. 7.28.040(e)(6) Bicycle paths constructed in public right of way meet TOA Standards. 7.28.040(e)(7) Bicycle paths in private communities will be CODE SECTION•D • NOCOMMENTS The proposed new subdivision street circulation maintained by the HOA. 7.28.040(f)(2)(i) plan provides multiple connections to the Bicycle/pedestrian paths connect all adjacent existing Town street network. 7.28.040(e)(8) developments, neighborhoods, and typical A cul de sac or dead-end street has been used destinations (schools, public trails, rec facilities, 7.28.040(f)(2)(ii)(A) due constraints such as existing topo, natural etc . features or vehicle safety. 7.28.040(e)(9) Location of paths takes into consideration A cul-de sac is not proposed for existing travel patterns. 7.28.040(f)(2)(ii)(A) commercial/industrial uses. 7.28.040(e)(1 0 Sidewalks are not located in areas prone to ice. MOBILITY AND CONNECTIVITY - Vehicle Circulation CODE SECTION•D • NOCOMMENTS The proposed new subdivision street circulation 7.28.040(f)(2)(i) plan provides multiple connections to the existing Town street network. A cul de sac or dead-end street has been used 7.28.040(f)(2)(ii)(A) due constraints such as existing topo, natural features or vehicle safety. A cul-de sac is not proposed for 7.28.040(f)(2)(ii)(A) commercial/industrial uses. All permanent dead end streets have been 7.28.040(f)(2)(ii)(B) designed as -cul de -sacs and extend no further than 1000 linear feet. 7.28.040(f)(2)(ii)(C) Proposed cul-de-sac conforms to Fire Code and has been approved by Fire District. Sir 7.28.040 f 2 ii D No half streets are proposed. A pedestrian access easement has been 7.28.040(f)(2)(ii)(E) provided (10 ft wide), between the cul-de-sac and the closest adjacent street or sidewalk. The arrangement of streets in a development provide for the alignment and continuation of 7.28.040(f)(3)(i) existing of proposed streets. Traffic calming measures shall be integrated into the development to mitigate the impact of future "cut -through) traffic. LANDSCAPE STANDARDS CODE SECTION•. Street ROW shall extend to or along adjoining NOCOMMENTS 7.28.050(d) property boundaries so that a roadway 7.28.040(f)(3)(ii) connection of street stub shall be provided for ever 1,500 feet. 7.28.050(e) Street and sidewalk connections shall be made 7.28.040(f)(3)(iii) between neighborhood commercial and residential. LANDSCAPE STANDARDS CODE SECTION•. • NOCOMMENTS 7.28.050(d) If required does the landscape buffer meet code requirements. Does the application provide the necessary 7.28.050(e) Landscape Units at a minimum of 1 unit per 50 square feet of landscaped area. Is perimeter parking lot landscaping provided at 7.28.050(f)(1) a minimum width of 6 feet and 1.2 landscape units per lineal foot. Is an internal landscape strip provided for every 7.28.050(f)(2) other row of double row parking, when more than 50 spaces are provided. 7.28.050(f)(4) Does the internal landscaping island meet the code's design requirements. 7.28.050(f)(5) Does the internal landscaping strip meet the code's design requirements. Parking Lot Landscaping in TC District. 7.28.050(f)(6) Does the proposed landscaping meet the code requirements. 7.28.050(g) Does the landscape plan respond to minimum sight distance triangle requirements. 7.28.050(h)(1) Existing native vegetation and mature trees I I have been preserved. No trees or vegetation have been removed (except for noxious or non-native) outside 7.28.050(h)(1)(i) designated site disturbance areas on lots greater than '/2 acre in the RL, RD and RM zone districts. All native landscaping has been kept in its 7.28.050(h)(1)(iii) native state. 7.28.050(h)(1)(iv) Significant Trees and vegetation that have been • N/A AEC STAFF COMMENTS 7.28.060(b)(1) removed from the site has been replaced. 7.28.050(h)(1)(iv)(C) The location of Protective Construction Fencing has been identified on the plans. 7.28.050(h)(2) Proposed plant materials' have been specified on the plans 7.28.050(h)(3) Noxious Vegetation has been identified for properties removal Temporary installations of gas/oil tanks are 7.28.050(h)(4) Irrigation Plan is included on the Landscape 7.28.060(b)(4) screened from public ROW and/or neighboring Plan. properties. SCREENING STANDARDS CODE SECTION•. • N/A AEC STAFF COMMENTS 7.28.060(b)(1) All outdoor refuse and recycling receptacles are screened All antennas are screened from view from an 7.28.060(b)(2) public ROW or neighboring property Satellite dishes are screened from neighboring 7.28.060(b)(3) properties Temporary installations of gas/oil tanks are 7.28.060(b)(4) screened from public ROW and/or neighboring properties. Mechanical equipment is screened from public 7.28.060(d) ROW and/or neighboring properties by a parapet wall or similar feature that is an integral part of the building's architectural design. Load and service areas are in the rear, side or 7.28.060(e) inside of building, not visible from public ROW or adjacent residential uses. 7.28.060(f) Outdoor storage areas are screen with approved materials. 7.28.060(g) Shopping carts are stored inside the building. Shopping cart corrals are not plastic. Dumpsters are screened with 6 fit masonry wall 7.28.060(h) or wooden fence not visible for public ROW or nei hboring property. 7.28.060(i)(1) Plant materials are used to screen utility boxes 7.28.060 i 2 No fence, wall or hedge is tall than 6 ft RETAINING WALLS • CODE SECTION•D • NOCOMMENTS 7.28.070(b)(1) Retaining walls are utilized because finished Wildridge fence does not delineate the grades cannot meet Code standards property boundaries, is less than 4 ft in height, Walls over 4 ft high are designed with a series of split rail with no more than 2 rails, does not 7.28.070(b)(2) terracing. The width of terrace is at least 5 ft. delineate an area > 2,000 sf, and does not Retaining walls over 7 ft in height have been 7.28.080(b)(1) negatively affect wildlife migration. Multi -family 7.28.070(b)(3) approved by PZC fence is integrated into overall design of the 7.28.070(b)(4) Wall material is compatible with site and property. Duplex fence received approval from buildings on site adjoining property and fence is integrated into Walls over 4 ft high have been structurally overall design of the property. 7.28.070(b)(5) designed and certified by Colo licensed Walls and fences are architecturally compatible engineer and approved by Town Engineer. 7.28.080(b)(2)(i) with the style, materials, color of primary FENCES CODE SECTION•. • NOCOMMENTS Wildridge fence does not delineate the property boundaries, is less than 4 ft in height, split rail with no more than 2 rails, does not delineate an area > 2,000 sf, and does not 7.28.080(b)(1) negatively affect wildlife migration. Multi -family fence is integrated into overall design of the property. Duplex fence received approval from adjoining property and fence is integrated into overall design of the property. Walls and fences are architecturally compatible 7.28.080(b)(2)(i) with the style, materials, color of primary building s). Fences and walls are not greater than 50 ft in 7.28.080(b)(2)(i) solid, unbroken expanse length. 7.28.080 b 2 ii A Fences material is compliant with Code 7.28.080(b)(2)(ii)(B) Fences in front yard is at least 50% open. Material has been approved by Director. 7.28.080(b)(2)(ii)(C) Solid fences have been designed to meet Building Code wind design criteria. 7.28.080(b)(2)(iii) Security fencing (razor , barbed wire or electric charge) are prohibited. 7.28.080(b)(2)(iv) Fence conforms to height limits. RESIDENTIAL DESIGN STANDARDS - Townhouse Design RESIDENTIAL DESIGN STANDARDS - Multi Family Buildings CODE SECTION.. • NOCOMMENTS Units with street frontage have individual 7.28.090(h)(1) Buildings are oriented parallel to public street 7.28.090(g)(1)(ii) ground -related entries accessible from the or to the neighboring internal streets. street. Enclosed rear yards backing up to the Site plan demonstrate a unified, organized street are not proposed. 7.28.090(h)(1)(i)(A) design that incorporates open space with solar Individual pedestrian entrances are exposure, (e.g., interior courtyards or on-site 7.28.090(g)(1)(iii) emphasized over garage entrances with trellis, 7.28.090(h)(1)(i)(B) Walkways connect the entries of each building. enclosed porch or other architectural feature. Building served by a private internal roadway r 7.28.090(g)(2) has driveways that are limited in depth to de- em hasize vehicular access. 7.28.090(g)(3) Project with at least 6 units has provided 400 sf of private common area for each unit. The primary face of each building is design so that it is evident where the units begin and end 7.28.090(g)(4)(i) through subtly varying the offsetting of building walls, material choices, parapet height and color. Building has achieved balance between repetition and variety by employing modulation 7.28.090(g)(4)(ii) techniques on individual units, such as changing rooflines, building articulation and windows. RESIDENTIAL DESIGN STANDARDS - Multi Family Buildings CODE SECTION.. • NOCOMMENTS 7.28.090(h)(1) Buildings are oriented parallel to public street or to the neighboring internal streets. Site plan demonstrate a unified, organized 7.28.090(h)(1)(i)(A) design that incorporates open space with solar exposure, (e.g., interior courtyards or on-site natural areas) as unifying elements. 7.28.090(h)(1)(i)(B) Walkways connect the entries of each building. C 7.28.090(h)(2) All ground floor units in a building with 6 or more units are provided with a patio directly accessible from units. All units above ground floor are provided with balconies. -family CODE SECTION•. • • N/A AEC STAFF COMMENTS Projects with at least 6 units have provided 400 Garage entries, carports, parking areas, and/or sf of private common area for each unit. Parking structures are internalized in building 7.28.090(h)(3) Covered balconies, porches, decks or patios groupings or oriented away from street have been used to meet 50% of this frontage. requirement. Parking areas and freestanding parking Buildings have been designed with human structures do not occupy more than thirty scale, interest and variety, by providing percent (30%) of each perimeter public street 7.28.090(h)(4) changes in vertical and/or horizontal frontage.. articulation, fenestration, building materials, Above -grade parking structures that are visible architectural style, and/or roof design. from perimeter public streets are sited so that RESIDENTIAL PARKING LOCATION AND LAYOUT - Multi -family CODE SECTION•. • • N/A AEC STAFF COMMENTS Garage entries, carports, parking areas, and/or 7.28.090(i)(1)(i) Parking structures are internalized in building groupings or oriented away from street frontage. Parking areas and freestanding parking structures do not occupy more than thirty 7.28.090(i)(1)(ii) percent (30%) of each perimeter public street frontage.. Above -grade parking structures that are visible from perimeter public streets are sited so that 7.28.090(i)(1)(iii) the narrow end of the parking structure is er endicular to the perimeter street. Detached garages and carports incorporate 7.28.090(i)(1)(iv) compatible materials, scale, colors, architectural details, and roof slopes similar to those of the primary buildings. Rear walls of detached garages over forty (40) feet in length that back onto the perimeter 7.28.090(i)(1)(v) street or adjacent property lines are articulated with window openings or other similar technique. DEVELOPMENT REVIEW CHECKLISTS — MIXED-USE, COMMERCIAL, & NON-RESIDENTIAL ZONE DISTRICT STANDARDS Date Zone District: Lot: Subdivision: This checklist is for the sole purpose of assisting the applicant in preparation of a development plan application. The applicant should refer to the Avon Development Code and Application Submittal Requirements to complete a development plan application. This checklist is not an official part of the Avon Development Code and should in no way be considered a replacement for the Code or instructions contained with the application. Code i Section 7.20 Code Requirement Minimum Lot Size Comply Not .Applicable Not Staff Comments 7.20 Minimum Lot Width NO NIA AEC STAFF COMMENTS 7.20 Maximum Lot Coverage Bicycle/pedestrian paths are designed with 7.20 Minimum Landscape Area 7.28.040(e) adequate widths, sight lines and appropriate § 7.20 Building Setbacks lighting. § 7.20 Max Building Height 7.20 Max Number of Dwelling Units 7.28.040(e)(3) § 7.20.100 0 Deed Restricted Units 7.24 Use Permitted MOBILITY AND CONNECTIVITY - Bicycle and Pedestrian Paths YES NO NIA AEC STAFF COMMENTS CODE SECTION•.REQUIREMENT Bicycle/pedestrian paths are designed with 7.28.040(e) adequate widths, sight lines and appropriate lighting. Public sidewalks are located along perimeter 7.28.040(e)(3) streets. There a continuous, internal pedestrian walkway 7.28.040(e)(4) provided from the perimeter public sidewalks to the princi al buildings entrances. 7.28.040(e)(5) Adequate bike parking facilities are provided. 7.28.040(e)(6) Bicycle paths constructed in public right of way meet TOA Standards. 7.28.040(e)(7) Bicycle paths in private communities will be CODE SECTION•D • NOCOMMENTS The proposed new subdivision street circulation maintained by the HOA. 7.28.040(f)(2)(i) plan provides multiple connections to the Bicycle/pedestrian paths connect all adjacent existing Town street network. 7.28.040(e)(8) developments, neighborhoods, and typical A cul de sac or dead-end street has been used destinations (schools, public trails, rec facilities, 7.28.040(f)(2)(ii)(A) due constraints such as existing topo, natural etc . features or vehicle safety. 7.28.040(e)(9) Location of paths takes into consideration A cul-de sac is not proposed for existing travel patterns. 7.28.040(f)(2)(ii)(A) commercial/industrial uses. 7.28.040(e)(1 0 Sidewalks are not located in areas prone to ice. MOBILITY AND CONNECTIVITY - Vehicle Circulation CODE SECTION•D • NOCOMMENTS The proposed new subdivision street circulation 7.28.040(f)(2)(i) plan provides multiple connections to the existing Town street network. A cul de sac or dead-end street has been used 7.28.040(f)(2)(ii)(A) due constraints such as existing topo, natural features or vehicle safety. A cul-de sac is not proposed for 7.28.040(f)(2)(ii)(A) commercial/industrial uses. All permanent dead end streets have been 7.28.040(f)(2)(ii)(B) designed as -cul de -sacs and extend no further than 1000 linear feet. 7.28.040(f)(2)(ii)(C) Proposed cul-de-sac conforms to Fire Code and has been approved by Fire District. Sir 7.28.040 f 2 ii D No half streets are proposed. A pedestrian access easement has been 7.28.040(f)(2)(ii)(E) provided (10 ft wide), between the cul-de-sac and the closest adjacent street or sidewalk. The arrangement of streets in a development provide for the alignment and continuation of 7.28.040(f)(3)(i) existing of proposed streets. Traffic calming measures shall be integrated into the development to mitigate the impact of future "cut -through) traffic. LANDSCAPE STANDARDS CODE SECTION•. Street ROW shall extend to or along adjoining NOCOMMENTS 7.28.050(d) property boundaries so that a roadway 7.28.040(f)(3)(ii) connection of street stub shall be provided for ever 1,500 feet. 7.28.050(e) Street and sidewalk connections shall be made 7.28.040(f)(3)(iii) between neighborhood commercial and residential. LANDSCAPE STANDARDS CODE SECTION•. • NOCOMMENTS 7.28.050(d) If required does the landscape buffer meet code requirements. Does the application provide the necessary 7.28.050(e) Landscape Units at a minimum of 1 unit per 50 square feet of landscaped area. Is perimeter parking lot landscaping provided at 7.28.050(f)(1) a minimum width of 6 feet and 1.2 landscape units per lineal foot. Is an internal landscape strip provided for every 7.28.050(f)(2) other row of double row parking, when more than 50 spaces are provided. 7.28.050(f)(4) Does the internal landscaping island meet the code's design requirements. 7.28.050(f)(5) Does the internal landscaping strip meet the code's design requirements. Parking Lot Landscaping in TC District. 7.28.050(f)(6) Does the proposed landscaping meet the code requirements. 7.28.050(g) Does the landscape plan respond to minimum sight distance triangle requirements. 7.28.050(h)(1) Existing native vegetation and mature trees I I have been preserved. No trees or vegetation have been removed (except for noxious or non-native) outside 7.28.050(h)(1)(i) designated site disturbance areas on lots greater than '/2 acre in the RL, RD and RM zone districts. All native landscaping has been kept in its 7.28.050(h)(1)(iii) native state. 7.28.050(h)(1)(iv) Significant Trees and vegetation that have been • N/A AEC STAFF COMMENTS 7.28.060(b)(1) removed from the site has been replaced. 7.28.050(h)(1)(iv)(C) The location of Protective Construction Fencing has been identified on the plans. 7.28.050(h)(2) Proposed plant materials' have been specified on the plans 7.28.050(h)(3) Noxious Vegetation has been identified for properties removal Temporary installations of gas/oil tanks are 7.28.050(h)(4) Irrigation Plan is included on the Landscape 7.28.060(b)(4) screened from public ROW and/or neighboring Plan. properties. SCREENING STANDARDS CODE SECTION•. • N/A AEC STAFF COMMENTS 7.28.060(b)(1) All outdoor refuse and recycling receptacles are screened All antennas are screened from view from an 7.28.060(b)(2) public ROW or neighboring property Satellite dishes are screened from neighboring 7.28.060(b)(3) properties Temporary installations of gas/oil tanks are 7.28.060(b)(4) screened from public ROW and/or neighboring properties. Mechanical equipment is screened from public 7.28.060(d) ROW and/or neighboring properties by a parapet wall or similar feature that is an integral part of the building's architectural design. Load and service areas are in the rear, side or 7.28.060(e) inside of building, not visible from public ROW or adjacent residential uses. 7.28.060(f) Outdoor storage areas are screen with approved materials. 7.28.060(g) Shopping carts are stored inside the building. Shopping cart corrals are not plastic. Dumpsters are screened with 6 fit masonry wall 7.28.060(h) or wooden fence not visible for public ROW or nei hboring property. 7.28.060(i)(1) Plant materials are used to screen utility boxes 7.28.060 i 2 No fence, wall or hedge is tall than 6 ft RETAINING WALLS • CODE SECTION•D • NOCOMMENTS 7.28.070(b)(1) Retaining walls are utilized because finished Wildridge fence does not delineate the grades cannot meet Code standards property boundaries, is less than 4 ft in height, Walls over 4 ft high are designed with a series of split rail with no more than 2 rails, does not 7.28.070(b)(2) terracing. The width of terrace is at least 5 ft. delineate an area > 2,000 sf, and does not Retaining walls over 7 ft in height have been 7.28.080(b)(1) negatively affect wildlife migration. Multi -family 7.28.070(b)(3) approved by PZC fence is integrated into overall design of the 7.28.070(b)(4) Wall material is compatible with site and property. Duplex fence received approval from buildings on site adjoining property and fence is integrated into Walls over 4 ft high have been structurally overall design of the property. 7.28.070(b)(5) designed and certified by Colo licensed Walls and fences are architecturally compatible engineer and approved by Town Engineer. 7.28.080(b)(2)(i) with the style, materials, color of primary FENCES CODE SECTION•. • NOCOMMENTS Wildridge fence does not delineate the property boundaries, is less than 4 ft in height, split rail with no more than 2 rails, does not delineate an area > 2,000 sf, and does not 7.28.080(b)(1) negatively affect wildlife migration. Multi -family fence is integrated into overall design of the property. Duplex fence received approval from adjoining property and fence is integrated into overall design of the property. Walls and fences are architecturally compatible 7.28.080(b)(2)(i) with the style, materials, color of primary building s). Fences and walls are not greater than 50 ft in 7.28.080(b)(2)(i) solid, unbroken expanse length. 7.28.080 b 2 ii A Fences material is compliant with Code 7.28.080(b)(2)(ii)(B) Fences in front yard is at least 50% open. Material has been approved by Director. 7.28.080(b)(2)(ii)(C) Solid fences have been designed to meet Building Code wind design criteria. 7.28.080(b)(2)(iii) Security fencing (razor , barbed wire or electric charge) are prohibited. 7.28.080(b)(2)(iv) Fence conforms to height limits. MIXED USE AND NON RESIDENTIAL - Site Layout and Design (Building Orientation, Outparcels, Parking, Common Spaces) CODE SECTION•. • NOCOMMENTS 7.28.0900)(3)(i)(A) Building(s) re -enforce street edges and create pedestrian scaled open space. _ Building fronts and entries are oriented to 7.28.0900)(3)(i)(B) street or public plaza 7.28.0900)(4)(ii) Ground floor of new building is at grade or 7.28.0900)(3)(i)(B) elevated above grade. Outparcels and buildings define street edges, 7.28.0900)(3)(ii) entry points and spaces for gathering or seating between buildings. Space between buildings includes pedestrian amenity. 7.28.0900)(3)(iii) Parking is located behind building, underground or at interior of lot. Project include on —site, indoor and outdoor 7.28.0900)(3)(iv) common spaces or community amenities as visible, accessible focal points. Common spaces have been designed to 7.28.0900)(3)(iv)(C) minimize conflict with snow management operations and ensure pedestrian safety. MIXED USE AND CODE SECTION•D NON RESIDENTIAL - Building Layout and • Design NOCOMMENTS Building Design. Building design is 7.28.0900)(4)(i) appropriate to the site and a positive element in the architectural character of Avon. _ Four-sided Design. The rear and side elevations of the new building that is visible 7.28.0900)(4)(ii) from public spaces and adjacent buildings is designed with equal care and quality as the front or principal face. All buildings within the development, including freestanding and accessory buildings, are 7.28.0900)(4)(iii)(A) organized around an architectural theme in terms of the character, materials, texture, color, and scale of building. Mixed-Use Buildings in Town Core To encourage appropriate commercial and mixed- use development in Town Core any portion of a new mixed-used building with street frontage 7.28.0900)(4)(iv) floor area located on E. Beaver Creek Boulevard, Lettuce Shed Lane, Benchmark Road, or Main Street must be occupied by retail, personal service and restaurant uses, as listed in Table 7.24-1 Scale and Massing. Form and massing of 7.28.0900)(4)(v) the building provides a human scale to adjacent streets, pedestrian walkways, plazas, or other public spaces. Buildings greater than two stories or 30 ft in height are designed to reduce apparent mass, 7.28.0900)(4)(v)(B) and visually anchor the building to the site by including a clearly identifiable base, body, and top, with horizontal elements separating these components Where primary building walls exceed 3 stories or 45 ft in height, as measured from finished grade to the underside of the eaves, building form steps back at least 8 feet in depth and generally occur between 12 t and 45 ft above 7.28.0900)(4)(v)(D) the finished grade. OR Due to large variations in topography or other unique site constraints, alternatives to the building massing and height configurations required have been approved. Development Transition. The proposed development relates to neighboring buildings 7.28.0900)(4)(vi) using approved development transition techniques.. Storefronts and Pedestrian Entrances. The first floor of the proposed development provides: a pedestrian friendly environment, with human -scale and natural building materials. Extensive storefront windows for 7.28.0900)(4)(vii)(A- display and views into the business; and B) access directly from adjacent sidewalks OR Transparency is in conflict with internal functions of the building, SO other means have been used to activate the street facing facades Building front entrances are located at intervals 7.28.0900)(4)(vii)(C) of 32 ft maximum. If applicable, primary access to retail spaces 7.28.0900)(4)(vii)(D) on Benchmark Road, Main Street, and W. Beaver Creek Boulevard, is from the sidewalk Building provides direct access to ground floor 7.28.0900)(4)(vii)(E) commercial space from the street. The principal building entrance faces an adjacent public street, public plaza, or primary public walkway. 7.28.0900)(4)(vii)(E)( OR 1-2) The principal entrance does not face the principal street, but the entrance is connected to the street and adjacent parking areas with a sidewalk. Building entrance is welcoming to pedestrian and easily identifiable and accessible from 7.28.0900)(4)(vii)(F) streets and sidewalks. Primary entries are clearly visible from the street and accentuated from the overall building fagade. Building Materials. The selection of building materials, colors, architectural elements, and 7.28.0900)(4)(viii) finishes contribute to the building's durability, usefulness, and compatibility. Roofs. Roofs use dormers to break up 7.28.0900)(4)(ix) expansive roofs and add visual interest All primary roofs and secondary shed roofs 7.28.0900)(4)(ix)(B) shall have pitches of no less than four -to - twelve 4:12 . Roof overhang length(s) meet Code 7.28.0900)(4)(ix)(C) requirements Flat roofs are limited to areas to conceal 7.28.0900)(4)(ix)(D) mechanical space or for architectural effect. MIXED USE AND NON RESIDENTIAL - Parking Structures CODE SECTION•. Roofs are varied and articulated but will not •COMMENTS 7.28.0900)(4)(ix)(E) result in excess ice build up 7.28.090(j)(5)(i) Roofs are proportional to the height and scale of the various building elevations. The primary 7.28.090(j)(4)(ix)(F) roof(s) and upper portion of the walls are articulated so as to minimize their visual impact on surrounding properties. 7.28.0900)(5)(iii) Roof Material consistent with Code 7.28.0900)(4)(ix)(G) requirements. Windows. Openings contribute to the image 7.28.0900)(4)(x)(A) and form of new building. Buildings located on Main Street, Benchmark Road, Lettuce Shed Lane, o E. Beaver Creek Boulevard - Storefront 7.28.0900)(4)(x)(B) incorporates a large display window or windows of clear glass, bulkheads, recessed entries, transom windows, and suitable locations for signs at ground levels. Upper floors are differentiated from ground floor through the use of more solid areas then voids and with smaller vertically oriented 7.28.0900)(4)(x)(C) windows in a regular pattern. Windows reflect a rhythm, scale and proportion compatible with the overall building design. Window materials and finishes consistent with 7.28.0900)(4)(x)(D) Code requirements Decks and Balconies are located to take advantage of solar exposure, and are used in 7.28.0900)(4)(xi) combination with bay windows and other exterior projections. MIXED USE AND NON RESIDENTIAL - Parking Structures CODE SECTION•. • •COMMENTS Ground floor of parking structures is wrapped 7.28.090(j)(5)(i) with retail storefronts or residential uses along those facades adjacent to or most visible from major pedestrian walkways. Exposed portions of the underground parking structures are faced with base -level materials 7.28.0900)(5)(iii) used on the active portions of the building above the parking structure. 7.28.0900)(5)(iv) Facades of single -use parking garage have been articulated with 3 or more architectural features. The parking structures is designed to significantly screen or buffer views of parked 7.28.0900)(5)(v) cars from surrounding properties through the use of architectural screens and other features. Parking structure provides pedestrian access to adjacent public walkways, public buildings, 7.28.0900)(5)(vi) and/or public plazas without using major access points along the primary street network 10 DEVELOPMENT REVIEW CHECKLISTS - NATURAL RESOURCE PROTECTION ZONE DISTRICT STANDARDS Date Zone District: Lot: Subdivision: This checklist is for the sole purpose of assisting the applicant in preparation of a development plan application. The applicant should refer to the Avon Development Code and Application Submittal Requirements to complete a development plan application. This checklist is not an official part of the Avon Development Code and should in no way be considered a replacement for the Code or instructions contained with the application. Steep Slopes CODE SECTION•. •COMMENTS Steep Slopes. Project is a new subdivision, 7.28.100(a)(2) PUD or zoning amendment that contains lots with naturally occurring slopes greater than 30%. Development is not located on steep slopes of 7.28.100(a)(3)(iii) 40% or greater and areas greater than 40% slope remain as natural open space. The Lot contains a natural slope area greater than 30% and larger than 2,500 sf and is a 7.28.100(a)(3)(iv) minimum of 1 acre in size with a minimum street frontage of 150 linear feet. Lot has not been mass -graded to avoid this section. The original, natural grade o f the Lot has not been raised or lowered more than 6 feet at 7.28.100(a)(3)(v) any point for construction of any structure or improvement. Graded or Filled Man -Made Cut man-made surfaces or slopes do not exceed a slope 7.28.100(a)(3)(vi)(A- between twenty-five percent (25%) and fifty C) percent (50%) OR Town Engineer has approved alternative. 7.28.100(a)(3)(vi)(D) Cut exposed bedrock is proposed to be sculpted to appear natural. Sheet notes indicate that all cut, filled, and 7.28. 1 00(a)(3)(vi)(E) graded slopes shall be re-contoured to the natural, varied contour of the surrounding terrain 7.28.100(a)(3)(vii)(A) Natural Design. Sharp angles have been rounded off. Slopes provide transition from graded areas 7.28.100(a)(3)(vi)(B) into natural areas by varying grade both up- slope and across the slope. 7.28.100(a)(3)(vi)(C) Natural grade at the lot line has been maintained. Separate Pads. The project does not cut and 7.28.100(a)(3)(viii)(A) grade to create benches or pads for buildings or structures. Accessory structures and buildings (other than 7.28.100(a)(3)(viii)(B) garage) are not located on separate building pads except for areas with slopes 20% or less. Parking Areas. Parking areas should be constructed on multiple levels and follow 7.28.100(a)(3)(ix) natural contours as necessary to minimize cut and fill. 7.28.100(a)(3)(x) Retaining walls have been used to minimize cut and fill. 7.28.100(a)(3)(xi)(A) Natural Drainage Patterns. Site plan does not change natural drainage patterns. Natural surface drainage patterns have been preserved OR 7.28.100(a)(3)(xi)(B) Natural drainage patterns are modified and appropriate stabilization techniques have been employed. Development has mitigated all negative or 7.28.100(a)(3)(xi)(C) adverse drainage impacts on adjacent and surrounding sites Standard erosion control methods shall be used during construction to protect water 7.28.100(a)(3)(xi)(D) quality, control drainage, and reduce soil erosion Revegatation. Landscape plan indicated that 7.28.100(a)(3)(xii) areas exposed during construction will be re ve atated. 7.28.100(a)(3)(xiii)(A) Streets, Roads, General Site Access. Project includes at least three units. 7.28.100(a)(3)(xiii)(B) Access to the development site is by road, street, or private access road Streets, roads, private access roads, and 7.28.100(a)(3)(xiii)(C) other vehicular routes comply with all requirements of the Town of Avon Streets, roads, private access roads, and other vehicular routes do not cross slopes between 30% and 50%. 7.28.100(a)(3)(xiii)(D) OR Roads that do cross slopes between 30 and 50% will require PZC approval. 7.28.100(a)(3)(xiii)(E) Under no circumstances do the proposed roads cross slopes greater than 50 percent.. Streets, roads, private access roads, and 7.28.100(a)(3)(xiii)(F) other vehicular routes have, to the maximum extent feasible, follow natural contour lines. DRIVEWAY ACCESS Grading for streets, roads, private access roads, and other vehicular routes has been limited to the asphalt portion of the right-of-way, plus up to an additional ten (10) feet on either side of the asphalt as needed. OR 7.28.100(a)(3)(xiii)(G) Access is on slopes in excess of twenty percent (25%), so only the asphalt portion of the right-of-way has been a graded plus the minimum area required for any necessary curb, gutter, or sidewalk improvements. The remainder of the access right-of-way has been left undisturbed to the maximum extent feasible. Roads, other vehicular routes, or trails ARE/ARE NOT required to provide access or maintain existing access to adjacent lands for 7.28.100(a)(3)(xiii)(H) vehicles, pedestrians, emergency services, and essential service and maintenance equipment. Stream, River, Waterbodv and Wetlands CODE SECTION•D • •COMMENTS Nondegradation. The applicant has provided evidence and plans to ensure that the proposed development does not result in 7.28.100(b)(3) reasonably avoidable degradation of streams, rivers, or wetlands. This condition applies to both the development activities and the ultimate use of the land Riparian buffers have been established from the mean annual high water line (AHWL), as 7.28.100(b)(4) determined by the Town Engineer, on each side of the perennial stream or river, water body, or wetland. The Riparian Protection Buffer is thirty (30) 7.28.100(b)(5)(ii) feet from the AHWL. 7.28.100(b)(5)(iii) The Director HAS/HAS NOT requested a specific survey of the extent of riparian zone. Permitted Uses and Activities. Except as required to accommodate a permitted use or activity, all existing vegetation within the 7.28.100(b)(5)(iv) riparian protection buffer has been preserved and, where necessary to provide adequate screening or to repair damaged riparian areas, supplemented with additional native or adapted planting and landscaping. The Uses and Management Activities in the 7.28. 1 00(b)(5)(v) riparian protection buffer comply with the Code. 7.28.100(b)(5)(v)(H) No disturbance of land has been proposed within riparian buffers. A proposed bridge over the riparian feature and within the riparian buffer has been planned and 7.28.100(b)(5)(v)(1) constructed so as to minimize impacts on the riparian feature and minimizes disturbance and removal of vegetation. Grading, Erosions Prevention and Sedimentation Control CODE SECTION•D. •STAFF Ephemeral Streams. Development is not Applicability. This section shall apply to any disturbance within one hundred (100) feet of a stream, all grading unless waived by the Town Engineer, all residential development disturbing more than one-quarter (1/4) acre, all mixed use, commercial, and industrial development and all proposed subdivisions and PVDs No grading has occurred without a permit located within the channel of an ephemeral 7.28.100(c)(3) issued by Town Engineer stream, as defined by its AHWL Grading plans conformances with the OR 7.28.100(c)(3)(i) 7.28.100(b)(6) The Town Council has granted waivers or Erosion Control Standards Construction modifications from this prohibition upon a 7.28.100(c)(4)(i) activities such as clearing, grading, road finding that the development will have no construction and utilities installation have been adverse environmental impacts, or that such phased to minimize soil exposure. impacts will be substantially mitigated Grading, Erosions Prevention and Sedimentation Control CODE SECTION•D. •STAFF COMMENTS Applicability. This section shall apply to any disturbance within one hundred (100) feet of a stream, all grading unless waived by the Town Engineer, all residential development disturbing more than one-quarter (1/4) acre, all mixed use, commercial, and industrial development and all proposed subdivisions and PVDs No grading has occurred without a permit 7.28.100(c)(3) issued by Town Engineer Grading plans conformances with the 7.28.100(c)(3)(i) International Building Code IBC Erosion Control Standards Construction 7.28.100(c)(4)(i) activities such as clearing, grading, road construction and utilities installation have been phased to minimize soil exposure. Soil Stabilization. All disturbed areas and soil stockpiles have been surface roughened, mulched, seeded and mulched, or otherwise protected from erosive forces if they are to 7.28.100(c)(4)(ii) remain exposed and inactive for periods longer than fourteen (14) days or if soil will be exposed during winter. On slopes greater than 20% or within 50 feet of any water body, exposed soils will be hydro -mulched or covered with nets or mats 7.28.100(c)(4)(iii) Excavation. Excavation for footings and foundations have been minimized. Cut and Fill Slopes. Permanent vegetation has been used as to stabilize cut and fill areas where slopes are less than or equal to two -to - one (2:1). On cut and fill slopes steeper than two -to -one 7.28. 1 00(c)(4)(iv) (2:1), stabilization has been attained by utilizing retaining walls, rock walls, up slope runoff diversions, slope drains, or other measures appropriate for the specific situation. Rockfall mitigation has been proposed for slopes steeper than two -to -one 2:1 . Construction in or Adjacent to a Water Body. Construction in or directly adjacent to 7.28.100(c)(4)(v) any water body, such as culvert or bridge installation, includes bed and bank stabilization. Channels and Ditches. New or re-routed irrigation ditches, receiving channels, and 7.28. 1 00(c)(4)(vi) streams have been protected so that flows from the site do not cause erosion and flooding. Stormwater Runoff. Stormwater runoff flows has been managed to minimize erosion and 7.28.100(c)(4)(vii) sediment transport. Concentrated flows have been diverted away from disturbed slopes. Sediment and Mud Control. Sediment and mud will be controlled and prevented from leaving the construction site by immediate 7.28.100(c)(4)(viii) placement of street base or construction of mud pads in access routes. Mud pads will be least 50 feet in length and comprised of angular rock and/or a wheel washing facility. Contributing drainage area, including off- site area, is greater than one (1) acre: Sediment detention ponds, infiltration devices, and other management practices that store or detain runoff have been used to treat sediment- 7.28.100(c)(4)(ix) containing runoff prior to discharge from the construction site. OR Contributing drainage area is less than one (1) acres: Specific engineered design for sediment trapping facilities is not required. Temporary Sediment Ponds. Temporary sediment ponds that will be removed after successful revegetation of the site are designed to safely detain and release all storms up to and including the twenty-five (25) year, twenty-four (24) hour storm at its historic, 7.28.100(c)(4)(x) pre -development rate of release. OR Ponds that will be left as permanent facilities have one hundred (100) year flood capacity and meet dam and diversion requirements of the state engineer. Construction De -Watering. All construction 7.28. 1 00(c)(4)(xi) de -watering activities conform with the state's construction de -watering permit requirements. Inspection and Maintenance. The applicant 7.28.100(c)(4)(xii) shall inspect all erosion and sediment control devices monthly. Permanent Revegetation. Any disturbed area that is not built upon for a period of one (1) 7.28.100(c)(4)(xiii) year or longer will be revegetated pursuant to §7.28.100(c)(6), Revegetation Plan Erosion and Sediment Control Plan. An applicant for any development listed in 7.28.100(c)(5) §7.28.100(c)(2), Applicability, has submitted an erosion and sediment control plan prepared by a qualified professional. Revegation Plan. A revegetation and land reclamation plan prepared and certified by a 7.28.100(c)(6) qualified professional IS/IS NOT required by the Director for review and approval. Geologic Hazard Areas CODE SECTION•D• NOCOMMENTS Applicability. After November 16, 2010, new development is prohibited within geologic hazard areas. In the event that there is no hazard -free area on a platted site, then development shall be restricted to the least hazardous area of a site, as approved by the Director based on a study by a qualified engineer licensed b the State of Colorado. _ Minimum Mitigations Standards: A. structural geologic hazard defenses that are designed by a certified engineer to withstand the impact forces. B. Utility lines or pipes that 7.28. 1 00(e)(3)(i) cross a geologic hazard area have been buried C. Clear -cutting or other large-scale removal of vegetation is prohibited D. Extractive operations have an approved program of eolo is control and defense measures. Surface pipes, poles, or towers for suspended 7.28.100(e)(3)(ii) transmission lines in hazard zones shall be protected _ Warning signs shall be placed along roads and 7.28.100(e)(3)(vi) trails that cross rockfall and avalanche hazard zones. Property owners who develop in geologic hazard areas or obtain driveway access 7.28.100(e)(3)(vii) through geologic hazard areas shall bear the costs of any control measures that may be required to mitigate the hazard Geological Hazard Study. Applicability. A geologic hazard study shall be required for all subdivisions, PUDs, rezonings, and lots containing or may contain geologic hazards as defined by the Development Code Requirements for Preliminary Approval of Study. A. Site specific analysis B. Evaluation 7.28.100(e)(4)(iii) of potentials impacts C. Plan includes building envelopes D. Identification and description of all proposed hazard mitigation and avoidance measures Study has been referred to Colorado 7.28.100(e)(4)(iv) Geological Survey for review and comments. Requirements for Final Approval. The applicant has demonstrated in the final plan or 7.28.100(e)(4)(v) plat how the development complies with all conditions imposed in the preliminary approval. DEVELOPMENT REVIEW CHECKLISTS - ALTERNATIVE ENERGY STANDARDS ZONE DISTRICT STANDARDS Date Zone District: Lot: ly • .'a Subdivision: This checklist is for the sole purpose of assisting the applicant in preparation of a development plan application. The applicant should refer to the Avon Development Code and Application Submittal Requirements to complete a development plan application. This checklist is not an official part of the Avon Development Code and should in no way be considered a replacement for the Code or instructions contained with the application. CODE SECTION•. • NOCOMMENTS Ground -Mounted Solar Collection System System is not located in the front yard between the principal structure and the public right-of- way. System complies with all setback requirements. If located in a residential district, the system does not exceed the greater of 1/2 the footprint of the principal structure or 600 square feet, 7.28. 1 00(g)(2)(i)(A) whichever is less. T If located in a mixed-use and non-residential districts he size of accessory arrays does not exceed 1/2 of the footprint of the principal structure. A ground -mounted system does not exceed ten (10) feet in height. Solar Easements. The property owner has been made aware that it is his/her responsible for negotiating with other property owners in 7.28. 1 00(g)(2)(i)(B) the vicinity for any necessary solar easement and shall record the easement in the Eagle County land records Roof -Mounted Solar Collection System System does not extend more than 2 feet above a pitched roof or 6 feet above a flat roof. With the exception of flat roofs, the system placed on the roof mimics the roof pitch it is attached to. 7.28.100(g)(3)(i)(A) System IS/IS NOT located on an accessory structure. Applicant will provide a structural certification as part of the building permit application. Solar Easements. The property owner has been made aware that it is his/her responsible for negotiating with other property owners in 7.28. 1 00(g)(3)(i)(B) the vicinity for any necessary solar easement and shall record the easement in the Eagle County land records. Small Wind Energy System Setback. The base of the tower is set back from all property lines, public right-of-ways, and public utility lines a distance equal to the total extended height (e.g., if on a roof, roof height plus tower height) plus five (5) feet. OR tower is closer to a property line than its total extended height because the abutting property owner(s) has provided written permission and the installation poses no interference with public utility lines or public road and rail right-of-ways 7.28.100(g)(4)(ii) Sound. Under normal operating conditions, the sound generated by turbine will not exceed (55) dBA (measured at property line). Appearance, Color, and Finish. The turbine and tower will be painted or finished in non - reflective, non -obtrusive color. Clearance. Minimum ground clearance is 15 feet as measured at the lowest point of the arc of the blades. Signage on system is prohibited. Lighting. No illumination unless required by the FAA. Access. Any climbing foot pegs or rungs below 12 feet of a freestanding tower will be removed to prevent unauthorized climbing. Compliance with FAA Regulations. System does not project above any of the imaginary airspace surfaces described in FAR Part 77 of the FAA guidance on airspace protection. Utility Notification. Applicant has provided evidence that the relevant electric utility company has been informed of the customer's intent to install an interconnected customer- owned generator.