My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
06/02/2020
CBCC
>
Meetings
>
2020's
>
2020
>
06/02/2020
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/19/2020 1:54:22 PM
Creation date
7/10/2020 12:47:54 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC Regular Meeting
Document Type
Agenda Packet
Meeting Date
06/02/2020
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.
/
321
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
By way of summary, during the extensive and time course of attempting to garner site approval for the <br />proposed project we were notified on February 14, 2020 - more than 240 days after the initial meeting <br />and multiple subsequent meetings, calls and submittals—that our plans needed to include multiple traffic <br />improvements on Indian River Boulevard. While there was absolutely no previous reference to any of <br />these required traffic improvements, we believe the costs thereof represent capital improvements that <br />should be paid for with Traffic Impact Fees collected in the traditional manner. <br />We question the logic and, despite not being attorneys, the legality of assessing a project traffic related <br />capital improvement (as well as the related costs) and then also assessing broad based Traffic Impact Fees <br />according the County's Traffic Impact Fee schedule without an offset. <br />• We believe this is duplicative and burdening the project with charges for the same intended use. <br />• We believe this process is not consistent with the intent of HB 7103 ratified in June 2019. <br />• We believe these improvements — all located on County owned land — are not exclusive to our <br />project. <br />+. We believe - and County staff has acknowledged — these last minute revisions were related to <br />concerns over "capacity" and additional trips. <br />• We believe Traffic Impact Fees are collected to pay specifically for these types of capital traffic <br />improvements so it seems inequitable that we would pay the costs and be assessed ordinary <br />Traffic Impact Fees. <br />We are not seeking to avoid Traffic Impact Fees but rather to realize a credit for the costs of the traffic <br />improvements required by the County that are being paid for by us. The amount of the credit requested <br />in the application is significantly below the total actual costs of said improvements ($213K versus actual <br />cost approaching $500K). We fully acknowledge and realize we will be paying Traffic Impact Fees- it's the <br />cost of progress and the responsibility of enjoying and supporting necessary infrastructure. We simply do <br />not believe it is equitable for us to be paying both without an offset. <br />The general question comes to mind is: If Traffic Impact Fees are "one time charges applied to new <br />development, providing revenue designed to accommodate capacity producing capital improvements to <br />accommodate the demand for those improvements generated by new development in order to maintain <br />adopted levels of service" AND we are being required to pay directly for those capital improvements as <br />determined by the County, where is the rest of the money going? <br />We respectfully ask that you review. the documents accompanying this letter and reflect upon the intent <br />of Traffic Impact Fees. Hopefully you will concur that the economic burden placed on our Project is not <br />equitable or in line with the customary method or intent of assessing costs to a community development. <br />We are looking forward to adding a wonderful project to Indian River County will further enhance <br />healthcare services for the community at Targe. <br />179 <br />
The URL can be used to link to this page
Your browser does not support the video tag.