My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
11-18-2019 Planning Commission Packet
Orono
>
Planning Commission
>
2019
>
11-18-2019 Planning Commission Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/19/2019 10:25:24 AM
Creation date
11/19/2019 9:44:17 AM
Metadata
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
521
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
FILE#LA19-000087 <br /> 18 Nov 19 <br /> Page 4 of 5 <br /> corridors and fire lanes as requested,taking into consideration the unique <br /> characteristics of each location, such as topography,water depth and quality, lake <br /> bottom conditions,the type of vegetation, and any potential for related lake access, <br /> drainage, or water quality improvement." (Part 4A, Page 23) <br /> These policies are a departure from past practice,when the Council would not consider a <br /> vacation. <br /> The nearest lake access is approximately 670 feet to the east, between 4075 and 4051 <br /> Highwood. That lake access appears to be less overgrown and has a more gradual grade to the <br /> lake.That access also includes utility improvements,with a storm sewer. <br /> The Council, in approving recent lake access vacations (Case No. LA19-000017 Paidosh) has <br /> accepted an easement to protect existing infrastructure. In that application,the City Council <br /> considered the proximity and the number of lakes accesses within that same bay. Lake accesses <br /> are shown on the 4E-2, attached as Exhibit F. <br /> Staff has noted confusion on the part of commenters regarding the "drainage-way" notation on <br /> the Lake Access Points map in the Parks section, attached as Exhibit F. The notation is intended <br /> by the drafters to identify the main use of the access. This notation is not intended as a <br /> limitation on other uses. The transportation section does not identify the designated use in the <br /> same manner as the parks section. The neighbor comments indicate a history of using this alley <br /> to access the lake in summer and winter for recreation. <br /> DNR Comments <br /> The Minnesota Department of Natural Resources has this request under review. A <br /> representative from the DNR, Nancy Spooner-Mueller, contacted staff with questions about the <br /> location of the vacation and indicated that comments would be forthcoming. She offered that <br /> the DNR recommendation was likely to be consistent with feedback in the past, and they would <br /> likely oppose the vacation.Their analysis indicated that the proposed vacation does not provide <br /> a public benefit nor does it protect future public use of the land to access the lake. Formal DNR <br /> comments have not been received;they are anticipated prior to the City Council's review on <br /> December 9th <br /> Public Comments <br /> Staff received written comments from neighbors which are attached as Exhibit L. <br /> Issues for Consideration <br /> — Does this request follow the Comprehensive Plan? <br /> — Does this request meet the statutory requirements for approval? <br /> — Would approving this action set precedent for future lake access vacations? <br /> — Are there any issues or concerns with this application? <br /> Planning Staff Recommendation <br /> Staff recommends denial of the request to vacate the right-of-way for the following reasons: <br /> 1. State Statute. The improvements within the right of way establish public purpose; state <br /> statute does not support vacation. <br /> 2. Finality. Vacation is final, and to reestablish access will in most cases be cost prohibitive. <br /> 3. Options. Vacation reduces options the Council can consider in the future. <br />
The URL can be used to link to this page
Your browser does not support the video tag.