Laserfiche WebLink
TSTool Documentation <br />Input Type <br />Description <br />StateCU <br />State of Colorado consumptive use model time series and report <br />formats. <br />StateCUB <br />State of Colorado consumptive use model binary output file. <br />StateMod <br />State of Colorado StateMod model time series file format. <br />StateModB <br />State of Colorado StateMod model output binary file. <br />USGS NWIS <br />United States Geological Survey National Water Information <br />System format <br />An example of a time series identifier for a monthly streamflow time series in HydroBase is: <br />09010500. USGS.Streamflow.Month — HydroBase <br />The same time series for a USGS NWIS input source might be identified using: <br />09010500. USGS .Streamflow.Month— USGSNWIS —C: \temp \09010500.txt <br />In this example, the optional scenario (fifth part) and sequence number are not used. This identifier string <br />can be saved in a command file or time series product description file, which can be processed again later. <br />The identifier string allows TSTool to determine how to re -query the time series. The time series <br />identifier is useful for managing time series. The TSTool GUI typically handles creation of all time series <br />identifiers; however, identifiers can be created with an editor once the format is familiar. The path to files <br />can be absolute or relative to the command file. The latter is recommended to improve portability of files <br />between computers. <br />Because time series identifiers are somewhat cumbersome to work with, TSTool allows a time series alias <br />to be used instead. For example, the following command illustrates how a HydroBase time series can be <br />read and associated with an alias: <br />TS X = ReadTimeSeries(" 09010500. USGS .Streamflow.Month — HydroBase ") <br />This allows the time series to be referred to as X during further processing (e.g., when manipulated with <br />commands). Whether full identifiers or aliases are used, the overall identifier must be unique during <br />processing to guarantee that time series commands are processed as desired (duplicate aliases and <br />identifiers can be present but the first one found will be used - see Section 2.4 Time Series Commands <br />and Processing Sequence for an example). TSTool ignores upper /lower case when comparing <br />identifiers, aliases, and other commands, although it is good practice to be consistent. <br />When editing commands, TSTool does not normally show the input type and input name parts of the <br />identifier because this information is most appropriate for read commands. There are cases where two <br />time series identifiers will be the same except for the input type and name. In these cases, an alias should <br />be assigned when reading the time series and the alias used in later commands. If for some reason an <br />alias cannot be used, the input type and name may need to be manually added if the command editors do <br />not display by default (e.g., in cases where the identifiers cannot be determined without actually running a <br />command). <br />Newer commands also allow the alias to be assigned even when reading multiple time series. This <br />convention uses an Alias parameter rather than the TS Alias = syntax and maybe phased in as the <br />preferred syntax. For example, the alias may be assigned to the location identifier only. <br />Introduction - 4 24 <br />