My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 05/02/2013
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2013
>
Agenda - Planning Commission - 05/02/2013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:17:58 AM
Creation date
4/29/2013 3:01:47 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
05/02/2013
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
143
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
The proposed revisions also specify that if removals exceed the allowable threshold, that the developer shall either <br />replace each significant tree inch removed with 1.25 inches (diameter) of new trees or provide the City with <br />$125.00 in restitution. These funds would be placed into a Community Reforestation Fund for reforestation efforts <br />throughout the community. Finally, the proposed revisions specify that trees removed for water quality treatment <br />ponds, public trails and sidewalks, and arterial and collector streets are exempt from the removal threshold <br />calculation as are the removal of invasive (undesirable) species. All required reforestation plantings would count <br />toward the required landscaping for the applicable zoning district. <br />Alternative Options <br />Option #1. The proposed amendments will accomplish several things. First, it eliminates ambiguity by replacing <br />the term Desirable Tree with Significant Tree. Desirable Tree is not defined in City Code and is subjective. <br />Significant Tree is already defined in City Code. Secondly, the amendments clarify that all projects, not just <br />multi -family projects, are subject to removal thresholds (forty percent (40%) for residential projects and thirty <br />percent (30%) for business and employment projects). Finally, the proposed amendments incorporate more <br />flexibility into the standards by identifying exemptions for certain required improvements and by providing <br />multiple options to address excess removals as part of a project. Both the EPB and Staff believe that these <br />amendments align more with the intent of the ordinance (protecting/enhancing the community forest) and support <br />adopting them. <br />Option #2. Do not amend the current Tree Preservation Ordinance While the current ordinance provides a <br />measure of protection for the community forest, only multi -family projects are subject to replacement <br />requirements. Presently, if a developer cannot comply with the replacement standards the only option available is a <br />variance. Again, the replacement standards are in addition to the required landscaping standards for new <br />development of the underlying zoning district. The current ordinance also does not provide exemptions for <br />removals due to other required improvements or for removal of invasive (undesirable) species. <br />Funding Source: <br />Preparation of the Ordinance is being handled as part of regular Staff duties. <br />Staff Recommendation: <br />The Environmental Policy Board (EPB) recommends adoption of Ordinance #13-10 amending City Code Article II <br />(Zoning) Division 5 (Tree Preservation). <br />Action: <br />Motion to recommend that the City Council adopt/not adopt Ordinance # 13-10 amending City Code Article II <br />(Zoning) Division 5 (Tree Preservation). <br />Tree Preservation Ordinance with Mark Ups <br />Proposed Ordinance #13-10 <br />Attachments <br />Form Review <br />Inbox Reviewed By Date <br />Tim Gladhill Tim Gladhill 04/26/2013 08:27 AM <br />Tim Gladhill Tim Gladhill 04/26/2013 02:29 PM <br />Form Started By: Chris Anderson Started On: 04/18/2013 05:42 PM <br />Final Approval Date: 04/26/2013 <br />
The URL can be used to link to this page
Your browser does not support the video tag.