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 can be viewed on Movebank (www.movebank.org) in the study "3D flights of European free-tailed bats" (Movebank Study ID 312057662). 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: 3D flights of European free-tailed bats.csv 3D flights of European free-tailed bats-reference-data.csv TadaridaHighFast_annotated.csv AppA_SuppData_2_3D_staticPlot_minusLat_studyArea_allBats.html AppB_SuppData_3_3D_verticalArrowsPlot_minusLat_zoomBat.html Data package citation: O'Mara MT, Amorim F, McCracken GF, Mata V, Safi K, Wikelski M, Beja P, Rebelo H, Dechmann DKN. 2021. Data from: European free-tailed bats use topography and nocturnal updrafts to fly high and fast. Movebank Data Repository. https://doi.org/10.5441/001/1.52nn82r9 These data are described in the following written publication: O'Mara MT, Amorim F, Scacco M, McCracken GF, Safi K, Mata V, TomeĢ R, Swartz S, Wikelski M, Beja P, Rebelo H, Dechmann DKN. 2021. Bats use topography and nocturnal updrafts to fly high and fast. Curr Biol. https://doi.org/10.1016/j.cub.2020.12.042 ----------- 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 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 life stage: The age class or life stage of the animal at the beginning of the deployment. Can be years or months of age or terms such as 'adult', 'subadult' and 'juvenile'. Best practice is to define units in the values if needed (e.g. '2 years'). example: juvenile, adult units: not defined entity described: deployment animal mass: The mass of the animal, typically at the beginning of the deployment. example: 500 units: grams entity described: deployment animal reproductive condition: The reproductive condition of the animal at the beginning of the deployment. example: lactating units: none entity described: deployment 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 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 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 end comments: A description of the end of a tag deployment, such as cause of mortality or notes on the removal and/or failure of tag. example: data transmission stopped after 108 days. Cause unknown units: none entity described: deployment deployment end type: A categorical classification of the tag deployment end, from a controlled list: captured = The tag remained on the animal but the animal was captured or confined dead = The deployment ended with the death of the animal that was carrying the tag equipment failure = The tag stopped working fall off = The attachment of the tag to the animal failed, and it fell of accidentally other = other released = The tag remained on the animal but the animal was released from captivity or confinement removal = The tag was purposefully removed from the animal unknown = The deployment ended by an unknown cause format: controlled list units: none entity described: deployment deployment ID: A unique identifier for the deployment of a tag on animal, provided by the data owner. If the data owner does not provide a Deployment ID, an internal Movebank deployment identifier may sometimes be shown. example: Jane-Tag42 units: none entity described: deployment duty cycle: Remarks associated with the duty cycle of a tag during the deployment, describing the times it is on/off and the frequency at which it transmits or records data. Units and time zones should be defined in the remarks. example: 15-min fixes from 8:00-18:00 local time (0:00-10:00 UTC) units: not defined entity described: deployment 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 HDOP: Horizontal dilution of precision provided by the GPS. example: 1.2 units: unitless entity described: event GPS maximum signal strength: The signal reception strength of the strongest GPS satellite of those used to calculate the location estimate. example: 39 units: dBm entity described: event GPS satellite count: The number of GPS satellites used to estimate the location. example: 8 units: none entity described: event ground speed: The estimated ground speed provided by the sensor or calculated between consecutive locations. example: 7.22 units: m/s entity described: event height above mean sea level: The estimated height of the tag above mean sea level, typically estimated by the tag. If altitudes are calculated as height above an ellipsoid, use 'height above ellipsoid'. example: 34 units: m entity described: event same as: height above msl 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 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 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 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 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 entity described: deployment 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 ----------- TadaridaHighFast_annotated.csv This file contains the tracking data annotated for the analysis. event-id: see above animal-id: see above animal-sex: see above timestamp: see above BatDay: an adjusted numerical day for the day each bat was tracked gps:hdop: see above gps:maximum-signal-strength: see above location-long: see above location-lat: see above height-above-msl: see above height_terrain: height of the terrain taken from a 30 m ASTER Digital Elevation Model (meters amsl) height_true: height above ground level (meters) tdif: time lag between fixes (seconds) U.Component: U (zonal) vectorial component of wind (meters per second) V.Component: V (meridional) vectorial component of wind (meters per second) W.Component: W (vertical) vectorial component of wind (meters per second) ws: two-dimensional wind support (meters per second) cw: two-dimensional cross wind support (meters per second) ws.3d: three-dimensional wind support (meters per second) cw.3d: three-dimensional cross wind support (meters per second) ground.speed: ground speed (meters per second) ground.distance: horizontal distance covered between fixes (meters) airspeed: two-dimensional airspeed (meters per second) seg.dist3d: three-dimensional segment distance between fixes (meters) seg.speed3d: three-dimensional segment speed between fixes (meters) airspeed.3d: three-dimensional airspeed between fixes (meters per second) climb.rate: vertical speed between fixes (meters per second) ----------- AppA_SuppData_2_3D_staticPlot_minusLat_studyArea_allBats.html This file contains an interactive 3D plot of Figure 1 showing the topography of the study area and the trajectories of the eight bats included in the study in different colors. Terrain elevation was extracted from a DEM with a spatial resolution of 100 m, but given the large area to display the surface was resampled to a spatial resolution of 500 m. ----------- AppB_SuppData_3_3D_verticalArrowsPlot_minusLat_zoomBat.html This file contains an interactive 3D plot of Figure S1 capturing a small section of the study area shown in Appendix A (Figure 1) and including a portion of the GPS trajectory (200 fixes) of a bat tracked on the night of August 08, 2017 between 20:00 and 04:00 of the following morning. The green and red spheres indicate the start and the end of the trajectory. The trajectory of the bat is colored according to 3D airspeed from purple (0.032 m/s) to yellow (15.12 m/s, see Figure 2 of O'Mara et al. [2021] for details). A subsample of the uplifting wind vectors at 23 pressure levels (from 10 to 2156 m AGL) is represented by vertical arrows. The length of these arrows represents the vertical wind component. ----------- 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.