Laserfiche WebLink
Approach 2 -Separate layers for each time series data type: <br />Precipitation stations layer: <br />station_id <br />station_name <br />...other attributes... <br />Temperature stations layer: <br />station_id <br />station_name <br />...other attributes... <br />The above approaches are further complicated by the fact that time series may have multiple data <br />intervals (e.g., real-time, hourly, daily, monthly, annual, irregular). Consequently, to completely <br />recognize the types of data that are available for a station, the first approach would need attributes like <br />"is_daily~recip". The second approach could be extended to including these same attributes, or in an <br />extreme case, separate layers could be created for each time series data interval. <br />One of the issues with the HydroBase design is that the separation between structures and stations is not <br />always clear. For example, real-time diversion amounts may be collected at major headgates (e.g., FORT <br />LYON CANAL, which has a station identifier and abbreviation of FLYCANCO). However, these <br />locations are treated as stations and a link to the administrative structure does not appear to be present in <br />the database. Therefore, it may not be possible to create spatial data attributes like the following using <br />HydroBase: <br />station_id <br />structure_id <br />is realtime <br />Another issue in HydroBase is that within the stations' data, there is not always a match between real-time <br />and historical stations. For example, NORTH FORK CACHE LA POUDRE RIVER BELOW SEAMAN <br />RESERVOIR, which has a station identifier and abbreviation of CLANSECO (a DWR gage) is used for <br />administration but apparently the real-time data are not archived for historical data. The State also <br />collects a variety of real-time data for precipitation, temperatures, water temperature, and other data types, <br />but these data are not readily available in HydroBase and therefore cannot be displayed by <br />StateView/CWRAT, TSTooI, and other tools. <br />The above examples illustrate that even if spatial data layers are created with attributes to indicate <br />secondary information (e.g., the time series data that are available at the locations), this information could <br />be misleading due to the database design and data. <br />3. Recommendations <br />Based on the above information and current HydroBase design, it does not appear that information about <br />the time series data types and intervals can be readily included in spatial data attributes. However, there <br />is some value in providing additional spatial data layers. Therefore, the following specific <br />recommendations are made regarding new spatial data layers: <br />• Instead of distributing a climate stations layer, distribute precipitation, temperature, and <br />evaporation stations. HydroBase uses a geoloc.loctype value of "CS" for climate stations. <br />Therefore, to be able to distinguish precipitation and temperature stations, the meas type table <br />Page 3 Of 5 ~RTversfde TeChnafogy, Inc, <br />W.~fe: Resources Er`gineering and C.onsufting <br />