README This data file is published by the Movebank Data Repository (www.datarepository.movebank.org). As of the time of publication, a version of the published animal tracking data set can be viewed on Movebank (www.movebank.org) in the study "Foraging behaviour and fuel accumulation of pink-footed geese (data from Chudzińska et al. 2016)" (Movebank Study ID 49535504). 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: Foraging behaviour and fuel accumulation of pink-footed geese (data from Chudzińska et al. 2016)-argos.csv Foraging behaviour and fuel accumulation of pink-footed geese (data from Chudzińska et al. 2016)-gps.csv Foraging behaviour and fuel accumulation of pink-footed geese (data from Chudzińska et al. 2016)-reference-data.csv These data are described in the following written publications: Chudzinska ME, Nabe-Nielsen J, Nolet BA, Madsen J (2016) Foraging behaviour and fuel accumulation of capital breeders during spring migration as derived from a combination of satellite-and ground-based observations. Journal of Avian Biology. doi: 10.1111/jav.00899 Hans JMB, Bergjord A-K, Bjerke JW, Chudzińska ME, Pellissier L, Simonsen CE, Madsen J, Tombre IM, Nolet BA (under review) Combining modelling tools to evaluate a regional goose management scheme: designating a sufficiently large refuge area at the best location. Data package citation Chudzinska ME, Madsen J (2016) Data from: Foraging behaviour and fuel accumulation of capital breeders during spring migration as derived from a combination of satellite-and ground-based observations. Journal of Avian Biology. Movebank Data Repository. doi:10.5441/001/1.s9s86319 ----------- 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 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 mass: The mass of an the animal. example: 500 units: grams Argos latitude 1: Solution 1. platform latitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 19.493 units: decimal degrees, WGS84 reference system same as: Argos lat1 Argos latitude 2: Solution 2. platform latitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 14.773 units: decimal degrees, WGS84 reference system same as: Argos lat2 Argos location class: The location class retrieved from Argos. Allowed values are 0, 1, 2, 3, A, B, and Z (definition from Argos User's Manual 2011). example: A units: none same as: Argos lc Argos longitude 1: Solution 1. platform longitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 99.712 units: decimal degrees, WGS84 reference system same as: Argos lon1 Argos longitude 2: Solution 2. platform longitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 120.286 units: decimal degrees, WGS84 reference system same as: Argos lon2 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 event comments: Additional information about individual records or events in a data set that is not described by other reference data terms. example: we observed the animal foraging (see photo BT25) same as: comments THIS DATASET: Local time (hh:mm) 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 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 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. 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. 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 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 latitude (UTM): The geographic longitude of the geographic center of a location along an animal track as estimated by the processed sensor data. example: 3628361.84012295 units: meters, WGS84 reference system same as: utm northing 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. 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 longitude (UTM): The geographic longitude of the geographic center of a location along an animal track as estimated by the processed sensor data. example: 756243.7836 units: meters, WGS84 reference system same as: utm easting 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. ring ID: A number or color scheme for a band or ring attached to the animal. example: 26225 units: none same as: animal ring id sensor type: The type of sensor with which data were collected. Values are chosen from a controlled list: Argos Doppler Shift: The sensor is using Argos Doppler shift for determining position. GPS: The sensor uses GPS to find location and stores these. solar geolocator: The sensor uses measure for sunset and sunrise for determining position. radio transmitter: The sensor is a classical radio transmitter. bird ring: The animal is identified by a ring that has a unique ID. natural mark: The animal is identified by a natural marking. acceleration: The sensor collects acceleration data. other: The sensor is a type other than those described above. sex: The sex of the biological individual(s) represented in the Occurrence. Values are from a controlled list: m: male f: female study: The name of the study in Movebank in which data are stored. 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: Anser brachyrhynchus 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. ----------- 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.