My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
03-25-1991 Council Minutes
Orono
>
City Council
>
1991
>
03-25-1991 Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/30/2019 8:27:43 AM
Creation date
4/30/2019 8:27:41 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
34
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
REGULAR CITY COUNCIL MEETING HELD MARCH 25, 1991 <br />($12)HIGaV ?AY 12 CORRIDOR RECOMMENDATION CONTINUED <br />necessary for us to take a stand against a certain highway <br />design. We are not design engineers, such a recommendation may <br />lead us into a fight with MNDOT over design, and. at this point we <br />do not know what MNDOT is going to propose. I am not sure that <br />including a recommendation regarding the type of road ..we would <br />like, will yield the results we want. Perhaps it would be more <br />appropriate for Council to indicate gnat we agree with the <br />recommendation, particularly in regard to the corridor location <br />and the necessity to not have any a3ditional east /,vest access, <br />and those items which more directly relate to the location of the <br />corridor. We could then work on a draft to send to PINDOT. I do <br />not feel that we are pressed at this point to get this to MNDOT, <br />and some of the things we will be saying will give them an <br />opportunity to divert our attention.' Goetten believed that the <br />recommendation, as presented by the Planning Commission, provides <br />the City with a negotiating tool. Callahan stated that the point <br />of negotiating has not been reached yet, because MNDOT has not <br />taken a position. He said, "However, once we send this document, <br />we will be making them aware of our position, and yet we have not <br />take_Z a precise position on design. We have narrowed PINDOT's <br />choices. I would vote in favor of accepting the recommendation, <br />even though I may not come to the same conclusions regarding the <br />gray areas of design. I would figure that as the plan develops <br />from our point of view that we could adjust it as things begin to <br />happen. If I were adopting this -recommendation, :based solely on <br />what the .City would like to do, I would have no problem with <br />that." Jabbour suggested, in light of Goetten's and Callahan's <br />concerns, that it may be appropriate for Council's motion to <br />include adoption of the recommendation only, and reserve the time <br />frame for sending it to MND,.)T at a. later. Butler stated that <br />obviously the document before them would not be stuffed into an <br />envelope and Mailed to MND.:)T tomorrow. She said, "A cover letter <br />will have to be drafted explaining our position. When working <br />with the County Highway Department on County Road 15, they had <br />taken a position that the road had to be upgraded to a four -lane. <br />The three Cities got together and provided them with a position <br />that they could do anything within.the existing right -of -way, and <br />that we wanted the road paved and striped in accordance with its <br />usage. The County officials were pleased to have had that <br />direction and proceeded to do exactly what we had asked them to <br />do." Goetten agreed with Jabbour that a cover letter could be <br />drafted and presented at the April 8, 1991 Council meeting prior <br />to sending the recommendation to MNDOT. She stated that the <br />newspapers will publish the City's recommendation, so the <br />citizens will know. Butler noted that her motion was to accept <br />the recommendation and send it to . MNDOT, but did not include a <br />specific time for sending it. <br />Mayor Peterson recognized Maureen Bellows. <br />- 27 - <br />
The URL can be used to link to this page
Your browser does not support the video tag.