My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2014-07-24_PERMIT FILE - M2014038
DRMS
>
Day Forward
>
Permit File
>
Minerals
>
M2014038
>
2014-07-24_PERMIT FILE - M2014038
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/5/2020 6:43:45 AM
Creation date
7/24/2014 4:01:40 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M2014038
IBM Index Class Name
Permit File
Doc Date
7/24/2014
Doc Name
New 110c Application
From
Routt County
To
DRMS
Email Name
GRM
DMC
Media Type
D
Archive
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
42
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
Public Involvement <br /> A proposal to treat 6,838 acres was listed in the Schedule of Proposed Actions during the last <br /> five quarters ending 9/31/2009. The proposal was provided to the public and other agencies for <br /> comment during scoping from October 6 through November 4, 2008. Field trips were requested <br /> by the public and accommodated by Forest Service specialists. A press release on the scoping <br /> was sent to the area newspaper. <br /> We received five comment letters addressing the proposed project. Using comments from the <br /> public, other federal and state agencies, and local groups, the interdisciplinary team developed a <br /> list of important issues to address. Main issues of concern included, suitable lynx habitat, <br /> watershed degraded sites, noxious and invasive weeds, goshawk nest habitat, wildlife viability, <br /> and protecting regeneration from livestock grazing(see EA pages 14-18). To address these <br /> concerns, the Forest Service specialists refined the alternative described above. <br /> Finding Of No Significant Impact <br /> I have reviewed the direct, indirect, and cumulative effects of the proposed activities in the EA <br /> for the Little Snake North Analysis Area. I have also reviewed the project record for this <br /> analysis and the effects of the proposed action and alternatives as disclosed in the EA. <br /> Regulations from NEPA (40 CFR 1508.27)provide criteria for determining the significance of <br /> effects. A determination of significant, as used in NEPA, requires consideration of both context <br /> and intensity. <br /> (a) Context. This means that the significance of an action must be analyzed in several contexts <br /> such as society as a whole (human, national), the affected region, the affected interests, and the <br /> locality. Significance varies with the setting of the proposed action. For instance, in the case of <br /> a site-specific action, significance would usually depend upon the effects in the locale rather than <br /> in the world as a whole. Both short- and long-term effects are relevant (40 CFR 1508.27); the <br /> disclosure of effects in the EA found the actions limited in context. The project area is limited in <br /> size and the activities are limited in duration. Effects are local in nature and are not likely to <br /> significantly affect regional or national resources. <br /> (b) Intensity. This refers to the severity of impact. Responsible officials must bear in mind that <br /> more than one agency may make decisions about partial aspects of a major action. The <br /> following are considered in evaluation of intensity (40 CFR 1508.27): <br /> (1) Environmental Effects— Environmental effects associated with the project are discussed in <br /> the Environmental Consequences section of the EA (pp. 29-56). These impacts are within <br /> the range of those identified in the Forest Plan and would not have significant impacts on <br /> resources identified and described in the EA. <br /> (2) Public Health or Safety—Treatment activities would be conducted in a safe manner to <br /> protect the public. <br /> 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.