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 />As part of the approval of the Amended PUD and EAW in April of2001 Veritas <br />prepared an update to the ISP Permit Application submitted to the MPCA and <br />approved in 1997. That application included extensive analysis to estimate the <br />potential impact of the proposed project upon air quality in the vicinity of the site. <br />The analysis focuses upon carbon monoxide (CO), which is the primary pollutant <br />of concern with vehicle emissions. Subsequent to the MPCA approving the ISP <br />in June of2001, the State Legislature has repealed the requirements for preparing <br />an ISP. For purposes of responding to this section of the EA W, calculations <br />predicting carbon monoxide levels in the vicinity of the development were <br />utilized from the April 2001 Amendment. Because the increase in traffic is <br />minimal the following analysis is based on the previously approved EA W. <br /> <br />The basic methodological approach used in performing CO calculations for ISP <br />Pennit Applications, and this analysis, is as follows: <br /> <br />1. Establish an assessment year defined as one year following the anticipated <br />occupancy of the project. <br />2. Determine busiest intersection in the vicinity of the project which will be <br />significantly impacted by the project (source intersection). <br />3. Project CO levels generated at the source intersection for the assessment year <br />by non-project traffic in combination with project-related traffic. <br />4. Determine potentially sensitive receptors which could be impacted by CO <br />dispersion from the source intersection. <br />5. Model CO dispersion from the source intersection to the identified receptors. <br />6. Add the CO from the source intersection to projected background CO levels, <br />and compare this sum to state air quality standards for CO concentrations. <br /> <br />The year 2004 has been established as the assessment year (estimated one year <br />after development). Source intersections modeled in this analysis were <br />determined to be the intersection of Cleveland Avenue and County Road C and <br />Cleveland Avenue and County Road D. Vehicular CO generation for 2004 at the <br />source intersection was projected using MOBILE5a with traffic projection <br />information from Benshoof and Associates, Inc. referenced in Response 22. <br />Receptor locations for the modeling study were selected based upon locations <br />where the general population may be during the appropriate averaging times for <br />the MPCA CO standard (one hour and eight hour). The receptor locations used <br />in the ISP analysis for the proposed project are identified in Figure 10. CO <br />dispersion from the source intersections to the receptor locations was modeled <br />using the CAL3QHC model. Background CO levels for the area were based <br />upon historical data projected to 2004 levels taking into account anticipated <br />overall increases in traffic levels and other factors. The methods and procedures <br />used in this analysis were consistent with Indirect Source Permit Application <br />Guidelines provided by the Minnesota Pollution Control Agency. <br /> <br />Page 24 <br />
The URL can be used to link to this page
Your browser does not support the video tag.