Comments about the death of the animal. Summary information can be reported in 'animal mortality date', 'animal mortality latitude', 'animal mortality longitude', and 'animal mortality type'. Example: 'hit by a car'; Units: none; Entity described: individual
Whether the G-Matrix device is moving (definition from RAMAC CALLBACK Specification, v2.0.2, August 2021). Allowed values are A1 = true (moving) or 0 = false (static). Format: controlled list; Entity described: event
The average current from or to the battery since the previous transmission (definition from Global Satellite Engineeering, 2024). Allowed values are Discharge = battery is discharging (<0 mA); ChargeSlow = low charging (0-8 mA); ChargeMedium = medium charging (8-16 mA); ChargeHigh = high charging (>16 mA). Format: controlled list; Entity described: event
Whether low power mode was enabled at the time of transmission. Allowed values are TRUE or FALSE (definition from Global Satellite Engineeering, 2024). Units: none; Entity described: event
The x-y covariance, measure of the quality of the location estimate, calculated by the ATLAS system. Lower values indicate linear independence of the errors in the easting and northing directions. Example: '3.64854761612132'; Units: m^2; Entity described: event
The source of the location estimate from the Sensolus tag. Example: 'network'; Units: none; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 20 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '5343'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 21 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '3562'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 22 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '7124'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 23 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '113984'; Units: m/s^2; Entity described: event
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_42818'; Units: none; Entity described: deployment
The device depth below the water surface. Example: '16.4'; Units: meters; Entity described: event
The type of sensor with which data were collected. All sensors are associated with a tag id, and tags can contain multiple sensor types. Each event record in Movebank is assigned one sensor type. If values from multiple sensors are reported in a single event, the primary sensor is used. Values are chosen from a controlled list: acceleration = The sensor collects acceleration data; accessory-measurements = The sensor collects accessory measurements, such as battery voltage; acoustic-telemetry = The sensor transmits an acoustic signal that is detected by receivers to determine location; argos-doppler-shift = The sensor location is estimated by Argos using Doppler shift; atlas-geolocation = The sensor location is estimated by an ATLAS system; barometer = The sensor records air or water pressure; bird-ring = The animal is identified by a band or ring that has a unique identifier; derived = Information is derived from other sensor data; geolocation-api = The location is determined based on detection by nearby cell towers or other wireless network connectors using the World Wide Web Consortium Geolocation API Recommendation; gnss = The sensor uses one or more global navigation satellite systems to determine location; gps = The sensor uses GPS to determine location; gyroscope = The sensor records angular velocity; heart-rate = The sensor records or is used to calculate heart rate; magnetometer = The sensor records the magnetic field; natural-mark = The animal is identified by a unique natural marking; orientation = Quaternion components describing the orientation of the tag are derived from accelerometer and gyroscope measurements; proximity = The sensor identifies proximity to other tags; radio-transmitter = The sensor transmits a radio signal that is detected by receivers to determine location; sigfox-geolocation = The sensor location is determined by Sigfox using the received signal strength indicator; solar-geolocator = The sensor collects light levels, which are used to determine position (for processed locations); solar-geolocator-raw = The sensor collects light levels, which are used to determine position (for raw light-level measurements); solar-geolocator-twilight = The sensor collects light levels, which are used to determine position (for twilights calculated from light-level measurements); tdr = The sensor is a time-depth recorder. Format: controlled list; Entity described: event
Used in the REST API. The ID for the type of sensor with which data were collected. Allowed values are 2365683 = acceleration; 7842954 = accessory-measurements; 1239574236 = acoustic-telemetry; 82798 = argos-doppler-shift; 4342918458 = atlas-geolocation; 77740391 = barometer; 397 = bird-ring; 3090218819 = derived; 3090218812 = geolocation-api; 3090218818 = gnss; 653 = gps; 1297673380 = gyroscope; 2206221896 = heart-rate; 77740402 = magnetometer; 2365682 = natural-mark; 819073350 = orientation; 2645090675 = proximity; 673 = radio-transmitter; 2299894820 = sigfox-geolocation; 3886361 = solar-geolocator; 9301403 = solar-geolocator-raw; 914097241 = solar-geolocator-twilight; 4264744764 = tdr. Format: controlled list; Entity described: event
The orientation of the unit as measured by the accelerometer (definition from Global Satellite Engineeering, 2024). Values indicate the axis that is directed up (away from the horizontal ground surface). Allowed values are XPositive; XNegative; YPositive; YNegative; ZPositive; Znegative. Format: controlled list; Entity described: event
The variance in the easting (X, longitude) estimate in the local UTM zone, calculated by the ATLAS system. Lower values indicate better accuracy. Example: '3.08617'; Units: m^2; Entity described: event
The variance in the northing (Y, latitude) estimate in the local UTM zone, calculated by the ATLAS system. Lower values indicate better accuracy. Example: '8.69957'; Units: m^2; Entity described: event
The difference between the fix time given by the satellite and that given by the internal tag clock. Example: '-597'; Units: seconds; Entity described: event
The data format of the tag used to decode the data. Example: 'TinyFoxStarOddi'; Units: ; Entity described: event
The type of Sensolus fix. Possible values include activity, location and status. Example: 'activity'; Units: none; Entity described: event
The character from the 19th hexadecimal character in the Sigfox payload used to define the format of University of Konstanz Sigfox tags (definition from G. Heine, 2024). Allowed values are 0 = battery voltage 3.2 volts with GPS coordinates; 1 = battery voltage 3.3 volts with GPS coordinates; 2 = battery voltage 3.4 volts with GPS coordinates; 3 = battery voltage 3.5 volts with GPS coordinates; 4 = battery voltage 3.6 volts with GPS coordinates; 5 = battery voltage 3.7 volts with GPS coordinates; 6 = battery voltage 3.8 volts with GPS coordinates; 7 = battery voltage 3.9 volts with GPS coordinates; 8 = sensor data 3 x word; 9 = sensor data 6 x byte; A = alarm message (animal death and coordinates); B = alarm message (animal death and logger status); C = not defined; D = not defined; E = not defined; F = logger status (no GPS) Format: controlled list; Entity described: event
The raw sensor data from the tag encoded in hexadecimal format. Units: none; Entity described: event
The percentage of activity (VeDBA above a predetermined threshold) recorded by the tag over the last 24 hours. Units: none (percent); Entity described: event
Indicates whether the self diagnostic routine of the tag found a problem. TRUE indicates the tag might not work correctly. Allowed values are TRUE or FALSE. Units: none; Entity described: event
Indicates whether the onboard memory of the tag is full and needs to be emptied by an uplink command. Allowed values are TRUE or FALSE. Units: none; Entity described: event
Minimum air pressure measured by the tag in the past 24 hours. Air pressure is sampled once per minute. Units: mbar (hPa); Entity described: event
The software version of the TinyFox tag. Units: none; Entity described: event
Indicates whether the event is an initial tag activation. Allowed values are TRUE or FALSE. Units: none; Entity described: event
Maximum temperature measured by the tag in the last 24 hours. Temperature is sampled once per minute. Units: degrees Celsius; Entity described: event
Minimum temperature measured by the tag in the last 24 hours. Temperature is sampled once per minute. Units: degrees Celsius; Entity described: event
The vector of the dynamic body acceleration (VeDBA) over the previous hour. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '3562'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 1 hour before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '5343'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 2 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '7124'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 3 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '5343'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 4 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '5343'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 5 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '5343'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 6 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '3562'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 7 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '5343'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 8 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '28496'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 9 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '44525'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 10 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '42744'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 11 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '17810'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 12 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '32058'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 13 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '87269'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 14 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '78364'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 15 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '60554'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 16 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '69459'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 17 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '96174'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 18 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '46306'; Units: m/s^2; Entity described: event
The hourly vector of the dynamic body acceleration (VeDBA) recorded 19 hours before the timestamp. This is calculated as the sum of VeDBA values over 1-second acceleration bursts, recorded at 28 Hz, one time each minute. Example: '5343'; Units: m/s^2; Entity described: event
The barometric water pressure depth. Example: '-11'; Units: meters; Entity described: event
raptor workshop deployment special event
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: BiologicallyIrrelevant = 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; ReleaseSite = The location where the animal is released; TagFailure = The observation where the tag was found, or determined, to have failed. Format: controlled list; Entity described: event
The number of messages transmitted to GPS satellites. Example: '278'; Units: count; Entity described: event
A list of additional measurements taken during recapture of the animal at the end of the deployment. Recommended best practice is to define units and use a key:value encoding schema for a data interchange format such as JSON. Example: "{"tarsusLengthInMillimeters":17.3, "wingChordInMillimeters":125}"; Units: not defined; Entity described: deployment
A list of additional measurements taken during capture of the animal at the start of the deployment. Recommended best practice is to define units and use a key:value encoding schema for a data interchange format such as JSON. Example: "{"tarsusLengthInMillimeters":17.3, "wingChordInMillimeters":125}"; Units: not defined; Entity described: deployment
The number of conspecifics observed, including the tagged animal. Units: count; Entity described: event
The estimated accuracy of 'ground speed'. Units: m/s; Entity described: event
The Africa Wildlife Tracking current battery alarm condition. TRUE indicates a low battery. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current CBit alarm condition. TRUE indicates that a continuous built-in-test fault has occurred. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current coverage alarm condition. TRUE indicates no service coverage. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current geofence alarm condition. TRUE indicates a perimeter breach. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current memory alarm condition. TRUE indicates low memory. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current movement alarm condition. TRUE indicates that no movement has been detected. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current tamper foil alarm condition. TRUE indicates that the tag has been tampered with. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current track mode alarm condition. TRUE indicates that the tag is in track mode. Allowed values are TRUE or FALSE (definition from the Africa Wildlife Tracking API User Manual, 2021). Units: none; Entity described: event
The Africa Wildlife Tracking current logger interval (definition from the Africa Wildlife Tracking API User Manual, 2021). Possible values are off; every 10 minutes; every 1 hour; every 6 hours; every 12 hours; every 24 hours; every 48 hours; every 3 hours; every 30 minutes; every 2 hours; every 4 hours; every 5 hours; every 8 hours. Format: controlled list; Entity described: event
The battery charging voltage. Example: '1235.25'; Units: mV; Entity described: event
The breeding stage of the animal. Example: 'chick-rearing'; Units: none; Entity described: event
The Druid alert. Allowed values are 1 = dead. Format: controlled list; Entity described: event
Modes of data collecting for Druid tags. Allowed values are [1] = scheduled collecting based on the preset collection frequency; [2] = dynamic collecting, with BOOST data collection triggered based on voltage conditions; [4] = in-flight collecting, with BOOST data collection triggered based on speed conditions; [8] = edge intelligence; [10] = inflow and outflow; [100] = algorithm event death; [101] = algorithm event flight. Format: controlled list; Entity described: event
The number of connected base stations in the positioning session. Example: '4'; Units: count; Entity described: event
Dilution of precision provided by a GNSS. Example: '1.8'; Units: unitless; Entity described: event
The type of GNSS fix. To import non-numeric characters use 'GNSS fix type raw'. Allowed values are 1 = no fix; 2 = 2D fix (altitude typically not valid); 3 = 3D fix (altitude typically valid). Format: controlled list; Entity described: event
The type of GNSS 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 'GNSS fix type'. Example: '3D'; Units: none; Entity described: event
Horizontal dilution of precision provided by a GNSS. Example: '1.2'; Units: unitless; Entity described: event
The signal reception strength of the strongest GNSS satellite of those used to calculate the location estimate. Example: '39'; Units: dBm; Entity described: event
The number of messages transmitted to GNSS satellites. Example: '278'; Units: count; Entity described: event
Position dilution of precision provided by a GNSS. Example: '1.9'; Units: unitless; Entity described: event
The number of satellites used to estimate the location. Example: '8'; Units: count; Entity described: event
The time required to obtain the GNSS location fix. Example: '36'; Units: seconds; Entity described: event
Vertical dilution of precision provided by a GNSS. Example: '1.9'; Units: unitless; Entity described: event
The LoRaWAN data transmission rate used for the data packet. Example: '3'; Units: none; Entity described: event
The Gateway ID of the best LoRaWAN Gateway that received the data packet. Example: 'b827ebfffee234c6'; Units: none; Entity described: event
The geographic latitude of the LoRaWAN gateway. Units: decimal degrees, WGS84 reference system; Entity described: event
The geographic longitude of the LoRaWAN gateway. Units: decimal degrees, WGS84 reference system; Entity described: event
The undecoded raw LoRaWAN payload. Example: '9A4EAIwClUeAfosUL1UAAA=='; Units: none; Entity described: event
The LoRaWAN port number used by the device for this packet. Example: '4'; Units: none; Entity described: event
The received signal strength indicator measured by the best LoRaWAN Gateway that received the data packet. Example: '-49'; Units: dBm; Entity described: event
The SNR (signal-to-noise ration) measured by the best LoRaWAN Gateway that received the data packet. Example: '14'; Units: dB; Entity described: event
The LoRaWAN spreading factor used to determine the transmission rate of the data packet. Example: '9'; Units: none; Entity described: event
The LoRaWAN uplink frame count (FCNT) for the data packet. Example: '332'; Units: count; Entity described: event
Whether the GPS fix of the OpenCollar device has been acquired using active tracking. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The number of cold GPS fix attempts for the OpenCollar device (definition from Smart Parks, 2023). Example: '0'; Units: count; Entity described: event
The accelerometer error state of the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The battery error state of the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The bluetooth error state of the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The flash memory error state of the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The error state of the LR chipset on the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The LoRaWAN join error state of the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The u-blox module error state of the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The u-blox fix error state of the OpenCollar device. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The number of hot GPS fix attempts of the OpenCollar device (definition from Smart Parks, 2023). Example: '0'; Units: count; Entity described: event
Whether the OpenCollar device is locked with a PIN code. Allowed values are TRUE or FALSE (definition from Smart Parks, 2023). Units: none; Entity described: event
The number of unread user messages on the OpenCollar device (definition from Smart Parks, 2023). Example: '0'; Units: count; Entity described: event
The payload type of the OpenCollar device, used to decode the payload (definition from Smart Parks, 2023). Example: 'opencollar_edge_4'; Units: none; Entity described: event
The reset code for the last reset of the OpenCollar device (definition from Smart Parks, 2023). Example: '4'; Units: none; Entity described: event
The uptime of the OpenCollar device since the last reset (definition from Smart Parks, 2023). Example: '71'; Units: weeks; Entity described: event
The major firmware version of the OpenCollar device (definition from Smart Parks, 2023). Example: '2'; Units: none; Entity described: event
The minor firmware version of the OpenCollar device (definition from Smart Parks, 2023). Example: '15'; Units: none; Entity described: event
The firmware type of the OpenCollar device (definition from Smart Parks, 2023). Example: '5'; Units: none; Entity described: event