My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
03/13/2018
CBCC
>
Meetings
>
2010's
>
2018
>
03/13/2018
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/11/2021 12:55:33 PM
Creation date
3/21/2018 2:30:08 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC Regular Meeting
Document Type
Agenda Packet
Meeting Date
03/13/2018
Meeting Body
Board of County Commissioners
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.
/
228
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
ORDINANCE 2018 - <br />AN ORDINANCE OF INDIAN RIVER COUNTY, FLORIDA, CONCERNING <br />AMENDMENTS TO ITS LAND DEVELOPMENT REGULATIONS (LDRS); PROVIDING <br />FOR AMENDMENTS TO CHAPTER 910, CONCURRENCY MANAGEMENT SYSTEM; BY <br />AMENDING SECTION 910.11(l)(B) DETERMINATION OF CONCURRENCY, <br />SPECIFICALLY; AND BY PROVIDING FOR REPEAL OF CONFLICTING PROVISIONS; <br />CODIFICATION; SEVERABILITY; AND EFFECTIVE DATE. <br />BE IT ORDAINED BY THE BOARD OF COUNTY COMMISSIONERS OF INDIAN RIVER <br />COUNTY, FLORIDA THAT THE INDIAN RIVER COUNTY LAND DEVELOPMENT <br />REGULATIONS (LDRs) CHAPTER 910, CONCURRENCY MANAGEMENT SYSTEM, BE <br />AMENDED AS FOLLOWS: <br />SECTION #1: <br />Amend LDR Section 910.11 (1)(b), first two paragraphs, "Concurrency analysis", <br />specifically; as follows: <br />(1) Transportation. <br />(b) Concurrency analysis. The public works department and community development <br />department shall be the agencies responsible for determining whether adequate capacity <br />is available to support traffic expected from a given proposed development such that a <br />finding of concurrency may be rendered. Using the information inventoried pursuant to <br />section 910.11(1)(a) above, expected development generated traffic shall be assigned to <br />those two-lane roadway segments identified as receiving at least eight (8) or more peak <br />season/peak hour/peak direction trips and those four -lane (or wider) roadway segments <br />identified as receiving fifteen (15) or more peak season/peak hour/peak direction trips <br />generated by the development under consideration pursuant to section 910.11(1)(a)2 <br />above. The community development department will review and assign trips to segments <br />for all individual single family residential traffic concurrency determination applications. <br />Trips for individual single-family concurrency determinations shall be assigned as <br />provided in 910.09(4)(b)3. Traffic Engineering Division staff will review and assign trips <br />to segments for all projects generating less than enefour hundred (-1 400) average trips <br />per day. <br />For larger projects generating on four hundred (4-0-04UO or more average trip ends per <br />day, the applicant shall submit a traffic impact analysis (TIA) or traffic impact statement <br />(TIS) as required by Chapter 952 regulations. Based on this TIA or TIS, the public <br />works department will assign trips to roadway segments. The community development <br />staff will update the database as concurrency determination certificates are issued. <br />SECTION #2: SEVERABILITY <br />If any clause, section or provision of this Ordinance shall be declared by a court of competent <br />jurisdiction to be unconstitutional or invalid for any cause or reason, the same shall be eliminated <br />from this Ordinance and the remaining portion of this Ordinance shall be in full force and effect <br />and be as valid as if such invalid portion thereof had not been incorporated therein. <br />Bold Underline: Additions to Ordinance <br />Sti4ke thretigT-. Deleted Text from Existing Ordinance <br />F:\Community Development\CurDev\Ordinances\20180rdinances\2018- 910.11(1)(b) - Determination of concurrency.docx <br />119 <br />
The URL can be used to link to this page
Your browser does not support the video tag.