My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
7/9/2002
CBCC
>
Meetings
>
2000's
>
2002
>
7/9/2002
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/17/2019 1:28:34 PM
Creation date
9/25/2015 4:42:36 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC
Document Type
Migration
Meeting Date
07/09/2002
Archived Roll/Disk#
2558
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
74
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
Section 927.15. Specimen tree protection. <br />Change: The sentence "A reasonable effort need not remove all economic value of the <br />property in order to be considered not 'practicable"' has been removed. <br />thin the <br />t this <br />Reason: There is allow the cncem county to isubstantiallregulated <br />proposed tprojectssto thee exnt that <br />the project would not be economically viable and could result in a takings <br />issue. Staff attempted to assure the regulated community that this was not <br />the case. In fact, staff has stated that, should a situation arise that is <br />unacceptable to an applicant, the applicant has the option to appeal staffs <br />decision. It is staff's opinion that the removal of this language does not alter <br />the authority of the proposed ordinance. <br />Section 927.18 (1)(d)(4). <br />Change: Specific language regarding the type of tag required for the tree and the <br />location of the tag on the tree has been added. <br />Reason: This change reflects the experience of the Town of Indian River Shores with <br />implementation of its tree protection ordinance. This revision will provide <br />for a uniform marking system that, in conjunction with the tree survey, will <br />allow staff to better locate trees that are to be saved on the project site. <br />Section 927.18(4). <br />Change: Increased, from one foot to five feet, the minimum distance from the tree <br />where the use of special techniques or methods may be used if approved by <br />staff If impacts are proposed within the five foot radial distance, a written <br />statement from a Certified Arborist will be required. This statement must <br />certify that the proposed special techniques or methods wilnot result in impact within the five foot <br />os <br />probability of damage to the tree. Any proposed <br />radial distance that would cause physical damage to the roots, trunk, or <br />buttresses of the tree will not be approved. <br />Reason: In previous drafts of this ordinance, the minimum distance was set at one <br />foot; however, it was felt that this was too close to the tree considering the <br />roots and buttressing of certain trees. The existing ordinance allows impacts <br />to within five feet of a tree <br />Major Chances <br />Section 927.16. Critical Root Zone determination. <br />Change: The calculation of the Critical Root Zone (CRZ) has been changed. The <br />CRZ definition is now in Section 901.03, Definitions. The CRZ is calculated <br />as a radius that is equal to one foot of radius for every inch of diameter at <br />breast height (dbh). A description of tree well construction and techniques <br />has replaced the CRZ information (see below). <br />Reason: The original calculation of the CRZ took into account four factors in arriving <br />at the size of the CRZ These factors were: the species of tree; the age of the <br />tree; the condition of the tree; and the relative tolerance of the tree species to <br />various impacts. Of these four factors, only the species of the tree and the <br />relative tolerance would generally be undisputed. The other two factors <br />require some subjective determinations. <br />Based on comments received at the public workshops, written comments, <br />July 9, 2002 <br />38 <br />
The URL can be used to link to this page
Your browser does not support the video tag.