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 "Barn Owl Breeding Napa Valley, California" (Movebank Study ID 1426277950). 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: Barn Owl Breeding Napa Valley California.csv Barn Owl Breeding Napa Valley California-reference-data.csv Data package citation: Huysman AE, CastaƱeda XA, Johnson MDData from: Habitat selection by a predator of rodent pests is resilient to wildfire in a vineyard agroecosystem. Movebank Data Repository. https://doi.org/10.5441/001/1.82b5h1rk These data are described in the following written publications: Huysman AE, Johnson MD. 2021. Habitat selection by a predator of rodent pests is resilient to wildfire in a vineyard agroecosystem. Ecol Evol. https://doi.org/10.1002/ece3.8416 CastaƱeda XA, Huysman AE, Johnson MD. 2021. Barn Owls select uncultivated habitats for hunting in a winegrape growing region of California. Ornithol Appl. 123(1):duaa058. https://doi.org/10.1093/ornithapp/duaa058 A version of the 2016 portion of this dataset is published as the following data package: Johnson M. 2021. Data from: Barn Owls select uncultivated habitats for hunting in a winegrape growing region of California. Dryad. https://doi.org/10.5061/dryad.mpg4f4qx0 ----------- 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. animal comments: Additional information about the animal that is not described by other reference data terms. example: sibling of #1423 units: none entity described: individual link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000012 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 mass: The mass of the animal, typically at the beginning of the deployment. example: 500 units: grams entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000019 animal reproductive condition: The reproductive condition of the animal at the beginning of the deployment. example: lactating units: none entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000021 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 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 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 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 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 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 units: none entity described: deployment link: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000154 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 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 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.