Which options for `observations.type`?

[Rafnuss]

The observation table needs to suscintcly summarize all possible observation type we might want to record from what is happing in the field.

We are using a combinaison of observation_type, device_status and condition to help us capture all possible situations.

❓ Are the options provided cover all possible cases?

Movebank does not have a great support to describe these "observervation" beside the deployment_end_type and deployment_end_comments.

• analysis-end = the end time represents the end of the period of interest;
• captured = The tag remained on the animal but the animal was captured or confined;
• dead = The deployment ended with the death of the animal that was carrying the tag;
• dead/fall-off = The tag stopped moving, and it is not possible to determine whether it is due to death of the animal or unscheduled tag detachment;
• equipment-failure = The tag stopped working;
• fall-off = The attachment of the tag to the animal failed, and it fell of accidentally;
• other = other;
• released = The tag remained on the animal but the animal was released from captivity or confinement;
• removal = The tag was purposefully removed from the animal;
• scheduled-detachment = The tag was programmed to detach from the animal;
• transmission-end = The tag stopped transmitting usable data;
• unknown = The cause of the end of data availability or transmission is unknown.

[Rafnuss]

How to deal with the follow strange case

• [x] bird found dead with (or without tag)
• [x] bird capture a few days after the initial equipment. (no retrieval)
• [x] tag never equipped on a bird

[Rafnuss]

Follow-up question, do we make latitude/longitude required?

[Rafnuss]

Follow-up question, do we make latitude/longitude required?

Yes