Laserfiche WebLink
Municode Page 4 of 4 <br />For every 35 feet of public road frontage, one overstory tree shall be planted on the <br />private property adjacent to the public road right -of -way. <br />b. Topsoil. All exposed ground areas of a site not occupied by building, parking or storage, <br />excluding natural areas that are left undisturbed, shall be covered with six inches of topsoil, as <br />defined in section 117 -1, or an approved alternative as referenced in section 117 -348 <br />c. Sodding and ground cover. All areas not otherwise improved in accordance with approved site <br />plans shall be finished with sod up to the edge of improved streets. Any alternative to the sod <br />requirement shall require city council approval. <br />d. Irrigation. <br />1. All landscaping areas required under this section shall include underground irrigation <br />systems. <br />2. Exceptions include natural areas that are left undisturbed. <br />e. Parking lot landscaping. All parking lots are required to provide internal overstory tree plantings <br />in an effort to shade parking surfaces and provide visual relief. Plantings are required at the <br />following minimum schedule. The planting schedule is established to provide an acceptable <br />number of plantings that may be planted in regular symmetrical patterns or irregular clusters or <br />groupings. <br />1. 1 tree per every ten parking spaces. <br />2. Every overstory tree planting shall be provided with a planting area of 162 square feet. <br />3. Acceptable ground cover materials include sod, mulch, and other natural ground cover. <br />Landscaping rock and plastic underlayment is not allowed. <br />4. All parking lot planting areas shall include underground irrigation systems. <br />f. Bufferyards. This section is intended to be minimum requirements to achieve screening between <br />differing uses with varied intensities and impacts that are not always complementary when <br />adjacent to one another. When a bufferyard is required under this section, the yard space and <br />planting requirements are not to be reduced for other purposes such as future parking and <br />driveways, building expansions, or other activities that are not in keeping with the purposes of <br />buffering and screening. <br />1. Bufferyards are intended to provide additional screening of businesses that are adjacent <br />to residential areas. The following table details the width of the bufferyard along the <br />common adjacent property line. An additional increase of landscape plantings would be <br />required in the bufferyard. That increase is expressed in the table below as a percentage <br />of the total required site landscaping: <br />2. As an alternative method for screening, fences that are 100 percent opaque may be used <br />to mitigate the impacts of businesses that are adjacent to residential areas. Fences shall <br />be subject to the provisions found in all applicable ordinances. When a fence is used for <br />screening purposes, the bufferyard planting requirements may be reduced by ten percent <br />from the stated minimum requirement. <br />(15) Off - street loading: One off - street loading dock /berth shall be provided for the first 10,000 square feet of <br />floor area and one additional dock/berth for each additional 25,000 square feet of floor area. Such <br />loading berth /dock shall be located in the rear or side wall of building. <br />(Code 1978, § 9.20.21; Ord. No. 80 -04, 5 -25 -1980; Ord. No. 86 -2, 8 -25 -1986; Ord. No. 93 -01, 3 -1 -1993; Ord. No. 93 -05, 4 -23- <br />1993; Ord. No. 96 -12, 7 -29 -1996; Ord. No. 03 -21, 8 -25 -2003; Ord. No. 04 -20, 6 -1 -2004; Ord. No. 09 -06, § 2, 4 -28 -2009; Ord. <br />No. 09 -12, § 2, 9 -8 -2009; Ord. No. 10 -04, § 2, 4 -13 -2010) <br />http : //library.municode. com/print. aspx ?clientlD= 14286 &HTMRequest =http %3 a %2f %2flib... 1/5/2012 <br />Existing Adjacent Development <br />Proposed <br />DevelopmentB <br />R -1 <br />R -2 <br />R -3 <br />-1 <br />Bufferyard <br />width <br />increase <br />in <br />plantings <br />required <br />40 ft. <br />30 ft. <br />20 ft. <br />25% <br />20% <br />20% <br />B -2 <br />Bufferyard <br />width <br />increase <br />in <br />plantings <br />required <br />50 ft. <br />40 ft. <br />30 ft. <br />30% <br />25% <br />20% <br />Municode Page 4 of 4 <br />For every 35 feet of public road frontage, one overstory tree shall be planted on the <br />private property adjacent to the public road right -of -way. <br />b. Topsoil. All exposed ground areas of a site not occupied by building, parking or storage, <br />excluding natural areas that are left undisturbed, shall be covered with six inches of topsoil, as <br />defined in section 117 -1, or an approved alternative as referenced in section 117 -348 <br />c. Sodding and ground cover. All areas not otherwise improved in accordance with approved site <br />plans shall be finished with sod up to the edge of improved streets. Any alternative to the sod <br />requirement shall require city council approval. <br />d. Irrigation. <br />1. All landscaping areas required under this section shall include underground irrigation <br />systems. <br />2. Exceptions include natural areas that are left undisturbed. <br />e. Parking lot landscaping. All parking lots are required to provide internal overstory tree plantings <br />in an effort to shade parking surfaces and provide visual relief. Plantings are required at the <br />following minimum schedule. The planting schedule is established to provide an acceptable <br />number of plantings that may be planted in regular symmetrical patterns or irregular clusters or <br />groupings. <br />1. 1 tree per every ten parking spaces. <br />2. Every overstory tree planting shall be provided with a planting area of 162 square feet. <br />3. Acceptable ground cover materials include sod, mulch, and other natural ground cover. <br />Landscaping rock and plastic underlayment is not allowed. <br />4. All parking lot planting areas shall include underground irrigation systems. <br />f. Bufferyards. This section is intended to be minimum requirements to achieve screening between <br />differing uses with varied intensities and impacts that are not always complementary when <br />adjacent to one another. When a bufferyard is required under this section, the yard space and <br />planting requirements are not to be reduced for other purposes such as future parking and <br />driveways, building expansions, or other activities that are not in keeping with the purposes of <br />buffering and screening. <br />1. Bufferyards are intended to provide additional screening of businesses that are adjacent <br />to residential areas. The following table details the width of the bufferyard along the <br />common adjacent property line. An additional increase of landscape plantings would be <br />required in the bufferyard. That increase is expressed in the table below as a percentage <br />of the total required site landscaping: <br />2. As an alternative method for screening, fences that are 100 percent opaque may be used <br />to mitigate the impacts of businesses that are adjacent to residential areas. Fences shall <br />be subject to the provisions found in all applicable ordinances. When a fence is used for <br />screening purposes, the bufferyard planting requirements may be reduced by ten percent <br />from the stated minimum requirement. <br />(15) Off - street loading: One off - street loading dock /berth shall be provided for the first 10,000 square feet of <br />floor area and one additional dock/berth for each additional 25,000 square feet of floor area. Such <br />loading berth /dock shall be located in the rear or side wall of building. <br />(Code 1978, § 9.20.21; Ord. No. 80 -04, 5 -25 -1980; Ord. No. 86 -2, 8 -25 -1986; Ord. No. 93 -01, 3 -1 -1993; Ord. No. 93 -05, 4 -23- <br />1993; Ord. No. 96 -12, 7 -29 -1996; Ord. No. 03 -21, 8 -25 -2003; Ord. No. 04 -20, 6 -1 -2004; Ord. No. 09 -06, § 2, 4 -28 -2009; Ord. <br />No. 09 -12, § 2, 9 -8 -2009; Ord. No. 10 -04, § 2, 4 -13 -2010) <br />http : //library.municode. com/print. aspx ?clientlD= 14286 &HTMRequest =http %3 a %2f %2flib... 1/5/2012 <br />