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 "Switzerland Solothurn - Long term study on migratory movement of Alpine swifts (Apus melba)" (Movebank Study ID 1266896491). 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: Switzerland Solothurn - Long term study on migratory movement of Alpine swifts (Apus melba)-barometer.csv Switzerland Solothurn - Long term study on migratory movement of Alpine swifts (Apus melba)-light-levels.csv Switzerland Solothurn - Long term study on migratory movement of Alpine swifts (Apus melba)-tracks.csv Switzerland Solothurn - Long term study on migratory movement of Alpine swifts (Apus melba)-twilights.csv Switzerland Solothurn - Long term study on migratory movement of Alpine swifts (Apus melba)-reference-data.csv Data package citation: Meier CM, Liechti F. 2020. Data from: Study "Switzerland Solothurn - Long term study on migratory movement of Alpine swifts (Apus melba)". Movebank Data Repository. https://www.doi.org/10.5441/001/1.nn518dc4 These data are described in the following written publication: Meier CM, Karaardıç H, Aymí R, Peev SG, Witvliet W, Liechti F. 2020. Population-specific adjustment of the annual cycle in a super-swift trans-Saharan migrant. J Avian Biol. 51(11):e02515. https://doi.org/10.1111/jav.02515 ----------- 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 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 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 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 barometric pressure: The barometric air or water pressure. example: 32536.0 units: mbar (hPa) entity described: event behavioural classification: Behavioural classifications assigned to the animal by the data owner. The method for defining and assigning these classifications are unique to the study and can be described using 'behaviour according to'. Recommended best practice is to use a controlled list. example: roosting, foraging, running units: none entity described: event comments: Additional information about events that is not described by other event data terms. example: we observed the animal foraging (see photo BT25) units: none entity described: event data processing software: Name of the software program/s, scripts, etc. used to process raw sensor data and derive location estimates. example: BASTrack units: none entity described: deployment deploy off latitude: The geographic latitude of the location where the deployment ended (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data). example: -38.6866 units: decimal degrees, WGS84 reference system entity described: deployment deploy off longitude: The geographic longitude of the location where the deployment ended (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data). example: 146.3104 units: decimal degrees, WGS84 reference system entity described: deployment deploy off timestamp: The timestamp when the tag deployment ended. example: 2009-10-01 12:00:00.000 format: yyyy-MM-dd HH:mm:ss.SSS units: UTC or GPS time entity described: deployment same as: deploy off date deploy on latitude: The geographic latitude of the location where the animal was released (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data). example: 27.3516 units: decimal degrees, WGS84 reference system entity described: deployment deploy on longitude: The geographic longitude of the location where the animal was released (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data). example: -97.3321 units: decimal degrees, WGS84 reference system entity described: deployment deploy on 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 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 geolocator calibration: A description of how solar geolocators were calibrated. Best practice is to refer to a publication and/or analysis software/parameters used. example: on-animal calibration over a two-week period in the breeding site; see Jameson et al. (2011) units: none entity described: deployment geolocator light threshold: The light threshold used for location estimation with solar geolocators. example: 16 units: not defined entity described: deployment geolocator rise: The period of day used to estimate location by geolocation. TRUE = sunrise, FALSE = sunset. units: none entity described: event lat lower: The lower bound of the latitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'. example: 23.4 units: decimal degrees, WGS84 reference system entity described: event same as: latitude lower lat upper: The upper bound of the latitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'. example: 32.4 units: decimal degrees, WGS84 reference system entity described: event same as: latitude upper light level: Light-level values measured by a solar geolocator. Best practice is to define values in the reference data. example: 28 units: not defined entity described: event 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 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 long lower: The lower bound of the longitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'. example: 0.236 units: decimal degrees, WGS84 reference system entity described: event same as: longitude lower long upper: The upper bound of the longitude estimate. Values can be described using 'location error percentile' and 'location accuracy comments'. example: -0.489 units: decimal degrees, WGS84 reference system entity described: event same as: longitude upper 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 study site: A location such as the deployment site or colony, or a location-related group such as the herd or pack name. example: Pickerel Island North units: none entity described: deployment tag 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 twilight excluded: Whether a twilight identified by automated processing was excluded from subsequent analysis. Allowed values are TRUE or FALSE. units: none entity described: event twilight inserted: Whether a twilight was inserted for a time when automated processing did not identify a twilight. Allowed values are TRUE or FALSE. units: none entity described: event 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.