Laserfiche WebLink
The TSTooI HydroBase Input Type appendix lists data types that were determined in order to <br />allow TSTooI to support data from HydroBase. As much as possible, the VAXFIELD <br />information was minimized to allow a transition to a more modern database design. Existing data <br />types from the meas type table were used as much as possible, unless an ambiguity or <br />inconsistency resulted. Amore consistent storage scheme for time series data related to stations <br />and structures would simplify joining station and structure time series data with spatial data. In <br />particular, more consistent data types and intervals are needed. <br />• Consider storing basic time series statistics in HydroBase, which could be saved as attributes in <br />spatial data layers (e.g., shapefiles). For example, store in HydroBase the average monthly <br />streamflow. This may not be a simple task, given that the averages will be impacted by the <br />amount of missing data and the period of record. In any case, the limitations of the data could be <br />documented and used qualitatively. <br />4. Comments and Concerns <br />Creating additional point layers from HydroBase is a relatively simple exercise, but doing so without a <br />plan can lead to inconsistent data and maintenance issues. It is now possible to evaluate the potential point <br />layers because GIS data inventory is now relatively complete, especially with respect to data in <br />HydroBase, and the TSTooI HydroBase Input Type appendix now lists all of the time series available in <br />HydroBase. <br />Rather than create every layer that is possible, it is recommended that the climate data layer be split into <br />layers for each data type; precipitation, temperature, and evaporation. StateView/CWRAT did not use <br />these layers in the past because they were not available. In order to evaluate the recommendations made <br />in this memorandum, to satisfy the project scope for StateView/CWRAT, and to supply data for the SWSI <br />project, the StateView/CWRAT software was modified and now allows the display of precipitation and <br />temperature stations as a layer in the map interface. The StateView/CWRAT Installation and <br />Configuration Appendix includes the GeoView Configuration section which explains how to configure <br />these layer types. The GeoView project files distributed with GIS files to support StateView/CWRAT <br />have not been updated to display these layers, mainly because the map displays are already very <br />congested. Instead, it is envisioned that tools like StateDMI and the StateCU interface might benefit from <br />the new layer types. Further review of StateView/CWRAT and the modeling environment should be <br />performed by the State to help decide which data layer should be made available with each software tool. <br />In any case, functional software has been put in place to illustrate how new layers can be created and <br />these features can be enabled by properly configuring the data. Additional enhancements to <br />StateView/CWRAT and ArcCDSS will be similar to the features that have previously been implemented <br />and will be relatively straightforward. <br />Further evaluation of the HydroBase design should consider the suggestions made in this memorandum. <br />Future versions of HydroBase may benefit from a more integrated spatial/relational design that would <br />allow software to make spatial queries and link to time series data in an integrated fashion. The current <br />approach of using shapefiles for spatial data and allowing HydroBase queries as a separate step is <br />functional, but could be improved upon with an integrated database. <br />Page 5 Of 5 ~RTversfde TeChnafogy, Inc, <br />W.~fe: Resources Er`ginee.: ing and C.onsufting <br />