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 "Vultures Acopian Center USA 2003-2016" (Movebank Study ID 217784323). 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: Vultures Acopian Center USA 2003-2016.csv Vultures Acopian Center USA 2003-2016-reference-data.csv This data package represents the data collected by an ongoing project managed in the Movebank study "Turkey Vulture Acopian Center USA GPS" (Movebank Study ID 481458) and includes all GPS data collected in this study to December 8, 2016. A smaller portion of these data were previously published with DOI 10.5441/001/1.46ft1k05 and are described in Dodge et al. (2014). Portions of these data are described in the following written publications: Graña Grilli M, Lambertucci SA, Therrien J-F, Bildstein KL (2016) Wing size but not wing shape is related to migratory behavior in a soaring bird. Journal of Avian Biology 47: 1–10. doi:10.1111/jav.01220 Dodge S, Bohrer G, Bildstein K, Davidson SC, Weinzierl R, Mechard MJ, Barber D, Kays R, Brandes D, Han J (2014) Environmental drivers of variability in the movement ecology of turkey vultures (Cathartes aura) in North and South America. Philosophical Transactions of the Royal Society B 20130195. doi:10.1098/rstb.2013.0195 Portions of the data used for each analysis are described in the reference data file under "deployment comments". For analysis in Graña Grilli et al. (2016), all the parameters of migration were calculated from day to day data. To this end we filtered the data to keep one record per day during the whole migration, which was defined as described in Materials and Methods. The first record after 03:00 h was kept and then, daily distance and speed was calculated. Outliers were identified through visual inspection of the data. The data published here include all data records, not filtered to one per day. Data package citation: Bildstein KL, Barber D, Bechard MJ, Graña Grilli M (2016) Data from: Wing size but not wing shape is related to migratory behavior in a soaring bird. Movebank Data Repository. doi:10.5441/001/1.37r2b884 ----------- 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. algorithm marked outlier: Identifies events marked as outliers using a user-selected filter algorithm in Movebank. Outliers have the value TRUE. THIS DATASET: Marked outliers are intended to remove extreme outliers and are the result of running the Movebank General Purpose Data Filters with settings to (1) flag duplicate records based on Tag ID and Timestamp and (2) filter by speed using the Valid Anchor method, max. plausible speed = 30 m/s, and max. location error = 100 m (read more at www.movebank.org/node/27252). Maximum plausible speed is based on 109 km/h used in the analysis described in Dodge (et al.) 2014. 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 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 mass: The mass of an the animal. example: 500 units: grams 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 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 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 (Coordinated Universal Time) 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: This deployment was excluded from analysis because the tag failed. 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. 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 GPS HDOP: Horizontal dilution of precision provided by the GPS. example: 1.2 units: unitless GPS satellite count: The number of GPS satellites used to estimate the location. example: 8 units: none GPS time to fix: The time required to obtain the GPS location fix. example: 36 units: seconds GPS VDOP: Vertical dilution of precision provided by the GPS. example: 1.9 units: unitless ground speed: The estimated ground speed between consecutive locations. example: 7.22 units: meters per second heading: The direction in which the tag moved from this location to the subsequent location, calculated as the bearing between consecutive locations, in decimal degrees clockwise from north; for example, 0 = north, 90 = east, 180 = south. example: 315.88 units: decimal degrees height above ellipsoid: The estimated height above the ellipsoid returned by the GPS unit. (If altitudes are calculated as height above mean sea level, use height above mean sea level.) example: 24.8 units: meters height raw: Raw values for the height of the tag above ellipsoid or mean sea level provided by the tag. Values are stored as raw text values because non-numeric characters are used or processing is required to derive the correct height estimate. example: 425, 2D fix units: undefined 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 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. location error text: An estimate of the horizontal error of the location estimate, typically provided in the original data file, described using more than numbers. Units should be provided in the values. (If the values are purely numerical, use location error numerical.) These values can be described using location error percentile and location accuracy comments. example: > 25 ft units: defined in the values 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. manually marked outlier: An event marked manually as an outlier, typically using the Event Editor in Movebank. Allowed values are TRUE or FALSE. raptor workshop: migration state: Migration states used for analysis as part of the Movebank raptor workshop in Hawk Mountain, USA, February 2009. Values are chosen from a controlled list: breeding grounds: In the breeding grounds. fall migration: On fall migration. migration: On a seasonal migration. natal area: In the area where the animal was born. non-breeding grounds: In the non-breeding grounds, i.e. wintering grounds. spring migration: On spring migration. stopover: In a stopover site during a migration. summer non-breeding: In a summer non-breeding grounds. 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 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 production date: The approximate date the tag was produced (can be a year, month, or day). example: March 2011 units: none specified 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, serial no 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 taxon detail: A more specific name and/or reference for the taxon name provided by the taxon term. This can be used, for example, to specify a subspecies or other taxonomic category not supported by the ITIS. example: Calonectris diomedea borealis (Cory, 1881) same as: animal taxon detail 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 vertical error numerical: An estimate of the vertical error of the location. These values can be described using location error percentile and location accuracy comments. example: 112 units: m 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.