My WebLink
|
Help
|
About
|
Sign Out
Home
Search
02/28/2011 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2011
>
02/28/2011 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/29/2014 10:46:20 AM
Creation date
1/27/2014 12:11:28 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
02/28/2011
Council Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
64
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
CITY COUNCIL WORK SESSION February 7, 2011 <br />DRAFT <br />46 The council has more questions and would like to continue discussion of the matter at the <br />47 March work session. <br />48 <br />49 <br />50 <br />51 <br />52 <br />53 <br />54 <br />55 <br />56 <br />57 <br />58 <br />59 When the council asked about how improvements could be funded, Mr. Grochala <br />60 suggested that while funding hasn't been identified for any improvements, cost sharing <br />61 with the watershed district and the site developer would be the most probable. <br />62 <br />63 Developer Gary Uhde told the council that he feels this is an individual concern that <br />64 doesn't represent the homeowners association; he is interested in working on a solution <br />65 but not alone. <br />66 <br />67 The council requested a legal opinion on the possibility of any city liability. <br />68 <br />69 4. Periodic Financial Updates — Finance Director Rolek noted that the council has <br />70 requested periodic financial/budget updates in order that they stay apprised of the status <br />71 of the city budget. He has provided a possible format that includes revenue and expense <br />72 information. <br />73 <br />74 Council members noted that there is interest in seeing the revenue information provided <br />75 by such a report; there is interest in getting as much budget related information as <br />76 possible. A council member distributed written information that he had compiled relative <br />77 to the Centennial Fire District budget, including the approved budget compared with <br />78 expenditures in 2010. He is curious as to why the budget and expenditures don't <br />79 balance. <br />80 <br />81 Finance Director Rolek explained that some fire district expenses are not just to the city; <br />82 some expenses may be paid by Lino Lakes and then reimbursed. <br />83 <br />84 The council directed staff to provide the additional financial information to the council <br />85 regularly and in electronic form. There was discussion about the city's financial <br />86 accounting system (software) and if there is a need to update. A council member also <br />87 suggested that the city utilize a credit card that gives a bonus. <br />88 <br />89 5. 2011 Goal Setting Session — Administration Director Tesch noted that the <br />90 council is interested in a goal setting process; he reviewed the process used in 2009. <br />3. Century Farms North Drainage — Community Development Director Grochala <br />explained that the Century Farm North development includes an area where drainage has <br />been a concern for some time. The city has taken measures to address the situation but <br />the area isn't effectively draining at the current time. It involves an infiltration basin that <br />particularly concerns one resident; the area is inundated with water /ice and attracts <br />waterfowl that in turn cause safety concerns (for the airpark). After a study of the <br />situation, the Rice Creek Watershed District has presented options to address the resident <br />concern with one option being to no- action since no measurable change in water quality <br />would result from improvements. <br />P31 <br />• <br />• <br />• <br />
The URL can be used to link to this page
Your browser does not support the video tag.