My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01/08/2013AP
CBCC
>
Meetings
>
2010's
>
2013
>
01/08/2013AP
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/26/2018 10:47:48 AM
Creation date
3/23/2016 8:54:01 AM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC Regular Meeting
Document Type
Agenda Packet
Meeting Date
01/08/2013
Meeting Body
Board of County Commissioners
Book and Page
163
Subject
Greenway
Supplemental fields
FilePath
H:\Indian River\Network Files\SL00000E\S0004BE.tif
SmeadsoftID
14193
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
163
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
UNDER DISCUSSION: <br /> Vice-Chairman Chandler suggested the committee have a discussion on the <br /> possible negative impacts it would have to the County and future projects and opined <br /> there was no way of measuring potential future economic impacts. <br /> Attorney Polackwich remarked if a business were to move into the EZ from out <br /> of the zone and established a business, they would have to pay impact fees. He said if <br /> the County did not collect the impact fees, the County would have to make it up. He <br /> brought up the issue of how often that would happen and felt it was difficult to predict. <br /> He raised the question of how often a business would expand enough in such a way to <br /> call for new impact fees. <br /> Ms. Caseltine asked if this was only for projects in the unincorporated County. At <br /> which time Attorney Polackwich explained some impact programs were County-wide, so <br /> for example, transportation impact fees were collected for businesses expanding into <br /> the City because it was a County-wide program, and other impact fees were only in the <br /> County. He said the greatest impact fees were in transportation. <br /> Mr. Zimmerman asked if the shortfall would be made up out of the general fund. <br /> At which time Attorney Polackwich responded he felt they could be made up through <br /> fuel tax revenues (transportation) and thought other revenues like the one-cent sales <br /> tax. He said there could be other means of sources but usually the first place was the <br /> general fund. <br /> Attorney Polackwich stated it was complicated because if it came from fuel tax, <br /> the complicated formulas used to determine, what if any, was the proportionate share <br /> and what would be the amount of the impact fee to be paid. Attorney Polackwich said it <br /> was assumed the shortfall would come out of the general fund. <br /> Mr. Godfrey Gipson asked if this was applicable for new projects in established <br /> areas, or was it just for un-developed areas. Attorney Polackwich answered it would <br /> apply primarily for new businesses. Attorney Polackwich explained if a business were <br /> constructing a new building to house their business, whether or not it were in a <br /> developed area or un-developed area, the business would have to pay impact fees. <br /> Attorney Polackwich explained in some cases impact fees were based on square <br /> footage, for example, if you have a one-thousand square-foot building, the business <br /> would pay X amount in impact fees and a business that had two-thousand square-foot <br /> building would pay XX amount in impact fees based on that square footage. <br /> Attorney Polackwich explained if a business had a one-thousand square-foot <br /> business and would then expand to a two-thousand square foot-building the business <br /> would be required to pay the impact fees based on the expanded footage (one <br /> thousand feet). <br /> EZDA UN-APPROVED 4 November 08, 2012 <br /> CADocuments and Settings\apolackwich\Local Settings\Temporary Internet <br /> Files\Content.Outlook\5ERVKF3F\11-08-12.doc 125 <br />
The URL can be used to link to this page
Your browser does not support the video tag.