README This data file is published by the Movebank Data Repository (www.datarepository.movebank.org). As of the time of publication, a version of this published animal tracking dataset, with additional data, can be viewed on Movebank (www.movebank.org) in the study "LifeTrack Rough-legged buzzards" (Movebank Study ID 9493874). Individual attributes in the data files are defined below, in the NERC Vocabulary Server at http://vocab.nerc.ac.uk/collection/MVB and in the Movebank Attribute Dictionary at www.movebank.org/cms/movebank-content/movebank-attribute-dictionary. Metadata describing this data package are maintained at https://datacite.org. This data package includes the following data files: LifeTrack Rough-legged buzzards_part-acceleration.csv.zip LifeTrack Rough-legged buzzards_part-gps.csv LifeTrack Rough-legged buzzards_part-reference-data.csv Data package citation: Pokrovsky I, Kulikova O, Wikelski M. 2021. Data from: Longer days enable higher diurnal activity for migratory birds [rough-legged buzzards]. Movebank Data Repository. https://doi.org/10.5441/001/1.dg3sm625 These data are described in the following written publication: Pokrovsky I, Kölzsch A, Sherub S, Fiedler W, Glazov P, Kulikova O, Wikelski M, Flack A. 2021. Longer days enable higher diurnal activity for migratory birds. J Anim Ecol. https://doi.org/10.1111/1365-2656.13484 ----------- Terms of Use This data file is licensed by the Creative Commons Zero (CC0 1.0) license. The intent of this license is to facilitate the re-use of works. The Creative Commons Zero license is a "no rights reserved" license that allows copyright holders to opt out of copyright protections automatically extended by copyright and other laws, thus placing works in the public domain with as little legal restriction as possible. However, works published with this license must still be appropriately cited following professional and ethical standards for academic citation. We highly recommend that you contact the data creator if possible if you will be re-using or re-analyzing data in this file. Researchers will likely be interested in learning about new uses of their data, might also have important insights about how to properly analyze and interpret their data, and/or might have additional data they would be willing to contribute to your project. Feel free to contact us at support@movebank.org if you need assistance contacting data owners. For additional information, see License description: http://creativecommons.org/publicdomain/zero/1.0 General Movebank Terms of Use: www.movebank.org/cms/movebank-content/general-movebank-terms-of-use Movebank user agreement: https://www.movebank.org/cms/movebank-content/data-policy#user_agreement ----------- Data Attributes These definitions come from the Movebank Attribute Dictionary, available at http://vocab.nerc.ac.uk/collection/MVB and www.movebank.org/node/2381. animal comments: Additional information about the animal that is not described by other reference data terms. example: sibling of #1423 units: none entity described: individual animal ID: An individual identifier for the animal, provided by the data owner. If the data owner does not provide an Animal ID, an internal Movebank animal identifier is sometimes shown. example: 91876A, Gary units: none entity described: individual same as: individual local identifier animal latest date born: The latest date an animal is thought to have been born. example: 2001-12-12 16:54:00.000 format: yyyy-MM-dd HH:mm:ss.SSS units: UTC (sometimes date is provided based on local time) entity described: individual animal life stage: The age class or life stage of the animal at the beginning of the deployment. Can be years or months of age or terms such as 'adult', 'subadult' and 'juvenile'. Best practice is to define units in the values if needed (e.g. '2 years'). example: juvenile, adult units: not defined entity described: deployment animal ring ID: A number or color scheme for a band or ring attached to the animal. example: 26225 units: none entity described: individual animal sex: The sex of the animal. Allowed values are m = male f = female u = unknown format: controlled list entity described: individual animal taxon: The scientific name of the species on which the tag was deployed, as defined by the Integrated Taxonomic Information System (ITIS, www.itis.gov). If the species name can not be provided, this should be the lowest level taxonomic rank that can be determined and that is used in the ITIS taxonomy. Additional information can be provided using the term 'taxon detail'. example: Buteo swainsoni format: controlled list entity described: individual same as: individual taxon canonical name 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 entity described: deployment data decoding software: The name or version of software used to decode the sensor data. example: 11 units: not defined entity described: event deploy off timestamp: The timestamp when the tag deployment ended. example: 2009-10-01 12:00:00.000 format: yyyy-MM-dd HH:mm:ss.SSS units: UTC or GPS time entity described: deployment same as: deploy off date deploy on person: The name of the person/people who attached the tag to the animal and began the deployment. example: G. Smith units: none entity described: deployment deploy on timestamp: The timestamp when the tag deployment started. example: 2008-08-30 18:00:00.000 format: yyyy-MM-dd HH:mm:ss.SSS units: UTC or GPS time entity described: deployment same as: deploy on date deployment comments: Additional information about the tag deployment that is not described by other reference data terms. example: body length 154 cm; condition good units: none entity described: deployment deployment 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 eobs acceleration axes: This tells you about the enabled ACC axes, like X and/or Y and/or Z (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011). example: XYZ units: none entity described: event eobs acceleration sampling frequency per axis: This is the sampling frequency for one axis. Don't mix this up with the sampling frequency for all axes together. For example if you have three ACC axes enabled, then the sampling frequency for all axes together is three times the sampling frequency for one axis. The sampling frequency is measured in Hertz, which is the same as 1/second. For example a sampling frequency of 10 Hz means that you get 10 samples per second (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011). example: 5.93 units: Hz entity described: event eobs accelerations raw: Acceleration along the X and or Y and or Z axes of the tag, depending on which axes were activated on the tag as described in 'eobs acceleration axes'. Measurements alternate one measurement for each active axis in alphabetical order. The values are digital readings between 0 and 4095 of the analogue digital converter on the tag, and can be converted to m/s^2 with proper calibration. These samples are made at the rate described by the field 'eobs acceleration sampling frequency per axis' starting with the first sample at the time described in the field 'e-obs start timestamp'. Tags with numbers e-obs numbers 2242 and higher, which began being provided in spring 2012, have Y-axis values in the opposite direction from those in older tags (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011; Wolgang Heidrich, e-obs Digital Telemetry, personal communication, 2012). example: 1844 1889 1653 1845 1896 1653 1837 1897 1653 1842 1898 1650 1844 1899 1644 1840... units: not defined entity described: event eobs battery voltage: Unloaded battery voltage (definition from Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012). example: 3712 units: mV entity described: event eobs fix battery voltage: Loaded battery voltage, i.e. battery voltage when GPS module is acquiring a fix (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010; Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012). example: 3535 units: mV entity described: event eobs horizontal accuracy estimate: A horizontal (in)accuracy estimate, calculated by the GPS module (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010; Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012). example: 35.07 units: m entity described: event eobs key bin checksum: A checksum of the original binary data, so that Movebank can quickly compare different lines by comparing their checksums (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011). example: 4152324118 units: none entity described: event eobs speed accuracy estimate: A speed (in)accuracy estimate, calculated by the GPS module. The speed accuracy estimate (better named 'inaccuracy estimation') may show very high values, since the GPS module calculates a very conservative value. These speed measurements are potentially very inaccurate when interpreting the data (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010; Franz Kuemmeth, e-obs Digital Telemetry, personal communication, 2012). example: 6.58 units: m/s entity described: event eobs start timestamp: The date and time of day when the acceleration burst belonging to this line begins. The exact time of the first sample is a little later (up to 1 second) for older e-obs tags, especially when the ACC-pinger is enabled (4 pings before the start of each ACC burst) (definition from 'e-obs GPS-acceleration-tags application note: How to use the acceleration sensor, interpret, analyse its data and how to get values in m/s^2', 2011). example: 2011-01-03 13:45:00.000 format: yyyy-MM-dd HH:mm:ss.SSS units: GPS time entity described: event eobs status: The record status, from e-obs GPS/accelerometer tags (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010). Allowed values are A = position and time within accuracy masks B = only time of week and weeknumber valid C = only weeknumber valid D = no valid data format: controlled list units: none entity described: event eobs temperature: Temperature; this value is not calibrated and therefore very inaccurate (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010). example: 45, -8 units: degrees Celsius entity described: event eobs type of fix: The type of fix of data from e-obs GPS/accelerometer tags (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010). Allowed values are 3 = 3D fix and 2 = 2D fix format: controlled list units: none entity described: event eobs used time to get fix: The amount of time that was needed for this GPS fix; interesting for estimating power requirements (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010). example: 22 units: seconds entity described: event 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 GPS DOP: Dilution of precision provided by the GPS. example: 1.8 units: unitless entity described: event ground speed: The estimated ground speed provided by the sensor or calculated between consecutive locations. example: 7.22 units: m/s entity described: event heading: The direction in which the tag is moving, in decimal degrees clockwise from north, as provided by the sensor or calculated between consecutive locations. Values range from 0-360: 0 = north, 90 = east, 180 = south, 270 = west. example: 315.88 units: degrees clockwise from north entity described: event height above ellipsoid: The estimated height above the ellipsoid, typically estimated by the tag. If altitudes are calculated as height above mean sea level, use 'height above mean sea level'. example: 24.8 units: meters entity described: event 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 location lat: The geographic latitude of the location as estimated by the sensor. Positive values are east of the Greenwich Meridian, negative values are west of it. example: -41.0982423 units: decimal degrees, WGS84 reference system entity described: event location long: The geographic longitude of the location as estimated by the sensor. Positive values are east of the Greenwich Meridian, negative values are west of it. example: -121.1761111 units: decimal degrees, WGS84 reference system entity described: event 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 entity described: deployment 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 entity described: event study name: The name of the study in Movebank. example: Coyotes, Kays and Bogan, Albany NY units: none entity described: study, event tag comments: Additional information about the tag that is not described by other reference data terms. example: custom-made Doppler shift Argos tag with a special altitude sensor units: none entity described: tag tag ID: A unique identifier for the tag, provided by the data owner. If the data owner does not provide a tag ID, an internal Movebank tag identifier may sometimes be shown. example: 2342 units: none entity described: tag same as: tag local identifier tag manufacturer name: The company or person that produced the tag. example: Holohil units: none entity described: tag tag mass: The mass of the tag. example: 24 units: grams entity described: tag tag model: The model of the tag. example: T61 units: none entity described: tag tag production date: The approximate date the tag was produced (can be a year, month, or day). example: 40603 units: not defined entity described: tag tag serial no: The serial number of the tag. example: MN93-33243 units: none entity described: tag tag voltage: The voltage as reported by the tag. example: 2895 units: mV entity described: event timestamp: The date and time corresponding to a sensor measurement or an estimate derived from sensor measurements. example: 2008-08-14 18:31:00.000 format: yyyy-MM-dd HH:mm:ss.SSS units: UTC or GPS time entity described: event 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 ----------- More Information For more information about this repository, see www.movebank.org/cms/movebank-content/data-repository, the FAQ at www.movebank.org/cms/movebank-content/data-repository-faq, or contact us at support@movebank.org.