Standardized receiver_code
peterdesmet opened this issue · comments
To allow easier and more robust mapping between data and metadata, @PieterjanVerhelst and I have decided to also use receiver_code in the data. Together with receiver_id it will allow unique mapping between a transmitter and a receiver at a certain location + date.
The code will be standardized: ak-1-2 (ak = project, 1 = location, 2= deploy).
- @PieterjanVerhelst will define the codes
- @peterdesmet will process the old data to include the new codes
- Newly deployed receivers will use the new code
- Data coming back from currently deployed receivers will be processed to include the new code (to be discussed how - but one file will just have one code).
This ticket can be closed if all 4 items are completed.
All codes are filled in, except for some of BPNS because they are not deployed anymore and weren't for a long time (so far no detection data).
'Rivierprik' are not filled in, because location and coordinates is missing.
For 'Albertkanaal' receivers on left and right bank have the same coordinates. @ammouton Will this give a problem for data analyses? Is it necessary to know which bank the fish had chosen or is it sufficient to know if the fish passed the specific location?
@PieterjanVerhelst @ammouton: has a decision been taken about left/right bank? If so, does it have consequences for the codes we assigned?
I checked the receiver codes and the coordinates. Every code has a unique location and time, so problem is solved (I don't know where I saw the same coordinates for a different place, probably a 'ghost detection' ;-) ).