My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 08/24/2010
Ramsey
>
Public
>
Agendas
>
Council
>
2010
>
Agenda - Council - 08/24/2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/18/2025 2:43:58 PM
Creation date
8/19/2010 3:08:41 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
08/24/2010
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.
/
330
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
Proposed Draft MRCCA Standards <br />The following standards apply corridor -wide, unless specified otherwise. <br />Sheet 5b: Facilities <br />Prepared by Minnesota Department of Natural Resources, August 5, 2010 <br />Standard <br />Draft Standard Narrative <br />Private roads, driveways, and parking areas must be designed to take advantage of natural vegetation and <br />General <br />topography to achieve maximum screening from view from the river or the OHWL of the opposite shore. They must <br />Design <br />be designed and constructed to minimize and control runoff and erosion to public waters consistent with Minnesota <br />Stormwater Manual and Protecting Water Quality in Urban Areas <br />Roads, driveways, parking areas must meet structure setbacks and must not be placed on bluffs or within slope <br />Placement <br />preservation zones (SPZ) or shore impact zones (SIZ). <br />Private Roads, <br />Private Roads <br />Low-volume private roads or privately maintained roads shall have pavement widths of < 22 feet. <br />Driveways & <br />Parking areas with > 10 spaces or > 3,000 square feet must be designed to permanently treat 1" of runoff from the <br />Parking Areas <br />impervious surfaces created. Preference must be given to volume reduction techniques. Runoff reduction may be <br />Private <br />accomplished through use of soil amendments, infiltration, bioretention, permeable pavement, rain gardens, <br />Parking Areas <br />enhanced swales, disconnected impervious surfaces, or other LGU-approved reduction techniques. If the runoff <br />reduction standard is not physically possible due to physical characteristics of the site, mitigation will be required <br />A private watercraft access ramp and associated access path may be allowed within the shore impact zone provided <br />Private Water <br />the requirements of chapter 6115, the buffer standards, and erosion and stormwater control standards are met. The <br />Access <br />access path must not be placed on a bluff or within the SPZ. <br />Design for public roads, rail lines, trails, and recreational facilities must preserve or enhance vegetation and <br />topography when reasonable and consistent with the purpose of the facility to aid in screening of these areas from <br />Screening <br />view from the river and the OHWL of the opposite shore. <br />Public <br />Transportation & <br />Public roads, rail lines, and non -water -oriented structures including parking & other impervious areas must meet <br />Recreational <br />Setbacks <br />structural setbacks and must not be placed within shore and slope preservation zones when there are reasonable <br />Facilities <br />placement alternatives exist, consistent with the purpose of the facility. <br />Water -oriented parking areas and approach roads must not be placed on bluffs or within the SIZ and SPZ when other <br />Water <br />reasonable and prudent placement alternatives exist. Water -oriented facilities, ramp approach roads, and access <br />Oriented <br />paths may be placed within the SIZ and SPZ if construction methods are consistent with the most applicable best <br />Parking Areas <br />management practice standards or guidelines. <br />Prepared by Minnesota Department of Natural Resources, August 5, 2010 <br />
The URL can be used to link to this page
Your browser does not support the video tag.