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 "Elk in southwestern Alberta" (Movebank Study ID 933711994). 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/node/2381. Metadata describing this data package are maintained at https://datacite.org. This data package includes the following data files: Elk in southwestern Alberta.csv Elk in southwestern Alberta-reference-data.csv Data package citation: Boyce MS, Ciuti S (2020) Data from: Human selection of elk behavioural traits in a landscape of fear. Movebank Data Repository. https://doi.org/10.5441/001/1.j484vk24 These data are described in the following written publications: Paton DG, Ciuti S, Quinn M, Boyce MS (2017) Hunting exacerbates the response to human disturbance in large herbivores while migrating through a road network. Ecosphere 8(6): e01841. https://doi.org/10.1002/ecs2.1841 Prokopenko CM, Boyce MS, Avgar T (2017) Characterizing wildlife behavioural responses to roads using integrated step selection analysis. Journal of Applied Ecology 54: 470-479. https://doi.org/10.1111/1365-2664.12768 Prokopenko CM, Boyce MS, Avgar T (2017) Extent-dependent habitat selection in a migratory large herbivore: road avoidance across scales. Landscape Ecology 32: 313-325. https://doi.org/10.1007/s10980-016-0451-1 Roberts DR et al. (2017) Cross-validation strategies for data with temporal, spatial, hierarchical, or phylogenetic structure. Ecography 40: 913-929. https://doi.org/10.1111/ecog.02881 Thurfjell H, Ciuti S, Boyce MS (2017) Learning from the mistakes of others: How female elk (Cervus elaphus) adjust behaviour with age to avoid hunters. PLoS ONE 12(6): e0178082. https://doi.org/10.1371/journal.pone.0178082 Benz RA, Boyce MS, Thurfjell H, Paton DG, Musiani M, Dormann CF, et al. (2016) Dispersal ecology informs design of large-scale wildlife corridors. PLoS ONE 11(9): e0162989. https://doi.org/10.1371/journal.pone.0162989 Ensing EP, Ciuti S, de Wijs FALM, Lentferink DH, ten Hoedt A, et al. (2014) GPS based daily activity patterns in European red deer and North American elk (Cervus elaphus): indication for a weak circadian clock in ungulates. PLoS ONE 9(9): e106997. https://doi.org/10.1371/journal.pone.0106997 Killeen J, Thurfjell H, Ciuti S, Paton D, Musiani M, Boyce MS (2014) Habitat selection during ungulate dispersal and exploratory movement at broad and fine scale with implications for conservation management. Movement Ecology 2:15. https://doi.org/10.1186/s40462-014-0015-4 Thurfjell H, Ciuti S, Boyce MS (2014) Applications of step-selection functions in ecology and conservation. Movement Ecology 2:4. https://doi.org/10.1186/2051-3933-2-4 Ciuti S, Muhly TB, Paton DG, McDevitt AD, Musiani M, Boyce MS (2012) Human selection of elk behavioural traits in a landscape of fear. Proc. R. Soc. B 279: 4407-4416. https://doi.org/10.1098/rspb.2012.1483 Ciuti S, Northrup JM, Muhly TB, Simi S, Musiani M, et al. (2012) Effects of humans on behaviour of wildlife exceed those of natural predators in a landscape of fear. PLoS ONE 7(11): e50611. https://doi.org/10.1371/journal.pone.0050611 ----------- 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 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 animal death comments: Comments about the death of the animal. example: hit by a car units: none entity described: individual 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 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 animal reproductive condition: The reproductive condition of the animal at the beginning of the deployment. example: lactating units: none entity described: deployment animal sex: The sex of the animal. Allowed values are m = male f = female format: controlled list entity described: individual 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'. example: Buteo swainsoni format: controlled list entity described: individual same as: individual taxon canonical name 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 animal tape = The tag is attached to the animal using tape other = user specified format: controlled list entity described: deployment comments: Additional information about events that is not described by other event data terms. example: we observed the animal foraging (see photo BT25) units: none entity described: event 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 or GPS time entity described: deployment same as: deploy off date 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 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 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 units: none entity described: deployment 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 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 external temperature: The temperature measured by the tag (different from ambient temperature or internal body temperature of the animal). example: 32.1 units: degrees Celsius entity described: event same as: temperature external GPS DOP: Dilution of precision provided by the GPS. example: 1.8 units: unitless entity described: event GPS fix type: The type of GPS fix. To import non-numeric characters use 'GPS fix type raw'. Allowed values are 1 = no fix 2 = 2D fix (altitude typically not valid) 3 = 3D fix (altitude typically valid) format: controlled list units: none entity described: event GPS satellite count: The number of GPS satellites used to estimate the location. example: 8 units: none entity described: event 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 location lat: 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: -41.0982423 units: decimal degrees, WGS84 reference system entity described: event 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 Lotek CRC status text: Cyclic Redundancy Check provided by Lotek (definition from '11884 PinPoint User Manual Rev 5.pdf', Lotek, personal correspondence 2018). Allowed values are OK = good data Fail = data has been corrupted on transmission, and therefore cannot be trusted OK(corrected) = the message was corrected with Lotek's error correction algorithm format: controlled list units: none entity described: event same as: Lot:CRC status text manipulation type: The way in which the animal was manipulated during the deployment. 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 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 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 Argos Doppler shift = The sensor uses Argos Doppler shift to determine position 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 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) 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 study name: The name of the study in Movebank. example: Coyotes, Kays and Bogan, Albany NY units: none entity described: study, event 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 tag manufacturer name: The company or person that produced the tag. example: Holohil units: none entity described: tag tag model: The model of the tag. example: T61 units: none entity described: tag 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 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 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 ----------- 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.