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 "Spatial ecology of urban copperheads" (Movebank Study ID 1199929756). 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: Spatial ecology of urban copperheads.csv Spatial ecology of urban copperheads-reference-data.csv AllCapturesData.csv DerivedMovementMetricsData.csv MorphologyData.csv SocialData.csv A portion of this dataset was previously published with DOI 10.5441/001/1.3v106n1n. Data package citation: Carrasco-Harris MF, Cole JA, Reichling S. 2020. Data from: Cozy in the city: the morphology and spatial ecology of copperheads in an urban forest. Movebank Data Repository. https://doi.org/10.5441/001/1.1rs3j824 These data are described in the following written publications: Carrasco-Harris MF, Cole JA, Reichling S. 2020. Cozy in the city: the morphology and spatial ecology of copperheads in an urban forest. Urban Naturalist. 35:1-19. https://eaglehill.us/URNAonline2/access-pages/035-Carrasco-Harris-accesspage.shtml Carrasco-Harris MF, Bowman D, Reichling S, Cole JA. 2020. Spatial ecology of copperhead snakes (Agkistrodon contortrix) in response to urban park trails. J Urban Ecol. 6(1):juaa007. https://www.doi.org/10.1093/jue/juaa007 ----------- 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 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 mass: The mass of the animal, typically at the beginning of the deployment. example: 500 units: grams 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 u = unknown 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 latitude: The geographic latitude of the location where the animal was released (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data). example: 27.3516 units: decimal degrees, WGS84 reference system entity described: deployment deploy on longitude: The geographic longitude of the location where the animal was released (intended primarily for instances in which the animal release and tag retrieval locations have higher accuracy than those derived from sensor data). example: -97.3321 units: decimal degrees, WGS84 reference system entity described: deployment 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 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 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 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 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 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 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 tag beacon frequency: The frequency of the radio tag or tag retrieval beacon. example: 450.5 units: MHz entity described: tag 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 mass: The mass of the tag. example: 24 units: grams 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 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 THIS DATASET: Values are the temperature and relative humidity, separated by ":", recorded using a psychrometer (Temperature Pen 800012, Sper Scientific, Scottsdale, AZ). 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 ----------- File AllCapturesData.csv These definitions are specific to this original data file from the author. This file contains information on all the captured animals (including those not relocated using telemetry). catch-number: Number for the capture. animal-id: Same as above. date: Date in format mm/dd/yyyy in local time (CST/CDT) time: Time of the capture in HH:mm local time (CST/CDT) animal-sex: Same as above. animal-reproductive-condition: Same as above. GF = gravid female, M = male, NA = unknown, NGF = non-gravid female animal-mass: Same as above. snout-vent-length: The snout-to-vent length in cm animal-reproductive-condition-raw: Notes on reproductive status for females study-site: Same as above temperature: Temperature (in degrees C) at the site measured using a psychrometer. percent-humidity: Relative humidity at the site measured using a psychrometer. capture-type: OUT or TRAP ----------- File DerivedMovementMetricsData.csv These definitions are specific to this original data file from the author. This file contains calculated movement metrics based off the movement data. animal-id: Same as above. total_distance: Total distanced moved in meters over the length of time subject tracked daily_movement: Daily movement in meters is the summation of the distance between relocations divided by the number of days the animal was observed. relocation-number: Number of relocations per each animal (i.e. 58 relocations used for snake ID_4187) mean-movement-sampling: summation of hte distance between relocations divided by the number of observations mcp_100: Minimum convex polygon 100% kud_95: kernel density estimator utilization distribution 95% kud_50: kernel density estimator utilization distribution 50% locoh_95: local convex hull 95% locoh_50: local convex hull 50% study-site: Same as above. animal-sex: Same as above. animal-reproductive-condition: Same as above. year: The year of the study (yy). ----------- File MorphologyData.csv These definitions are specific to this original data file from the author. This file contains morphology data for all non-gravid females and males (including those not relocated using telemetry). animal-id: Same as above. date: Same as above. animal-reproductive-condition: Same as above. animal-mass: Same as above. snout-vent-length: The snout-to-vent length in cm scaled-mass-index: a standardized mass body condition indicator study-site: Same as above. ----------- File SocialData.csv These definitions are specific to this original data file from the author. This file contains relocations during which the snake was with conspecifics. animal-id: Same as above. animal-sex: Same as above. animal-reproductive-condition: Same as above. date-time: Date and time in format mm/dd/yyyy hh:mm in local time (CST/CDT) location-lat: Same as above. location-long: Same as above. conspecific-sex: The sex of the conspecific/s present. conspecific-number: The number of conspecifics present. study-site: Same as above. notes: Additional notes. ----------- More Information For more information about this repository, see www.movebank.org/cms/movebank-content/data-repository, the FAQ at www.movebank.org/cms/movebank-content/data-repository-faq, or contact us at support@movebank.org.