Giters

inbo / fish-tracking

🐟 Collection of scripts for processing and analysing fish tracking data

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Receiver prefix

peterdesmet opened this issue · comments

commented

Receiver codes seem to have the prefix VR2W-. What does this stand for and will all receivers have that exact prefix?

commented

There are currently two different types of receivers used: VR2W and VR2C (the latter sends real-time data from the offshore wind mill park). So not all receivers will have the same prefix.

commented

Same remark as for tags: receiver_id in metadata should then contain the whole ID, otherwise, we could have errors matching the data coming from the receivers.

commented

Here there is no problem, Vemco software (VUE) provides the whole ID in 1 column.

commented

I think this means that the information (VR2W or VR2C or ...) needs to be
added to the column "receiver_id" in the metadata Pieterjan. Correct me if
I am wrong.

Now the vrl- and csv-files contain the full receiver-ID (e.g. VR2W-124076)
and the column "receiver_id" in the metadata contains only the number (e.g.
124076). The latter should contain VR2W-124076 instead, to be able to match
the vrl/csv-files with the metadata..

commented

@IPauwels, that's what I think as well...

commented

Indeed, that is what I meant. I thought, as the Vemco export provides the whole ID in 1 column, this could be extrapolated to the metadata (just upload export from vemco into metadata and its done).

commented

OK. @IPauwels, I'm assigning this issue to you (but you can of course delegate). This is what needs to be done:

  1. Export all receiver_ids from VEMCO software
  2. Update receiver_id in Google Spreadsheet to contain full ID (e.g. VR2W-124076). I think this needs to be done manually.
  3. CartoDB will update the field type from number to string automatically.
commented

The update of column "receiver_id" in the metadata indeed needs to be done
manually, because not all receivers that are in the metadata are active now
and even if they would, potentially not all receivers detect fish (VEMCO
output).

I don't understand why the receivers need to be exported from the VEMCO
software if we adapt it manually?

A last question: if I try to adapt something in the column "receiver_id" I
get the message that I should enter a valid receiver ID (so initially CDB
as problems with the string)?

thanks!

commented

If we adapt manually, there is no need for export from VUE. I thought the csv files could be uploaded directly in the google spreed sheets? In that way, the export files come in handy, they have the column heading with the total receiver_id.
Also easy copy paste when applying manually.

commented

@IPauwels: right... I'll update the validation in the Google Spreadsheet, so it doesn't throw an error when entering strings instead of numbers.

commented

Column "receiver_id" is adapted for the following projects: Boekhoute,
Demer and Rivierprik, so Peter you can proceed with the test

Pieterjan, could you adapte the column for Westerschelde and Albertkanaal?
Thanks

commented

"receiver_id" is updated for Westerschelde and Albertkanaal.
I updated information in "is_active", "data_downloaded_at", "has_weight" and "is_moored" for the receivers that have been offloaded on 15/10/2104, 17/10/2014, 5/12/2014 and 9/12/2014.

commented

Nice, I assume that the odd codes like VR2-4231 and VR2C69-450114 are correct. The spreadsheet now shows a red background colour if is_moored or has_weight is FALSE, to quickly show receivers that need attention.

commented

Great! Yes, I suppose the VR2 is an older model. The VR2C is a different type of acoustic receiver.