Skip to content

Improve local storage to TSV #10

@patricktokeeffe

Description

@patricktokeeffe

Can we transition the TSV files to psuedo-TOA5? (relocated from comment on #9)

Campbell Scientific TOA5

  • comma-separated values
  • multi-line header

Excerpted from CR1000 User Manual, rev 2/18, section 7.6.3.11.1:

Line 1: Environment Line

Field Description Proposed value for Urbanova AQ node
1 TOA5 TOA5 (part of standard)
2 Station name name/ID of assembled sensor package?
3 Datalogger model lookup values corresponding to specific hardware configurations?
4 Datalogger serial number serial number of just raspberry Pi? of entire assembled AQ node?
5 Datalogger OS version Git tag/hash of installed software version
6 Datalogger program name name of DAQ script?
7 Dataloger program signature blank/not used? other sentinel to emphasize not a real TOA5 file? use for Git tag/hash instead?
8 Table name ?

Line 2: Header

This line consists of comma-delimited strings that identify the name of individual fields as given in the datalogger program.

Line 3: Units

This line identifies engineering units for that field of data, as declared at the beginning of the CRBasic program.

Line 4: Aggregation

The fourth line reports abbreviations of the data process used to produce the field of data. See table 20 within user manual section 7.6.3.17 (rev 2/18).

All additional lines

Subsequent lines are observed data and associated record keeping. The first field being a timestamp, and the second being the record (sequential) number.

Notes

  • station name
    • sensor packages record lat/long... but that's not a name. Monitoring locations need names and multiple units can be installed at any one location so that name cannot be the same as the sensor unit.
    • if station represents assembled package, then logger serial can represent the Pi specifically (or whatever hardware is doing DAQ)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions