Laserfiche WebLink
<br />/"003J31 <br />-. Definition of Data Requirements <br /> <br />e <br /> <br />e <br /> <br />Having detennined the user needs and required models for providing <br />information and analysis, the next step in the study concerns reviewing the data <br />required to support all this. Not only does such an inventory provide a good <br />overview of the efforts needed to support CRDSS with appropriate data, it also <br />serves as the basic inventory from which CRDSS data acquirement cost <br />analyses can be made, <br /> <br />Inventorying data to support the tasks mentioned in the various user scenario's <br />reyealed a need for over 100 pieces of data, Iii Appendix D, Tables n:l <br />through D-14 represent these data requirements. <br /> <br />Data were categorized into the following seven categories: <br /> <br />Spatial data refer to information defined by coordinates on the surface of the <br />earth (e,g. latitude. longitude. etc,). Some of the spatial data are points (e,g, <br />stream gage locations). some are lines (e.g. narrow streams and rivers), others <br />are polygons (e.g. reservoirs). and some are rasters (e.g, satellite images), <br /> <br />A station is defined as a physical device that measures something (e,g, <br />streamflow) or physical device where something impacts the river system (e.g, <br />diversion strUcture). Most stations are point features thaI are already <br />represented in the spatial data. Additional non-spatial, descriptive information <br />is stored/managed as station data attributes (e.g, station name. station type. <br />etc,) <br /> <br />Physical characteristics data describe "static" physical characteristics of <br />features (e.g. diversion strUcture capacities, bank storage characteristics of a <br />reservoir, etc.), These characteristics are considered static because. for the <br />most pan. they rarely change over time, <br /> <br />Near real time/historical data represent time series of what has actually <br />happened at a location (e.g. what are the historical and current "states" of <br />features in a river basin. e.g. river flow, reservoir storage, etc.). <br /> <br />Model inputs/outputs represent scenarios of what "might be." Typically, the <br />inputs are composed of real and/or hypothetical physical characteristics and <br />time series. Model outputs are typically hypothetical time series (e.g, <br />forecasts). <br /> <br />Policy data refer to characteristics of the river system which directly or <br />indirectly relate to the achievement of specific policy goals and/or objectives. <br />These data are frequently expressed in terms of operational constraintS and/or <br />operational targets, <br /> <br />User data represent administrative information about users and are used to <br />distribute and collect information to/from users of the CRDSS, <br /> <br />Each of these data categories were summarized in a parr of tables, Tile first <br />table presents the relationship between user scenario needs and the specific <br /> <br />Spatial Data <br /> <br />Station Data <br /> <br />Physical <br />Characteristics <br /> <br />Near Real Time <br />Historical Data <br /> <br />Model Input/Output <br /> <br />Policy Data <br /> <br />User Data <br /> <br />DAMES& MOORE/CADSWES-20 <br />