My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
PERMFILE60710
DRMS
>
Back File Migration
>
Permit File
>
700000
>
PERMFILE60710
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 11:07:31 PM
Creation date
11/20/2007 6:49:36 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1983148
IBM Index Class Name
Permit File
Doc Date
1/10/1984
Doc Name
MONTROSE COUNTYS LIMITED IMPACT APPLICATIONS FILE 83-148 THRU 83-153 83-157 THRU 83-163 adequacy iss
From
MLRD
To
MONTROSE COUNTY
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.
/
4
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 />t~1r. Patrick Marren -2- January 10, 1934 <br />2. The staff encourages the operator to post (flayginy, stakes, etc.) the <br />permit boundaries and topsoil stockpiles. This posting is not required by law <br />but will provide for a more orderly operation and may aid tin avoiding possiole <br />future problems involving permit area - property boundary conflicts and <br />unauthorized topsoil removal. <br />3. A location map showing common access from readily identifiable roads, <br />proximity to towns, etc. should be provided for each site in order to <br />facilitate easy location during field inspections. Please note tnat, for some <br />of the sites, this is possible to interpret per the topographic maps and other <br />maps provided -- other applications do not. One of the applications nos a <br />general county map showing these. It is good. Perhaps you have enough copies <br />to provide this for the other applications. <br />4. As enlarged site map (hand-drawn in acceptable) should be provided for <br />each pit snowing: permit boundary; landowners immediately adjacent to the <br />permit boundary; areas of remaining topsoil resource; topsoil stockpiles; <br />general direction of mining; drainages; manmade water transporting structures <br />such as canals; access road; significant, pennanent, valuaole manmade <br />structures located within 200 feet of the permit boundary; scale, north arrow. <br />5. Because of the droughty conditions experienced at most of these sites, <br />we recommend that all final slopes oe graded to no steeper than 3:1 (h:v), and <br />preferably 4:1. <br />6. The plans should indicate the minimum thickness of topsoil to oe <br />replaced. Consideration should be given to the amount of remaining resource <br />and the area to be covered, and other possiole measures which could oe <br />provided if the topsoil would have to be spread to thicknesses less tnan <br />approximately 6 inches. <br />7. Several of the applications (83-148, 83-150, 83-153, 83-160, 83-161, <br />83-207) do not give a specific seed mixture (with rates), or the plan proposes <br />natural invasion as a preferred means of revegetation. <br />Rule 6.5 should be reviewed for additional information governing revegetation <br />of disturbed lands. In general, these applications should include a plan for <br />reveggetation which will include, but not be limited to, development of plant <br />growth medium, incorporation of appropriate amendments (eg. fertilizer, <br />mulch), seeding infix and other cultural practices necessary for establishment <br />of the vegetative stand. <br />8. A plan for the reclamation of access roads mould be provided. <br />9. Grazing of re vegetated areas should be pronibited until vegetation has <br />had an opportunity to establish. <br />Other <br />File fJo. 83-153 is rather confusing as to whether this is a dryland pit or <br />otherwise. The Division of Wildlife impact report indicates that operation <br />will be in the stream, but inucn of your application sugyests that it will oe <br />another dry pit. Please clarify this matter. <br />
The URL can be used to link to this page
Your browser does not support the video tag.