My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
6.1. PCSR 01-29-2019
ElkRiver
>
City Government
>
Boards and Commissions
>
Planning Commission
>
Planning Packets
>
2011-2020
>
2019
>
01-29-2019
>
6.1. PCSR 01-29-2019
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2019 9:16:08 AM
Creation date
1/25/2019 9:16:04 AM
Metadata
Fields
Template:
City Government
type
PCSR
date
1/29/2019
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
21
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
18.Submit full MIDSreport. <br />A full MIDS report will be completed during the construction documents phase. <br />Staff will review these documents once they have been submitted. <br /> <br />19.Staff reserves the right to continue review of all site, grading and utilityplans. <br />So noted <br />Environmental: <br />1.MnDNR will follow up with comments regarding requirements for state floodplain and the <br />Mississippi River Wild and Scenic and Recreational requirements. <br />So noted <br />Comments were received from MnDNR on January 11, 2019. Please review attached letter and <br />respond to their concerns. <br /> <br />2.Provide before and after hardcover calculations for the Saxon site. Ordinance limits impervious <br />surfaces to 25% or no net increase. <br />The preliminary plans have been updated with pre and post hardcover calculations for both <br />projects. <br />The plans show a 30.5% hardcover calculation, which does not meet city standards. Please <br />verify your hardcover calculations. <br /> <br />3.Section 30-2022 requires a 30 foot setback from the top-of-bluff. Move structures outside of the setback. <br />Both of these projects are proposed as a PUD which includes the flexibility of building <br />within the 30’ setback from the top of bluff. <br />A deviation from the standard will require approval from the DNR and City Council. Any <br />approved deviations will be memorialized in a PUD agreement. <br /> <br />4.Submitted plans showing the hardcover calculations. Sketches indicate the area inside the <br />building, courtyard, will have impervious surfaces. <br />a.If land along the river is dedicated for park use, the hardcover calculations will change. <br />Updated plans will be required based on park recommendations. <br />The preliminary plans have been updated with pre and post hardcover calculations for both projects. <br />The plans do not match calculated hardcover existing/proposed numbers. The discrepancies <br />need further explanation. <br /> <br />5.The proposed site does not meet setbacks from the Mississippi River, does not meet bluff <br />setbacks and potential grading plans are concerning from an environmental standpoint. Bluff <br />destabilization is the biggest concern overall for proposed project. There is no wetland <br />delineation on file for this site. Any encroachment into the bluff setback or bluff area may <br />require approval from the Department of Natural Resources. As submitted previously, there <br />are height restriction concerns as well. Structures along the Mississippi like this may not be <br />higher than 30 feet tall. <br /> The only proposed site improvements within the 100-foot setback from the 100-year base flood elevation <br />boundary is the expansion of the existing stormwater basin below the bluff. The existing bluff will be protected <br />and monitored by an independent testing company during construction. A wetland determination was completed <br />for this site with no wetlands identified. Height restrictions for both of the proposed buildings will be met. <br /> If hardcover is proposed within 45 feet of a suspected wetland, a wetland delineation will be <br />required. Building elevations showing the proposed heights have not been received and will be <br />
The URL can be used to link to this page
Your browser does not support the video tag.