My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
10/23/2001
CBCC
>
Meetings
>
2000's
>
2001
>
10/23/2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/25/2020 4:53:33 PM
Creation date
9/25/2015 4:30:09 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC
Document Type
Migration
Meeting Date
10/23/2001
Archived Roll/Disk#
2547
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
145
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
landscaping standards. The Board then directed staff to make changes to some of the ordinance <br />sections, but not the landscape replacement standards. The Board also established a policy that <br />public road projects include roadside and median landscaping. The result was a decision to <br />increase private sector and public sector landscaping requirements. Staff then drafted a post - <br />workshop final ordinance. <br />The post -workshop final ordinance, which included the current 926.12(3) standards, was <br />considered by the PSAC at its October 16, 1997 meeting. At that meeting, the PSAC voted 5-0 <br />to recommend adoption of the final ordinance. At its November 13, 1997 meeting, the PZC voted <br />5-0 to recommend adoption of the final ordinance. At its December 16, 1997 meeting, the Board <br />adopted the final ordinance by a vote of 3-1. The sole dissenting vote was due to one <br />commissioner's belief that certain landscaping standards were not stringent enough. <br />In summary, the current landscaping requirements (including the replacement size standards) <br />were part of a comprehensive and extensive review of the county's landscape standards that <br />occurred in 1997. <br />• Reason for Replacement Standards <br />The current replacement size standards were established in 1997 in response to a <br />fundamental problem that Planning and Zoning Commissioners and staff had observed with <br />landscape maintenance on completed, older project sites. The problem was that landscaping <br />material was not maturing on many sites due to insufficient material quality at the time of <br />planting and due to the fact that replacement landscaping was being installed at the same <br />minimum sizes required at the outset of a project. In addition, the 926.12(3) requirements at <br />that time did not provide a strong disincentive for inadequate maintenance and landscape <br />material growth. Consequently, replacements resulting from code enforcement action did not <br />adequately "boost" site landscaping appearances. To address these problems, the current <br />926.12(3) replacement standards were established to ensure that landscaping material on <br />project sites matures as intended and to provide a strong disincentive for inadequate <br />maintenance and inadequate landscape material growth on project sites. <br />• Current and Proposed Replacement Requirements <br />The current 926.12(3) requirements (see attachment #2) apply only to the minimum number <br />of required trees on a project site. These requirements allow landscaping material to be <br />replaced at the original project minimum sizes for the first 18 months after project C.O. <br />(Certificate of Occupancy). Thereafter, replacement requirements for shrubs, understory <br />trees, and canopy trees are increased. <br />A. 0-18 months after C.O. <br />Current 926.12(3) Requirements <br />At -planting sizes allowed, as followed: <br />• Outside of Special Corridors <br />Shrubs: 18" <br />Understory trees: 5' (1" diameter at 0.5') <br />Canopy trees: 10' (2" diameter at 0.5') <br />• Within Special Corridors <br />Shrubs: 18"-30" <br />Understory trees: 5' (1" diameter at 0.5') <br />Canopy trees: 12' (2" diameter at 0.5') <br />OCTOBER 23, 2001 r f, r, �, <br />b i ; i 1I UU <br />-49- <br />
The URL can be used to link to this page
Your browser does not support the video tag.