Laserfiche WebLink
TSView Time Series Viewing Tools <br /> Appendix - TSView - 3 <br />and optionally: <br /> <br />• Sequence number (currently being evaluated) <br />• Input type <br />• Input name <br /> <br />These time series attributes are typically concatenated into a time series identifier string. The following <br />example illustrates how the basic identifier parts can be used (without input type and name): <br /> <br />12345678.USGS.Streamflow.DAY.HIST <br /> <br />The above example identifies a USGS streamflow gage identified as location 12345678 , at which <br />historic average daily flow data are available. If pos sible, data types appropriate for the input type should <br />be used to avoid confusion; however, time series file input types often do not contain a simple data type <br />abbreviation (see the input type appendices in the TSTool Documentation for more information). The <br />above example illustrates that the scenario can be used to qualify the data (in this case as historic data, <br />HIST ). The scenario is often omitted. When the scenario is used, it often indicates some specific <br />condition (e.g., FLOOD , DROUGHT , HIST , FIL LED ) <br /> <br />The optional input type and input name are used to specify the time series input format and storage <br />location, especially in cases where the identifier is saved in a file and the input type is needed for later <br />processing. For example: <br /> <br />12345678.USGS.Streamflow.DAY.HIS T ~USGSNWIS~C:\data \12345678.txt <br />12345678.USGS.Streamflow.DAY~HydroBase <br /> <br />The first example illustrates a time series identifier for a USGS National Water Information System data <br />file. The second example illustrates the identifier for the same time series, in the HydroBase database. <br />Using the input parts of the identifier allows software to transparently locate the data, and for the above <br />examples, would allow the time series to be read from each input source and compared. <br /> <br />The use of the input type and name is being phased into TSView and related components. Input types <br />that have been added to software more recently (e.g., as of version 05.04.00 of the TSTool application) <br />use the new convention and older input types are being updated acco rdingly. The TSTool appendices that <br />describe each input type identify issues with compatibility. <br />Using the above time series identifier convention omits use of time series attributes like the period of <br />record and the units, even though these attributes co uld conceivably be used to distinguish between time <br />series that are otherwise the same. Instead, it is assumed that the period of record and units can be <br />determined from the input and do not need to be part of the identifier. If necessary, different inpu t files <br />can be used to further differentiate time series. <br /> <br />The TSView components use the time series identifiers extensively to locate and manage time series. For <br />example, graph properties for each time series are cross -referenced to time series by using the identifiers. <br />Perhaps most importantly, the time series identifiers as simple strings can be stored in files and can be <br />used by a variety of software to consistently and reliably locate data for processing. <br /> <br />157