My WebLink
|
Help
|
About
|
Sign Out
Home
CC - Agendas - City Council - REGULAR - 8/29/2006
>
City Clerk
>
Permanent Records
>
Permanent
>
CC - Agendas - City Council - REGULAR - 8/29/2006
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/2/2022 4:28:20 PM
Creation date
3/2/2022 11:10:00 AM
Metadata
Fields
Template:
CC - Agendas
Department
City Clerk
Sub
Clerk Records
Content
Agendas
Committee Status
Current
Document Type
City Council
Meeting Type
REGULAR
Meeting Date
8/29/2006
Retention
Permanent
Retention Type
Permanent
Security
Public
Scanner
COP\torey.dawson
Scan Date
3/2/2022
Record Series
GS1016, #10260
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
113
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).
Show annotations
View images
View plain text
In 2001, the impact fees were updated to reflect the rapidly changing demographics and the <br /> continued strain on our existing facilities and to ensure that the charges, and the underlying <br /> assumptions, were meeting the needs for which they were established. In addition to updating the <br /> fees, a new public buildings fee for was initiated. <br /> Since 1995, the city has collected nearly $13 million in impact fees that have helped to defray the <br /> cost of growth related projects totaling $11.1 million. Details of each fee and the related use of <br /> proceeds are shown in the appendix of this report. <br /> The City Council has authority to reduce or eliminate any of the impact fees, but cannot arbitrarily <br /> increase the fees. Increases require revisions to the public report to demonstrate justification and <br /> formula revisions. This report provides such an update. <br /> Process and Proposed Fees <br /> There are three methods used to calculate the various development impact fees. A plan-based <br /> method is best suited for public facilities that have adopted plans or commonly accepted service <br /> delivery standards to guide capital improvements. <br /> The incremental expansion approach documents the current service level (SL) for each type of <br /> public facility. SL standards are determined using the City's current inventory of capital facilities and <br /> assets as well as current costs to construct or acquire comparable facilities or assets. An incremental <br /> expansion cost approach is best suited for public facilities that will be expanded in regular <br /> increments, with SL standards based on current conditions in the community. This approach was .romik <br /> used extensively in this study. <br /> A third approach, known as the buy-in approach is best suited for facilities that have been overbuilt <br /> in anticipation of growth and have excess capacity available. New development would "buy-in" to <br /> the excess capacity of the facility. The basis for the buy-in approach is that new development will <br /> pay for its share of the useful life and remaining capacity of recently constructed or purchased <br /> facilities. <br /> Each department provided updates and improved information based on current replacement costs <br /> for the various impact fees as well as new projects anticipated as a result of growth. The updated <br /> information is presented in the supporting impact fee calculation section. The public building fee is <br /> restructured to reflect the addition of the City's vehicle fleet.This update proposes a 154% increase <br /> to the residential impact fees as shown below: <br /> Impact Fees: Residential Units 1994 2001 2006 <br /> Fire 128 167 525 <br /> Police 48 84 589 <br /> Parks 500 715 2,466 <br /> Recreation 400 401 708 <br /> Library 208 253 747 <br /> Public Buildings& Fleet N/A 275 511 <br /> Streets(not included in this update) N/A 469 469 <br /> Total 1,284 2,364 6,015 -�•. <br />
The URL can be used to link to this page
Your browser does not support the video tag.