Laserfiche WebLink
Item -by -item guidance Chapter <br />of the project will be unusually noisy — the blasting of rock, for <br />example; prolonged; affect especially sensitive receptors — a <br />hospital, for example; or otherwise can be expected to have <br />unusual noise impacts during construction. The locations of and <br />distances to sensitive receptors should be given. For projects in <br />the vicinity of major noise sources, such as highways, railroads or <br />airports, noise levels should be estimated using generally ac- <br />cepted noise prediction models, regardless of whether the noise <br />standards are legally enforceable with respect to the project. <br />Mitigation measures should be described, and their effects as- <br />sessed. <br />Projects requiring PCA Indirect Source air quality permits, de- <br />scribed under item 23, often require a noise analysis as part of the <br />permit application, which should be induded in the EAW. <br />• Dust. Wind -blown dust from construction, demolition, haul <br />roads and other activities should be addressed here instead of <br />under item 23 if the quantities of dust will be large, prolonged or <br />otherwise greater than routinely expected during project con- <br />struction. Mitigation measures should be discussed. <br />25. Nearby resources <br />• Archaeological, historical or architectural resources. <br />Contact the State Historical Preservation Office, Minnesota His- <br />torical Society, listed in the appendix, for information about <br />possible archaeological or historical resources at the site. A local <br />"heritage preservation" committee may also provide assistance. <br />Where archaeological resources exist, a site survey by a qualified <br />archeologist may be necessary. Results of the survey should be <br />presented in the EAW. <br />• Prime or unique farm lands and agricultural pre- <br />serves. Information on prime and unique farmlands is available <br />from the Natural Resources Conservation Service or the Minne- <br />sota Planning Office Land Management Information Center. The <br />local unit of govemment (county or city) has information on any <br />established agricultural preserves. <br />• Designated parks, recreational areas or trails. Loca- <br />tions of these may be obtained from the local unit's planning and <br />zoning or recreation office or from the DNR. <br />• Scenic views and vistas. These may include spectacular <br />viewing points along lakes, rivers or bluffs; virgin timber tracts; <br />prairie remnants; geological features; waterfalls; specimen trees; <br />or plots of wildflowers. Many are not officially designated or <br />marked, but because of their local or statewide interest should be <br />considered by the RGU. Impacts on the visual quality or integrity <br />of these resources should be addressed as well as the physical <br />impacts. <br />26. Visual impacts <br />Describe any nonroutine impacts that may be due to the emission <br />of light or a "visual nuisance" caused by the project during con- <br />struction or operation. An example of an emission impact is an <br />intense Tight causing a glare problem for passing motorists. Ex- <br />amples of "visual nuisances" include lights on tall communication <br />towers intruding on the visual integrity of a scenic vista, or a large <br />water vapor plume from an exhaust stack or cooling tower. <br />27. Compatibility with plans and land use <br />regulations <br />Discuss whether the project is subject to any official govemmental <br />management plans adopted for the area. These could indude a <br />local comprehensive land use plan (likely in any city in the Twin <br />Cities metropolitan area); a local comprehensive water plan; or <br />management plans specific to resource areas under public man- <br />agement such as parks, watershed districts or rivers. Plans of all <br />levels of govemment should be considered here: local, regional, <br />state and federal. The local planning and zoning office is probably <br />the best source of this kind of information. <br />If no such plans exist in the area, the EAW should so indicate. If <br />there is a plan, but the project is not subject to the plan, the EAW <br />should indicate why not. <br />If the project is subject to a plan, the EAW should identify its <br />requirements relevant to the project and discuss how the project <br />complies with the plan. The RGU should consult with the govern- <br />ment unit responsible for the implementation of the plan <br />regarding provisions that relate to the project and about the <br />consistency of the project with the plan. Emphasis in the EAW <br />should be given to any conflicts or incompatibilities between the <br />project and plan provisions that relate to the environment or use <br />of natural resources. <br />28. Infrastructure and public services <br />Identify new or expanded public services or public works neces- <br />sary to serve the project such as sewers, storm sewers, streets, <br />water mains, water towers, power lines, gas lines, police protec- <br />tion, fire protection and schools. <br />NOTE: Any infrastructure utilities constructed to serve the project <br />and not independent of this specific project must be treated in the <br />EAW as part of the project for example, a road built to serve a <br />specific project must be treated as part of the project and its <br />impacts should be included in the EAW. According to the EQB <br />rules, all "connected actions" are to be reviewed as one project. <br />Connected actions are defined as projects related in any of the <br />three following ways: (1) one project would induce the other, (2) <br />one project is a prerequisite for another, or (3) neither project is <br />justified by itself (part 4410.0200, subpart 9b). Further guidance <br />regarding connected actions is presented in Chapter 2 of the <br />Guide to Minnesota Environmental Review Rules. <br />Environmental Quality Board 13 <br />