Laserfiche WebLink
<br />drought or excessive floodings, the interruption should not be ignored but rather should be used, if possible, <br />as evidence for adding one or more estimated peaks to the systematic record. Thus, the systematic record is <br />intended to constitute an unbiased and representative sample of the population of all possible annual peaks <br />at the site. <br />In contrast to the systematic record, the historic record consists of annual peaks that would not have <br />been observed except for evidence indicating their unusual magnitude. Flood information acquired from old <br />newspaper articles, letters, personal recollections, and other historical sources almost invariably refer to <br />floods of noteworthy, and hence, extraordinary size. Similarly, the very existence of an indirect streamflow <br />determination outside a period of systematic record suggests that the detennination was made because an <br />unusually large streamflow had occurred. Thus, historic records, by the conditions of their collection, form <br />a biased and unrepresentative sample of flood experience. Despite this bias, however, the historic record can <br />be used to supplement the systematic record provided that all historic peaks above some historic threshold <br />have been recorded. <br />The systematic record may contain one or more peaks for which historic information is available or <br />which exceed the smaller historic peaks. Such peaks are called high outliers. They are used as part of the <br />systematic record but also are treated like historic peaks in the historic-record adjustment procedure. <br />The U.S. Geological Survey maintains a peak flow data base. In the past, these data were stored in <br />the WATSTORE peak flow file. The data are now maintained in the National Water Information System data <br />base. Qualification codes may be assigned to some peaks, identifying (I) basin or environmental conditions <br />that may have affected the magnitude or accuracy of the streamflow value or (2) historical peaks. For <br />example, if the peak is too small to measure, then an estimate of lower bound on the magnitude may be <br />stored (this might occur during a drought period when the actual peak was less than the gage could record). <br />In this case, the peak-flow file would contain a qualification code of 4 (Lepkin and others, 1979) associated <br />with the peak. Note that an individual peak flow can have more than one qualification code associated with <br />it. Table I contains a description of the qualification codes that can be found in the peak-flow file. To make <br />things interesting, peakfq recognizes a subset of peak-flow-file qualification codes and uses a different code <br />to identify these peaks. Table la defines the correspondence between the peakfq and peak-flow-file <br />qualification codes and briefly describes how the peakfq program handles the associated peaks. <br /> <br />Table 1. Streamflow-qualification codes for peak streamflow <br /> <br />Streamflow <br />qualification <br />code <br /> <br />Definition <br /> <br />1 <br />2 <br />3 <br />4 <br />5 <br />6 <br />7 <br />8 <br />9 <br />A <br />B <br />C <br /> <br />Streamflow is a maximum daily average. <br />Streamflow is an estimate. <br />Streamfiow affected by dam failure. <br />Streamflow less than indicated value, which is minimum recordable value at this site. <br />Streamflow affected to an unknown degree by regulation or diversion <br />Streamflow affected by regulation. At least 10 percent of basin controlled by reservoirs. <br />Streamflow is an historic peak. <br />Streamflow actually greater than indicated value, <br />Streamflow due to snow melt, hurricane, ice-jam or debris dam breakup. <br />Year of occurrence is unknown or not exact. <br />Month or day of occurrence is unknown or not exact. <br />All or part of the record affected by urbanization, mining, agricultural changes, channelization, or other <br />activity, The urbanized basins contain at least 10 percent impervious cover. <br />Only peak streamflow recorded for this year. <br /> <br />E <br /> <br />PEAKFO <br /> <br />2 <br /> <br />DRAFT - 1/30/98 <br />