My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 09/23/2003
Ramsey
>
Public
>
Agendas
>
Council
>
2003
>
Agenda - Council - 09/23/2003
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/24/2025 3:54:18 PM
Creation date
9/22/2003 7:34:35 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
09/23/2003
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.
/
486
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
AUAR. The action of officially mapping lands along TH 10 would have no <br />impact on the Blanding's turtle, therefore no mitigative actions are necessary. <br /> <br />12. <br /> <br />Physical impacts on water resources <br />Will the project involve the physical or hydrologic alternation - dredging, filling, stream <br />diversion, outfall structure, diking, and impoundment - of any surface waters such as a lake, <br />pond, zoetland, stream or drainage ditch? __ Yes X No <br /> <br />If yes, identify water resource affected and give the DNR Protected Waters Inventory number(s) <br />if the water resources affected are on the PWI: . Describe measures to <br />minimize or avoid adverse impacts. <br /> <br />For an AUAR, the information called for on the EAW form should be supplied for any of the <br />infrastructure associated with the A UAR development scenarios, and for any development <br />expected to physically impact any water resources. Where it is uncertain whether water resources <br />will be impacted depending on the exact design of future development, the A UAR should cover <br />the possible impacts through a "worst case scenario" or else prevent impacts through the <br />provisions of the mitigation plan. <br /> <br />13. Water Use <br /> Will the project involve installation of abandonment of any water wells, connection to or changes <br /> in any public water supply or appropriation of any ground or surface zoater fincluding <br /> dewatering) ? Yes X No <br /> If yes, as applicable, give location and purpose of any new wells; public supply affected, changes <br /> to be made, and water quantities to be used; the source, duration, quantity and purpose of any <br /> appropriations; unique well numbers and DNR appropriation permit numbers, if known. <br /> IdentiJid any existing and new wells on the site map. If there are no wells known on site, explain <br /> methodology used to determine. <br /> <br />If the area requires new water supply wells specific information about that appropriation and its potential <br />impacts on groundwater levels should be given; if groundwater levels would be affected, any impacts <br />resulting on other resources should be addressed <br /> <br />14. <br /> <br />Water-related Land Use Management Districts <br />Does any part of the project involve a shoreland zoning district, a delineated l O0-year flood plain, <br />or a state or federally designated wild or scenic river land use district? <br /> <br />Yes X No <br />If yes, identiJ~j the district and discuss project compatibility with district land use restrictions. <br /> <br />For an A UAR, such districts should be delineated on appropriate maps and the land use <br />restrictions applicable in those districts should be described. If any variances or deviations from <br />these restrictions within the A UAR area are envisioned, this should be discussed. <br /> <br />15. <br /> <br />Water surface use <br />Will the project change the number or hype of watercraft on any water body? Yes __ <br /> <br />If yes, indicate the current and projected watercraft usage and discuss any potential <br />overcrowding or conflicts zoith other uses. <br /> <br />X No <br /> <br />RAMSEY TH 10 CORRIDOR AUAR 14 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.