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 "GPS tracking of eastern whip-poor-will" (Movebank Study ID 1895314026). 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: GPS tracking of eastern whip-poor-will.csv GPS tracking of eastern whip-poor-will-reference-data.csv Data package citation: Skinner AA, Ward MP, Souza-Cole I, Wright JR, Thompson FR, Benson TJ, Matthews SN, Tonra CM. 2023. Data from: Study "GPS tracking of eastern whip-poor-will". Movebank Data Repository. https://doi.org/10.5441/001/1.k6s7916g These data are described in the following written publications: Skinner AA, Ward MP, Souza-Cole I, Wright JR, Thompson FR, III, Benson TJ, Matthews SN, Tonra CM. 2022. High spatiotemporal overlap in the non-breeding season despite geographically dispersed breeding locations in the eastern whip-poor-will (Antrostomus vociferus). Divers Distrib. 28(4):712–726. https://doi.org/10.1111/ddi.13477 Skinner AA, Matthews SN, Ward MP, Souza-Cole I, Wright JR, Thompson FR III, Benson TJ, Tonra CM. 2022. Eastern Whip-poor-wills have larger nonbreeding home ranges in areas with more agriculture and forest fragmentation. Ornithol Appl. duac050. https://doi.org/10.1093/ornithapp/duac050 This dataset contains data that overlap with those published as Tonra CM, Wright JR, Matthews SN. 2021. Data from: Remote estimation of overwintering home ranges in an elusive migratory nocturnal bird. Movebank Data Repository. https://doi.org/10.5441/001/1.6v110sv8 Also see Skinner A. 2022. Data from: High spatiotemporal overlap in the non-breeding season despite geographically dispersed breeding locations in the eastern whip-poor-will (Antrostomus vociferus). Dryad, Dataset. https://doi.org/10.5061/dryad.hhmgqnkh9 ----------- 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. algorithm marked outlier: Identifies events marked as outliers using a user-selected filter algorithm in Movebank. Outliers have the value TRUE. units: none entity described: event link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000011 THIS DATASET: The value range filter in Movebank was run in February 2022 with settings to flag records with "GPS HDOP" => 20, retaining records with null values in this field. 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000016 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000018 animal ring ID: A number or color scheme for a band or ring attached to the animal. example: 26225 units: none entity described: individual link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000022 animal sex: The sex of the animal. Allowed values are m = male f = female u = unknown format: controlled list entity described: individual link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000023 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' format: controlled list entity described: individual same as: individual taxon canonical name link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000024 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 fin mount = The tag is attached to the animal's fin 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000052 behaviour according to: A description of behavioral categories contained in the event data and/or how they were derived. example: Behavior was derived using acceleration data and an automated algorithm calibrated using field observations. units: none entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000066 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000067 THIS DATASET: See "behaviour according to". Classification of points depending on what the bird was likely doing when the point was taken. Abbreviations are as follows (alphabetical order): B1 = first breeding, B2 = second breeding (if a bird returned to breeding site the following spring), Day = a roosting point taken during the day, Day2 = a roosting point taken during the day at the second wintering site, FM = fall migration, LFW = looking for first winter location (see Skinner et al. 2022, doi: 10.1111/ddi.13477, Appendix S2), LFW-2 = looking for second winter location, rm = remove (1 tag was sent to Lotek for help with data extraction, but the data did not seem trustworthy, so many points were removed), SM = spring migration, SM.stop1 = first stopover on spring migration, SM.stop2 = second stopover on spring migration, Stop1 = first stopover, Stop2 = second stopover, UNK.XXXX = if a GPS fix was missing between a change in "season" (e.g., UNK.FMW1 = a missing data point between FM and W1), W1 = first wintering site, W2 = second wintering site. deploy off timestamp: The timestamp when the tag deployment ended, as defined by the data owner. 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 link: 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 link: 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000079 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000081 deployment comments: Additional information about the tag deployment that is not described by other reference data terms. example: body length 154 cm; condition good units: none entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000082 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 entity described: deployment link: 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-Tag42 units: none entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000085 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000103 GPS HDOP: Horizontal dilution of precision provided by the GPS. example: 1.2 units: unitless entity described: event link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000118 GPS satellite count: The number of GPS satellites used to estimate the location. example: 8 units: none entity described: event link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000120 habitat: A category or description of the habitat. Information about how the values were obtained can be provided using 'habitat according to'. example: oak savannah units: none entity described: event link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000127 habitat according to: A description of habitat categories contained in the event data, how they were derived and/or a reference to indicate which habitat classification system was used. example: visual analysis using 2018 satellite imagery units: none entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000128 height above ellipsoid: The estimated height above the ellipsoid, typically estimated by the tag. If altitudes are calculated as height above mean sea level, use 'height above mean sea level'. example: 24.8 units: meters entity described: event link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000130 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 link: 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000146 manipulation type: The way in which the animal was manipulated during the deployment. Additional information 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 format: controlled list entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000155 manually marked outlier: Identifies events flagged manually as outliers, typically using the Event Editor in Movebank, and may also include outliers identified using other methods. Outliers have the value TRUE. units: none entity described: event link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000156 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 uses Argos Doppler shift to determine location 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 transmits a radio signal that is detected by receivers to determine location 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000170 study name: The name of the study in Movebank. example: Coyotes, Kays and Bogan, Albany NY units: none entity described: study (event) link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000173 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000175 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000181 tag manufacturer name: The company or person that produced the tag. example: Holohil units: none entity described: tag link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000183 tag mass: The mass of the tag. example: 24 units: grams entity described: tag link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000184 tag model: The model of the tag. example: T61 units: none entity described: tag link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000185 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000188 tag tech spec: Values for a tag-specific technical specification. Can be used to store measurements not described by existing Movebank attributes. Best practice is to define the values and units in the reference data or study details. example: 8.31 units: not defined entity described: event link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000190 THIS DATASET: Values represent "eRes" A secondary measurement of the accuracy of a given point generated by Lotek. Note that HDOP performed better in predicting the accuracy of our points from calibration data. 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 link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000200 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 link: 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.