Appendix
Motus data file formats
This page describes the information contained in the file name and contents for the three receivers supported by the Motus system
1. File types
1a. SensorGnome format
This format is the default for units running the SensorGnome software (including for the SensorGnome component of the SensorStation). Each file contains individual pulses, gps readings, etc. The data can also be separated for each antenna, as well as for LifeTag detections only (type = ctt).
1
Filename format: <site_label>-<receiver_number>-<boot_num>-<datetime><prec>-<type>-<ext>.gz
2
​
3
Example: changeMe-3114BBBK2178-000074-2018-01-22T00-29-13.3300T-all.txt.gz
4
changeMe-3114BBBK2178-000074-2018-01-22T00-29-13.3300T-ctt.txt.gz
5
​
6
site_label: user-entered site label (default: changeMe)
7
receiver_number: for SensorGnomes, receiver serial number (without the SG prefix, e.g. 3114BBBK2178)
8
for SensorStation, receiver serial number (with the CTT prefix, e.g. CTT-123456789012345)
9
boot_num: boot number
10
datetime: yyyy-mm-ddTHH:MM:ss.ssss
11
prec: single digit representing the clock precision:
12
P: clock not set by GPS
13
Z: 1 second
14
Y: 0.1 second
15
X: 0.01 second
16
W: 0.001 second
17
V: 0.0001 second
18
U: 0.00001 second
19
T: 0.000001 second
20
type: all (for all antennae), specific antenna number or ctt (ctt and gps data only)
21
ext: extension (typically txt)
22
gz: indicates compressed files (other types of compressions are also supported: bz2, etc.)
Copied!
1b. SensorStation format
This format is the default for units running the SensorStation software. Data components are divided separate files: data, node data and gps. Data contains the 32-bit codes interpreted by the CTT dongles, node data contains detections from external node units and gps includes gps readings (only for the base station so far, not for nodes).
1
File format: CTT-<serial>-<data_type>.<datetime>.<ext>.gz
2
​
3
Example : CTT-867459049219777-data.2019-07-18_191832.csv.gz
4
CTT-867459049219777-node-data.2019-07-18_191832.csv.gz
5
CTT-867459049219777-gps.2019-07-18_191832.csv.gz
6
​
7
serial : 15 digit numeric (old) or 12 digit alphanumeric value (new)
8
data_type : one of data, raw-data (same as data), data-node or gps
9
datetime : <yyyy-MM-dd_HHmmss>
10
ext : csv only so far
11
gz : indicates compressed files
Copied!
1c. Lotek format
This is the default format used by Lotek units. Each file contains a header and individual tag detections (not pulses, only putative tags). There are other formats available for export from the Lotek units (e.g. binary), but we require the DTA format.
1
Filename format: <filename>.DTA
2
​
3
Example : OldCut0001.DAT
4
​
5
filename : any arbitrary value provided by the user
Copied!
Filename: the file name is entirely determined by the user and doesn't contain useful information about its content.
2. File content
2a. SensorGnome format
The following prefix can be found in SensorGnome files. Files of type ctt will only contain T and G prefix.
C : (GPS clock setting precision record: outlines the time the GPS was set (ts), the precision it was set to (prec), and the time elapsed in running the time (elapsed))
1
Format : C,<ts>,<prec>,<elapsed>
2
Example : C,1528750333.246,1,0.399892479
3
Example : C,1561257097.681,6,8.6e-7
Copied!
G : GPS data entry
1
Format : G,<ts>,<lat>,<lon>,<alt>
2
Example : G,1526683597,-23.002083333,118.931118333,736.4
Copied!
p : individual pulse on FunCube Dongles
1
Format : p<port_num>,<ts>,<dfreq>,<sig>,<noise>
2
Example : p3,1526683680.8316,0.4,-35.4,-42.56
Copied!
S : frequency setting record (see fields below for possible name values)
1
Format : S,<ts>,<port_num>,<name>,<value>,<rc>,<err>
2
Example : S,1366227448.192,5,-m,166.376,0,
3
Example : S,946684811.244,3,frequency,151.496,0,
4
Example : S,946684811.249,3,gain_mode,1,0,
5
Example : S,946684811.25,3,tuner_gain,40.2,0,
6
Example : S,946684811.25,3,test_mode,0,0,
7
Example : S,946684811.251,3,agc_mode,0,0,
Copied!
T : LifeTag hit on CTT/CVRX dongle or SensorStation
1
Format : T<port_num>,<ts>,<tag_code>
2
Example : T4,1557450282.889,04452182
Copied!
Fields:
1
-m : antenna listening frequency (FunCube and FunCubePro)
2
-w : FunCube and FunCubePro parameter settings
3
(see https://github.com/sensorgnome-org/sensorgnome-control/blob/77d8ba9b2cf1ba6d3eef895fe7e2155c3f6ccd73/master/usbaudio.js#L32)
4
alt : altitude (m)
5
dfreq : frequency offset (KHz)
6
err : blank on success, else error message (frequency setting)
7
freq : nominal frequency
8
lat : latitude (degrees)
9
lon : longitude (degrees)
10
name : arbitrary parameter name
11
noise : noise level (dB?)
12
port_num : port number (antenna)
13
rc : response code (?). E.g. zero if frequency setting succeeded, else non-zero error code
14
sig : signal strength (dB)
15
tag_code : 32-bit tag code (e.g. LifeTag)
16
ts : Unix timestamp (seconds)
17
value : arbitrary parameter value
Copied!
2b. SensorStation (LifeTag) format
SensorStation (LifeTag) files will contain headers specifying their content. No assumptions should be made about the order or the list of fields included within those files. The formats below are those currently in use at the time of this document.
data (or raw-data) files:
1
Format : <Time>,<RadioId>,<TagId>,<TagRSSI>,<NodeId>
2
Format : <Time>,<RadioId>,<TagId>,<TagRSSI>,<NodeId>,<Validated>
3
​
4
Example : 2019-07-16 20:18:39.845,3,6161527F,-96,
5
​
6
Time : datetime (UTC) yyyy-MM-dd HH:mm:ss.sss
7
RadioId : Port number (numeric). Those ports are saved with a L prefix in the metadata and the data tables
8
TagId : tag number (e.g. AF7709D3)
9
TagRSSI : Received Signal Strenght Indication
10
NodeId : hex ID of the node that originally captured the signal (3-digit for old models. Should be unique in more recent models)
11
Validated : 0 or 1 to indicate whether the tag was considered valid by CTT algorithms (details unknown).
Copied!
node-data files: meta information about the nodes
1
Format : <Time>,<RadioId>,<NodeId>,<NodeRSSI>,<Battery>,<Celcius>
2
Format : <Time>,<RadioId>,<NodeId>,<NodeRSSI>,<Battery>,<Celcius>,<RecordedAt>,<Firmware>,<SolarVolts>,<SolarCurrent>,<CumulativeSolarCurrent>,<Latitude>,<Longitude>
3
​
4
Time : datetime (UTC) yyyy-MM-dd HH:mm:ss.sss when the data was received at the base station
5
RadioId : Port number (numeric). Those ports are saved with a L prefix in the metadata and the data tables
6
NodeRSSI : Received Signal Strenght Indication (node signal on the base station)
7
Battery : battery power level
8
Celcius : node temperature
9
RecordedAt : datetime (UTC) when the data was recorded on the node
10
Firmware : node firmware
11
SolarVolts : solar voltage
12
SolarCurrent : solar current
13
CumulativeSolarCurrent : cumulative solar current
14
Latitude : node latitude
15
Longitude : node longitude
Copied!
gps files: gps readings of the base station
1
Format : <recorded at>,<gps at>,<latitude>,<longitude>,<altitude>,<quality>
2
Format : <recorded at>,<gps at>,<latitude>,<longitude>,<altitude>,<quality>,<mean lat>,<mean lon>,<n fixes>
3
​
4
Example : 2019-08-17T03:09:27.458Z,2019-08-17T03:09:26.000Z,38.240977833,-75.1360325,2.7,3
5
​
6
recorded at : datetime (UTC) yyyy-MM-ddTHH:mm:ss.sssZ
7
gps at : datetime of gps clock (UTC) yyyy-MM-ddTHH:mm:ss.sssZ
8
latitude : latitude (degrees)
9
longitude : longitude (degrees)
10
altitude : altitude (m)
11
quality : signal quality (units?)
12
mean lat : mean latitude
13
mean lon : mean longitude
14
n fixes : number of fixes used to calculate mean
Copied!
2c. Lotek format
Data segment: individual tag detections. We request that users export their DTA file using GMT times, but there is no guarantee. Hopefully, newer versions will format dates as ISO 8601 to include the time zone.
1
Format: <Date> <Time> <Channel> <Tag ID> <Antenna> <Power>
2
Example: 06/05/15 12:43:10.6489 0 393 A1+A2+A3+A4 131
Copied!
Last modified 1yr ago