Laserfiche WebLink
• Two (2) aggregated stock ponds were added to represent stock pond storage not <br />explicitly modeled in Phase II (approximately 4,800 ac-ft). <br />• One (1) aggregated municipal and industrial (M&I) demand was added to represent <br />the remaining M&I consumptive use not explicitly modeled in Phase II <br />(approximately 1,100 ac-ft). <br />• Miscellaneous refinements to the Phase II product (see Section 6.0, Calibration) <br />Three data sets were developed for the White Model: historic, calculated, and baseline. The historic <br />data set was used to develop baseflows and calibrate parameters such as return flows. It provides <br />results, which allow the modeled hydrology to be checked against recorded streamflows along with <br />the ditch efficiencies and return flow patterns to be evaluated. <br />The calculated data set uses the historic data set as its foundation, but it allows selected ditch systems <br />and reservoirs to operate by demand. The demands are computed using irrigated acreage and current <br />crop patterns from the State's 1993 geographic information system (GIS) coverage. <br />The baseline data set uses the calculated data set as its foundation; thus allowing selected ditch <br />systems and reservoirs to operate by demand. A baseline data set has been prepared which, unlike the <br />calibration data set, assumes all existing water resources systems were on line and operational from <br />water years 1975 to 1991. This baseline set is appropriate for evaluating various "what if 'scenarios <br />over a long hydrologic time period containing dry, average, and wet hydrologic cycles. <br />3.3 File Directory Convention <br />To assist in file organization and maintenance of the official State data, the files associated with a <br />basin model and the Data Managment Interfaces (DMPs) used to generate that data have been <br />organized as follows: (Note these directory conventions are not a requirement of the model, simply a <br />data management convention for official State data. Also, the directory ./Ts_files is often omitted <br />when time series files are stored in the directory where they are used.) <br />Director Descri tion <br />./statemod/basin name Model data and results <br />./statemod/basin name/Makenet/ Su ortin files for the DMI makenet <br />./statemod/basin name/Watri ht/ Su ortin files for the DMI watri ht <br />./statemod/basin name/Demandts/ Su ortin files for the DMI demandts <br />./statemod/basin name/Tstool/ Su ortin files for the DMI tstool <br />./statemod/basin name/Ts_files Time series files used to replace or supplement <br />database information. <br />./statemod/basin name/GIS/ Su ortin files for the GIS ro ram ArcView <br />Where: basin name = coloupT for the Colorado, gunnT for the Gunnison, sanjuanT for the San Juan, <br />whiter for the White and yampaT for the Yampa. <br />3.4 File Naming Convention <br />Model Development 3-3 <br />