My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC06213
CWCB
>
Water Supply Protection
>
Backfile
>
17000-17999
>
WSPC06213
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 10:22:22 AM
Creation date
10/9/2006 5:44:52 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8283.200
Description
Colorado River Basin-Colorado River Computer Models-Colorado River Decision Support System-Ray
State
CO
Water Division
5
Date
4/5/1994
Title
Consumptive Use Modeling-Task 1.14a-Evaluation of Consumptive Use Models-Consumptive Use Data Input Requirements
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
7
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />Qv.i529 <br />" Task 1.14(a) - Evaluation of Consumptive Use Models <br /> <br />Phvsical Characteristics Database <br />The Physical Characteristics Database will store "static" attribute data. <br /> <br />Station and UseT Databases <br />These Databases will store infonnation about the users of the CRDSS and geneTal <br />infonnation about weather stations such as reliability of data and contacts for obtaining <br />data. <br /> <br />Scenario Database <br />We are assuming the Consumptive Use model will be generating some of its own <br />"data" in the form of "what if' scenarios and modeling, These data may be more <br />efficiently stored outside the model and a consistent process for handling the generation of <br />scenarios should be developed, <br /> <br />1.3 Unit Types for Data <br />Representation of units will be a majoT factor in detennining the quality and ease-of - <br />use for the system. There are often different choices of units for any given data field. <br />Sometimes the source of the data will determine the units for data storage, but the user <br />may define how those units are expressed in the interface. Therefore, in this document the <br />unit-less quantity names will be used and some standard unit types will be anticipated for <br />the expression of the quantities. <br /> <br />Table 1: Unit TYpes <br /> <br />Unltless Quantity Name <br />Length <br />Volume <br />Area <br />TIme <br />Date <br />Temperature <br />Flow (volumellime) <br />Velocny (Iengthllime) <br />Location <br /> <br />Metric Representation <br />meters (m) <br />cubic meter (m3) <br />hectares <br />hour, day, week. month, year <br />day/month/year <br />degrees Celsius fC) <br />cubic meters per second (ems) <br />meters per second (m/s) <br />Universal Transverse Mercator (UTM) <br /> <br />Standard Representation <br />feet (It) <br />acre-feet (acre-It) <br />acres <br />hour, day, week, month, year <br />julian days <br />degrees Fahrenheit (OF) <br />cubic feet per second (cis) <br />miles per hour (mph) <br />Latitude and Longnude (LatILong) <br /> <br />2.0 Baseline Scenario Data <br /> <br />When the user accesses the model he/she will be presented with information that will be <br />stored as a baseline scenario and will be asked to specify certain parameters needed to <br />estimated consumptive use. These values may be used as default values or altered by user <br />input and will specify which data the DMI returns to the CU model. <br /> <br />4/5/94 - Evaluation Document (for internal use) 2 <br /> <br />Database Requirements: CSU- AD05 <br />
The URL can be used to link to this page
Your browser does not support the video tag.