My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
09.01 - Road Turnbacks
Laserfiche
>
City Council (Permanent)
>
Agenda Packets (Permanent)
>
2015
>
06-02-2015 Council Meeting
>
09.01 - Road Turnbacks
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/28/2015 9:46:50 AM
Creation date
5/28/2015 9:46:17 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
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
interchange from 9% of the total cost to 6% of the total <br /> cost. The figure that has been used for the total cost to build <br /> the interchange is 6.2 million dollars. The City's share @ <br /> 9% is $558,000. Reducing the City's responsibility of 9% <br /> to 6% brings the City's share to $372,000 (a savings of <br /> $186,000) <br /> The Council must keep in mind that the interchange cost of <br /> 6.2 million is an estimate. The cost could be a bit lower or <br /> higher. The bottom line is that the City will realize an <br /> additional $100,000 for CR 112 and see an additional <br /> savings in its share of the interchange of approximately <br /> $186,000. <br /> Attached is a spreadsheet showing three different financial <br /> analysis scenarios: <br /> 1. The green (top) spreadsheet depicts the financial <br /> analysis if the City received no additional funds from the <br /> County — (this was the original proposal). <br /> 2. The blue (middle) spreadsheet depicts the financial <br /> analysis if the City received an additional $500,000 from <br /> the County. <br /> 3. The yellow (bottom) spreadsheet depicts the financial <br /> analysis if the City receives approximately $300,000 <br /> additional funds from the County (current offer on the <br /> table). <br />
The URL can be used to link to this page
Your browser does not support the video tag.