My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2003-01-29_REVISION - M1998014
DRMS
>
Day Forward
>
Revision
>
Minerals
>
M1998014
>
2003-01-29_REVISION - M1998014
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/15/2021 2:56:04 PM
Creation date
11/21/2007 9:26:31 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1998014
IBM Index Class Name
Revision
Doc Date
1/29/2003
Doc Name
Amendment Application
From
DMG
To
Lafarge West Inc
Type & Sequence
AM1
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.
/
152
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 />~s 15.Z~a <br />MtN~ <br />`T~:.93.5t <br />M,itA1 <br />b. JXDATE and JXTIlVIE Ifthe starting date and time of time series data are the same <br />as the NDDATE and NDTIIvIE on the IT record, then these pazameters are not <br />needed and may be left blank. Using SCS unit hydrograph methods, they aze not <br />required. <br />TABLE P-9 <br />SUGGESTED HYDROLOGICAL TIME SPECIFICATIONS <br />Storm IT Record Range of IT Record IN Record <br />Duration NMIN Appropriate NQ Value JXMIN <br />(hours) Value' Subbasin Tc (#) Value`" <br /> (minutes) Values (minutes) <br /> minutes <br />2 1 4-10 " 130 2 <br />6 00 2 <br />24 5 20 - 50 300 ~_ <br /> 10 ~ 40 - 100 150. 15 <br /> 15 60 - 150 100 15"' <br />'If Modified Puls (Normal Depth-Storage) or Muskingum channel <br />routing is pertormed, NMIN values are involved, and a review of <br />Section V-I-182 (pages P-31 to P-36) and VI-B (page P~1) is <br />recommended. <br />'"When using precipitation data per Appendix "A". <br />""'When the JXMIN value matches the NMIN value, the IN record <br />probably is unnecessary. <br />4. 9 Record The IO record prescribes output options to be used for the entire job, which <br />may be overridden for individual operation components by use of a KO record. The IO <br />record is not required, but the default setting results in full calculations and output that may <br />not be necessary. Use of an IO record is recommended, with revisions on "successive file <br />runs as model refinement proceeds. Data fields and input parameters are discussed below. <br />a. IPRT For the first model run, a value of 4 is recommended, resulting in an output <br />consisting of input data and a master summary. This results in minimal review or <br />printing time to see if the file will run, and can be used to detect major structural or <br />data input errors. On a second nm, I.eve13 is suggested because some error messages <br />may not be printed with higher level settings. <br />P-26 DEC 1994 <br />
The URL can be used to link to this page
Your browser does not support the video tag.