Laserfiche WebLink
M M <br />It should be noted that, since July 23rd, the enhanced arterial and collector roadway landscape <br />strip standards have been applied to 5 new development projects. <br />4. Perimeter (Compatibility) Buffer Standards <br />Requires a masonry wall or earthen berm to be the opaque feature component of the <br />buffer unless otherwise approved by the Planning and Zoning Commission. <br />Reason: Ensures that the opaque feature is at required height and opacity at C.O., <br />rather than relying on a 2 year grow -in period. <br />Requires compatibility buffers adjacent to a local road to be provided but reduced one <br />category (e.g. from a Type "B" to a Type "C" buffer). The height of any required <br />opaque feature would remain the same. Buffers required adjacent to thoroughfare <br />plan roads would be reduced two categories (e.g from B to D). This concept is <br />presently not addressed in chapters 911 or 926, but parallels the way buffers are <br />treated in the planned development regulations of Chapter 915. <br />Reason: Establishes a set rule as to how buffering requirements apply when an <br />intervening roadway exists between two incompatible uses. Recognizes that <br />intervening roadways provide more separation between uses, resulting in the need for <br />less intensive compatibility buffers. <br />Establishes the finished floor elevation of the proposed project building(s) to be the <br />benchmark for measuring the height of 3' and 6' opaque features, unless using such <br />a benchmark would result in a feature exceeding 8' in actual height and the Planning <br />& Zoning Commission agrees to modify the requirement. <br />Reason: Establishes a reasonable and consistent benchmark that relates opaque <br />feature height to the facility it is intended to screen -out. <br />Allows 50% of the normally required buffer hedge material to be deleted when a 6' <br />wall or fence is constructed, if remaining required vegetation (hedge and understory <br />trees) is planted between the wall and the project property line. <br />Reason: Recognizes that less hedge material (lower height vegetation) is needed <br />when a wall is used. Also recognizes that some landscape material is needed to <br />"soften" the appearance of wall exteriors. <br />5. Buffers Between Commercial & Residential Uses <br />AND <br />6. Buffers Between Industrial & Residential Uses <br />Requires loading docks to be screened by an 8' tall masonry wall, when the loading <br />dock is adjacent to or visible from a residential site. <br />Reason: Applies the Wabasso and SR 60 corridor plan requirements for loading dock <br />buffers countywide. Recognizes that an 8' wall at docks would screen more of the <br />taller vehicles (trucks). that use such facilities and more effectively attenuate noise <br />impacts of loading docks. <br />During the PSAC's June 26, 1997 review of the pending ordinance, some members expressed <br />concerns about the increased costs resulting from the new requirements, and one member questioned <br />the need for any increase in landscaping requirements. An estimate of costs associated with the <br />pending ordinance requirements (see attachment #3) was provided to the PSAC, Planning and Zoning <br />Commission, and Board of County Commissioners when those boards reviewed the pending <br />ordinance. Some members also expressed concerns that, by requiring larger trees at time of planting, <br />supply constraints could be a problem, and taller planted trees take longer to settle -in and start <br />growing vigorously. Planning staff agrees with some concerns discussed at the PSAC meeting <br />regarding the pending ordinance's proposed loading dock buffering. In stars opinion, better <br />5 <br />September 8, 1997 <br />bonyPACE <br />