Laserfiche WebLink
Within each basin, several official State data sets are maintained to archive the calibration and <br />simulation phases of modeling as follows: (Note these naming conventions are not a requirement of <br />the model, simply a data management convention for official State data.) <br />File Name Descri tion <br />basin name.* Generic basin files <br />Basin nameTBF* Basin files s ecific to the baseflow eneration rocess. <br />basin_nameH.* Basin files specific to the historical data set (e.g. historical diversion and <br />reservoir time series . <br />basin_nameC.* Basin files specific to the calculated data set (e.g. calculated demands from the <br />consum tive use model, reservoir tar ets rather than historical EOM contents . <br />basin_nameB.* Basin files specific to the baseline data set (e.g. current conditions for <br />reservoirs and munici al, industrial and transmountain demands . <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.5 Data Centered Model Development <br />The water resources planning model data presented in this report was developed using a fully <br />integrated data centered approach which allows information to flow from a central database to <br />StateMod input files using programs called Data Management Interfaces (DMI's). In very general <br />terms, a DMI does the following: <br />• Takes auser-supplied list of commands and structures to be modeled. <br />• Accesses the database to select data associated with those structures. <br />• Revises or adds to information found in the database. <br />• Formats information for use by the Water Resource Planning Model, StateMod. <br />• Provides one or more reports of the DMI operation. <br />The above procedure is extremely efficient because it (1) allows new structures or information to be <br />added quickly and efficiently once the central database is updated, (2) allows the user to focus on the <br />system operation without being burdened with model input formats, (3) is self-documenting by <br />automatically transferring the user-supplied commands file to a header on top of each output file, and <br />(4) recognizes that official data stored in the database often needs enhancement before it can be used <br />for modeling. Two examples of such a required database enhancement are as follows: The San Juan <br />Chama diversion in Division 7 has historically diverted water from Colorado to New Mexico but has <br />no decreed water rights. The Government Highline diversion in Division 5 has historic diversion <br />records that represent several users that must be broken into individual irrigation and power users for <br />modeling purposes. <br />The following is a summary of the ten steps taken to construct the Gunnison Model input files using <br />a data centered approach. <br />Step -1 Network and River Station Files To create the StateMod Network and River Station files, <br />the user must develop a network file (*.net) that contains all diversions, reservoirs, instream flow <br />reaches, and streamflow gages to be included in the model, and a file of makenet commands <br />Model Development 3-4 <br />