Laserfiche WebLink
<br />1,1 ...\ III <br /> <br />South Platte Water Rights Management System <br /> <br />as the plane topology modelID, which in turn would be used throughout the relational <br />model to identify stream gauge data. <br /> <br />1.2 SPRMS Relational Database <br /> <br />This section describes the relational database component of the SPWRMS database. the <br />overall structure of the database, and the categories of the database tables. In addition, <br />table structures and data sources for SPWRMS database are presented. <br /> <br />Relational Database Overview <br /> <br />The South Platte Water Rights Management System Database is an Informix database <br />which consists of two primary types of tables. The first type of table holds static data <br />about the river system and its components, some of which correspond to portions of the <br />SEa database currently maintained in DBase (such as the water rights tabulation and the <br />structures tabulation). Other tables. within this first type, such as the gagingstations table. <br />simply hold names and IDs for elements of the river system. The second typc of table <br />holds dynamic data which is updated regularly by a variety of means (e.g., streamflow <br />tables receive data continuously via satellite telemetry, and Water Information Sheet tables <br />hold data sent in daily by the Water Commissioners). <br /> <br />Upon starting the SPWRMS application, most of the static data are read in during initial- <br />ization. The application builds a river network 'tree,' reads in all the information associ- <br />ated with structures and stream gauges located on the network, and stores these data in <br />memory for the duration of the application's use. During this initialization, structure and <br />stream gauge names and IDs are loaded from the structures table, and a current set of <br />water rights for each structure is derived from the information contained in the water <br />rights table. In addition, some dynamic data are read in from the table containing current <br />calls in order to create the call structure in effect on the river system. This information is <br />updated as calls are set and released. <br /> <br />After initialization is complete, the application operates primarily on the dynamic tables <br />via run-time queries to the database. This type of query is performed when the user asks <br />for streamflow data for a particular time interval, in which the application searches the <br />streamflow table to find the relevant data. When the user loads a Water Information Sheet. <br />the application must perform a sequence of queries: flow numbers on the sheet itself are <br />retrieved from the wis_data table; comments at the bottom of the sheet are found in the <br />wis_comments table; priority diversions and exchanges at each structure are retrieved <br />from the diversions and exchanges tables; and the calls affecting the district are found in <br />the calls table. Some data (such as diversion structure name, stream gauge name, and <br />water rights available for priority diversions) that appear on the Water Information Sheet <br />are read from memory, are initialized at program start-up, rather than from a run-time <br />query of the database. <br /> <br />Primary keys on most tables are enforced by unique indices on the columns used in the <br />key. The primary key in each of the following tables is indicated by.. after the column <br />name. <br /> <br />2 <br /> <br />Database Manual <br />