Laserfiche WebLink
ADCPs) allowing channel inflow and outflow to the reach to be estimated. Pressure transducers <br />will be used to measure water stage at selected locations along the reach and canal cross-section <br />geometry will be surveyed at appropriate intervals between the upstream and downstream ends <br />to evaluate storage changes along the reach. Evaporation from the water surface, and minor <br />inflows and outflows along the reach will also be estimated, allowing canal seepage to be <br />calculated from the mass balance equation. <br />Task 6: Database Development <br />A database will be developed that will house both the compiled and the gathered data. Existing <br />data compiled from other sources under Task 1 will be converted into a format that will be <br />uniform with that of the data gathered under Tasks 1-5. It is proposed that the MS SQL Server <br />relational database management system be utilized as the database platform, since it supports <br />Microsoft's version of the Structured Query Language (SQL), the most common database <br />language. The database will be designed for enterprise data management, with numerous VB.net <br />forms developed for easy data entry, editing, and retrieval of field data collected during the <br />project. Stored procedures can also be created for easily executing series of SQL commands for <br />implementation of the VB.net forms. <br />An object-oriented, minimalist design paradigm will be used to make the database easy to access, <br />adapt, and expand for future use. Foreign keys will be specified for effectively defining <br />relationships between the tables for one-to-one, one-to-many, many-to-one, and the occasional <br />need for many-to-many relations. It is proposed that the security of the database be enhanced <br />through development of encapsulation layers. With the implementation of encapsulation, the <br />database management system can be changed without affecting other components within the <br />system as long as the interface to that component did not change. This will reduce the coupling <br />between the object schema and the data schema, allowing implementation of all data-related <br />code in one place, thereby simplifying the job of linking the database to the application models <br />eventually selected for the Arkansas River DSS. <br />Development of the database will be carried out in cooperation with DWR's HYDROBASE <br />database manager, which is facilitated by the fact that HYDROBASE is also developed under the <br />SQL Server platform. Attempts will be made to avoid duplication of data stored in both data <br />bases. It is proposed that scripts be prepared that will allow interchange of data between the two <br />databases, but with procedures in place for insuring necessary security and data integrity. <br />Both existing compiled data and newly-gathered data will be stored in the proposed database, <br />including but not limited to: <br />¦ Field locations (i.e., geo-spatial locations and descriptions of individual field parcels with data <br />monitoring); <br />¦ Field measurements of crop yield, soil moisture, soil temperature, selected irrigation practices, etc.; <br />¦ Field salinity data and electromagnetic induction meter (EM38) calibration data; <br />10