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 "LifeTrack White Stork Rheinland-Pfalz" (Movebank Study ID 76367850). 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/node/2381. Metadata describing this data package are maintained at https://datacite.org. This published dataset contains data in the study "LifeTrack White Stork Rheinland-Pfalz" through 31 March, 2019. The study is ongoing and newer data are publicly available from the Movebank study. This data package includes the following data files: LifeTrack White Stork Rheinland-Pfalz_2015-2019-gps.csv.zip LifeTrack White Stork Rheinland-Pfalz_2015-2019-acceleration-1of2.csv.zip LifeTrack White Stork Rheinland-Pfalz_2015-2019-acceleration-2of2.csv.zip LifeTrack White Stork Rheinland-Pfalz_2015-2019-reference-data.csv Data package citation: Fiedler W, Hilsendegen C, Reis C, Lehmann J, Hilsendegen P, Schmid H, Wikelski M (2019) Data from: Study "LifeTrack White Stork Rheinland-Pfalz" (2015-2019). Movebank Data Repository. https://doi.org/10.5441/001/1.4192t2j4 These data are described in the following written publication: Cheng Y, Fiedler W, Wikelski M, Flack A (2019) "Closer-to-home" strategy benefits juvenile survival in a long-distance migratory bird. Ecology and Evolution. https://doi.org/10.1002/ece3.5395 Individuals from this dataset used in the analysis of Cheng et al. (2019) are listed below. ----------- 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 comments: Additional information about the animal that is not described by other reference data terms. example: sibling of #1423 animal death comments: Comments about the death of the animal. example: hit by a car animal exact date of birth: The exact date on which animal was born. example: 2001-10-31 00:00:00.000 format: yyyy-MM-dd HH:mm:ss.sss units: if time is not included, day is determined by local time; if time is included, times are in UTC 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 is sometimes shown. example: 91876A, Gary same as: individual local identifier animal latest date born: The latest date an animal is thought to have been born. example: 2001-12-12 00:00:00.000 formats: yyyy-MM-dd HH:mm:ss.sss units: if time is not included, day is determined by local time; if time is included, times are in UTC 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 animal mass: The mass of an the animal, typically at the beginning of the deployment. example: 500 units: grams animal nickname: An alternate identifier for the animal. Used as the display name for animals shown in the Animal Tracker App. example: Ali animal ring ID: A number or color scheme for a band or ring attached to the animal. example: 26225 units: none animal sex: The sex of the animal. Allowed values are m: male f: female 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 same as: species, 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) same as: animal taxon detail 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 deploy off person: The name of the person/people who removed the tag from the animal and ended the deployment. example: J. Smith 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, which is a few leap seconds different from UTC 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 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, which is a few leap seconds different from UTC 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 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. 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. 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 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) 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 e-obs 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 e-obs 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: hertz (Hz) e-obs 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 e-obs 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 e-obs acceleration sampling frequency per axis starting with the first sample at the time described in 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 e-obs battery voltage: Unloaded battery voltage (definition from Franz Kümmeth, e-obs Digital Telemetry, personal communication, 2012). example: 3712 units: millivolt (mV) e-obs 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 Kümmeth, e-obs Digital Telemetry, personal communication, 2012). example: 3535 units: millivolt (mV) e-obs 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 Kümmeth, e-obs Digital Telemetry, personal communication, 2012). example: 35.07 units: meters e-obs 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 e-obs 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 Kümmeth, e-obs Digital Telemetry, personal communication, 2012). example: 6.58 units: meters per second e-obs 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 units: GPS time (GPST), which is a few leap seconds different from UTC e-obs 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 example: D units: none e-obs temperature: Temperature; this value is not calibrated and therefore very inaccurate (definition from e-obs Digital Telemetry Manual for DataDecoder Software, 2010). example: 45 units: degrees Celsius e-obs 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 2 = 2D fix example: 3 units: none e-obs 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 ground speed: The estimated ground speed provided by the sensor or calculated between consecutive locations. example: 7.22 units: meters per second 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 height above ellipsoid: The estimated height above the ellipsoid returned by the tag. (If altitudes are calculated as height above mean sea level, use height above mean sea level.) example: 24.8 units: meters location lat: 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 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 same as: location long manipulation comments: Additional comments about the way in which the animal was manipulated during the deployment. Use manipulation type to define the general type of manipulation. example: Relocated from breeding colony on Smithers Island to release location at 70.02E, 21.21S 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. 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. 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). study name: The name of the study in Movebank. 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 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 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 same as: tag local identifier tag manufacturer name: The company or person that produced the tag. example: Holohil tag mass: The mass of the tag. example: 24 units: grams tag model: The model of the tag. example: T61 tag production date: The approximate date the tag was produced (can be a year, month, or day). example: March 2011 units: undefined 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. tag serial number: The serial number of the tag. example: MN93-33243 units: none same as: tag serial no 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 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 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. THIS DATASET: This study contains a large number of records with duplicate tag and timestamp due to data obtained both through GSM and (more complete) records sometimes also downloaded from base stations. These duplicates were flagged as outliers (manually-marked-outlier = TRUE), with a preference for retaining the more complete record. These flagged duplicates along with a small number of other marked outliers are excluded from the published data files. ----------- Individuals from this dataset used in the analysis of Cheng et al. (2019) local_identifier hatching.rank survival.days Voyager I + / DER AW182 (eobs 4346) NA 228 Süwe I + / DER AT242 (eobs 4347) 4 36 Ede + / DER AT243 (eobs4348) 2 52 Borni + / DER AT244 (eobs 4349) 1 220 Vroni +/ DER AT245 (eobs 4350) 3 234 Fuchur + / DER AT203 (eobs 4351) 2 76 Johannes + / DER AT247 (eobs 4353) 2 43 Odysseus / DER AT248 (eobs 4354) 3 213 Felix + / DER AT249 (eobs 4355) 1 229 Otto I + / DER AT250 (eobs 4356) 2 22 Mercedes + / DER AT252 (eobs 4358) 1 105 Rhenus + / DER AT070 (eobs 4359) 1 62 Utes + / DER AT071 (eobs 3086) 2 24 Adios + / DER AT069 (eobs 3087) 3 245 Jünter + / DER AX006 (eobs 4361) 2 57 Paul I + / DER AX007 (eobs 4362) 1 54 Siggi + / DER AX001 (eobs 4363) 1 51 Cosima + / DER AX002 (eobs 4364) 2 51 Dirgni +/ DER AX003 (eobs 4365) 3 81 Emma + / DER AV742 (eobs 4367) 1 32 Lieselotte + / DER AV743 (eobs 4368) 3 133 Victor II + / DER AX381 (eobs 4345) 2 46 Voyager II + / DER AX382 (eobs 4346) 3 200 Marieta / DER AX383 (eobs4353) 1 219 Maximilian + / DER AX141 (eobs4361) 2 229 Adebar / DER AX142 (eobs 4360) 1 235 Jona + / DER AX144 (eobs3086) 3 12 Rudi / DER AX145 (eobs 4986) 2 224 Andra II + / DER AX146 (eobs 4351) 1 57 Victoria + / DER AX150 (eobs3945) 1 54 Henning + / DER AV846 (eobs 4984) 1 178 Sylvia + / DER AV847 (eobs 4367) 3 177 Kurt + / DER AV848 (eobs4368) 2 234 Enaitsirhc / DER AN444 (eobs 4363) NA 254 Nimrip / DER AN443 (eobs 4364) NA 255 Peter + / DER AX367 (eobs 4983) 1 235 Otto II + / DER AX386 (eobs 4356) 1 53 The Rose / DER AW244 (eobs 4359) 2 237 Sommerwind + / DER AW242 (eobs 4357) 1 32 Chrisi + / DER AX388 (eobs 4706) 1 55 SÜWE II / DER AW256 (eobs 4347) NA 179 Daisy + / DER AW257 (eobs 4558) 1 159 Borni II / DER AX351 (eobs 3076) 1 224 Yvonne + / AX444 (eobs 4362) NA 18 Tungdil + / DER A1Y01 (eobs 4357) NA 207 Hedwig + / DER A1Y00 (eobs 3041) NA 30 Lissy + / DER A1Y02 (eobs 3055) 3 104 Süwe III + / DER AX689 (eobs 4347) 2 65 Maxi / DER AX688 (eobs 5524) 1 237 Borni III + / DER A1Y17 (eobs 4349) 2 59 Gerhard + / DER A1Y18 (eobs 3999) 1 49 Hannes II + / DER AX273 (eobs 5526) 1 47 Jockel / DER AX274 (eobs 5527) 2 225 Alexa + / DER AX629 (eobs 4355) 1 171 Vinzenza + / DER AX630 (eobs 5525) 2 94 Nicole / DER AX555 (eobs 3020) NA 230 ----------- 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.