My WebLink
|
Help
|
About
|
Sign Out
06
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2018
>
121818
>
06
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/12/2018 1:47:49 PM
Creation date
12/12/2018 1:47:45 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
12/18/2018
DESTRUCT DATE
15Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
21
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
Lower Income Housing Fund (Fund 122) — This fund is utilized to account for the receipt <br /> of Lower Income Housing fees and their disbursement for lower income housing <br /> projects. Fund balance, revenues, expenditures and transfers for this fund for fiscal <br /> years 2013/14 through 2017/18 are detailed in Attachment 2. <br /> Unexpended Funds After Five Years <br /> Government Code section 66001(d) requires that five years after collecting a <br /> development fee subject to AB 1600 and SB 1693, a local agency shall make findings <br /> that year and every five years thereafter, with respect to any portion of the fee <br /> remaining unexpended. The findings must identify the purpose for which the fee is to <br /> be used and demonstrate a nexus between the fee and the purpose for which it was <br /> originally charged. The findings must also identify all sources and amounts of funding <br /> for completion of the improvement and the approximate date that the improvement will <br /> be fully funded. After five years, a local agency is also required to refund the <br /> unexpended portion of the fee, and any accrued interest, for which a need cannot be <br /> demonstrated. However, when a city makes appropriate findings (including that the <br /> purpose for the developer impact fee remains), the city may retain the fee. <br /> Staff reviewed development impact fees collected five or more years ago and has <br /> determined that all funds held for more than five years are necessary to complete <br /> identified projects as shown below by fund. <br /> Public Facilities Fund (Fund 203) <br /> Amount collected in previous fiscal years subject to 5 year limitation: $0 <br /> Funds are 100% expended as accounted for in Attachment 2. <br /> Park Development Fund (Fund 222) <br /> Amount collected in previous fiscal years subject to 5 year limitation: $0 <br /> Funds are 100% expended as accounted for in Attachment 2. <br /> Traffic Impact Fund (212) <br /> Amount collected in previous fiscal years subject to 5 year limitation: $0 <br /> Funds are 100% expended as accounted for in Attachment 2. <br /> Tri-Valley Transportation Fund (214) <br /> Amount collected in previous fiscal years subject to 5 year limitation: $61,018 <br /> Funds are committed to the following project: <br /> • Tri-Valley Transportation Development Fee Reserve project#01541 <br /> Description: This project establishes a reserve fund for various regional projects <br /> to help mitigate traffic congestion in the Tri-Valley area. These funds represent a <br /> portion of the costs and are the City's 20% set-aside portion of the Tri-Valley <br /> Transportation Development Fees (TVTDF) collected in the City of Pleasanton. <br /> The Tri-Valley projects include the following: 1-580/1-680 flyover and hook ramps, <br /> State Route 84/1-580 corridor improvements from 1-580 to 1-680, Isabel Route <br /> 84/1-680 Interchange, 1-680 auxiliary lanes between Bollinger Canyon Road and <br /> Diablo Road, West Dublin-Pleasanton BART Station, 1-580 HOV lanes from <br /> Tassajara Road to Vasco Road, 1-680 HOV lanes from State Route 84 to the top <br /> of Sunol Grade, I-680/Alcosta Boulevard Interchange Modifications, Crow <br /> Canyon Road Safety Improvements, Vasco Road Safety Improvements, and <br /> Page 4 of 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.