My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2010-252A (16)
CBCC
>
Official Documents
>
2010's
>
2010
>
2010-252A (16)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/10/2022 2:59:27 PM
Creation date
10/5/2015 10:00:50 AM
Metadata
Fields
Template:
Official Documents
Official Document Type
Report
Approved Date
10/12/2010
Control Number
2010-252A (16)
Agenda Item Number
10.A.3
Entity Name
2030 Comprehensive Plan
Subject
EAR based Amendments 2030 Complrehensive Plan
Chapter 1 Introductory Element
Supplemental fields
SmeadsoftID
13448
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
57
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 Introductory Element <br />with various individual elements. As existing advisory bodies to the county, these groups also <br />possessed knowledge of county policies and regulations. The responsibilities of those primary <br />review groups were: reviewing staff drafts and reports; conducting public meetings; and <br />recommending draft elements to the Planning and Zoning Commission. <br />Other civic and professional groups were also encouraged to participate in the development and <br />review of the comprehensive plan by participating in the formal public review process as well as <br />conducting their own reviews. <br />Throughout the development and review of the plan, planning staff had the responsibility of <br />providing the necessary coordination and support. That included: conducting research and analysis; <br />preparing and presenting draft elements and reports; and conducting public meetings and workshops. <br />Upon completion of the elements, the formal adoption process began. Pursuant to the requirements <br />of Florida Statutes, the Planning and Zoning Commission held a public hearing and made its <br />recommendations to the Board of County Commissioners. The County Commission then conducted <br />a public hearing and transmitted the plan to DCA for state review. <br />As structured, the public participation plan provided for the availability and inspection of documents <br />by the public; the solicitation and encouragement of the public to provide written comments which <br />were incorporated into the public record; and the provision of public notice of all meetings, <br />workshops and hearings. Other efforts to keep the public informed included the issuance of press <br />releases, the provision of information, and the maintenance of records pertaining to public review. <br />Documents were posted on the County's website and were provided in hardcopy form as part of <br />various meeting packets. <br />Consistent with state law, plan amendments have been processed in a manner similar to the plan <br />adoption process. <br />Development of both EARs followed largely the same process as development of the comprehensive <br />plan. That process is outlined in the third EAR Public Participation Plan, which the Board of County <br />Commissioners adopted on June 20, 2006. Consistent with state law, the Planning and Zoning <br />Commission, as the designated local planning agency, was primarily responsible for developing the <br />EAR. Similar to the plan development process, county boards and commissions provided direct <br />input in the development of the EAR for individual elements of the comprehensive plan. <br />When all the EAR elements were complete, the Planning and Zoning commission approved the <br />proposed EAR. Following two public workshops, the adopted EAR was approved by the Board of <br />County Commissioners at a public hearing. Subsequently, EAR based amendments to the plan were <br />adopted through the regular plan amendment process. <br />Community Development Department Indian River County <br />z <br />
The URL can be used to link to this page
Your browser does not support the video tag.