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 on-animal 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. To request additions to this list, select Request Attribute from the import interface 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. These can include institutions that provided funding or site access and the names of field assistants, collaborators, etc.
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

citation: One or more citations for the study. Include citations for published papers or reports describing the data in 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

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 ID

grants used: A list or description of grants used to fund the research.
example: This project was funded by an NSF grant to RK.
units: none
entity described: study

license terms: Terms of use for the data in the study, provided by the study owner. If no license terms are specified, the General Movebank Terms of Use apply.
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

principal investigator: The name and username of the Movebank account for the principal investigator (PI) or lead researcher for the study.
example: Rolandisimo (Roland Kays)
units: none
entity described: study

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

study reference location: A 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, resesarch institute location, or other location relevant to the study.
example: -73.856, 42.718
units: decimal degrees, WGS84 reference system
entity described: study

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

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

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

principal investigator name: The principal investigator (PI) or lead researcher for the study. Used when the PI does not have a Movebank account.
example: Charles Darwin
units: none
entity described: study

study name: The name of the study in Movebank.
example: Coyotes, Kays and Bogan, Albany NY
units: none
entity described: study

Animal terms

These terms are used to describe individual animals. Also see the deployment terms for animal descriptors that vary with time.

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

animal death comments: Comments about the death of the animal.
example: hit by a car
units: none
entity described: individual

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

animal exact date of birth: The exact date on which animal was born.
example: 2001-10-31 18:36:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC (sometimes date is provided based on local time)
entity described: individual

animal ID: An individual identifier for the animal, provided by the data owner. If the data owner does not provide an Animal ID, an internal Movebank animal identifier is sometimes shown.
example: 91876A, Gary
units: none
entity described: individual
same as: individual local identifier

animal latest date born: The latest date an animal is thought to have been born.
example: 2001-12-12 16:54:00.000
format: yyyy-MM-dd HH:mm:ss.SSS
units: UTC (sometimes date is provided based on local time)
entity described: individual

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

animal ring ID: A number or color scheme for a band or ring attached to the animal.
example: 26225
units: none
entity described: individual

animal sex: The sex of the animal. Allowed values are m = male; f = female
format: controlled list
units: none
entity described: individual

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'.
example: Buteo swainsoni
format: controlled list
units: none
entity described: individual
same as: individual taxon canonical name

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

Deployment terms

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

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: not defined
entity described: deployment

animal mass: The mass of the animal, typically at the beginning of the deployment.
example: 500
units: grams
entity described: deployment

animal reproductive condition: The reproductive condition of the animal at the beginning of the deployment.
example: lactating
units: none
entity described: deployment

attachment type: The way a tag is attached to an animal. Values are chosen from a controlled list: collar = The tag is attached by a collar around the animal's neck
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
tape = The tag is attached to the animal using tape
other = user specified. format: controlled list
units: none
entity described: deployment

behaviour according to: A description of behavioral categories contained in the event data and/or how they were derived.
example: Behavior was derived using acceleration data and an automated algorithm calibrated using field observations.
units: none
entity described: deployment

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

deploy off latitude: The geographic latitude of the location where the deployment ended (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data).
example: -38.6866
units: decimal degrees, WGS84 reference system
entity described: deployment

deploy off longitude: The geographic longitude of the location where the deployment ended (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data).
example: 146.3104
units: decimal degrees, WGS84 reference system
entity described: deployment

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

deploy off timestamp: The timestamp when the tag deployment ended.
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

deploy on latitude: The geographic latitude of the location where the animal was released (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data).
example: 27.3516
units: decimal degrees, WGS84 reference system
entity described: deployment

deploy on longitude: The geographic longitude of the location where the animal was released (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data).
example: -97.3321
units: decimal degrees, WGS84 reference system
entity described: deployment

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

deploy on timestamp: The timestamp when the tag deployment started.
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

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

deployment end comments: A description of the end of a tag deployment, such as cause of mortality or notes on the removal and/or failure of tag.
example: data transmission stopped after 108 days. Cause unknown
units: none
entity described: deployment

deployment end type: A categorical classification of the tag deployment end, from a controlled list:
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
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
unknown = The deployment ended by an unknown cause
format: controlled list
units: none
entity described: deployment

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

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: not defined
entity described: deployment

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

geolocator light threshold: The light threshold used for location estimation with solar geolocators.
example: 16
units: not defined
entity described: deployment

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

geolocator sun elevation angle: The sun elevation angle used for location estimation with solar geolocators.
example: -2.86
units: degrees
entity described: deployment

habitat according to: A description of habitat categories contained in the event data, how they were derived and/or a reference to indicate which habitat classification system was used.
example: visual analysis using 2018 satellite imagery
units: none
entity described: deployment

location accuracy comments: Comments about the 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

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

manipulation type: The way in which the animal was manipulated during the deployment. Values are chosen from a controlled list:
confined = The animal's movement was restricted to within a defined area
none = The animal received no treatment other than the tag attachment
relocated = The animal was released from a site other than the one at which it was captured
manipulated other = The animal was manipulated in some other way, such as a physiological manipulation
format: controlled list
units: none
entity described: deployment

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

tag readout method: The way the data are received from the tag. Values are chosen from a controlled list:
satellite = Data are transferred via satellite
phone network = Data are transferred via a phone network, such as GSM or AMPS
other wireless = Data are transferred via another form of wireless data transfer, such as a VHF transmitter/receiver
tag retrieval = The tag must be physically retrieved in order to obtain the data
format: controlled list
units: none
entity described: deployment

Tag terms

These terms are used to describe individual tags.

tag beacon frequency: The frequency of the radio tag or tag retrieval beacon.
example: 450.5
units: MHz
entity described: tag

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

tag failure comments: Comments about tag failure.
example: tag stopped transmitting 23/12/08, was not found
units: none
entity described: tag

tag ID: A unique identifier for the tag, provided by the data owner. 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

tag manufacturer name: The company or person that produced the tag.
example: Holohil
units: none
entity described: tag

tag mass: The mass of the tag.
example: 24
units: grams
entity described: tag

tag model: The model of the tag.
example: T61
units: none
entity described: tag

tag processing type: Used to distinguish between data formats produced by different types of Microwave tags (currently not used). Units: none
entity described: tag

tag production date: The approximate date the tag was produced (can be a year, month, or day).
example: 40603
units: not defined
entity described: tag

tag serial no: The serial number of the tag.
example: MN93-33243
units: none
entity described: tag

Event terms

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

acceleration axes: Indicates the enabled accelerometer axes.
example: XYZ
units: none
entity described: event

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

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

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

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

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

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

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

accelerations raw: Burst of acceleration sensor values.
example: -0.609 -0.094 0.820 -0.562 -0.117 0.820 -0.586 -0.141 0.796 -0.679 -0.117 0.750 -0.656 -0.117 0.773 -0.586 -0.187 0.867 -0.468 -0.234 0.656 -0.960 0.094 0.609 -1.148 0.164 0.492 -0.773 0.164 0.398 -0.843 0.351 0.515 -1.312 0.468 0.468
units: none
entity described: event

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

Argos altitude: Altitude used for location calculation, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 27
units: m
entity described: event

Argos best level: Best signal strength, Argos diagnostic data (definition from Argos User's Manual 2011).
example: -117
units: dB
entity described: event

Argos calcul freq: Calculated frequency, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 401.6732709
units: Hz
entity described: event

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: m
entity described: event

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

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.
example: 68
format: controlled list
units: none
entity described: event

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

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

Argos LC: The location class retrieved from Argos (0, 1, 2, 3, A, B, Z), Argos diagnostic data (definition from Argos User's Manual 2011)
format: controlled list
units: none
entity described: event

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

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

Argos nb mes: The number of messages received [to calculate location], Argos diagnostic data (definition from Argos User's Manual 2011).
example: 8
units: none
entity described: event

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: none
entity described: event

Argos NOPC: Number of plausibility checks successful (from 0-4), Argos diagnostic data (definition from Argos User's Manual 2011).
example: 3
units: none
entity described: event

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

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: s
entity described: event

Argos sat ID: The satellite identifier, Argos diagnostic data (definition from Argos User's Manual 2011).
example: P
units: none
entity described: event

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: m
entity described: event

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: m
entity described: event

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

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

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

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

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

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
units: none
entity described: event

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
units: none
entity described: event

barometric depth: The barometric water pressure depth.
example: -11
units: m
entity described: event

barometric height: Altitude estimated by a barometric pressure sensor on the tag.
example: 179
units: m
entity described: event

barometric pressure: The barometric air or water pressure.
example: 32536.0
units: mbar (hPa)
entity described: event

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

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

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
units: none
entity described: event

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

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

BAS transition 1: Time of sunrise (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 0.530555555555556
units: GMT
entity described: event

BAS transition 2: Time of sunset (definition from British Antarctic Survey Geolocator Manual v. 8, 2010).
example: 0.690972222222222
units: GMT
entity described: event

battery charge percent: The battery charge as a percentage of full charge.
example: 25
units: none (percent)
entity described: event

battery charging current: The battery charging current reported by the tag.
example: 0
units: milliamperes (mA)
entity described: event

behavioural classification: Behavioural classifications assigned to the animal by the data owner. The method for defining and assigning these classifications are unique to the study and can be described using 'behaviour according to'. Recommended best practice is to use a controlled list.
example: roosting, foraging, running
units: none
entity described: event

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

compass heading: The tilt-compensated horizontal compass heading.
example: 62
units: degrees clockwise from magnetic north
entity described: event

conductivity: The maximum conductivity recorded during the measurement interval.
example: 17
units: none
entity described: event

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

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

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; Wolgang 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

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: none
entity described: event

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: none
entity described: event

eobs battery voltage: Unloaded battery voltage (definition from Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012).
example: 3712
units: mV
entity described: event

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

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: m
entity described: event

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

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

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

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
units: none
entity described: event

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

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
units: none
entity described: event

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

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

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

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

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
units: none
entity described: event
same as: Fleetronic switch

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

Gt sys week: The week number since the device was activated (definition from GeoTrak's 'PTT Decode Overview', 2014).
example: 4
units: weeks
entity described: event
same as: GeoTrak sys week

Gt tx count: The number of transmissions since last rollover (definition from GeoTrak's 'PTT Decode Overview', 2014).
example: 4840
units: none
entity described: event
same as: GeoTrak Tx Count

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

GPS activity count: A value provided by some tags that can be used to generally indicate whether an animal is active.
example: 209
units: none
entity described: event

GPS DOP: Dilution of precision provided by the GPS.
example: 1.8
units: unitless
entity described: event

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
units: none
entity described: event

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 the more standardized 'GPS fix type'.
example: 3D
units: none
entity described: event

GPS HDOP: Horizontal dilution of precision provided by the GPS.
example: 1.2
units: unitless
entity described: event

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

GPS satellite count: The number of GPS satellites used to estimate the location.
example: 8
units: none
entity described: event

GPS time to fix: The time required to obtain the GPS location fix.
example: 36
units: s
entity described: event

GPS VDOP: Vertical dilution of precision provided by the GPS.
example: 1.9
units: unitless
entity described: event

ground speed: The estimated ground speed provided by the sensor or calculated between consecutive locations.
example: 7.22
units: m/s
entity described: event

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

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

habitat: A category or description of the habitat. Information about how the values were obtained can be provided using 'habitat according to'.
example: oak savannah
units: none
entity described: event

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

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

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: m
entity described: event
same as: height above msl

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

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

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

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

light level: Light-level values measured by a solar geolocator. Best practice is to define values in the reference data.
example: 28
units: not defined
entity described: event

local timestamp: The date and time a sensor measurement was taken in 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: specific to the study time zone
entity described: event

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: m
entity described: event

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: unitless (percent)
entity described: event

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

location lat: 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: -41.0982423
units: decimal degrees, WGS84 reference system
entity described: event

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

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

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

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
units: none
entity described: event
same as: Lot:CRC status

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
units: none
entity described: event
same as: Lot:CRC status text

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

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

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

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

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

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: none
entity described: event
same as: Microwave activity count

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

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

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
units: none
entity described: event

modelled: Can be used to identify locations or light level values that are modelled, interpolated, or otherwise added or changed based on the original location or light level estimates from the original data collection system. These may include movement model outputs, locations added to create a dataset with equal time intervals, etc. Allowed values are TRUE or FALSE.
units: none
entity described: event

Ornitela transmission protocol: The way in which the data from Ornitela tags were transmitted. Allowed values are SMS or GPRS
format: controlled list
units: none
entity described: event
same as: orn:transmission protocol

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

sampling frequency: The sampling frequency.
example: 5.93
units: Hz
entity described: event

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
Argos Doppler shift = The sensor uses Argos Doppler shift to determine position
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
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 is a classical radio transmitter
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
units: none
entity described: event

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

study time zone: 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.
example: Mountain Standard Time
format: controlled list
units: none
entity described: event

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

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

tag voltage: The voltage as reported by the tag.
example: 2895
units: mV
entity described: event

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
units: none
entity described: event

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

temperature max: The maximum temperature measured during the measurement interval.
example: 12.4
units: degrees Celsius
entity described: event

temperature min: The minimum temperature measured during the measurement interval.
example: 7.4
units: degrees Celsius
entity described: event

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

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

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

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

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

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

underwater count: The number of times the tag went underwater during the current measurement period (30 minutes).
example: 11
units: none
entity described: event

underwater time: The amount of time the tag was underwater during the current measurement period (30 minutes).
example: 547
units: seconds
entity described: event

UTM easting: The easting of the location as estimated by the sensor.
example: 756243.7836
units: meters, WGS84 reference system
entity described: event

UTM northing: The northing of the location as estimated by the sensor.
example: 3628361.84012295
units: meters, WGS84 reference system
entity described: event

UTM zone: The UTM zone used to convert locations from decimal degrees to UTM. Selected based on the location of each event.
example: 14N
format: controlled list
units: none
entity described: event

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: m
entity described: event

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

wet count: The wet count during the measurement interval.
example: 11
units: none
entity described: event

data decoding software: The name or version of software used to decode the sensor data.
example: 11
units: not defined
entity described: event

geolocator rise: The period of day used to estimate location by geolocation. TRUE = sunrise, FALSE = sunset.
units: none
entity described: event

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

magnetic field axes: The enabled magnetic field axes.
units: none
entity described: event

magnetic field sampling frequency per axis: The sampling frequency for each axis measured. Can be used to report bursts of values associated with a single timestamp.
example: 20
units: Hz
entity described: event

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.
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

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: none
entity described: event

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: none
entity described: event

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: none
entity described: event

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: none
entity described: event

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: none
entity described: event

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

speed accuracy estimate: Estimated accuracy of the ground speed. Units: m/s
entity described: event

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

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

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