My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Council - 04/25/1995
Ramsey
>
Public
>
Minutes
>
Council
>
1995
>
Minutes - Council - 04/25/1995
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/1/2025 3:54:18 PM
Creation date
7/10/2003 9:37:26 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Council
Document Date
04/25/1995
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
23
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
dealing with same. The Board also adopted a Fire Department Attendance Policy, to <br />become effective July 1, 1995. The services provided by the Fire Department were <br />discussed and consensus of the Board was to maintain current service levels with medical <br />response but to not increase the service level. Discussion also ensued regarding response <br />time and possibly looking at the new Public Works building location as a f'u'e station. <br /> <br />The report was accepted by Council. No further action was necessary. <br /> <br />Case #16: Report from Road and Bridge Committee <br /> <br />City Engineer Jankowski reported that the fa'st case discussed by the Road and Bridge <br />Committee was the Bison Street paving. The purpose of the case was to gain input from <br />the Commission so if a petition was circulated, the number of benefited parties would be <br />determined. It was decided that the number of benefitted lots is six. <br /> <br />Council agreed that the benefitted number of lots is six. <br /> <br />The second item for discussion was the Trunk Highway g47 Corridor Study. Consensus <br />of the Committee was that Mr. Jankowski should draft the study and define the scope. <br /> <br />Council agreed that Mr. Jankowski should continue to work on the scope for the Trunk <br />Highway g47 Corridor Study and that he indicate where the money should come from to <br />pay for this study. <br /> <br />Mr. Jankowski explained that thc third issue discussed was Transportation Impact Fees. It <br />was directed at the City Council workshop to review such fees. We found that several <br />communities extract the fee from developers. The alternative would be to deal with this on <br />a case by case basis. <br /> <br />Consensus of Council was that Staff should pursue developing an impact fee approach to <br />funding improvements on streets. The consensus was to do it via ordinance. 'They also <br />directed that Mr. Jankowski solicit ordinances from other communities and bring the issue <br />back to Council. <br /> <br />Case #18: <br /> <br />Adopt Resolution Receiving Petition and Calling for a <br />Feasibility Study on Improvement Project #95-14 (Municipal <br />Sanitary Sewer and Water Extension' to Haubrich Addition) <br /> <br />City Administrator Schroeder stated it is the normal course of events when the City receives <br />a petition, adopting a resolution receiving it and ordering preparation of plans and <br />specifications is placed on the Consent Agenda. Even though this was a controversial <br />project, it's a standard form. If Council passes this resolution, you are receiving the <br />petition and ordering a feasibility study; it's not stating that the City is for or against <br />anything. When the Engineer comes back with it, the neighborhood can petition against it. <br /> <br />Councilmember Zimmerman inquired how many owners are involved to which City <br />Engineer Jankowski replied there are six properties and five owners. <br /> <br />Councilmember Beyer inquired how many lots are built on to which Mr. Schroeder replied <br />five. <br /> <br />Upon inquiry, Mr. Jankowski stated that this is the entire subdivision. <br /> <br />City Council/April 25, 1995 <br /> Page 22 of 23 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.