Laserfiche WebLink
CRDSS <br />TASK MEMORANDUM 1.08-2 <br />Historical Database <br />Year 1 Summary <br />1.0 ISSUE <br />The purpose of this task memorandum is to document the historical database task activities performed <br />during Year 1. <br />2.0 DISCUSSION/ANALYSIS <br />The primary focus of the database effort was to create a populated database to support the modeling <br />efforts. During Phase I, the database design was formulated, and construction of the database began. <br />Beginning in Phase IIa, the database design was refined, and database construction and population <br />continued. As part of this effort, database utility programs were created to partially automate the <br />population process and to make administration of the database easier. Once this important database <br />creation and population phase produced a workable and populated structure, data management interface <br />(DMI) libraries were built to allow access to the database. Character-based displays were built using the <br />INFORMIX tools as a prototyping tool, debugging tool, and a tool to verify database contents. Also, <br />other displays were built to prototype other ways of viewing the time series data and to test different <br />ways to access the database. Comments from potential users were collected through the user <br />involvement process, and this user input will be used to improve the database and displays as part of <br />Phase IIb. <br />The progress on the historical database task is summarized first by a brief discussion of the work <br />products as specified in the scope of work. Then, important parts of the work plan will be discussed, <br />particularly where products were produced that were not discussed in the work products section. <br />Work Products <br />1.A historical time series database populated with the data needed to develop the CRDSS <br />prototype on the Gunnison River basin. <br />Table 1 summarizes the data types and progress made in populating the database during Phase IIa. The <br />data types in Table 1 are those identified in Phase 1. Overall, much more data were populated than the <br />project team had originally planned for several of the data types. The State's management team set a <br />high priority on data population. Also, some of the data that were originally intended to be populated <br />into the database were not available or there was a delay in obtaining the data in time to be populated <br />during Phase IIa. There are several related points that need further explanation. <br />Streamflow, temperature, and precipitation are examples of environmental data available from <br />? <br />public agencies. Data for the entire state west of the Continental Divide were populated into <br />the database during this phase. The State's management team emphasized the importance of <br />this data, so a high priority was placed on population of the data. Also, delays were <br />encountered in obtaining some of the rest of the State Engineer?s Office data (Irrigated Acreage <br />1 <br />A275 01.09.95 1.08-2 Greer <br />