My WebLink
|
Help
|
About
|
Sign Out
Home
pf_03338
Roseville
>
Planning Files
>
Old Numbering System (pre-2007)
>
PF3000 - PF3801
>
3300
>
pf_03338
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/17/2007 1:29:43 PM
Creation date
12/9/2004 7:26:11 AM
Metadata
Fields
Template:
Planning Files
Planning Files - Planning File #
3338
Planning Files - Type
Planned Unit Development
Address
3015 CENTRE POINTE DR
Applicant
CENTRE POINTE/SOLUTIA
Status
Approved
PIN
052923110037
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.
/
466
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 />According to the MPCA, noise monitoring, is recommended, although not required: <br />III To establish baseline levels and indicate if a noise problem already exists. <br />· To calibrate the noise analysis model, thereby lending greater reliability to its estimates. <br /> <br />Noise monitoring was conducted at the intersections of County Road C and Cleveland and <br />County Road D and Cleveland on December 29,2000. Although residential areas are located <br />significantly far from the intersection of Cleveland and County Road C, residences are located <br />in the southeast quadrant of Cleveland and County Road D, Refer to the following table for <br />noise monitoring results. The noise monitoring was done using an Ametek Model Mark 3 <br />Audio Dosimeter. <br /> <br />It can be seen from the results of the noise monitoring (see table below) that current traffic <br />noise levels currently exceed the Minnesota Residential noise standards at County Road D and <br />Cleveland. It is anticipated that a significant portion of the noise levels observed are <br />attributable to traffic on Interstate 35W immediately west ofthe development. <br /> <br /> Traffic Noise Momtorim <br />Monitoring Point Morning Rush (7-9 a.m.) Evening Rush (4:30-6:30 p.m.) <br /> LIO (dBA) L50 (dBA) LIO (dBA) L50 (dBA) <br />Intersection of 74.24 64.40 69.2 60.0 <br />Cleveland and Co. <br />Rd.D <br />Intersection of 71.3 64.9 71.9 62.4 <br />Cleveland and Co. <br />Rd.C <br /> <br />Noise impacts from post-project traffic volumes were evaluated using the STAMINA 2.0 <br />(FHW A 1982) model provided by MnDOT. STAMINA 2.0 predicts A-weighted noise levels <br />(LEQ, Ll 0, L50 and L90) based on traffic volume, speed, and vehicle type. For this analysis, <br />vehicles were placed into three categories: cars, medium trucks, and heavy trucks. <br /> <br />As indicated above, the main source of the noise causing the measured exceedances appears to <br />be from Interstate 35W. However, the principal source of any additional noise anticipated to be <br />caused by the proposed development is from additional traffic generated along the roadways <br />surrounding the development, mainly Cleveland, County Road C and County Road D. The <br />nearest residences are located near the intersection of County Road D and Cleveland. Other <br />potentially noise sensitive areas would include any nearby schools, churches or parks, hotels, as <br />well as outdoor restaurants. A hotel (receptor #3) and an office (receptor #4) have been <br />included in the modeling as well. <br /> <br />Only daytime (rush hour) impacts were predicted using STAMINA 2.0. Nighttime noise <br />standards only differ from daytime noise standards in residential areas. Residential areas <br />located in close proximity to the development are not expected to experience significant <br />increases in noise levels. In addition, peak nighttime traffic is assumed to be 78 percent of the <br />peak daytime volume, using MnDOT methods. <br /> <br />Environmental Assessment Worksheet <br />Centre Pointe Business Park <br /> <br />Page 24 of 29 <br />
The URL can be used to link to this page
Your browser does not support the video tag.