My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2019-090
CBCC
>
Official Documents
>
2010's
>
2019
>
2019-090
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/27/2019 1:30:42 PM
Creation date
6/17/2019 11:08:50 AM
Metadata
Fields
Template:
Official Documents
Official Document Type
Plan
Approved Date
06/11/2019
Control Number
2019-090
Agenda Item Number
10.A.1.
Entity Name
IRC Comprehensive Plan 2030 (with RESO 2019-041)
Subject
Text Amendments for Capital Improvements and Transportation
Text of amendments sent to state and regional authority for approval before adoption
Document Relationships
2019-041
(Agenda)
Path:
\Resolutions\2010's\2019
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.
/
202
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
Comprehensive Plan Capital Improvements Element <br />Table 6.16 provides the criteria for establishing a demand to capacity comparison for a proposed <br />project. While most of the characteristics are self-explanatory, one needs clarification; that is the <br />geographic scope for the traffic public facility category. For concurrency purposes, affected <br />roadways are those roadways impacted by a project's traffic. Regardless of size, all projects impact <br />the roadway on which the project fronts. In addition, other roadways further removed from the <br />project may be impacted. For concurrency purposes, two lane roadways which are assigned 8 or <br />more peak hour/peak season/peak direction project trips and four or more lane roadways that are <br />assigned 15 or more peak hour/peak season/peak direction project trips are considered impacted <br />roadways. <br />For transportation concurrency related facilities, level -of -service standards are applied to all impacted <br />roadways. Those level -of -service standards range from A to F and are associated with peak <br />hour/peak season/peak direction trips. <br />Demand <br />Demand is an important component of the concurrency management system. Essentially, demand is a <br />measure of facility use. When compared to facility capacity, demand can indicate the level -of -service <br />for the facility. <br />As depicted in Table 6.16, demand can be measured quantitatively for each public facility category. <br />While the demand function for each facility consists of applying a rate to the number of facility users, <br />estimation of total demand is more complex. For concurrency management purposes, demand can be <br />divided into three types: existing, committed, and projected. Each must be considered separately for <br />purposes of concurrency management. <br />Existing Demand <br />Existing demand is simply the current level of use for a facility. For a roadway, it is the number of <br />peak hour/peak season/peak direction trips; for a school, it is the number of full-time enrolled <br />students; for water and wastewater treatment plants, it is the existing flow volume measured in <br />gallons per day. Those figures are included within applicable plan elements. <br />Existing demand then reflects the use of a facility by the current population. When compared to <br />capacity, existing demand can show if the facility has unused capacity or if it is functioning over <br />capacity. <br />Existing demand, however, is not static. As population increases and dwelling units come on-line, <br />existing demand increases. Those increases in existing demand can be identified through facility use <br />measurements. For example, regular traffic counts done on roads or treatment plant flow records are <br />Community Development Department Indian River County <br />Adopted , 2019, Ordinance 2019-1/ 42 <br />Appendix A - CIE Amendment <br />
The URL can be used to link to this page
Your browser does not support the video tag.