Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

Singapore OMS Lake Diagnostic System file format (Since 2010_01)

Basically files Files in the Singapore OMS Lake Diagnostic System file format are expected to be text files.

Implementation details

...

The parameters are collected from lines containing a slash '/', where the actual parameterId is taken from the left part before the slash. The parameters for SCHEDULE A are retrieved from the lines between SCHEDULE A and SCHEDULE B. The parameters for SCHEDULE B are retrieved from the lines between SCHEDULE B and Data Section. The actual data with measurements is retrieved from the lines after the Data Section tag. Each line with data that starts with 'A' or 'B' will contain also a number of space delimited values. The first value is the Julian day since 1-Jan-2000. The second value is the number of seconds in that day. The timestamp that is derived from this is supposed to be in same timezone as specified in the importTimeZone value of the import configuration. The other values are measurement data, for each parameter in the corresponding schedule. The import will determine the timestep from the difference in time between the first two data rows for each schedule. The other rows in a schedule must follow the same timestep for the schedule otherwise the import run will produce error messages. Also when either no data values for schedule A or B are found, a warning messages is produced.

Sample Input

The following sample shows equidistant timeseries data for schedule A with a timestep of 30 seconds and equidistant timeseries data for schedule B with a timestep of 15 minutes. The sample also shows the definition of two parameters TCHN 1 and TCHN 2 for schedule A and two parameters CHAN 8 for schedule B. The current implementation rounds the actual timestamps to make them acceptable as equidistant data for FEWS.

...