Laserfiche WebLink
Task 128, 129, 130 -Groundwater and Other Data Displays in StateView <br />Objective: <br />Enhance StateView software to display new groundwater data and enhance existing <br />StateView groundwater displays based on changes in HydroBase, and make display <br />enhancements to other data displays due to other changes in HydroBase or the system. <br />Background: <br />HydroBase was enhanced during the RGDSS project to store groundwater-related data, <br />including wells that are not structures or permits, well physical data, pumping tests, and <br />well level time series. The design that wa;~ implemented was limited due to a lack of <br />experience about how data would be used by software and technical issues that made <br />integration of the data difficult (e.g., it is d''.ifficult to evaluate how many holes in the <br />ground there actually are when evaluating well permits). Since the initial RGDSS <br />implementation, it has become obvious that changes to the well data storage in <br />HydroBase are necessary in order to corre~~t the original limitations and to store new data <br />collected during the SPDSS effort. During; and subsequent to the RGDSS effort, <br />StateView and TSTooI were enhanced to display well-related data. StateDMI also <br />processes well data. The State HydroBase, DBA has been implementing changes in <br />HydroBase to better store groundwater-related data. Activities will be required to <br />understand and evaluate the HydroBase changes, and to design and implement changes to <br />StateView software, in order to provide general data viewing capabilities. These changes <br />will also require changes to the low-level code that interacts with HydroBase. Additional <br />changes in HydroBase tables that store data other than groundwater will also require <br />changes to the StateView displays. <br />Assumptions: <br />The State of Colorado HydroBase DBA will make available to RTi a current HydroBase <br />data dictionary (and ideally an entity relationship diagram), as well as a copy of the <br />HydroBase database that contains actual groundwater data in the new table structure. <br />Approach: <br />128.1 Evaluate HydroBase Design for lroundwater Data. Review the updated <br />HydroBase design for groundwater data relating to well structures, well permits, <br />and well data that were not originaily for a structure or permit, considering the <br />following: <br />• What are the major categories of groundwater data? <br />• What is the role of StateView/CWRAT in displaying groundwater data? <br />Will all available data be viewable? Will displays be tabular or graphical? <br />• Will tools other than StateView/CWRAT provide display capabilities? <br />• Are the relationships between data in HydroBase conducive to data <br />displays and other uses? <br />