My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
5/22/2001
CBCC
>
Meetings
>
2000's
>
2001
>
5/22/2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/25/2019 9:52:35 AM
Creation date
9/25/2015 4:20:59 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC
Document Type
Migration
Meeting Date
05/22/2001
Archived Roll/Disk#
2277
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
336
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
In this case. the minimum floor elevation level of service standards do not apply, since the property <br />does not lie within a floodplain. However. both the on-site retention and discharge standards apply. <br />With the most intense use of this site under the proposed amendment. the maximum area of <br />impervious surface would be approximately 8.5 acres. The maximum runoff volume. based on that <br />amount of impervious surface and the 25 year/24 hour design storm, and given the IRFWCD 2 inch <br />discharge requirement, would be approximately 321 320 cubic feet. In order to maintain the <br />county's adopted level of service, the applicant would be required to retain approximately 239.720 <br />cubic feet of runoff on-site. With the soil characteristics of the subject property, it is estimated that <br />the pre -development runoff rate is 35 cubic feet/second. <br />Based upon the County Engineering Division's analysis. the stormwater management level of service <br />standard would be met by limiting off-site discharge to the IRFWCD's maximum discharge rate of <br />2 inches in 24 hours, and requiring retention of the 239,720 cubic feet of runoff for the most intense <br />use of the property. <br />As with all development, a more detailed drainage review will be conducted during the development <br />approval process. <br />Recreation <br />Recreation concurrency requirements apply only to residential development. Therefore, this <br />Comprehensive Plan amendment/rezoning request would not be required to satisfy recreation <br />concurrency requirements. <br />Concurrencv Summary <br />Based upon the analysis conducted, staff has determined that all concurrency -mandated facilities. <br />including stormwater management. roads, solid waste. wastewater. and water. have adequate <br />capacity to accommodate the most intense use of the subject properties under the proposed land use <br />designation. Therefore, the concurrency test has been satisfied for the subject request. <br />Consistency with Comprehensive Plan <br />Comprehensive Plan amendment requests are reviewed for consistency with all policies of the <br />Comprehensive Plan. As per section 800.07(1) of the County Code. the 'Comprehensive Plan may <br />only be amended in such a way as to preserve the internal consistency of the plan pursuant to Section <br />163.3177(2)F.S. Amendments must also show consistency with the overall designation of land uses <br />as depicted on the Future Land Use Map, which includes agricultural, residential, recreational, <br />conservation. and commercial and industrial land uses and their densities. <br />The goals. objectives and poiicies are the most important parts of the Comprehensive Plan. Policies <br />are statements in the plan that identify the actions which the county will take in order to direct the <br />community s development As courses of action committed to by the county, policies provide the <br />basis for all county land development decisions. While all Comprehensive Plan policies are <br />important, some have more applicability than others in reviewing plan amendment requests. Of <br />particular applicability for this request are the following policies: <br />May 22, 2001 <br />28 <br />
The URL can be used to link to this page
Your browser does not support the video tag.