My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2008-002
CBCC
>
Ordinances
>
2000's
>
2008
>
2008-002
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/2/2019 2:15:13 PM
Creation date
9/30/2015 4:16:51 PM
Metadata
Fields
Template:
Ordinances
Ordinance Number
2008-002
Adopted Date
01/08/2008
Agenda Item Number
9.A.3.
Ordinance Type
Land Development Regulations
State Filed Date
01\17\2008
Entity Name
Proportionate Share of Major Roadway Improvements
Code Number
Chapter 910
Subject
Concurrency Management System
Codified or Exempt
Codified
Supplemental fields
SmeadsoftID
3683
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
21
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
2008- 002 <br />(6) The coordinating agency will be responsible for compiling the level of service reviews into a <br />concurrency report within five (5) days after receipt of the evaluating agencies' report for <br />each concurrency application identified in section 910.08(2), except for final concurrency <br />applications. Each concurrency report will document <br />(a) The current land use and zoning designation, type and intensity of proposed use, and <br />public facility availability upon which the reviews were based; <br />(b) The specific facilities impacted by the proposed development; <br />(c) The extent of the impact on those facilities by the proposed development; and <br />(d) Conditions or stipulations regarding the timing and phasing of the development or <br />provision of facility improvements necessary to ensure that adequate facilities will be <br />available concurrent with the impact of the development. <br />For each concurrency application review, the coordinating agency will be responsible for <br />monitoring and enforcing any conditions and/or stipulations contained in previous <br />concurrency determinations. This will be done in order to ensure that consistent concurrency <br />review procedures are maintained and that unnecessary duplication as a result of different <br />concurrency reviews is avoided. <br />(7) <br />SECTION #2: <br />Section 910.08. Determination of concurrency, generally. <br />(1) Consistent with comprehensive plan policies, the approval of development orders shall be <br />contingent upon a finding that adequate public facilities are available, consistent with their <br />adopted levels of service and concurrent with the impact of the proposed development. Such <br />determination of concurrency made during the review of a concurrency application which is <br />not an initial or final concurrency certificate does not guarantee that there will automatically <br />be a finding of concurrency at subsequent steps in the process for a given property or a <br />proposed development. However, a finding of concurrency made at the initial concurrency <br />stage may be used as a basis for a finding of concurrency during the review of a final <br />concurrency application provided that: <br />(a) The previously approved concurrency determination remains in effect, as determined <br />by the time limit imposed upon the concurrency certificate; <br />(b) The impact of the proposed development under consideration was fully taken into <br />account during the concurrency review and in the finding of concurrency associated <br />with the previously approved concurrency certificate; <br />(c) The conditions related to land uses and facility availability upon which the previous <br />finding was based have not changed due to an act of nature or other situation out of the <br />county's control; and <br />Bold Underline: Additions to Ordinance <br />Sole enghtt Deleted Text from Existing Ordinance <br />F:\Community Development\Users\CurDev\ORDINANCE\2008\2008-_ 910 (1-8-08BCC).RTF <br />
The URL can be used to link to this page
Your browser does not support the video tag.