Movebank Attribute Dictionary

The following are definitions of terms used in Movebank to describe studies, events (locations and sensor measurements), animals, deployments and tags. Movebank's data model uses these core entities to organize and document tracking and other animal-borne sensor data. Animals, deployments and tags are all part of each study's reference data.

These terms are also published as a persistent, machine-readable vocabulary at the Natural Environment Research Council's Vocabulary Server at http://vocab.nerc.ac.uk/collection/MVB. See the published version for data attributes accessible only by API, and representations in other formats including JSON and RDF/XML. This vocabulary can be cited as

Max Planck Institute of Animal Behavior. 2022. Movebank Attribute Dictionary. British Oceanographic Data Centre, Natural Environment Research Council Vocabulary Server. http://vocab.nerc.ac.uk/collection/MVB/current accessed on [date].

To request additions, select Request Attribute from during a data file import and fill out the form that appears.

Study terms

The following terms are used to describe individual studies in Movebank.

acknowledgements: Acknowledgements for the study. For example, people or institutions that provided logistics support or site access, and names of field assistants or collaborators.
example: We thank Carrie Smith and John Johnson for help in the field and the Delaware Parks Association for access to our research site and logistical support.
units: none
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000010

citation: One or more citations for the study. Include citations for published papers or reports describing the data in the study, or datasets derived from the study. If the data have not been published, an 'unpublished data' or 'in progress' citation should be used, listing authors and a title for the dataset.
example: McIntyre CL, Douglas DC, Collopy MW (2008) Movements of golden eagles (Aquila chrysaetos) from interior Alaska during their first year of independence. The Auk 125(1): 214-224. https://doi.org/10.1525/auk.2008.125.1.214
units: none
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000068

contact person: The name and username of the Movebank account for the person who is the contact for the study.
example: Rolandisimo (Roland Kays)
units: none
entity described: study
same as: contact person name
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000072

grants used: A list or description of grants and other funding sources for the research.
example: This project was funded by an NSF grant to RK.
units: none
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000123

license terms: Terms of use for the data in the study, provided by the study owner. Also see 'license type' for use of Creative Commons licenses. In addition to terms listed, the General Movebank Terms of Use and User Agreement apply for all studies.
example: Data can be viewed publicly and used for educational purposes, but cannot be shared or used in publications without prior written permission from principal investigator.
units: none
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000138

license type: The license that currently applies to data that are publicly downloadable from the study. Chosen by the study owner. If CUSTOM is selected, details may be available in 'license terms'. Allowed values are
CC_BY = Creative Commons Attribution (BY) License;
CC_BY_NC = Creative Commons Attribution-NonCommercial (BY-NC) License;
CC_0 = Creative Commons Universal (CC0) License;
CUSTOM = Custom terms of use defined by the study owner.
format: controlled list
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000257

main location lat: The latitude of the reference location for the study chosen by the data owner that is used as the location for the study marker shown on the Movebank map. This location can represent a colony, homing location, deployment site, research institute location, or other location relevant to the study.
example: 42.718
units: decimal degrees, WGS84 reference system
entity described: study
same as: study reference location latitude
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000222

main location long: The longitude of the reference location for the study chosen by the data owner that is used as the location for the study marker shown on the Movebank map. This location can represent a colony, homing location, deployment site, research institute location, or other location relevant to the study.
example: -73.856
units: decimal degrees, WGS84 reference system
entity described: study
same as: study reference location longitude
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000223

principal investigator: The principal investigator (PI) or lead researcher for the study. Reported either as the PI name or the name and username of the associated Movebank account.
example: Rolandisimo (Roland Kays)
units: none
entity described: study
same as: principal investigator name
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000164

principal investigator address: Address, affiliation or other contact information for the principal investigator (PI) or lead researcher for the study. Used when the PI does not have a Movebank account. Units: none
entity described: study
same as: PI contact details
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000234

principal investigator email: Email address for the principal investigator (PI) or lead researcher for the study. Used when the PI does not have a Movebank account. Units: none
entity described: study
same as: PI email
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000235

study ID: A unique identifier for the study in Movebank that is created automatically by the database.
example: 2911040
units: none
entity described: study
same as: Movebank ID
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000172

study name: The name of the study in Movebank.
example: Coyotes, Kays and Bogan, Albany NY
units: none
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000173

study reference location: This attribute has been merged with 'main location lat' and 'main location long'. Geographic coordinates for a reference location for the study, chosen by the data owner, which is used as the location for the study marker shown on the Movebank map. This location typically represents the deployment site and can represent a colony, homing location, or other location relevant to the study.
example: -73.856, 42.718
units: decimal degrees, WGS84 reference system
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000174

study summary: A description of the study objectives, methods, and results.
example: To examine how well coyotes survive in suburban areas in the study region by assessing individual movements, habitat use, survivorship and correlates of cause-specific mortality.
units: none
entity described: study
same as: study objective
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000176

study type: Type of study. Standard studies are 'research' studies.
format: controlled list
entity described: study
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000272

Animal terms

These terms are used to describe individual animals. Also see the deployment terms for information about animals that varies with time and typically represents conditions at capture and the start of deployment.

animal comments: Additional information about the animal that is not described by other reference data terms.
example: sibling of #1423
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000012

animal death comments: Comments about the death of the animal.
example: hit by a car
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000013

animal earliest date born: The earliest date an animal is thought to have been born.
example: 2001-01-01 00:00:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC (sometimes date is provided based on local time)
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000014

animal exact date of birth: The exact date on which animal was born.
example: 2001-10-31 00:00:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC (sometimes date is provided based on local time)
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000015

animal ID: An individual identifier for the animal, provided by the data owner. Values are unique within the study. If the data owner does not provide an Animal ID, an internal Movebank animal identifier is sometimes shown.
example: TUSC_CV5
units: none
entity described: individual
same as: individual local identifier
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000016

animal latest date born: The latest date an animal is thought to have been born.
example: 2001-12-12 00:00:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC (sometimes date is provided based on local time)
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000017

animal nickname: An alternate identifier for the animal. Used as the display name for animals shown in the Animal Tracker App.
example: Ali
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000020

animal ring ID: A number or color scheme for a band or ring attached to the animal.
example: 26225
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000022

animal sex: The sex of the animal. Allowed values are
m = male;
f = female;
u = unknown.
format: controlled list
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000023

animal taxon: The scientific name of the species on which the tag was deployed, as defined by the Integrated Taxonomic Information System (ITIS, www.itis.gov). If the species name can not be provided, this should be the lowest level taxonomic rank that can be determined and that is used in the ITIS taxonomy. Additional information can be provided using the term 'taxon detail'.
format: controlled list
entity described: individual
same as: individual taxon canonical name
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000024

animal taxon detail: A more specific name and/or reference for the taxon name provided by 'animal taxon'. This can be used, for example, to specify a subspecies or a taxon not supported by the ITIS.
example: Calonectris diomedea borealis (Cory, 1881)
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000025

Deployment terms

These terms are used to describe individual deployments of tags on animals.

alt project ID: A name or unique identifier for a project associated with the deployment, for example a monitoring program or another data platform. Best practice is to include the name of the related database or organization followed by the project identifier.
example: MOTUS145
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000244

animal life stage: The age class or life stage of the animal at the beginning of the deployment. Can be years or months of age or terms such as 'adult', 'subadult' and 'juvenile'. Best practice is to define units in the values if needed (e.g. '2 years').
example: juvenile, adult
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000018

animal mass: The mass of the animal, typically at the beginning of the deployment.
example: 500
units: grams
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000019

animal reproductive condition: The reproductive condition of the animal at the beginning of the deployment.
example: lactating
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000021

attachment type: The way a tag is attached to an animal. Values are chosen from a controlled list:
backpack-harness = The tag is attached to the animal using a backpack-style harness;
collar = The tag is attached by a collar around the animal's neck;
fin mount = The tag is attached to the animal's fin;
glue = The tag is attached to the animal using glue;
harness = The tag is attached to the animal using a harness;
implant = The tag is placed under the skin of the animal;
leg-band = The tag is attached as a leg band or ring;
leg-loop-harness = The tag is attached to the animal using a leg-loop-style harness;
none = No tag was attached, e.g., for observations using natural markings;
other = The tag is attached using another method;
suction-cup = The tag is attached using one or more suction cups;
tape = The tag is attached to the animal using tape.
format: controlled list
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000052

behavior according to: A description of behavioral categories contained in 'behavioural classification', how they were derived and/or a reference to the method or classification system used.
example: Behavior was derived using acceleration data and an automated algorithm calibrated using field observations.
units: none
entity described: deployment
same as: behaviour according to
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000066

data processing software: Name of the software program/s, scripts, etc. used to process raw sensor data and derive location estimates.
example: BASTrack
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000073

deploy off latitude: The geographic latitude of the location where the deployment ended. Intended primarily for cases in which the recapture, tag retrieval or other final location has higher accuracy than that derived from sensor data.
example: -38.6866
units: decimal degrees, WGS84 reference system
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000074

deploy off longitude: The geographic longitude of the location where the deployment ended. Intended primarily for cases in which the recapture, tag retrieval or other final location has higher accuracy than that derived from sensor data.
example: 146.3104
units: decimal degrees, WGS84 reference system
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000075

deploy off person: The name of the person/people who removed the tag from the animal and ended the deployment.
example: J. Smith
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000076

deploy off timestamp: The timestamp when the tag deployment ended. Data records recorded after this day and time are not associated with the animal related to the deployment. Values are typically defined by the data owner, and in some cases are created automatically during data import. Further information can be provided in 'deployment end type' and 'deployment end comments'.
example: 2009-10-01 12:00:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC or GPS time
entity described: deployment
same as: deploy off date
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000077

deploy on latitude: The geographic latitude of the location where the animal was released. Intended primarily for cases in which the animal release location has higher accuracy than that derived from sensor data.
example: 27.3516
units: decimal degrees, WGS84 reference system
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000078

deploy on longitude: The geographic longitude of the location where the animal was released. Intended primarily for cases in which the animal release location has higher accuracy than that derived from sensor data.
example: -97.3321
units: decimal degrees, WGS84 reference system
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000079

deploy on person: The name of the person/people who attached the tag to the animal and began the deployment.
example: G. Smith
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000080

deploy on timestamp: The timestamp when the tag deployment started. Data records recorded before this day and time are not associated with the animal related to the deployment. Values are typically defined by the data owner, and in some cases are created automatically during data import.
example: 2008-08-30 18:00:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC or GPS time
entity described: deployment
same as: deploy on date
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000081

deployment comments: Additional information about the tag deployment that is not described by other reference data terms.
example: body length 154 cm; condition good
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000082

deployment end comments: Additional information about the end of a tag deployment. Also see 'deployment end type', 'animal death comments', and 'tag failure comments'.
example: data transmission stopped after 108 days. Cause unknown
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000083

deployment end type: A categorical classification describing the end of the tag deployment on the animal. Best practice is to clarify how the 'deploy-off timestamp', if present, was chosen. Values are chosen from a controlled list:
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.
format: controlled list
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000084

deployment ID: A unique identifier for the deployment of a tag on animal, provided by the data owner. If the data owner does not provide a Deployment ID, an internal Movebank deployment identifier may sometimes be shown.
example: Jane-Tag42
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000085

duty cycle: Remarks associated with the duty cycle of a tag during the deployment, describing the times it is on/off and the frequency at which it transmits or records data. Units and time zones should be defined in the remarks.
example: 15-min fixes from 8:00-18:00 local time (0:00-10:00 UTC)
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000086

geolocator calibration: A description of how solar geolocators were calibrated. Best practice is to refer to a publication and/or analysis software/parameters used.
example: on-animal calibration over a two-week period in the breeding site; see Jameson et al. (2011)
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000106

geolocator light threshold: The light threshold used for location estimation with solar geolocators. Range and units may vary by provider and tag settings.
example: 16
units: not defined
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000108

geolocator sensor comments: Description of light and other sensors, e.g. range of light intensity, light spectra (nm) that is not described by other reference data terms.
example: tag includes light-level and wet-dry sensors
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000109

geolocator sun elevation angle: The sun elevation angle used for location estimation with solar geolocators.
example: -2.86
units: degrees
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000110

habitat according to: A description of habitat categories contained in 'habitat', how they were derived and/or a reference to the method or classification system used.
example: visual analysis using 2018 satellite imagery
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000128

location accuracy comments: Comments about the location accuracy. This can further describe values provided in 'location error text', 'location error numerical', 'vertical error numerical', 'lat lower', 'lat upper', 'long lower' and/or 'long upper'. The percentile uncertainty can be provided using 'location error percentile'.
example: 1 standard deviation errors, assuming normal distribution, provided by the GPS unit
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000141

manipulation comments: Additional comments about the way in which the animal was manipulated during the deployment. Use 'manipulation type' to define the general type of manipulation.
example: Relocated from breeding colony on Smithers Island to release location at 70.02E, 21.21S
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000154

manipulation type: The way in which the animal was manipulated during the deployment. Additional information can be provided using 'manipulation comments'. Values are chosen from a controlled list:
confined = The animal's movement was restricted to within a defined area;
domesticated = The animal is domesticated, for example, is a house pet or part of a managed herd;
manipulated-other = The animal was manipulated in some other way, such as a physiological manipulation;
none = The animal received no treatment other than tag attachment and related measurements and sampling (if applicable);
reintroduction = The animal has been reintroduced as part of wildlife conservation or management efforts;
relocated = The animal was released from a site other than the one at which it was captured.
format: controlled list
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000155

study site: A location such as the deployment site or colony, or a location-related group such as the herd or pack name.
example: Pickerel Island North
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000175

tag readout method: The way the data are received from the tag. Values are chosen from a controlled list:
ISS = Data are transferred via the International Space Station;
LPWAN = Data are transferred through a low-power wide-area network, such as LoRa or Sigfox;
multiple = Data are acquired using multiple methods;
none = Data are obtained without use of an animal-borne tag, such as by observing a unique marking;
other-wireless = Data are transferred via another form of wireless data transfer, such as a VHF transmitter/receiver;
phone-network = Data are transferred via a phone network, such as GSM or AMPS;
satellite = Data are transferred via satellite;
tag-retrieval = The tag must be physically retrieved in order to obtain the data;
telemetry-network = Data are obtained through a radio or acoustic telemetry network;
Wi-Fi/Bluetooth = Data are transferred via a local Wi-Fi or Bluetooth system.
format: controlled list
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000188

Tag terms

These terms are used to describe individual tags. Also see the deployment terms for information about tags that can vary between deployments.

tag beacon frequency: The frequency of the radio tag or tag retrieval beacon.
example: 450.5
units: MHz
entity described: tag
same as: beacon frequency
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000065

tag comments: Additional information about the tag that is not described by other reference data terms.
example: custom-made Doppler shift Argos tag with a special altitude sensor
units: none
entity described: tag
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000179

tag failure comments: Comments about tag malfunction or failure.
example: tag stopped transmitting 23/12/08, was not found
units: none
entity described: tag
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000180

tag ID: An identifier for the tag, provided by the data owner. Values are unique within the study. If the data owner does not provide a tag ID, an internal Movebank tag identifier may sometimes be shown.
example: 2342
units: none
entity described: tag
same as: tag local identifier
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000181

tag manufacturer name: The company or person that produced the tag.
example: Holohil
units: none
entity described: tag
same as: manufacturer name
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000183

tag mass: The mass of the tag.
example: 24
units: grams
entity described: tag
same as: weight
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000184

tag model: The model of the tag.
example: T61
units: none
entity described: tag
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000185

tag production date: The approximate date the tag was produced (can be a year, month, or day).
example: March 2011
units: none
entity described: tag
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000187

tag serial no: The serial number of the tag.
example: MN93-33243
units: none
entity described: tag
same as: serial no
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000189

Event terms

These terms are used to describe individual locations or other sensor measurements (events).

acceleration axes: The enabled accelerometer axes.
example: XYZ
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000001

acceleration raw x: Raw acceleration values provided by the tag for the X axis. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: 0.556641
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000002

acceleration raw y: Raw acceleration values provided by the tag for the Y axis. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: 0.09375
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000003

acceleration raw z: Raw acceleration values provided by the tag for the Z axis. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: -0.84375
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000004

acceleration sampling frequency per axis: The sampling frequency for one axis of an accelerometer within a burst.
example: 5.93
units: Hz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000005

acceleration x: Acceleration values provided by the tag for the X axis. For acceleration values not in units of m/s^2, use 'acceleration raw x'.
example: -0.125
units: m/s^2
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000006

acceleration y: Acceleration values provided by the tag for the Y axis. For acceleration values not in units of m/s^2, use 'acceleration raw y'.
example: -0.156
units: m/s^2
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000007

acceleration z: Acceleration values provided by the tag for the Z axis. For acceleration values not in units of m/s^2, use 'acceleration raw z'.
example: 0.453
units: m/s^2
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000008

accelerations raw: Burst of raw acceleration sensor values. Range and units may vary by provider, tag, and orientation of the sensor on the animal. To interpret values, best practice is to further define the measurements using 'acceleration axes' and 'acceleration sampling frequency per axis', and to order the burst by alternating one measurement for each active axis in alphabetical order.
example: 1844 1889 1653 1845 1896 1653 1837 1897 1653 1842 1898 1650 1844 1899 1644 1840...
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000009

activity count: A value provided by some tags that can be used to generally indicate whether an animal is active.
example: 209
units: count
entity described: event
same as: GPS Activity Count
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000114

algorithm marked outlier: Identifies events marked as outliers using a user-selected filter algorithm in Movebank. Outliers have the value TRUE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000011

angular velocities raw: Burst of angular velocity values along the X, Y, and/or Z axes of the tag, depending on which axes are enabled. Measurements alternate one measurement for each active axis in alphabetical order. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: 19.5625 -53.0625 7.1250 71.3125 -130.3125 15.9375 123.4375 -140.7500 8.6250
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000245

angular velocity X: The speed of rotational motion around the X axis of the gyroscope.
example: 6.0625
units: deg/s
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000246

angular velocity Y: The speed of rotational motion around the Y axis of the gyroscope.
example: -1.875
units: deg/s
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000247

angular velocity Z: The speed of rotational motion around the Z axis of the gyroscope.
example: 0.8125
units: deg/s
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000248

Argos altitude: Altitude used for location calculation, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 27
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000026

Argos best level: Best signal strength, Argos diagnostic data (definition from Argos User's Manual 2011).
example: -117
units: dB
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000027

Argos calcul freq: Calculated frequency, Argos diagnostic data. It should be between 401.620 and 401.680 MHz (definition from Argos User's Manual 2011). The '401.' is sometimes missing from the source data and should be added to the values for correct intepretation.
example: 401.6732709
units: MHz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000028

Argos error radius: One standard deviation (sigma) of the estimated location error, assuming isotropic error, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 229
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000029

Argos GDOP: Geometric dilution of precision, a measure of the effect of the geometry of the satellite-beacon configuration on location accuracy, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 254
units: m/Hz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000030

Argos IQ: This quality indicator gives information on the transmitter in terms of two digits, X and Y. X is the first digit and indicates residual error on the frequency calculation; Y is the second digit and indicates transmitter oscillator frequency drift between two satellite passes. Values provided in Argos diagnostic data (definition from Argos User's Manual 2011). Values obtained through some Argos channels do not include leading 0s, so 1-digit values indicate X = 0 and blank values or values of '0' indicate both X and Y = 0. Allowed values are
X = 0: No calculation of residual frequency error (fewer than four messages received);
X = 1,2,3: Unsatisfactory convergence of calculation;
X = 4: Residual frequency error > 1.5 Hz;
X = 5: 0.15 Hz < residual frequency error < 1.5 Hz;
X = 6: Residual frequency error < 0.15 Hz;
Y = 0: No check on transmit frequency drift, as the two results are more than 12 hours apart;
Y = 1: Frequency discrepancy > 400 Hz Probably due to transmit frequency discrepancy, change of oscillator, etc.;
Y = 2: Previous location is less than 1/2 hour old. Frequency discrepancy > 30 Hz, i.e. F/F (over 10 min) >2.5 E-8;
Y = 3: Frequency drift > 4 Hz/minute, i.e. F/F (10 min) > 1.10-7;
Y = 4: Frequency drift < 4 Hz/minute, i.e. F/F (10 min) < 1.10-7;
Y = 5: Frequency drift < 2 Hz/minute, i.e. F/F (10 min) < 5.10-8;
Y = 6: Frequency drift < 1 Hz/minute, i.e. F/F (10 min) < 2.5 . 10-8;
Y = 7: Frequency drift < 0.4 Hz/minute, i.e. F/F (10 min) < 1.10-8;
Y = 8: Frequency drift < 0.2 Hz/minute, i.e. F/F (10 min) < 5.10-9.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000031

Argos lat1: Solution 1. platform latitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 19.493
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000032

Argos lat2: Solution 2. platform latitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 14.773
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000033

Argos LC: The location class retrieved from Argos, Argos diagnostic data. Classes are based on the type of location (Argos Doppler Shift or GPS) and the number of messages received during the satellite pass. Location classes in order of decreasing accuracy are G (GPS), 3, 2, 1, 0, A, B and Z (definition from Argos User's Manual V1.6.6, 2016)
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000034

Argos location algorithm: The processing algorithm used by Argos to estimate locations using Doppler shift. If the location data represent model output rather than the original estimates from Argos, also use 'modelled'. Values are chosen from a controlled list:
least squares = locations were calculated by Argos using a least-squares analysis;
Kalman = locations were calculated by Argos using Kalman filtering.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000278

Argos lon1: Solution 1. platform longitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 99.712
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000035

Argos lon2: Solution 2. platform longitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 120.286
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000036

Argos nb mes: The number of messages received [to calculate location], Argos diagnostic data (definition from Argos User's Manual 2011).
example: 8
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000037

Argos nb mes 120: The number of messages received by the satellite at a signal strength greater than -120 decibels, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 2
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000038

Argos NOPC: Number of plausibility checks successful (from 0-4), Argos diagnostic data (definition from Argos User's Manual 2011).
example: 3
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000039

Argos orientation: The orientation of the semi-major axis of the error elipse, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 83
units: degrees clockwise from north
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000040

Argos pass duration: Time elapsed between the first and last message received by the satellite, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 118
units: seconds
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000041

Argos sat ID: The satellite identifier, Argos diagnostic data (definition from Argos User's Manual 2011).
example: P
units: none
entity described: event
same as: Argos satellite ID
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000042

Argos semi major: Length of the semi-major axis of the error ellipse, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 300
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000043

Argos semi minor: Length of the semi-minor axis of the error ellipse, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 175
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000044

Argos sensor 1: The value of the first Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 229
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000045

Argos sensor 2: The value of the second Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 42
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000046

Argos sensor 3: The value of the third Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 3
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000047

Argos sensor 4: The value of the fourth Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 63
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000048

Argos transmission timestamp: UTC time for the location, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 2012-03-26 12:27:32.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000049

Argos valid location algorithm: Indicates which of the two location estimates provided by Argos is the valid location, using a user-selected filter algorithm in Movebank. Allowed values are
1 = The Argos filter algorithm has chosen the primary location (solution 1, lat1/lon1) as the valid location;
2 = The Argos filter algorithm has chosen the alternate location (solution 2, lat2/lon2) as the valid location.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000050

Argos valid location manual: Indicates which of the two location estimates provided by Argos is the valid location, as chosen by the user. Values override the results of 'Argos valid location algorithm'. Allowed values are
1 = The user has chosen the primary location (solution 1, lat1/lon1) as the valid location;
2 = The user has chosen the alternate location (solution 2, lat2/lon2) as the valid location.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000051

barometric depth: The barometric water pressure depth.
example: -11
units: meters
entity described: event
same as: bar barometric depth
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000053

barometric height: Altitude estimated by a barometric pressure sensor on the tag.
example: 179
units: meters
entity described: event
same as: bar barometric height
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000054

barometric pressure: The barometric air or water pressure.
example: 32536.0
units: mbar (hPa)
entity described: event
same as: bar barometric pressure
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000055

BAS compensated latitude: Latitude compensated for longitudinal movement assuming uniform movement, .trj (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 86.03
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000056

BAS confidence: Confidence level of the fix, defined by the individual who processed the data (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 9
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000057

BAS fix type: Time of day used to obtain location estimate (definition from British Antarctic Survey Geolocator Manual v. 8, 2010). Allowed values are
noon = The fix was obtained using sunrise followed by sunset;
midnight = The fix was obtained using sunset followed by sunrise.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000058

BAS mid value secs: The time of local noon/midnight as number of seconds since 1st Jan 1900 (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 39734.64931
units: seconds
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000059

BAS stationary latitude: The latitude [of the location estimate] calculated using a stationary target (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 84.18
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000060

BAS transition 1: Time of sunrise (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 0.530555555555556
units: GMT
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000061

BAS transition 2: Time of sunset (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 0.690972222222222
units: GMT
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000062

battery charge percent: The battery charge as a percentage of full charge.
example: 25
units: none (percent)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000063

battery charging current: The battery charging current reported by the tag.
example: 0
units: milliamperes (mA)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000064

behavioural classification: Behavioural classifications assigned to the animal. Information about the values and how they were obtained can be provided in 'behaviour according to'. Recommended best practice is to use a controlled list.
example: roosting, foraging, running
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000067

comments: Additional information about events that is not described by other event data terms.
example: we observed the animal foraging (see photo BT25)
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000069

compass heading: The tilt-compensated horizontal compass heading.
example: 62
units: degrees clockwise from magnetic north
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000070

conductivity: The maximum conductivity recorded during the measurement interval. Range and units may vary by provider and tag settings.
example: 17
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000071

CPU temperature: Temperature reported by the CPU core on the tag.
example: 26.65
units: degrees Celsius
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000249

CTT solar current since last fix: The cumulative current pushed from the solar panel into the battery of a CTT tag since the last GPS fix.
example: 231
units: milliamperes (mA)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000300

data decoding software: The name or version of software used to decode the sensor data.
example: 11
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000214

ECG raw: Raw ECG values provided by the tag. Range and units may vary by provider and tag settings. Units: not defined
entity described: event
same as: heartrate ECG raw
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000281

ECG sampling frequency: The sampling frequency for ECG measurements. Units: Hz
entity described: event
same as: heartrate ECG sampling frequency
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000282

ECGs raw: Burst of raw ECG values. Range and units may vary by provider and tag settings. In some cases, values can be multiplied by 'voltage resolution' to obtain voltages. Units: not defined
entity described: event
same as: heartrate ECGs raw
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000283

end timestamp: The date and time when the sampling interval or burst ended.
example: 2011-01-03 13:45:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC or GPS time
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000102

eobs acceleration axes: This tells you about the enabled ACC axes, like X and/or Y and/or Z (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011).
example: XYZ
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000087

eobs acceleration sampling frequency per axis: This is the sampling frequency for one axis. Don't mix this up with the sampling frequency for all axes together. For example if you have three ACC axes enabled, then the sampling frequency for all axes together is three times the sampling frequency for one axis. The sampling frequency is measured in Hertz, which is the same as 1/second. For example a sampling frequency of 10 Hz means that you get 10 samples per second (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011).
example: 5.93
units: Hz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000088

eobs accelerations raw: Acceleration along the X and or Y and or Z axes of the tag, depending on which axes were activated on the tag as described in 'eobs acceleration axes'. Measurements alternate one measurement for each active axis in alphabetical order. The values are digital readings between 0 and 4095 of the analogue digital converter on the tag, and can be converted to m/s^2 with proper calibration. These samples are made at the rate described by the field 'eobs acceleration sampling frequency per axis' starting with the first sample at the time described in the field 'e-obs start timestamp'. Tags with numbers e-obs numbers 2242 and higher, which began being provided in spring 2012, have Y-axis values in the opposite direction from those in older tags (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011; Wolfgang Heidrich, e-obs Digital Telemetry, personal communication, 2012).
example: 1844 1889 1653 1845 1896 1653 1837 1897 1653 1842 1898 1650 1844 1899 1644 1840...
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000089

eobs activity: An indication of activity since the previous data message was sent, based on raw acceleration data, provided in SMS messages sent by e-obs GSM tags. Values range from 0 (least activity) to 256 (most activity). The number of acceleration measurements used to determine activity is indicated in e-obs activity samples (Wolgang Heidrich, e-obs Digital Telemetry, personal communication, 2013). Units: not specified
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000090

eobs activity samples: The number of acceleration measurements used to calculate e-obs activity divided by 171. This is provided in SMS messages sent by GSM tags (Wolgang Heidrich, e-obs Digital Telemetry, personal communication, 2013). Units: not specified
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000091

eobs battery voltage: Unloaded battery voltage (definition from Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012).
example: 3712
units: mV
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000092

eobs fix battery voltage: Loaded battery voltage, i.e. battery voltage when GPS module is acquiring a fix (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010
Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012).
example: 3535
units: mV
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000093

eobs horizontal accuracy estimate: A horizontal (in)accuracy estimate, calculated by the GPS module (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010
Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012).
example: 35.07
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000094

eobs key bin checksum: A checksum of the original binary data, so that Movebank can quickly compare different lines by comparing their checksums (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011).
example: 4152324118
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000095

eobs speed accuracy estimate: A speed (in)accuracy estimate, calculated by the GPS module. The speed accuracy estimate (better named 'inaccuracy estimation') may show very high values, since the GPS module calculates a very conservative value. These speed measurements are potentially very inaccurate when interpreting the data (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010
Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012).
example: 6.58
units: m/s
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000096

eobs start timestamp: The date and time of day when the acceleration burst belonging to this line begins. The exact time of the first sample is a little later (up to 1 second) for older e-obs tags, especially when the ACC-pinger is enabled (4 pings before the start of each ACC burst) (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011).
example: 2011-01-03 13:45:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: GPS time
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000097

eobs status: The record status, from e-obs GPS/accelerometer tags (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010). Allowed values are
A = position and time within accuracy masks;
B = only time of week and weeknumber valid;
C = only weeknumber valid;
D = no valid data.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000098

eobs temperature: Temperature
this value is not calibrated and therefore very inaccurate (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010).
example: 45, -8
units: degrees Celsius
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000099

eobs type of fix: The type of fix of data from e-obs GPS/accelerometer tags (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010). Allowed values are 3 = 3D fix and 2 = 2D fix.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000100

eobs used time to get fix: The amount of time that was needed for this GPS fix
interesting for estimating power requirements (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010).
example: 22
units: seconds
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000101

event ID: An identifier for the set of values associated with each event, i.e. sensor measurement. A unique event ID is assigned to every time-location or other time-measurement record in Movebank. If multiple measurements are included within a single row of a data file, they will share an event ID. If users import the same sensor measurement to Movebank multiple times, a separate event ID will be assigned to each.
example: 6340565
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000103

external temperature: The temperature measured by the tag (different from ambient temperature or internal body temperature of the animal).
example: 32.1
units: degrees Celsius
entity described: event
same as: temperature external
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000104

Flt switch: The 'switch' value provided by Fleetronic tags. Identifies the action carried out by the tag, relevant for logger performance testing and data filtering (definition from Kris Van Uffelen, Fleetronic, personal communication 2014). Allowed values are
0 = SV_LowestPositionSwitch;
6 = SV_PositionAcceleration;
48 = SV_PowerUp;
49 = SV_InternalStatus1;
64 = SV_Network;
69 = SV_ReceivedSMS;
72 = SV_SettingsAccepted;
77 = SV_TimeAlive;
112 =SV_LcdData1.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000105

geolocator fix type: The period of day (or a value indicating the period of day) used to estimate location by geolocation.
example: sunrise
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000107

geolocator rise: The period of day used to estimate location by geolocation. TRUE = sunrise, FALSE = sunset. Units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000215

geolocator twilight3: The date and time of twilight detected by automated processing.
example: 2008-08-14 18:31:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC or GPS time
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000216

GMatrix alert: Alert status of the G-Matrix tag. The value is 0 if there is no alert and a numeric value greater than 0 if there is an alert. Further information about alerts is provided in 'GMatrix alert message' (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: 19
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000301

GMatrix alert message: If Alert > 0 then the alert message which shows information regarding why the alert was generated (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: P1 Panic
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000302

GMatrix device type: The type of the G-Matrix device (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: 12
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000303

GMatrix event: The G-Matrix event (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
16 = Panic;
48 = Short press;
49 = Single press;
50 = Double press;
51 = Triple press;
52 = Long press;
80 = Fall.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000304

GMatrix firmware version: The firmware version of the G-Matrix tag (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: 8
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000305

GMatrix GPS event: The G-Matrix GPS event (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
0 = Unknown location;
1 = Alert;
2 = Panic;
3 = Timed;
4 = Fall;
5 = Heartbeat.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000306

GMatrix GPS event text: The text equivalent of 'GMatrix GPS event' (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
Unknown location;
Alert;
Panic;
Timed;
Fall;
Heartbeat.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000307

GMatrix GPS fix interval: The GPS fix interval for the G-Matrix tag (0 means disabled) (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: 69
units: seconds
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000308

GMatrix GPS fix interval text: The text equivalent of 'GMatrix GPS fix interval' (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: 5 minutes
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000309

GMatrix hardware version: The hardware version of the G-Matrix tag (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: 1
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000310

GMatrix is moving: Whether the G-Matrix device is moving (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
A1 = true (moving);
0 = false (static).
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000311

GMatrix is moving text: The text equivalent of 'GMatrix is moving' (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are MOVING or STATIC.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000312

GMatrix last location: The last known location of the G-Matrix tag (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
null = not available;
0 = new location;
1 = last known location.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000313

GMatrix last location text: The text equivalent of 'GMatrix last location' (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
not available;
new location;
last known location.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000314

GMatrix mode: The currently configured G-Matrix mode (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
0 = reserved;
1 = help me;
2 = press it;
3 = track it;
4 = guard it;
5 = monitor it;
6 = don’t lose it.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000315

GMatrix mode text: The text equivalent of 'GMatrix mode' (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are
reserved;
help me;
press it;
track it;
guard it;
monitor it;
don't lose it.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000316

GMatrix packet type: The type of G-Matrix packet. The value 0 indicates status packet (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021).
example: 2
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000317

GPS DOP: Dilution of precision provided by the GPS.
example: 1.8
units: unitless
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000115

GPS fix type: The type of GPS fix. To import non-numeric characters use 'GPS fix type raw'. Allowed values are
1 = no fix;
2 = 2D fix (altitude typically not valid);
3 = 3D fix (altitude typically valid).
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000116

GPS fix type raw: The type of GPS fix as provided by the tag. Common values are 1D = no fix;
2D = altitude typically not valid;
3D = altitude typically valid. Other values might be present. Where possible, use 'GPS fix type'.
example: 3D
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000117

GPS HDOP: Horizontal dilution of precision provided by the GPS.
example: 1.2
units: unitless
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000118

GPS maximum signal strength: The signal reception strength of the strongest GPS satellite of those used to calculate the location estimate.
example: 39
units: dBm
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000119

GPS message count: The number of messages transmitted to satellites.
example: 278
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000251

GPS PDOP: Position dilution of precision provided by the GPS.
example: 1.9
units: unitless
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000284

GPS satellite count: The number of GPS satellites used to estimate the location.
example: 8
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000120

GPS speed accuracy estimate: Estimated accuracy of the ground speed. Units: m/s
entity described: event
same as: speed accuracy estimate
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000237

GPS time to fix: The time required to obtain the GPS location fix.
example: 36
units: seconds
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000121

GPS twilight: An indication of twilight or time of day based on the GPS location and timestamp.
example: DARK
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000285

GPS VDOP: Vertical dilution of precision provided by the GPS.
example: 1.9
units: unitless
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000122

ground speed: The estimated ground speed provided by the sensor or calculated between consecutive locations.
example: 7.22
units: m/s
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000124

GSM MCC-MNC: The mobile country code (MCC) (digits 1-3) and mobile network code (MNC) (digits 4-5 or 4-6) uniquely identifying the wireless operator through which the data are transferred.
example: 50711
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000125

GSM signal strength: An integer proportional to the GSM signal strength measured by the tag. Valid values are 0–31, or 99 for unknown or undetectable. Higher values indicate better signal strength.
example: 39
units: arbitrary strength units (asu)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000126

Gt sys week: The week number since the device was activated (definition from GeoTrak's 'PTT Decode Overview', 2014).
example: 4
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000111

Gt tx count: The number of transmissions since last rollover (definition from GeoTrak's 'PTT Decode Overview', 2014).
example: 4840
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000112

gyroscope axes: The enabled gyroscope axes.
example: XYZ
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000252

gyroscope sampling frequency per axis: The sampling frequency for each axis measured by the gyroscope. Can be used to report bursts of values associated with a single timestamp.
example: 5.93
units: Hz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000253

habitat: A category or description of the habitat. Information about the values and how they were obtained can be provided in 'habitat according to'.
example: oak savannah
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000127

heading: The direction in which the tag is moving, in decimal degrees clockwise from north, as provided by the sensor or calculated between consecutive locations. Values range from 0-360: 0 = north, 90 = east, 180 = south, 270 = west.
example: 315.88
units: degrees clockwise from north
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000129

heart rate: The animal's heart rate. Units: beats per minute
entity described: event
same as: heartrate heart rate
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000287

height above ellipsoid: The estimated height above the ellipsoid, typically estimated by the tag. If altitudes are calculated as height above mean sea level, use 'height above mean sea level'.
example: 24.8
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000130

height above mean sea level: The estimated height of the tag above mean sea level, typically estimated by the tag. If altitudes are calculated as height above an ellipsoid, use 'height above ellipsoid'.
example: 34
units: meters
entity described: event
same as: height above msl
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000131

height raw: Raw values for the height of the tag above ellipsoid or mean sea level, typically estimated by the tag. Values are stored as raw text values because non-numeric characters are used or processing is required to derive the correct height estimate. Best practice is to define values in the reference data.
example: 425, 2D fix
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000132

Icarus solar cell current: The charging current of the solar cell reported by an Icarus transmitter. Units: milliamperes (mA)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000288

import marked outlier: Identifies events as outliers. Typically used to import a record of outliers that were identified by the data provider or owner with automated methods outside of Movebank. Outliers have the value TRUE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000133

internal temperature: The internal body temperature of the animal measured by the tag.
example: 37.1
units: degrees Celsius
entity described: event
same as: temperature internal
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000256

lat lower: The lower bound of the latitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'.
example: 23.4
units: decimal degrees, WGS84 reference system
entity described: event
same as: latitude lower
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000136

lat upper: The upper bound of the latitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'.
example: 32.4
units: decimal degrees, WGS84 reference system
entity described: event
same as: latitude upper
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000137

light level: Light-level values measured by a solar geolocator. Range and units may vary by provider and tag settings. Best practice is to define values in the reference data.
example: 28
units: not defined
entity described: event
same as: gls light level
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000139

location error numerical: An estimate of the horizontal error of the location including only numbers. (If the error estimates include non-numerical characters such as '>' use 'location error text'.) These values can be described using 'location error percentile' and 'location accuracy comments'.
example: 50
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000142

location error percentile: The percentile error for horizontal error values provided in 'location error text', 'location error numerical', 'lat lower', 'lat upper', 'long lower' and/or 'long upper'. Additional comments about these values can be provided using 'location accuracy comments'.
example: 67
units: none (percent)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000143

location error text: An estimate of the horizontal error of the location estimate, typically provided in the original data file, described using more than numbers. Units should be provided in the values. (If the values are purely numeric, use 'location error numerical'.) Best practice is to define values and units using 'location error percentile' and/or 'location accuracy comments'.
example: > 25 ft
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000144

location lat: The geographic latitude of the location as estimated by the sensor.
example: -41.0982423
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000145

location long: The geographic longitude of the location as estimated by the sensor. Positive values are east of the Greenwich Meridian, negative values are west of it.
example: -121.1761111
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000146

long lower: The lower bound of the longitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'.
example: 0.236
units: decimal degrees, WGS84 reference system
entity described: event
same as: longitude lower
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000147

long upper: The upper bound of the longitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'.
example: -0.489
units: decimal degrees, WGS84 reference system
entity described: event
same as: longitude upper
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000148

Lotek CRC status: Cyclic Redundancy Check (raw values) provided by Lotek. These translate to the values stored in 'Lotek CRC status text' (definition from '11884 PinPoint User Manual Rev 5.pdf', Lotek, personal correspondence 2018). Allowed values are
G = OK (good data);
E = Fail (data has been corrupted on transmission, and therefore cannot be trusted);
F = OK(corrected) (the message was corrected with Lotek's error correction algorithm).
format: controlled list
entity described: event
same as: Lot CRC status
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000149

Lotek CRC status text: Cyclic Redundancy Check provided by Lotek (definition from '11884 PinPoint User Manual Rev 5.pdf', Lotek, personal correspondence 2018). Allowed values are
OK = good data;
Fail = data has been corrupted on transmission, and therefore cannot be trusted;
OK(corrected) = the message was corrected with Lotek's error correction algorithm.
format: controlled list
entity described: event
same as: Lot CRC status text
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000150

magnetic field axes: The enabled magnetometer axes.
example: XYZ
units: none
entity described: event
same as: mag magnetic field axes
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000219

magnetic field raw x: Raw magnetic field values provided by the tag for the X axis. May include an unknown offset. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: -0.5197
units: not defined
entity described: event
same as: mag magnetic field raw x
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000151

magnetic field raw y: Raw magnetic field values provided by the tag for the Y axis. May include an unknown offset. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: -0.993
units: not defined
entity described: event
same as: mag magnetic field raw y
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000152

magnetic field raw z: Raw magnetic field values provided by the tag for the Z axis. May include an unknown offset. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: -0.8857
units: not defined
entity described: event
same as: mag magnetic field raw z
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000153

magnetic field sampling frequency per axis: The sampling frequency for each axis measured by the magnetometer. Can be used to report bursts of values associated with a single timestamp.
example: 20
units: Hz
entity described: event
same as: mag magnetic field sampling frequency per axies
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000220

magnetic field x: The magnetic field strength measured by the magnetometer for the X axis. For magnetic field strength values not in units of microtesla, use 'magnetic field raw x'.
example: 40.1367
units: microtesla (μT)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000258

magnetic field y: The magnetic field strength measured by the magnetometer for the Y axis. For magnetic field strength values not in units of microtesla, use 'magnetic field raw y'.
example: -12.3047
units: microtesla (μT)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000259

magnetic field z: The magnetic field strength measured by the magnetometer for the Z axis. For magnetic field strength values not in units of microtesla, use 'magnetic field raw z'.
example: 99.0234
units: microtesla (μT)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000260

magnetic fields raw: Burst of magnetic field values along the X, Y, and/or Z axes of the tag, depending on which axes are enabled. Measurements alternate one measurement for each active axis in alphabetical order. Range and units may vary by provider, tag, and orientation of the sensor on the animal.
example: -1 115 -29 12 112 -26 3 103 -27 14 112 -30 10 108 -22 12 100 -30 6 106 -26 16 102 -26 2 102 -18 2 102 -18
units: not defined
entity described: event
same as: mag magnetic fields raw
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000221

manually marked outlier: Identifies events flagged manually as outliers, typically using the Event Editor in Movebank, and may also include outliers identified using other methods. Outliers have the value TRUE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000156

manually marked valid: An event marked manually as valid to override the results of a Movebank data filter (stored in 'algorithm marked outlier'), typically using the Event Editor in Movebank. These values also override values in 'manually marked outlier' and 'import marked outlier'. Records marked as valid have the value TRUE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000157

migration stage: The migration stage of the animal. Values are specific to the study. To use a controlled list of migration stages that can be compared across studies, use migration stage standard.
example: Stopover #1d
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000160

migration stage standard: Migration state of the animal. Values are chosen from a controlled list:
altitudinal migration;
breeding grounds;
fall migration;
foraging grounds;
foraging migration;
irruptive migration;
latitudinal migration;
migration to molt site;
molt site;
natal area;
nomadic migration;
other seasonal migration;
removal migration;
reproductive migration;
spawning grounds;
spring migration;
stopover;
summer non-breeding;
vertical migration (aquatic);
wintering grounds.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000161

modelled: Can be used to identify locations or light level values that are modelled, interpolated, or otherwise added or changed based on original sensor measurements. These may include movement model outputs, locations added to create a dataset with equal time intervals, etc. Details about the procedures used can be provided in 'data processing software'. Allowed values are TRUE or FALSE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000162

mortality status: The mortality status, as reported by the tag. Use 'animal death comments' to report details about the death of the animal.
example: 1
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000261

Mw activity count: The activity counter value. This value increments when the PTT is moving while it is transmitting. If the activity counter is constant for two or more transmission periods (and the GPS locations are unvarying), you should consider the possibility that the PTT has become detached or the bird is down (definition from the Microwave Telemetry, Inc. Solar Argos/GPS PTT-100 Field Manual, 2012).
example: 209
units: count
entity described: event
same as: Microwave activity count
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000158

Mw show in KML: Used by Microwave GPS tags to flag implausible locations. Allowed values are TRUE or FALSE; implausible locations have the value FALSE.
units: none
entity described: event
same as: Microwave show in KML
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000159

orientation quaternion raw w: The w component of the quaternion representing the orientation of the tag, in raw values provided by the tag. Component values must be converted in order to get true quaternions.
example: 492
units: not defined
entity described: event
same as: quaternion-raw-w
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000228

orientation quaternion raw x: The x component of the quaternion representing the orientation of the tag, in raw values provided by the tag. Component values must be converted in order to get true quaternions.
example: -90
units: not defined
entity described: event
same as: quaternion-raw-x
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000229

orientation quaternion raw y: The y component of the quaternion representing the orientation of the tag, in raw values provided by the tag. Component values must be converted in order to get true quaternions.
example: 127
units: not defined
entity described: event
same as: quaternion-raw-y
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000230

orientation quaternion raw z: The z component of the quaternion representing the orientation of the tag, in raw values provided by the tag. Component values must be converted in order to get true quaternions.
example: -103
units: not defined
entity described: event
same as: quaternion-raw-z
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000231

orientation quaternions raw: Burst of raw coordinate values of quaternions defining the orientation of the tag.
example: -10136 -6 -3 -121 -10944 -3 2 -120 -12516 -1 11 -117 -17502 2 15 -107 -19954 -11 10 -100 -20825 -7 12 -97 -19864 -12 18 -99 -21930 -1 6 -94 -22438 -3 19 -91 -21594 -7 24 -92
units: not defined
entity described: event
same as: guaternions-raw
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000232

orientation quaternions sampling frequency: The sampling frequency for quaternion measurements. Can be used to report bursts of values associated with a single timestamp.
example: 20
units: Hz
entity described: event
same as: quaterions-sampling-frequency
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000233

Ornitela transmission protocol: The way in which the data from Ornitela tags were transmitted. Allowed values are SMS or GPRS.
format: controlled list
entity described: event
same as: orn transmission protocol
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000163

pitch: The pitch of the tag, as measured by the gyroscope, accelerometer and/or magnetometer on the tag. Values range from -180 to 180, with positive values indicating backward pitch and negative values indicating forward pitch.
example: -3.37
units: degrees
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000263

proofed: Can be used to indicate whether or not records have been proofed by an expert involved with the study. Allowed values are TRUE or FALSE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000165

provider update timestamp: The timestamp on which the event was last updated by the data provider.
example: 2020-12-18 08:50:06.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC
entity described: event
same as: provider update ts
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000264

receiver deployment ID: An identifier for the deployment of a radio or acoustic receiver.
example: V21-987
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000292

receiver detector ID: Identifier for the detector or antenna on an acoustic or radio receiver.
example: 2
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000293

receiver ID: An identifier for the receiver that detected the signal from the tag.
example: Schillig
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000265

relative humidity: The relative humidity measured by the tag.
example: 23.8
units: none (percent)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000266

roll: The roll of the tag, as measured by the gyroscope, accelerometer and/or magnetometer on the tag. Values range from -180 to 180, with positive values indicating clockwise roll (rotation to the right) around the axis and negative values indicating anticlockwise roll (rotation to the left) around the axis.
example: -7.35
units: degrees
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000267

RR interval: The difference in time between heart beats, measured as the time elapsed between two successive R-waves of the QRS signal on the electrocardiogram (and its reciprocal, the HR). Units: seconds
entity described: event
same as: heartrate RR interval
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000294

sampling frequency: The sampling frequency. If multiple sensors are deployed, use sensor-type-specific frequency attributes.
example: 5.93
units: Hz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000169

Savannah alarm type: For alarm-triggered records of Savannah tags, this indicates the type of alarm that triggered the update. This will always be blank unless 'Savannah record type' has the value A (alarm).
example: GEO ZONE EXIT
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000318

Savannah record type: Indicates whether the Svannah tag record is a normal position/location update or an alarm-triggered update. Allowed values are
P = Normal position updates and A = Alarm-triggered update. For Alarm records (A) the actual alarm that triggered the update is contained in 'Savannah alarm type'.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000319

sensor type: The type of sensor with which data were collected. All sensors are associated with a tag id, and tags can contain multiple sensor types. Each event record in Movebank is assigned one sensor type. If values from multiple sensors are reported in a single event, the primary sensor is used. Values are chosen from a controlled list:
acceleration = The sensor collects acceleration data;
accessory measurements = The sensor collects accessory measurements, such as battery voltage;
acoustic telemetry = The sensor transmits an acoustic signal that is detected by receivers to determine location;
Argos Doppler shift = The sensor location is estimated by Argos using Doppler shift;
barometer = The sensor records air or water pressure;
bird ring = The animal is identified by a band or ring that has a unique identifier;
GPS = The sensor uses GPS to determine location;
gyroscope = The sensor records angular velocity;
heart rate = The sensor records or is used to calculate heart rate;
magnetometer = The sensor records the magnetic field;
natural mark = The animal is identified by a unique natural marking;
orientation = Quaternion components describing the orientation of the tag are derived from accelerometer and gyroscope measurements;
radio transmitter = The sensor transmits a radio signal that is detected by receivers to determine location;
Sigfox geolocation = The sensor location is determined by Sigfox using the received signal strength indicator;
solar geolocator = The sensor collects light levels, which are used to determine position (for processed locations);
solar geolocator raw = The sensor collects light levels, which are used to determine position (for raw light-level measurements);
solar geolocator twilight = The sensor collects light levels, which are used to determine position (for twilights calculated from light-level measurements).
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000170

sequence number: The sequence number of the event.
example: 3776
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000320

Sigfox computed location radius: The radius limit that defines the zone in which the device is located (definition from Sigfox support, 2022).
example: 12000
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000321

Sigfox computed location source: The data source from which the geolocation was computed (definition from Sigfox Support, 2022). Allowed values are
1 = GPS data inside the payload;
2 = the network location;
6 = the WiFi location (external provider).
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000322

Sigfox computed location status: The status of the computation made by the location service (definition from Sigfox Support, 2022). Allowed values are
00 = no position;
01 = OK;
02 = fallback of WiFi location;
20 = invalid payload.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000323

Sigfox country: The country code of the operator who received the Sigfox message (definition from Sigfox support, 2022).
example: 710
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000324

Sigfox device type: The name for a group of Sigfox devices with shared means for processing transmitted data (definition from Sigfox support, 2022). Units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000325

Sigfox duplicates: The list of the duplicates including the base station ID (bsId), the number of repetitions received (nbRep), and the best signal to noise ratio of the received repetitions (RSSI) (definition from Sigfox support, 2022).
example: [{bsId:49AC,rssi:-137,nbRep:3}]
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000326

Sigfox link quality: The integer value corresponding to the value in 'Sigfox LQI' (definition from Sigfox Support, 2022). Allowed values are
0 = Limit;
1 = Average;
2 = Good;
3 = Excellent;
4 = NA.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000327

Sigfox LQI: The computed link quality based on the received signal strength indicator (RSSI), the number of stations that received a message (receiver redundancy) and the radio configuration (RC) zone, due to the difference between the RCs (definition from Sigfox Support, 2022). Allowed values are
Limit;
Average;
Good;
Excellent;
NA.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000328

Sigfox operator: The name of the operator who received the Sigfox message (definition from Sigfox support, 2022).
example: SIGFOX_Germany
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000329

Sigfox RSSI: The received signal strength indicator (definition from Sigfox support, 2022).
example: -93
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000330

Sigfox tx interval: The heartbeat interval in minutes as provided by Sigfox (0 indicates not used).
example: 134
units: minutes
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000331

Sigfox tx interval text: The text equivalent of 'Sigfox tx interval', the heartbeat interval as provided by Sigfox.
example: 6 Hours
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000332

solar cell voltage: The voltage of the solar panel. Units: mV
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000269

solar voltage percent: The voltage of the solar panel, reported as a percentage of maximum possible voltage. Units: none (percent)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000270

start timestamp: The date and time when the sampling interval or burst began.
example: 2011-01-03 13:45:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC or GPS time
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000171

study local timestamp: The date and time a sensor measurement was taken, converted from the values in 'timestamp' to the time zone of the study reference location. The time zone for the study reference location is determined using the IANA Time Zone Database and a shapefile of these zones provided by efele.net.
example: 2008-08-14 15:31:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: time zone is specific to the study
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000140

study timezone: The time zone at the study reference location, determined using the IANA Time Zone Database and a shapefile of these zones provided by efele.net
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000177

study-specific measurement: Values for a study-specific attribute. Best practice is to define the values and units in the reference data or study details.
example: 1112:01
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000178

tag tech spec: Values for a tag-specific technical specification. Can be used to store measurements not described by existing Movebank attributes. Best practice is to define the values and units in the reference data or study details.
example: 8.31
units: not defined
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000190

tag voltage: The voltage as reported by the tag.
example: 2895
units: mV
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000191

TechnoSmart activity: An indication of whether an animal is active. Possible values are 'active' and 'inactive'. The threshold used to define activity is dependent on how the tag is configured by the user
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000192

TechnoSmart signal quality: The strength of satellite reception. Ranges from 0 to 500. Higher values indicate better reception.
example: 230
units: dB-Hz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000193

telemetry detection count: Number of telemetry detections related to the location estimate.
example: 447
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000296

telemetry run ID: Identifier for a run of consecutive hits on a receiver station from a tag.
example: 3459209
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000297

temperature max: The maximum temperature measured during the measurement interval.
example: 12.4
units: degrees Celsius
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000194

temperature min: The minimum temperature measured during the measurement interval.
example: 7.4
units: degrees Celsius
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000195

tilt angle: The angle in which the tag is tilted in respect to the gravitational angle (0-180).
example: 78
units: degrees
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000196

tilt x: Tilt provided by the accelerometer for the X axis.
example: 0
units: g forces (1 g = 9.8 m s^-2)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000197

tilt y: Tilt provided by the accelerometer for the Y axis.
example: 0
units: g forces (1 g = 9.8 m s^-2)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000198

tilt z: Tilt provided by the accelerometer for the Z axis.
example: 1
units: g forces (1 g = 9.8 m s^-2)
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000199

timestamp: The date and time corresponding to a sensor measurement or an estimate derived from sensor measurements.
example: 2008-08-14 18:31:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC or GPS time
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000200

transmission protocol: The protocol used to transmit or otherwise obtain the event data from the tag. Best practice is to use when data are retrieved from the tag using multiple methods.
example: Iridium
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000276

transmission timestamp: The date and time that the data record was transmitted.
example: 2014-03-11 18:06:44.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC or GPS time
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000201

twilight: Identifies light-level measurements determined to represent twilight events. Typically 1 = sunrise, 2 = sunset, 0 = not twilight.
example: 2
units: none
entity described: event
same as: gls twilight
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000113

twilight excluded: Whether a twilight identified by automated processing was excluded from subsequent analysis. Allowed values are TRUE or FALSE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000242

twilight inserted: Whether a twilight was inserted for a time when automated processing did not identify a twilight. Allowed values are TRUE or FALSE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000243

underwater count: The number of times the tag went underwater during the measurement period.
example: 11
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000202

underwater time: The amount of time the tag was underwater during the measurement period.
example: 547
units: seconds
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000203

UTM easting: The easting of the location as estimated by the sensor.
example: 756243.7836
units: meters, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000205

UTM northing: The northing of the location as estimated by the sensor.
example: 3628361.84012295
units: meters, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000206

UTM zone: The UTM zone used to convert locations from decimal degrees to UTM. Selected based on the location of each event.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000207

vertical error numerical: An estimate of the vertical error of the location. These values can be described using 'location error percentile' and 'location accuracy comments'.
example: 12
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000208

visible: Determines whether an event is visible on the Movebank map. Values are calculated automatically, with TRUE indicating the event has not been flagged as an outlier by 'algorithm marked outlier', 'import marked outlier' or 'manually marked outlier', or that the user has overridden the results of these outlier attributes using 'manually marked valid' = TRUE. Allowed values are TRUE or FALSE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000209

voltage resolution: The voltage resolution of the sensor. Units: mV
entity described: event
same as: heartrate voltage resolution
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000298

wet: Whether the sensor is wet, as detected by a conductivity sensor. Details about how this is determined can be stored in 'conductivity sensor comments'. Allowed values are TRUE or FALSE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000299

wet count: The wet count during the measurement interval.
example: 11
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000213

References

Argos User's Manual, 2011

British Antarctic Survey Geolocator Manual v. 8, 2010

e-obs Digital Telemetry Manual for DataDecoder Software, 2010

e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2, 2011