README This data package 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 "Red Knot geolocator tracking New Zealand 2013" (Movebank Study ID 3389607769). 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: Red Knot geolocator tracking New Zealand 2013-light-levels.csv Red Knot geolocator tracking New Zealand 2013-tracks.csv Red Knot geolocator tracking New Zealand 2013-twilights.csv Red Knot geolocator tracking New Zealand 2013-reference-data.csv Data package citation: Battley PF, Lisovski S, Conklin JR. 2024. Data from: Study "Red Knot geolocator tracking New Zealand 2013". Movebank Data Repository. https://doi.org/10.5441/001/1.328 These data are described in the following written publication: Lisovski S, Hoye BJ, Conklin JR, Battley PF, Fuller RA, Gosbell KB, Klaassen M, Lee CB, Murray NJ, Bauer S. 2024. Predicting resilience of migratory birds to environmental change. Proc Natl Acad Sci USA. 121(19): e2311146121. https://doi.org/10.1073/pnas.2311146121 ----------- Terms of Use As of the time of publication, this data package is licensed by the Creative Commons Attribution (CC-BY) license: https://creativecommons.org/licenses/by/4.0/ View the data package online for the current license. Works published with this license should 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 about these data and expectations for use, see the General Movebank Terms of Use (movebank.org/cms/movebank-content/general-movebank-terms-of-use) and 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. Values are unique within the study. If the data owner does not provide an Animal ID, an internal Movebank animal identifier is sometimes shown. Example: TUSC_CV5 Units: none Entity described: individual Same as: individual local identifier URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000016 animal ring ID: A number or color scheme for a band or ring attached to the animal. Color bands and other markings can be stored in 'animal marker ID'. Example: 26225 Units: none Entity described: individual URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000022 animal taxon: The scientific name of the taxon on which the tag was deployed, as defined by the Integrated Taxonomic Information System (ITIS). 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'. The values 'test' and 'calibration' identify events relevant to animal tracking studies that should not be associated with a taxon. Format: controlled list Entity described: individual Same as: individual taxon canonical name URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000024 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000025 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000073 deploy off latitude: The geographic latitude of the location where the deployment ended. Intended primarily for cases in which the recapture, tag retrieval or other final location has higher accuracy than that derived from sensor data. Example: -38.6866 Units: decimal degrees, WGS84 reference system Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000074 deploy off longitude: The geographic longitude of the location where the deployment ended. Intended primarily for cases in which the recapture, tag retrieval or other final location has higher accuracy than that derived from sensor data. Example: 146.3104 Units: decimal degrees, WGS84 reference system Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000075 deploy off timestamp: The timestamp when the tag deployment ended. Data records recorded after this day and time are not associated with the animal related to the deployment. Values are typically defined by the data owner, and in some cases are created automatically during data import. Further information can be provided in 'deployment end type' and 'deployment end comments'. 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000077 deploy on latitude: The geographic latitude of the location where the animal was released. Intended primarily for cases in which the animal release location has higher accuracy than that derived from sensor data. Example: 27.3516 Units: decimal degrees, WGS84 reference system Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000078 deploy on longitude: The geographic longitude of the location where the animal was released. Intended primarily for cases in which the animal release location has higher accuracy than that derived from sensor data. Example: -97.3321 Units: decimal degrees, WGS84 reference system Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000079 deploy on timestamp: The timestamp when the tag deployment started. Data records recorded before this day and time are not associated with the animal related to the deployment. Values are typically defined by the data owner, and in some cases are created automatically during data import. 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000081 deployment end type: A categorical classification describing the end of the tag deployment on the animal. Best practice is to clarify how the 'deploy-off timestamp', if present, was chosen. Values are chosen from a controlled list: analysis-end = the end time represents the end of the period of interest; 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; dead/fall-off = The tag stopped moving, and it is not possible to determine whether it is due to death of the animal or unscheduled tag detachment; 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; scheduled-detachment = The tag was programmed to detach from the animal; transmission-end = The tag stopped transmitting usable data; unknown = The cause of the end of data availability or transmission is unknown. Format: controlled list Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000084 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_42818 Units: none Entity described: deployment Same as: deployment local identifier URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000085 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 or GPS time Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000102 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: 14328243575 Units: none Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000103 geolocator light threshold: The light threshold used for location estimation with solar geolocators. Range and units may vary by provider and tag settings. Example: 16 Units: not defined Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000108 geolocator rise: The period of day used to estimate location by geolocation. TRUE = sunrise, FALSE = sunset. Units: none Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000215 geolocator twilight3: The date and time of twilight detected by automated processing. Example: 2008-08-14 18:31:00.000 Format: yyyy-MM-dd HH:mm:ss.SSS Units: UTC or GPS time Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000216 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000136 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000137 light level: Light-level values measured by a solar geolocator. Range and units may vary by provider and tag settings. Best practice is to define values in the reference data. Example: 28 Units: not defined Entity described: event Same as: gls light level URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000139 location accuracy comments: Comments about the location accuracy. This can further describe 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000141 location lat: The geographic latitude of the location as estimated by the sensor. Example: -41.0982423 Units: decimal degrees, WGS84 reference system Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000145 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000146 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000147 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000148 manipulation type: The way in which the animal was manipulated during the deployment. Additional information can be provided using 'manipulation comments'. Changes in manipulation status during deployment can be identified using 'manipulation status'. Values are chosen from a controlled list: confined = The animal's movement was restricted to within a defined area; domesticated = The animal is domesticated, for example, is a house pet or part of a managed herd; manipulated-other = The animal was manipulated in some other way, such as a physiological manipulation; none = The animal received no treatment other than tag attachment and related measurements and sampling (if applicable); reintroduction = The animal has been reintroduced as part of wildlife conservation or management efforts; relocated = The animal was released from a site other than the one at which it was captured. Format: controlled list Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000155 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; acoustic-telemetry = The sensor transmits an acoustic signal that is detected by receivers to determine location; argos-doppler-shift = The sensor location is estimated by Argos using Doppler shift; atlas-geolocation = The sensor location is estimated by an ATLAS system; barometer = The sensor records air or water pressure; bird-ring = The animal is identified by a band or ring that has a unique identifier; derived = Information is derived from other sensor data; geolocation-api = The location is determined based on detection by nearby cell towers or other wireless network connectors using the World Wide Web Consortium Geolocation API Recommendation; gnss = The sensor uses one or more global navigation satellite systems to determine location; gps = The sensor uses GPS to determine location; gyroscope = The sensor records angular velocity; heart-rate = The sensor records or is used to calculate heart rate; 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; proximity = The sensor identifies proximity to other tags; radio-transmitter = The sensor transmits a radio signal that is detected by receivers to determine location; sigfox-geolocation = The sensor location is determined by Sigfox using the received signal strength indicator; 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); tdr = The sensor is a time-depth recorder. Format: controlled list Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000170 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 or GPS time Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000171 study name: The name of the study in Movebank. Example: Coyotes, Kays and Bogan, Albany NY Units: none Entity described: study URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000173 study site: A location such as the deployment site, study site, or colony name. Example: Pickerel Island North Units: none Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000175 tag ID: An identifier for the tag, provided by the data owner. Values are unique within the study. 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000181 tag readout method: The way the data are received from the tag. Values are chosen from a controlled list: ISS = Data are transferred via the International Space Station; LPWAN = Data are transferred through a low-power wide-area network, such as LoRa or Sigfox; multiple = Data are acquired using multiple methods; none = Data are obtained without use of an animal-borne tag, such as by observing a unique marking; other-wireless = Data are transferred via another form of wireless data transfer, such as a VHF transmitter/receiver; phone-network = Data are transferred via a phone network, such as GSM or AMPS; satellite = Data are transferred via satellite; tag-retrieval = The tag must be physically retrieved in order to obtain the data; telemetry-network = Data are obtained through a radio or acoustic telemetry network; Wi-Fi/Bluetooth = Data are transferred via a local Wi-Fi or Bluetooth system. Format: controlled list Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000188 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000200 twilight: Identifies light-level measurements determined to represent twilight events. Typically 1 = sunrise, 2 = sunset, 0 = not twilight. Example: 2 Units: none Entity described: event Same as: gls twilight URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000113 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000242 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000243 visible: Determines whether an event is visible on the Movebank map. Allowed values are TRUE or FALSE. 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. Units: none Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000209 ----------- More Information For more information about this repository, see www.movebank.org/cms/movebank-content/data-repository, the FAQ at https://www.datarepository.movebank.org/faq, or contact us at support@movebank.org.