My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
7.0. SR 09-14-1998
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
1993 - 1999
>
1998
>
09/14/1998
>
7.0. SR 09-14-1998
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2008 8:33:21 AM
Creation date
2/2/2004 4:24:23 PM
Metadata
Fields
Template:
City Government
type
SR
date
9/14/1998
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
22
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
Memo/East Elk River Project <br />September 14, 1998 <br />Page 3 <br /> <br />On the 14th it is appropriate to review the trunk sewer and water, street, and <br />storm sewer components of the project. By this, I mean we need to review the <br />cost estimates and revenue sources to finance the improvements. The vast <br />majority of the trunk sewer and water will be financed through assessments. <br />The major part of the street project will be financed with federal and state <br />funds. The developers, either directly or indirectly through TIF, will have <br />obligations for parts of the project. A majority of the storm sewer project will <br />be financed over time with the city surface water management fund, <br />although some assessments to benefited property owners are expected. It <br />should be noted that both the small and larger projects are closer to cash <br />flowing due to revised estimates and state/federal funds being available for <br />the street. <br /> <br />The East Elk River project is incredibly complex in trying to put all of its <br />financial components in order. The narrative in this paragraph is just a <br />listing of a very few of the issues involved in this overall project. The street <br />project can be divided into sections north and south of County Road 12, with <br />state funding allowed only to the north, and federal funds only to the south. <br />Making the project more complex, federal funds can be used for land <br />acquisition on the south side of 12, but state funds cannot be used for land <br />acquisition on the north side of 12. Accordingly, city MSA funds may be <br />needed to acquire land north of County Road 12 for the project. The <br />residential developer will be required to finance some of the road north of 12, <br />while the developer on the south side of 12 will be also required to finance <br />some of the street and storm drainage public improvements, but their <br />financial commitment may be taking place by way of tax increment <br />financing. When we get involved in tax increment financing, we also get <br />involved with a local match requirement and the source of this is uncertain. <br /> <br />Regarding the public improvements, the Council is reminded that it has <br />authorized Evergreen Land Services to negotiate right-of-way acquisition <br />between 175th and 171st. In this regard, Evergreen has completed <br />negotiations with three property owners and is ready to present its <br />recommendations to the Council. Staff supports the recommendations but <br />there is a concern over when the city should formally accept the proposals <br />and sign purchase agreements based on the ultimate funding source for this <br />land acquisition. At this time it is uncertain whether this land acquisition <br />should be with federal funds or if we should use city municipal state aid <br />street funds. Information on the Evergreen recommendations will be <br />presented to the Council on September 14th. Evergreen also continues to <br />work with the Browns on negotiating a price for their property. At this time, <br />Evergreen has not yet been authorized to work the Kirkeide family who owns <br /> <br />\\elkriver\sys\shrdoc\council\easter2.doc <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.