Laserfiche WebLink
<br />o G .t ]~ 1.14(a) - Evaluation of Consumptive Use Models <br /> <br />.... <br />'><::..~ " <br />Vs- ' <br />Vyr <br /> <br />',.J> <br />~ <br /> <br />>~ <br />.,,<>' -^<;' <br />, ~' <br />~'"' <br /> <br />'t <br />(' .(.' <br />\..,.,,~ <br /> <br />Consumptive Use Data Input Requirements <br /> <br />1.0 Introduction: <br /> <br />The goal of this document is to provide RTi and other team members designing and <br />building the databases an idea of the data input needs for the Consumptive Use Model. <br />The Consumptive Use (CU) Model will incorporate GIS capabilities for spatial data <br />TOC' culated an estimated consumptive water use amount for a user specified area <br />over a chosen time frame. The CU model will provide the user with a modeling environment <br />mcludes the selection and modification of parameters. Standard baseline scenarios for <br />model variables will be constructed, but the user will have the option of changing the baseline <br />scenarios to construct alternative scenarios. <br />Once an area and a time frame are selected, the CU model will communicate to the Data <br />Management Interface (OM!) the area being considered, the time frame selected, and the <br />modeling variables that have changed from the baseline scenario. The DMI will access the <br />various databases and return correct data needed for modeling; such as, crop type, planting <br />dates, livestock amounts and type, municipal areas, population density, reservoir <br />characteristics, historical temperature maximum and minimums, etc, These data and <br />corresponding attributes will be passed back to the CU model and an estimated consumptive <br />use amount will be calculated, <br /> <br /> <br />1,1 Core and Fringe Data , <br />Core data will be needed regardless of the final decision about which specific model(s) <br />or mtethod(s) will be used, Fringe data are what individual models may need, but the final <br />decision about the need fOT these data will wait until later in Phase I. Fringe data can also <br />be information that is available from multiple sources and an assessment of the quality of <br />the different sources will determine the final source. Most data can be accurately identified <br />at this point along with the attributes that define the data type. <br /> <br />1.2 Overview of Types of Data Stored in Databases <br />The Physical Characteristics, Historical, User, and Station Databases will reside in <br />Informix and will be relationally designed to allow the user to extract data using <br />Structured Query Language (SQL) or an equivalent method, and the Spatial Database will <br />be based on a geographical information system (GIS). The "Scenario Database" is a <br />concept described in this document for planning purposes. <br /> <br />Soatial Database: <br />The Spatial Database will display data in three graphical formats using a GIS; (1) <br />rasteT maps which are based on a grid system, each cell created by the grid is assigned one <br />value, (2) vector maps which are line segments defined by their end points, connected line <br />segments or polygons can be assigned one value for each polygon, and (3) Icon based site <br />maps with an icon representing the data collection site. <br /> <br />Historical Database <br /> <br />The Historical Database will store historical data, such as climate parameters. This data <br />may be accessed through the models or directly by a station identification number tied to a <br />location saved in the Spatial Database. <br /> <br />4/S/94 - Evaluation Document (for internal use) 1 <br /> <br />Database Requirements: CSU- AOOS <br />