Closed damianooldoni closed 4 years ago
In the datafile with birds I received there are 2 lines for this individual (different colorcodes). Neither had information about the year of birth
bird_id,bird_reference,bird_euring,bird_bto,bird_shorthand,bird_scheme,bird_ring_number,bird_name,bird_sex,bird_birth_year,bird_date_begin,bird_date_end,bird_rings_changed,bird_age_ringing,bird_ring_position,bird_ring_direction,bird_notes ,348,05910,,BW(AAAZ),BLB,L...904847,,M,,02-07-1999,06-06-2006,2,1,,, ,348,05910,,BW(D.FAY),BLB,L...904847,,M,,06-06-2006,,1,A,RB,U,
I have added a year of birth based on the ringing date and the age at ringing for all birds with known age.
Based on Excel file I got from Lisenka, we should not fill the field bird_birth_year
as it will be filled by SOVON. So, is it ok if we leave it empty in the new mapping as well?
That is ok if you have EURNG values for bird_age_ringing (https://euring.org/files/documents/E2000PLUSExchangeCodeV117.pdf#page=14)
Yes, indeed. I have just checked that we miss that field for 142 rings, typically birds where a ring is changed. I will fill it by calculating the date difference. Hopefully it gets solved easily.
I think that it should be ok of you only give an age the first time a bird is caught. If a bird is re-ringed you should sent 2 (or more) records. We'll see if that is enough. I don't think it is a good idea if you calculate the age on the recapture date from the age at ringing and the time since ringing.
Thanks @JeroenNienhuis.
There are only three birds (Larus, EURING 05910) ringed just once and without age while ringing.
From tblWaarneming
:
Datum | KleurringNummer | LeeftijdCode |
---|---|---|
2013-06-04 | GPS19 | |
2015-08-10 | MGAG | |
2015-08-10 | PNAN |
@EricStienen: could you please check it?
solved at DB level
Indeed, solved. Check added in data processing.
@EricStienen:
In my final ring file, crbirding_birds_20190410.csv, I can read indeed the same:
@JeroenNienhuis: are you maybe still working on this field? Thanks.