Laserfiche WebLink
<br />Uu\JJci~ <br /> <br />Use Model. Note, although a GIS tool such as ArcView is not anticipated for the Water <br />commissioner, selected applications will have geographic reference maps. <br /> <br />Other Users, who may include water conservation districts, federal agencies, cities, <br />consultants, etc., are expected to have equipment which is somewhere in-between a <br />division and water commissioner. A potential difference is that these users may be <br />interested in obtaining GIS data, consumptive use model and data, water resource <br />planning model and data, etc. from CRDSS and operating them from their own Pc. Note. <br />these users will obtain data using the same approach as a division office or water <br />commissioner (primarily a database query, some (GIS. Water Resource Planning. and <br />Consumptive Use) ti-om an FTP site. Also, there is nO intent to provide a GIS tool to <br />other users, only GIS data. Data Storagc(s) As presented in the above Tabk. three <br />separate, dependent data storage locations are envisioned as part of CRDSS in order to <br />meet user needs within the limitation of network communication speeds: Central Based <br />Data. Division Based Data. and Water Commissioner or Other Based Data. <br /> <br />The Central Based Data will contain HydroBase, the statewide relational database <br />operating under lnformix and other non relational graphically intensive information. <br />l-IydroBase will contain official, DWR data such as water rights, diversions. well records. <br />reservoirs, etc. In addition, HydroBase will contain real time streamflow measurements <br />via satellite monitoring stations, archived Water Administration Tool Worksheets, and <br />the relational data required for the planning components of CRDSS such as historic <br />streamflow, temperature, precipitation, snow pack, etc. Non relational data within the <br />Central Based Data, but not within HydroBase, includes official GIS coverage's, the <br />Depletion Analysis Model and data, the Curtailment Analysis Model and data, the Point <br />Flow Analysis Model, the Water Resource Planning model (StateMod) and data, and the <br />Consumptive Use model (CRDSS-CU) and data. <br /> <br />The Division Based Data will contain the same non relational data and models as those in <br />the Central Based Data because network speed is not expected to be adequate for <br />applications that require large graphic images. Because network speed is adequate for <br />relational data. they will not have local copies, but instead will use the official Central <br />Based Data. HydroBase. This application will be a traditional server client approach. <br /> <br />Water Commissioner or Other Data cannot use the traditional server client approach <br />because of inadequate network speed. Thereforc, they will have a local. relational <br />database on their PC s operating under ACCESS. This local database is expected to <br />mimic the HydroBase design to simplify maintenance. It will contain a subset, typically <br />a single water district, of all data necessary to operate the Water Right Administration <br />Tool off-line after refreshing real-time or archived information once a day. Note, if a <br />water commissioner needs to perform a division wide evaluation such as a depletion <br />analysis, a curtailment analysis, or a historical point flow analysis, they will have to <br />connect to the Central Based Data. <br /> <br />The three separate, dependent data storage locations described above are considered <br />realistic, not optimaL Indeed with better communications, all infomlation would be <br /> <br />c: \ w\crdsslscopelph 1 t I blscope .doc <br /> <br />2119197 - 3 <br />