Lotek: parse Gain Adjustment records from .DTA files and incorporate into DTAlines records in
receiver DBs. GA records are reported separately before any tag detections, rather than being interleaved
in chronological order, so we need to parse them into a table and join that with tag detections, also
using the values currently parsed from Gain Table blocks
SG: we record antenna gain settings in a separate table which isn't ending up in the master DB,
and hence is not available to motusServer::dataServer() and so not to the motus R package either.
all receivers: push gain/filtering settings into new master table as done with gps records, but with
antenna labels
new API entry for dataServer() to return relevant gain/filtering settings
motus package needs to grab gain/filtering settings too, and incorporate them into the alltags view
PARKING this issue until the 2nd or later round of data distribution
Lotek: parse
Gain Adjustmentrecords from .DTA files and incorporate into DTAlines records in receiver DBs. GA records are reported separately before any tag detections, rather than being interleaved in chronological order, so we need to parse them into a table and join that with tag detections, also using the values currently parsed fromGain TableblocksSG: we record antenna gain settings in a separate table which isn't ending up in the master DB, and hence is not available to motusServer::dataServer() and so not to the motus R package either.
all receivers: push gain/filtering settings into new master table as done with gps records, but with antenna labels
new API entry for dataServer() to return relevant gain/filtering settings
motus package needs to grab gain/filtering settings too, and incorporate them into the
alltagsviewPARKING this issue until the 2nd or later round of data distribution