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 "Migration of red-backed shrikes from southern Scandinavia (data from Pedersen et al. 2018)" (Movebank Study ID 533427629). Individual attributes in the data files are defined below and in the Movebank Attribute Dictionary, available at www.movebank.org/node/2381. This data package includes the following data files: Migration of red-backed shrikes from southern Scandinavia (data from Pedersen et al. 2018)-light levels.csv Migration of red-backed shrikes from southern Scandinavia (data from Pedersen et al. 2018)-tracks.csv Migration of red-backed shrikes from southern Scandinavia (data from Pedersen et al. 2018)-reference-data.csv Pederson-BAStag-output.csv These data are described in the following written publication: Pedersen L, Jackson K, Thorup K, Tøttrup AP (2018) Full-year tracking suggests endogenous control of migration timing in a long-distance migratory songbird. Behavioral Ecology and Sociobiology 72: 139. doi:10.1007/s00265-018-2553-z Data package citation: Pedersen L, Jackson K, Thorup K, Tøttrup AP (2018) Data from: Full-year tracking suggests endogenous control of migration timing in a long-distance migratory songbird. Movebank Data Repository. doi:10.5441/001/1.7mf48770 ----------- 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. See here for the full description of this license http://creativecommons.org/publicdomain/zero/1.0 ----------- Data Attributes These definitions come from the Movebank Attribute Dictionary, available at www.movebank.org/node/2381. animal ID: An individual identifier for the animal, provided by the data owner. This identifier can be a ring number, a name, the same as the associated tag ID, etc. If the data owner does not provide an Animal ID, an internal Movebank animal identifier may sometimes be shown. example: 91876A, Gary 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". Units should be defined in the values (e.g. "2 years"). example: juvenile, adult units: Any units should be defined in the remarks. animal reproductive condition: The reproductive condition of the animal at the beginning of the deployment. example: non-reproductive, pregnant 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 an animal. tape: The tag is attached to the animal using tape. other: user specified data processing software: Name of the software program/s, scripts, etc. used to process raw sensor data and derive location estimates. example: BASTrack 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 (Coordinated Universal Time) or GPS time, which is a few leap seconds different from UTC same as: deploy off date 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 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 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 (Coordinated Universal Time) or GPS time, which is a few leap seconds different from UTC same as: deploy on 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 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 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 deployment comments: Additional information about the tag deployment that is not described by other reference data terms. example: This deployment was excluded from analysis because the tag failed. deployment end type: A categorical classification of the tag deployment end. Values are chosen 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 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. 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. example: it turns off during the night units: Any units should be defined in the remarks. 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 (Coordinated Universal Time) or GPS time, which is a few leap seconds different from UTC event ID: An identifier for the set of information associated with each record or event in a data set. A unique event ID is assigned to every time-location or other time-measurement record in Movebank. example: 6340565 units: none geolocator calibration: A description of how solar geolocators were calibrated. example: We calibrated the geolocators while deployed on the animals over a two-week period in their breeding site (< 5 km^2). See Jameson et al. (2011) for additional details. 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 THIS DATASET: Values come from the R package GeoLight: either 1 or 2 depending on whether the start timestamp is sunrise (1) or sunset (2). See https://cran.r-project.org/web/packages/GeoLight. geolocator light threshold: The light threshold used for location estimation with solar geolocators. example: 16 units: undefined geolocator sun elevation angle: The sun elevation angle used for location estimation with solar geolocators. example: -2.86 units: degrees latitude (decimal degree): The geographic longitude of a location along an animal track as estimated by the processed sensor data. Positive values are east of the Greenwich Meridian, negative values are west of it. example: -121.1761111 units: decimal degrees, WGS84 reference system same as: location lat THIS DATASET: Values of 0.001 occur during equinoxes when latitude cannot be estimated and should be interpreted as null values. light level: Light-level values measured by a solar geolocator. example: 28 units: undefined same as: gls:light level longitude (decimal degree): The geographic longitude of a location along an animal track as estimated by the processed sensor data. Positive values are east of the Greenwich Meridian, negative values are west of it. example: -121.1761111 units: decimal degrees, WGS84 reference system same as: location long manipulation type: The way in which the animal was manipulated during the deployment. Additional details about the manipulation can be provided using manipulation comments. 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. migration stage custom: 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 same as: migration stage THIS DATASET: Values indicate estimated site: 0 = migration, 1 = breeding site, 2 = Balkan staging site, 3 = Sahel staging site in autumn, 4 = southern Africa staging site, 5 = Sahel staging site in spring. sensor type: The type of sensor with which data were collected. 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 is using Argos Doppler shift for determining position. barometer: The sensor records air or water pressure. bird ring: The animal is identified by a ring that has a unique ID. GPS: The sensor uses GPS to find location and stores these. magnetometer: The sensor records the magnetic field. natural mark: The animal is identified by a natural marking. 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). sex: The sex of the biological individual(s) represented in the Occurrence. Values are from a controlled list: m: male f: female 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 (Coordinated Universal Time) or GPS time, which is a few leap seconds different from UTC study: The name of the study in Movebank in which data are stored. study site: The name of the deployment site, for example a field station or colony. example: Pickerel Island North 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, ptt_4532 same as: tag local identifier tag manufacturer name: The company or person that produced the tag. example: Holohil same as: manufacturer tag mass: The mass of the tag. example: 24 units: grams tag model: The model of the tag. example: T61 same as: model 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 radio transmitter/receiver. tag retrieval: The tag must be physically retrieved in order to obtain the data. 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 same as: species, animal taxon, individual taxon canonical name timestamp: The date and time a sensor measurement was taken. example: 2008-08-14 18:31:00.000 format: yyyy-MM-dd HH:mm:ss.sss units: UTC (Coordinated Universal Time) or GPS time, which is a few leap seconds different from UTC visible: Determines whether an event is visible on the Movebank Search map. Values are calculated automatically, with FALSE indicating that the event has been marked as an outlier by manually marked outlier or algorithm marked outlier. Allowed values are TRUE or FALSE. ----------- File headers for the Migrate Technology loggers ***************************************************** Migrate Technology Ltd logger Type: 3.12.4, current settings: Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. Logger number: F121 MODE: 1 (full range light, temperature, wet/dry and conductivity recorded) LIGHT: Sampled every minute with max light recorded every 5mins. TEMPERATURE: Sampled every 5mins with max and min recorded every 4hrs. WET/DRY and CONDUCTIVITY: Sampled every 30secs with number of samples wet and max conductivity recorded every 4hrs. Max record length = 15 months. Total battery life upto 23 months. Logger is currently 15 months old. Start of logging (DD/MM/YYYY HH:MM:SS): 21/05/2013 14:48:30 Age at start of logging (secs): 1873204, approx 1 months End of logging (DD/MM/YYYY HH:MM:SS): 28/07/2014 11:50:51 Age at end of logging (secs): 39273898, approx 15 months Duration of logging (DDDDD:HH:MM:SS): 00432:21:04:54 Drift (secs): -153. Memory not full. Pointers: 66953,127272,2631720,2631720,0,0,63% light mem used,85% wet/dry/temp mem used Tcals (Ax^3+Bx^2+Cx+D): -1403.406,278.986,534.314,-61.661 Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. ******************************************************************* Migrate Technology Ltd logger Type: 3.12.4, current settings: Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. Logger number: M014 MODE: 1 (full range light, temperature, wet/dry and conductivity recorded) LIGHT: Sampled every minute with max light recorded every 5mins. TEMPERATURE: Sampled every 5mins with max and min recorded every 4hrs. WET/DRY and CONDUCTIVITY: Sampled every 30secs with number of samples wet and max conductivity recorded every 4hrs. Max record length = 15 months. Total battery life upto 23 months. Logger is currently 15 months old. Programmed: 20/05/2014 09:39:53. Start of logging (DD/MM/YYYY HH:MM:SS): 20/05/2014 09:39:53 Age at start of logging (secs): 1595622, approx 1 months End of logging (DD/MM/YYYY HH:MM:SS): 24/07/2015 12:37:31 Age at end of logging (secs): 38757654, approx 15 months Timer (DDDDD:HH:MM:SS): 00430:02:47:12 Drift (secs): 626. Memory not full. Pointers: 73585,127136,10526880,10526880,0,0,69% light mem used,84% wet/dry/temp mem used Tcals (Ax^3+Bx^2+Cx+D): -6190.762,9592.950,-5525.090,1256.166 Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. ******************************************************************* Migrate Technology Ltd logger Type: 3.12.4, current settings: Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. XT. Logger number: M021 MODE: 1 (full range light, temperature, wet/dry and conductivity recorded) LIGHT: Sampled every minute with max light recorded every 5mins. TEMPERATURE: Sampled every 5mins with max and min recorded every 4hrs. WET/DRY and CONDUCTIVITY: Sampled every 30secs with number of samples wet and max conductivity recorded every 4hrs. Max record length = 15 months. Total battery life upto 23 months. Logger is currently 39 months old. Programmed: 17/06/2014 14:26:23. Start of logging (DD/MM/YYYY HH:MM:SS): 17/06/2014 14:26:23 Age at start of logging (secs): 4029418, approx 2 months End of logging (DD/MM/YYYY HH:MM:SS): 05/05/2014 01:02:01 Age at end of logging (secs): 265970, approx 0 months Timer (DDDDD:HH:MM:SS): 00000:09:54:04 Drift (secs): -4294967310. Memory not full. Pointers: 454,1136,7368816,7368816,0,0,0% light mem used,17475838% wet/dry/temp mem used Tcals (Ax^3+Bx^2+Cx+D): 6088.127,-14893.609,10712.561,-2326.194 Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. XT. ******************************************************************* Migrate Technology Ltd logger Type: 3.12.4, current settings: Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. Logger number: M034 MODE: 1 (full range light, temperature, wet/dry and conductivity recorded) LIGHT: Sampled every minute with max light recorded every 5mins. TEMPERATURE: Sampled every 5mins with max and min recorded every 4hrs. WET/DRY and CONDUCTIVITY: Sampled every 30secs with number of samples wet and max conductivity recorded every 4hrs. Max record length = 15 months. Total battery life upto 23 months. Logger is currently 13 months old. Programmed: 17/06/2014 14:29:13. Start of logging (DD/MM/YYYY HH:MM:SS): 17/06/2014 14:29:13 Age at start of logging (secs): 4029544, approx 2 months End of logging (DD/MM/YYYY HH:MM:SS): 08/06/2015 13:53:00 Age at end of logging (secs): 34785608, approx 13 months Timer (DDDDD:HH:MM:SS): 00355:23:21:04 Drift (secs): 163. Memory not full. Pointers: 63059,123576,12105912,12105912,0,0,59% light mem used,69% wet/dry/temp mem used Tcals (Ax^3+Bx^2+Cx+D): 13149.572,-27641.234,18283.105,-3812.251 Approx 0.5'C resolution. Conductivity >63 for 'wets' count. Light range 4, ambient. ----------- File Pederson-BAStag-output.csv This file contains compiled output from the R package BAStag (https://github.com/SWotherspoon/BAStag) that document which twilights are deleted from the original raw light files. This file contains the following attributes: Twilight: Date and time of twilight estimate (UTC) Rise: logical variable indicating sunrise Deleted: logical variable identifying deleted twilights Marker: integer vector of marks Inserted: logical vector of marks Twilight3: logical variable indicating inserted twilights from stage 3 in preprocessLight function, r-package BAStag Marker3: logical vector of inserted marks ID: animal/tag identifier ----------- More Information For more information about this repository, see www.movebank.org/node/15294, the FAQ at www.movebank.org/node/2220, or contact us at support@movebank.org.