My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
04-14-08-R
ArdenHills
>
Administration
>
City Council
>
City Council Minutes
>
2000-2009
>
2008
>
04-14-08-R
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/8/2012 5:00:00 PM
Creation date
5/13/2008 12:24:44 PM
Metadata
Fields
Template:
General
Document
Regular City Council Meeting Minutes
General - Type
Minutes
Date
4/14/2008
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
30
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
<br />ARDEN HILLS CITY COUNCIL - April 14, 2008 <br /> <br />12 <br /> <br />Mr. Chromy stated that both current and future noise levels were looked at in the Highway 10 <br />noise study using the MINNOISE model. <br /> <br />Mr. Dale Maul, Environmental Planner from Bolton & Menk, provided information and <br />examples of noise levels and what they mean. He also presented State and Federal noise <br />abatement criteria and the study procedures and finding to the Council. He explained that the <br />noise analysis was prepared to evaluate whether noise barriers are warranted, feasible, and <br />reasonable or cost effective and that minimum levels had to be reached for each criteria in order <br />to proceed to the next level to determine if the noise barrier will be paid for with federal funding. <br /> <br />Mr. Chromy stated that there were four areas that were evaluated for noise barriers. These are <br />Round Lake noise barrier I which is 870' long and protects 5 homes, Round Lake noise barrier 2 <br />which is 2000' long and protects I 1 homes, Round Lake noise barrier 2 extension which is 3400' <br />long and protects 21 homes, and noise barrier east of Highway 10 which protects 4 homes. He <br />stated that even though the first three areas would benefit from noise barriers, the noise analysis <br />conclusion was that it was not cost effective or reasonable for use of Federal funding. Ifthe City <br />chose to have these barriers constructed then they would have to obtain funding through other <br />means. <br /> <br />Councilmember McClung requested that Staff provide the noise analysis documentation from <br />the 694 Project. He asked how it was determined that only four homes were impacted by the <br />noise along the east side and how was the Federal Activity Category selected. <br /> <br />Mr. Maul stated that the land use was reviewed and it was determined that under FHW A Noise <br />Abatement Criteria the Federal Activity Category B most closely fit the land use types for the <br />area. The number of homes was determined because they went a given distance from the road <br />for the decibel level and then they picked these four homes for receptor areas. <br /> <br />Councilmember McClung stated that by only having four homes or receptors, there were other <br />homes that were impacted that were being omitted. He then asked if these homes were included <br />if it would make the project more cost effective and qualifying it for TH I 0 funding. <br /> <br />Mr. Chromy stated that the homes north of Briarknoll had not made it into the cost effective <br />analysis because there was not enough attenuation provided at any of the receptors to make the <br />barrier acoustically effective. <br /> <br />Councilmember McClung stated that page 10 of the SEH report discusses the noise barriers <br />east of Highway 10. <br /> <br />Mr. Chromy stated that as you add more houses more receptors are added and more decibels to <br />monitor and the further from the highway the lower the decibel readings would be. These factors <br />would not decrease the cost amount per decibel per house but rather increase this amount. <br />Receptors are identified as the most affected residences. <br />
The URL can be used to link to this page
Your browser does not support the video tag.