| Identifier |
PrefLabel |
Definition |
Date |
| MVB000030 |
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 |
2019-10-03 |
| MVB000031 |
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 |
2019-10-03 |
| MVB000034 |
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 |
2019-10-03 |
| MVB000039 |
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 |
2019-10-03 |
| MVB000026 |
Argos altitude |
Altitude used for location calculation, Argos diagnostic data (definition from Argos User's Manual 2011). Example: '27'; Units: m; Entity described: event |
2019-10-03 |
| MVB000027 |
Argos best level |
Best signal strength, Argos diagnostic data (definition from Argos User's Manual 2011). Example: '-117'; Units: dB; Entity described: event |
2019-10-03 |
| MVB000028 |
Argos calcul freq |
Calculated frequency, Argos diagnostic data (definition from Argos User's Manual 2011). Example: '401.6732709'; Units: Hz; Entity described: event |
2019-10-03 |
| MVB000029 |
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 |
2019-10-03 |
| MVB000032 |
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 |
2019-10-03 |
| MVB000033 |
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 |
2019-10-03 |
| MVB000035 |
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 |
2019-10-03 |
| MVB000036 |
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 |
2019-10-03 |
| MVB000037 |
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 |
2019-10-03 |
| MVB000038 |
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 |
2019-10-03 |
| MVB000040 |
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 |
2019-10-03 |
| MVB000041 |
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 |
2019-10-03 |
| MVB000042 |
Argos sat ID |
The satellite identifier, Argos diagnostic data (definition from Argos User's Manual 2011). Example: 'P'; Units: none; Entity described: event |
2019-10-03 |
| MVB000043 |
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 |
2019-10-03 |
| MVB000044 |
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 |
2019-10-03 |
| MVB000045 |
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 |
2019-10-03 |
| MVB000046 |
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 |
2019-10-03 |
| MVB000047 |
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 |
2019-10-03 |
| MVB000048 |
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 |
2019-10-03 |
| MVB000049 |
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 |
2019-10-03 |
| MVB000050 |
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 |
2019-10-03 |
| MVB000051 |
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 |
2019-10-03 |
| MVB000056 |
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 |
2019-10-03 |
| MVB000057 |
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 |
2019-10-03 |
| MVB000058 |
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 |
2019-10-03 |
| MVB000059 |
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 |
2019-10-03 |
| MVB000060 |
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 |
2019-10-03 |
| MVB000061 |
BAS transition 1 |
Time of sunrise (definition from British Antarctic Survey Geolocator Manual v. 8, 2010). Example: '0.530555555555556'; Units: GMT; Entity described: event |
2019-10-03 |
| MVB000062 |
BAS transition 2 |
Time of sunset (definition from British Antarctic Survey Geolocator Manual v. 8, 2010). Example: '0.690972222222222'; Units: GMT; Entity described: event |
2019-10-03 |
| MVB000105 |
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 |
2019-10-03 |
| MVB000115 |
GPS DOP |
Dilution of precision provided by the GPS. Example: '1.8'; Units: unitless; Entity described: event |
2019-10-03 |
| MVB000118 |
GPS HDOP |
Horizontal dilution of precision provided by the GPS. Example: '1.2'; Units: unitless; Entity described: event |
2019-10-03 |
| MVB000122 |
GPS VDOP |
Vertical dilution of precision provided by the GPS. Example: '1.9'; Units: unitless; Entity described: event |
2019-10-03 |
| MVB000114 |
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 |
2019-10-03 |
| MVB000116 |
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 |
2019-10-03 |
| MVB000117 |
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 |
2019-10-03 |
| MVB000119 |
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 |
2019-10-03 |
| MVB000120 |
GPS satellite count |
The number of GPS satellites used to estimate the location. Example: '8'; Units: none; Entity described: event |
2019-10-03 |
| MVB000121 |
GPS time to fix |
The time required to obtain the GPS location fix. Example: '36'; Units: s; Entity described: event |
2019-10-03 |
| MVB000125 |
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 |
2019-10-03 |
| MVB000126 |
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 |
2019-10-03 |
| MVB000111 |
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 |
2019-10-03 |
| MVB000112 |
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 |
2019-10-03 |
| MVB000217 |
I am owner |
Used in the REST API. Whether the user credentials used in the request are for a Movebank user that is a Data Manager for the study. Allowed values are TRUE or FALSE. Units: none; Entity described: study |
2019-10-03 |
| MVB000218 |
I can see data |
Used in the REST API. Whether the user credentials used in the request are for a Movebank user that has permission to view some or all tracks on Movebank. Does not indicate whether this user has permission to download data. Allowed values are TRUE or FALSE. Units: none; Entity described: study |
2019-10-03 |
| MVB000149 |
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 |
2019-10-03 |
| MVB000150 |
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 |
2019-10-03 |
| MVB000158 |
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 |
2019-10-03 |
| MVB000159 |
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 |
2019-10-03 |
| MVB000163 |
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 |
2019-10-03 |
| MVB000192 |
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 |
2019-10-03 |
| MVB000193 |
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 |
2019-10-03 |
| MVB000205 |
UTM easting |
The easting of the location as estimated by the sensor. Example: '756243.7836'; Units: meters, WGS84 reference system; Entity described: event |
2019-10-03 |
| MVB000206 |
UTM northing |
The northing of the location as estimated by the sensor. Example: '3628361.84012295'; Units: meters, WGS84 reference system; Entity described: event |
2019-10-03 |
| MVB000207 |
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 |
2019-10-03 |
| MVB000001 |
acceleration axes |
Indicates the enabled accelerometer axes. Example: 'XYZ'; Units: none; Entity described: event |
2019-10-03 |
| MVB000002 |
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 |
2019-10-03 |
| MVB000003 |
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 |
2019-10-03 |
| MVB000004 |
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 |
2019-10-03 |
| MVB000005 |
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 |
2019-10-03 |
| MVB000006 |
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 |
2019-10-03 |
| MVB000007 |
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 |
2019-10-03 |
| MVB000008 |
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 |
2019-10-03 |
| MVB000009 |
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 |
2019-10-03 |
| MVB000010 |
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 |
2019-10-03 |
| MVB000011 |
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 |
2019-10-03 |
| MVB000016 |
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 |
2019-10-03 |
| MVB000012 |
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 |
2019-10-03 |
| MVB000013 |
animal death comments |
Comments about the death of the animal. Example: 'hit by a car'; Units: none; Entity described: individual |
2019-10-03 |
| MVB000014 |
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 |
2019-10-03 |
| MVB000015 |
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 |
2019-10-03 |
| MVB000017 |
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 |
2019-10-03 |
| MVB000018 |
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 |
2019-10-03 |
| MVB000019 |
animal mass |
The mass of the animal, typically at the beginning of the deployment. Example: '500'; Units: grams; Entity described: deployment |
2019-10-03 |
| MVB000020 |
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 |
2019-10-03 |
| MVB000021 |
animal reproductive condition |
The reproductive condition of the animal at the beginning of the deployment. Example: 'lactating'; Units: none; Entity described: deployment |
2019-10-03 |
| MVB000022 |
animal ring ID |
A number or color scheme for a band or ring attached to the animal. Example: '26225'; Units: none; Entity described: individual |
2019-10-03 |
| MVB000023 |
animal sex |
The sex of the animal. Allowed values are m = male; f = female. Format: controlled list; Units: none; Entity described: individual |
2019-10-03 |
| MVB000024 |
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 |
2019-10-03 |
| MVB000025 |
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 |
2019-10-03 |
| MVB000052 |
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 |
2019-10-03 |
| MVB000053 |
barometric depth |
The barometric water pressure depth. Example: '-11'; Units: m; Entity described: event |
2019-10-03 |
| MVB000054 |
barometric height |
Altitude estimated by a barometric pressure sensor on the tag. Example: '179'; Units: m; Entity described: event |
2019-10-03 |
| MVB000055 |
barometric pressure |
The barometric air or water pressure. Example: '32536.0'; Units: mbar (hPa); Entity described: event |
2019-10-03 |
| MVB000063 |
battery charge percent |
The battery charge as a percentage of full charge. Example: '25'; Units: none (percent); Entity described: event |
2019-10-03 |
| MVB000064 |
battery charging current |
The battery charging current reported by the tag. Example: '0'; Units: milliamperes (mA); Entity described: event |
2019-10-03 |
| MVB000066 |
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 |
2019-10-03 |
| MVB000067 |
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 |
2019-10-03 |
| MVB000068 |
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 |
2019-10-03 |
| MVB000069 |
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 |
2019-10-03 |
| MVB000070 |
compass heading |
The tilt-compensated horizontal compass heading. Example: '62'; Units: degrees clockwise from magnetic north; Entity described: event |
2019-10-03 |
| MVB000071 |
conductivity |
The maximum conductivity recorded during the measurement interval. Example: '17'; Units: none; Entity described: event |
2019-10-03 |
| MVB000072 |
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 |
2019-10-03 |
| MVB000214 |
data decoding software |
The name or version of software used to decode the sensor data. Example: '11'; Units: not defined; Entity described: event |
2019-10-03 |
| MVB000073 |
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 |
2019-10-03 |
| MVB000074 |
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 |
2019-10-03 |
| MVB000075 |
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 |
2019-10-03 |
| MVB000076 |
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 |
2019-10-03 |
| MVB000077 |
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 |
2019-10-03 |
| MVB000078 |
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 |
2019-10-03 |
| MVB000079 |
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 |
2019-10-03 |
| MVB000080 |
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 |
2019-10-03 |
| MVB000081 |
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 |
2019-10-03 |
| MVB000085 |
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 |
2019-10-03 |
| MVB000082 |
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 |
2019-10-03 |
| MVB000083 |
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 |
2019-10-03 |
| MVB000084 |
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 |
2019-10-03 |
| MVB000086 |
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 |
2019-10-03 |
| MVB000102 |
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 |
2019-10-03 |
| MVB000087 |
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 |
2019-10-03 |
| MVB000088 |
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 |
2019-10-03 |
| MVB000089 |
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 |
2019-10-03 |
| MVB000090 |
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 |
2019-10-03 |
| MVB000091 |
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 |
2019-10-03 |
| MVB000092 |
eobs battery voltage |
Unloaded battery voltage (definition from Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012). Example: '3712'; Units: mV; Entity described: event |
2019-10-03 |
| MVB000093 |
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 |
2019-10-03 |
| MVB000094 |
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 |
2019-10-03 |
| MVB000095 |
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 |
2019-10-03 |
| MVB000096 |
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 |
2019-10-03 |
| MVB000097 |
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 |
2019-10-03 |
| MVB000098 |
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 |
2019-10-03 |
| MVB000099 |
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 |
2019-10-03 |
| MVB000100 |
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 |
2019-10-03 |
| MVB000101 |
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 |
2019-10-03 |
| MVB000103 |
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 |
2019-10-03 |
| MVB000104 |
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 |
2019-10-03 |
| MVB000106 |
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 |
2019-10-03 |
| MVB000107 |
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 |
2019-10-03 |
| MVB000108 |
geolocator light threshold |
The light threshold used for location estimation with solar geolocators. Example: '16'; Units: not defined; Entity described: deployment |
2019-10-03 |
| MVB000215 |
geolocator rise |
The period of day used to estimate location by geolocation. TRUE = sunrise, FALSE = sunset. Units: none; Entity described: event |
2019-10-03 |
| MVB000109 |
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 |
2019-10-03 |
| MVB000110 |
geolocator sun elevation angle |
The sun elevation angle used for location estimation with solar geolocators. Example: '-2.86'; Units: degrees; Entity described: deployment |
2019-10-03 |
| MVB000216 |
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 |
2019-10-03 |
| MVB000123 |
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 |
2019-10-03 |
| MVB000124 |
ground speed |
The estimated ground speed provided by the sensor or calculated between consecutive locations. Example: '7.22'; Units: m/s; Entity described: event |
2019-10-03 |
| MVB000127 |
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 |
2019-10-03 |
| MVB000128 |
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 |
2019-10-03 |
| MVB000129 |
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 |
2019-10-03 |
| MVB000130 |
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 |
2019-10-03 |
| MVB000131 |
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 |
2019-10-03 |
| MVB000132 |
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 |
2019-10-03 |
| MVB000133 |
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 |
2019-10-03 |
| MVB000134 |
individual local identifier |
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 |
2019-10-03 |
| MVB000135 |
individual taxon canonical name |
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 |
2019-10-03 |
| MVB000136 |
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 |
2019-10-03 |
| MVB000137 |
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 |
2019-10-03 |
| MVB000138 |
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 |
2019-10-03 |
| MVB000139 |
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 |
2019-10-03 |
| MVB000140 |
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 |
2019-10-03 |
| MVB000141 |
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 |
2019-10-03 |
| MVB000142 |
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 |
2019-10-03 |
| MVB000143 |
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 |
2019-10-03 |
| MVB000144 |
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 |
2019-10-03 |
| MVB000145 |
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 |
2019-10-03 |
| MVB000146 |
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 |
2019-10-03 |
| MVB000147 |
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 |
2019-10-03 |
| MVB000148 |
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 |
2019-10-03 |
| MVB000219 |
magnetic field axes |
The enabled magnetic field axes. Units: none; Entity described: event |
2019-10-03 |
| MVB000151 |
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 |
2019-10-03 |
| MVB000152 |
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 |
2019-10-03 |
| MVB000153 |
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 |
2019-10-03 |
| MVB000220 |
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 |
2019-10-03 |
| MVB000221 |
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 |
2019-10-03 |
| MVB000222 |
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, resesarch institute location, or other location relevant to the study. Example: '42.718'; Units: decimal degrees, WGS84 reference system; Entity described: study |
2019-10-03 |
| MVB000223 |
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, resesarch institute location, or other location relevant to the study. Example: '-73.856'; Units: decimal degrees, WGS84 reference system; Entity described: study |
2019-10-03 |
| MVB000154 |
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 |
2019-10-03 |
| MVB000155 |
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 |
2019-10-03 |
| MVB000156 |
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 |
2019-10-03 |
| MVB000157 |
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 |
2019-10-03 |
| MVB000160 |
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 |
2019-10-03 |
| MVB000161 |
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 |
2019-10-03 |
| MVB000162 |
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 |
2019-10-03 |
| MVB000224 |
number of deployed locations |
The number of deployed locations in the study. Values in Movebank appear in the study details and are calculated within minutes when changes are made. Values obtained through the REST API are calculated approximately daily. Units: none; Entity described: study |
2019-10-03 |
| MVB000225 |
number of deployments |
The number of deployments in the study. Values in Movebank appear in the study details and are calculated within minutes when changes are made. Values obtained through the REST API are calculated approximately daily. Example: '10'; Units: none; Entity described: study |
2019-10-03 |
| MVB000226 |
number of individuals |
The number of individual animals in the study. Values in Movebank appear in the study details and are calculated within minutes when changes are made. Values obtained through the REST API are calculated approximately daily. Units: none; Entity described: study |
2019-10-03 |
| MVB000227 |
number of tags |
The number of tags in the study. Values in Movebank appear in the study details and are calculated within minutes when changes are made. Values obtained through the REST API are calculated approximately daily. Units: none; Entity described: study |
2019-10-03 |
| MVB000228 |
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 |
2019-10-03 |
| MVB000229 |
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 |
2019-10-03 |
| MVB000230 |
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 |
2019-10-03 |
| MVB000231 |
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 |
2019-10-03 |
| MVB000232 |
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 |
2019-10-03 |
| MVB000233 |
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 |
2019-10-03 |
| MVB000164 |
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 |
2019-10-03 |
| MVB000234 |
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 |
2019-10-03 |
| MVB000235 |
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 |
2019-10-03 |
| MVB000236 |
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 |
2019-10-03 |
| MVB000165 |
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 |
2019-10-03 |
| MVB000166 |
raptor workshop behaviorDEPRECATED |
Behavioral categories used for analysis as part of the Movebank raptor workshop in Hawk Mountain, USA, February 2009. Values are chosen from a controlled list: nesting = An observation where an animal is observed, or determined to be, at its nest site; roosting = An observation where an animal is observed, or determined to be, roosting. Format: controlled list; Units: none |
2019-10-03 |
| MVB000167 |
raptor workshop deployment special eventDEPRECATED |
Special events in the deployments used for analysis as part of the Movebank raptor workshop in Hawk Mountain, USA, February 2009. Values are chosen from a controlled list: biologically irrelevant = An observation that is found to be biologically irrelevant, for example because there was no animal wearing the tag; death = The location where an animal is found or determined to be dead; release site = The location where the animal is released; tag failure = The observation where the tag was found, or determined, to have failed. Format: controlled list; Units: none |
2019-10-03 |
| MVB000168 |
raptor workshop migration stateDEPRECATED |
Migration states used for analysis as part of the Movebank raptor workshop in Hawk Mountain, USA, February 2009. Values are chosen from a controlled list: breeding grounds = in the breeding grounds; fall migration = on fall migration; migration = on a seasonal migration; natal area = in the area where the animal was born; non-breeding grounds = in the non-breeding grounds, i.e. wintering grounds; spring migration = on spring migration; stopover = in a stopover site during a migration; summer non-breeding = in a summer non-breeding grounds. Format: controlled list; Units: none |
2019-10-03 |
| MVB000169 |
sampling frequency |
The sampling frequency. Example: '5.93'; Units: Hz; Entity described: event |
2019-10-03 |
| MVB000170 |
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 |
2019-10-03 |
| MVB000237 |
speed accuracy estimate |
Estimated accuracy of the ground speed. Units: m/s; Entity described: event |
2019-10-03 |
| MVB000171 |
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 |
2019-10-03 |
| MVB000172 |
study ID |
A unique identifier for the study in Movebank that is created automatically by the database. Example: '2911040'; Units: none; Entity described: study |
2019-10-03 |
| MVB000173 |
study name |
The name of the study in Movebank. Example: 'Coyotes, Kays and Bogan, Albany NY'; Units: none; Entity described: study (event) |
2019-10-03 |
| MVB000174 |
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 |
2019-10-03 |
| MVB000175 |
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 |
2019-10-03 |
| MVB000176 |
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 |
2019-10-03 |
| MVB000177 |
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 |
2019-10-03 |
| MVB000178 |
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 |
2019-10-03 |
| MVB000238 |
suspend license terms |
Used in the REST API. Whether or not the study owner allows users that are not data managers to download data without accepting license terms. This is sometimes done to facilitate access through external applications. Units: none; Entity described: study |
2019-10-03 |
| MVB000181 |
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 |
2019-10-03 |
| MVB000065 |
tag beacon frequency |
The frequency of the radio tag or tag retrieval beacon. Example: '450.5'; Units: MHz; Entity described: tag |
2019-10-03 |
| MVB000179 |
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 |
2019-10-03 |
| MVB000180 |
tag failure comments |
Comments about tag failure. Example: 'tag stopped transmitting 23/12/08, was not found'; Units: none; Entity described: tag |
2019-10-03 |
| MVB000182 |
tag local indentifier |
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 |
2019-10-03 |
| MVB000183 |
tag manufacturer name |
The company or person that produced the tag. Example: 'Holohil'; Units: none; Entity described: tag |
2019-10-03 |
| MVB000184 |
tag mass |
The mass of the tag. Example: '24'; Units: grams; Entity described: tag |
2019-10-03 |
| MVB000185 |
tag model |
The model of the tag. Example: 'T61'; Units: none; Entity described: tag |
2019-10-03 |
| MVB000186 |
tag processing type |
Used to distinguish between data formats produced by different types of Microwave tags (currently not used). Units: none; Entity described: tag |
2019-10-03 |
| MVB000187 |
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 |
2019-10-03 |
| MVB000188 |
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 |
2019-10-03 |
| MVB000189 |
tag serial no |
The serial number of the tag. Example: 'MN93-33243'; Units: none; Entity described: tag |
2019-10-03 |
| MVB000190 |
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 |
2019-10-03 |
| MVB000191 |
tag voltage |
The voltage as reported by the tag. Example: '2895'; Units: mV; Entity described: event |
2019-10-03 |
| MVB000194 |
temperature max |
The maximum temperature measured during the measurement interval. Example: '12.4'; Units: degrees Celsius; Entity described: event |
2019-10-03 |
| MVB000195 |
temperature min |
The minimum temperature measured during the measurement interval. Example: '7.4'; Units: degrees Celsius; Entity described: event |
2019-10-03 |
| MVB000239 |
there are data which I cannot see |
Used in the REST API. Whether the user credentials used in the request are for a Movebank user that does not have permission to view some or all tracks on Movebank. Does not indicate whether this user has permission to download data. Allowed values are TRUE or FALSE. Units: none; Entity described: study |
2019-10-03 |
| MVB000196 |
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 |
2019-10-03 |
| MVB000197 |
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 |
2019-10-03 |
| MVB000198 |
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 |
2019-10-03 |
| MVB000199 |
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 |
2019-10-03 |
| MVB000200 |
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 |
2019-10-03 |
| MVB000240 |
timestamp of first deployed location |
The timestamp of the first deployed location in the study. Values in Movebank appear in the study details and are calculated within minutes when changes are made. Values obtained through the REST API are calculated approximately daily. Example: '2008-08-14 15:31:00.000'; Format: yyyy-MM-dd HH:mm:ss.SSS; Units: UTC (sometimes date is provided based on local time); Entity described: study |
2019-10-03 |
| MVB000241 |
timestamp of last deployed location |
The timestamp of the last deployed location in the study. Values in Movebank appear in the study details and are calculated within minutes when changes are made. Values obtained through the REST API are calculated approximately daily. Example: '2014-03-11 18:06:44.000'; Format: yyyy-MM-dd HH:mm:ss.SSS; Units: UTC (sometimes date is provided based on local time); Entity described: study |
2019-10-03 |
| MVB000201 |
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 |
2019-10-03 |
| MVB000113 |
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 |
2019-10-03 |
| MVB000242 |
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 |
2019-10-03 |
| MVB000243 |
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 |
2019-10-03 |
| MVB000202 |
underwater count |
The number of times the tag went underwater during the current measurement period (30 minutes). Example: '11'; Units: none; Entity described: event |
2019-10-03 |
| MVB000203 |
underwater time |
The amount of time the tag was underwater during the current measurement period (30 minutes). Example: '547'; Units: seconds; Entity described: event |
2019-10-03 |
| MVB000204 |
update ts |
Used in the REST API. The date and time that the event was last updated. If the event has not been modified this will indicate when the event was created, i.e. imported to Movebank. Records created before this attribute was added to the database will have the value '1970-01-01 00:00:00.000'. Example: '1970-01-01 00:00:00.000'; Format: yyyy-MM-dd HH:mm:ss.SSS; Units: UTC; Entity described: event |
2019-10-03 |
| MVB000208 |
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 |
2019-10-03 |
| MVB000209 |
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 |
2019-10-03 |
| MVB000210 |
waterbird workshop: behaviorDEPRECATED |
Behavioral categories used for analysis as part of the Movebank waterbird workshop in Constance, Germany, September 2009. Values are chosen from a controlled list: nesting = An observation where an animal is observed, or determined to be, at its nest site; roosting = An observation where an animal is observed, or determined to be, roosting. Format: controlled list; Units: none |
2019-10-03 |
| MVB000211 |
waterbird workshop: deployment special eventDEPRECATED |
Special events in the deployments used for analysis as part of the Movebank waterbird workshop in Constance, Germany, September 2009. Values are chosen from a controlled list: biologically irrelevant = An observation that is found to be biologically irrelevant, for example because there was no animal wearing the tag; death = The location where an animal is found or determined to be dead; release site = The location where the animal is released; tag failure = The observation where the tag was found, or determined, to have failed. Format: controlled list; Units: none |
2019-10-03 |
| MVB000212 |
waterbird workshop: migration stateDEPRECATED |
Migration states used for analysis as part of the Movebank waterbird workshop in Constance, Germany, September 2009. Values are chosen from a controlled list: breeding grounds = in the breeding grounds; fall migration = on fall migration; migrationOther = on a seasonal migration; migration to molt = on migration to molting site; molt site = at a molting site; spring migration = on spring migration; stopover = in a stopover site during a migration; summer non-breeding adult = in a summer non-breeding grounds, animal is an adult; summer non-breeding immature = in a summer non-breeding grounds, animal is immature; winter grounds = in the wintering grounds. Format: controlled list; Units: none |
2019-10-03 |
| MVB000213 |
wet count |
The wet count during the measurement interval. Example: '11'; Units: none; Entity described: event |
2019-10-03 |
