My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2009-021
CBCC
>
Ordinances
>
2000's
>
2009
>
2009-021
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/6/2016 2:26:09 PM
Creation date
10/5/2015 8:52:37 AM
Metadata
Fields
Template:
Ordinances
Ordinance Number
2009-021
Adopted Date
11/10/2009
Agenda Item Number
10.A.3.
Ordinance Type
Comprehensive Plan Amendment
State Filed Date
11\19\2009
Entity Name
2020 Comprehensive Plan
Subject
Capital Improvements Element
Supplemental fields
SmeadsoftID
7423
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
102
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 />Service Standards <br />Level -of -service standards for concurrency related facilities are established in this plan for the <br />following facilities: sanitary sewer, potable water, solid waste, stormwater management, recreation, <br />public schools, and transportation. These are explained in detail in the applicable comprehensive plan <br />elements. <br />For each facility, level -of -service is a measure of the relationship between demand for the service and <br />the capacity of the facility. Capacity, however, is measured differently for each type of facility. Table <br />6.18 identifies both the capacity and demand measures for each public facility. These measures are <br />addressed in detail, and existing capacities are identified in the applicable Comprehensive Plan <br />Elements. <br />. Table 6.18: Service. Level Measures for Concurrency Related Facilities <br />Public Facility Category _ <br />Specific Facility <br />Capacity Measure <br />Demand Measure <br />Geographic Scope <br />Transportation <br />p <br />Roadway <br />y <br />Volume of cars <br />Peak Season/Peak <br />Affected Roadways <br />accommodated over time <br />Direction/Peak Hour Trips <br />SanitarySewer <br />Treatment Plant <br />Treatment design Capacity <br />(GPD) <br />Generation Rate (GPD) <br />Service Area <br />Potable Water <br />Treatment Plant <br />Treatment Design Capacity <br />(GPD) <br />Generation Rate (GPD) <br />Service Area <br />Solid Waste <br />Landfill <br />Volume in active cell (cubic <br />Generation Rate (tons per <br />Entire County <br />yards) <br />capita per year) <br />Recreation <br />Parks <br />Acres of park land <br />Acres of parks per thousandEntire <br />County <br />population <br />Stormwater Management <br />Drainage <br />Volume of water <br />Volume of stormwater <br />Basin <br />conveyances <br />outfalling for design storm <br />Education* <br />Public Schools (K- <br />Number of Children <br />Enrolled Students/ Future <br />Service Area <br />12) <br />accommodated over time <br />Student Generation <br />*Limited to participating Schools owned and operated by the Indian River County School District <br />Concurrency requires that each facility within the geographic scope of a proposed project's impact <br />area have sufficient capacity to accommodate the project's demand. If that capacity is not available, <br />the proj ect cannot be approved. The principal function of the concurrency management system then is <br />to provide a mechanism whereby demand and capacity measures can be compared on a project by <br />project basis. <br />Table 6.18 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; this is the <br />geographic scope for the traffic public facility category. For concurrency purposes, affected roadways <br />will be those roadways impacted by a project's traffic. All projects, regardless of size, impact the <br />roadway on which the project fronts. In addition, other roadways further removed from the project <br />Community Development Department Indian River County <br />Supplement #_; Adopted November _, 2009, Ordinance 2009- <br />44 <br />
The URL can be used to link to this page
Your browser does not support the video tag.