My WebLink
|
Help
|
About
|
Sign Out
Home
Search
10/26/2005 Env Bd Packet
LinoLakes
>
Advisory Boards & Commissions
>
Environmental Board
>
Packets
>
2005
>
10/26/2005 Env Bd Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/6/2014 11:11:58 AM
Creation date
8/5/2014 11:51:47 AM
Metadata
Fields
Template:
Environmental Board
Env Bd Document Type
Env Bd Packet
Meeting Date
10/26/2005
Env Bd Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
61
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
ENVIRONMENTAL BOARD MEETING OCTOBER 12, 2005 <br />Grochala stated that this was volume control, and was the first time it had been <br />intentionally addressed. Asleson added it was being dealt with adequately after <br />eight years. <br />Grochala noted that the AUAR was setting the limit, what were the resulting <br />repercussions. They received good comments from the agencies. Dan Huff from <br />the Friends of the Mississippi was invited staff to a meeting, but staff had already <br />attended the workshop. Dan Huff indicated the organization had decided to <br />concentrate on cities not adequately dealing with the issues. Grochala indicated <br />that there was probably more internal struggle than with other agencies. He stated <br />there was a 3 -2 vote for distribution, and commented it might not be approved. If <br />approved, it would assist in the Comprehensive Plan update in the region. The <br />other areas of the City were still unknowns. <br />Kukonen asked for clarification that the scenarios were really aggressive. <br />Grochala explained that each area needed a land use designation. They did not <br />spend time analyzing the areas of low density. The focus was on the medium and <br />high density areas, recognizing that things could change. <br />Chair O'Dea questioned staff on comments that could be made to indicate the <br />AUAR was a worst case scenario. She noted it was not explicitly stated that the <br />scenarios were the extreme situation, and did not mean that development should <br />occur this intensively. Grochala indicated there was no difference between the <br />AUAR and the Comprehensive Plan for most people. <br />Chair O'Dea clarified it needed to state that the AUAR was not and did not <br />replace the Comprehensive Plan. <br />O'Connell referred to page 5, "whenever a certain impact may or may not <br />occur..." Grochala reviewed the requirement of the worst case scenario out of the <br />Minnesota Rules. <br />O'Dea mentioned it appeared the objections were that the document could not be <br />supported, because the worst case scenario could not be supported. Grochala <br />stated that the City now knew what could be mitigated, and the necessary <br />measures for it. <br />Kukonen inquired if "level of service standards" might come into play. Grochala <br />affirmed that it would because the function of an intersection could be rated by <br />measuring the time it takes to proceed through an intersection. In the mitigation <br />plan, the levels of service standards were addressed on a global scale. He added <br />the domino effect of micro - analysis was not good for long -term assumptions. In <br />reviewing projects, if the developer met the requirements, the City did not have <br />much of a margin of discretion. A developer could fund infrastructure <br />improvements, or the project might not be approved because the present <br />3 DRAFT MINUTES <br />
The URL can be used to link to this page
Your browser does not support the video tag.