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 accuracy for small mammals (data from McMahon et al. 2017)" (Movebank Study ID 243688044). Individual attributes in the data files are defined below and in the Movebank Attribute Dictionary, available at www.movebank.org/node/2381. The Movebank-format data contain data for the GPS fixes paired with light sensor readings for tags deployed on study animals and for undeployed stationary tests of traditional GPS receivers under similar conditions. This data package includes the following data files: GPS accuracy for small mammals (data from McMahon et al. 2017).csv GPS accuracy for small mammals (data from McMahon et al. 2017)-reference-data.csv ConsistencyCheckLocations.csv This file contains the reference locations for consistency checks. FSR_animaltests.csv This file contains an overview of the GPS data collected from each animal in our study. RFdata_stattests.csv This file contains data for snapshot stationary tests. STTest_Veg.csv This file contains a description of site characteristics for each reference location. Tdata_stattests.csv This file contains data for traditional stationary tests. These data are described in the following written publication: McMahon LA, Rachlow JL, Shipley LA, Forbey JS, Johnson TR, Olsoy PJ (2017) Evaluation of micro-GPS receivers for tracking small-bodied mammals. PLoS ONE. doi:10.1371/journal.pone.0173185 Data package citation: McMahon LA, Rachlow JL, Shipley LA, Forbey JS (2017) Data from: Evaluation of micro-GPS receivers for tracking small-bodied mammals. Movebank Data Repository. doi:10.5441/001/1.b0g6rq1t ----------- 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. 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 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 event comments: Additional information about individual records or events in a data set that is not described by other reference data terms. example: we observed the animal foraging (see photo BT25) same as: comments THIS DATASET: Season 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 fix type: The type of GPS fix. 1 = no fix; 2 = 2D fix (altitude typically not valid); 3 = 3D fix (altitude typically valid). example: 3 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 height above mean sea level: The estimated height of the tag above mean sea level returned by the GPS unit. (If altitudes are calculated as height above an ellipsoid, use height above ellipsoid.) example: 34 units: meters same as: height above msl 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. light level: Light-level values measured by a solar geolocator. example: 28 units: undefined same as: gls:light level THIS DATASET: Light levels in lux location error numerical: An estimate of the horizontal error of the location including only numbers. (If the error estimates include non-numerical characters such as ">" use location error text.) These values can be described using location error percentile and location accuracy comments. example: 50 units: meters 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. 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 study-specific measurement: Values for a study-specific attribute. example: 1112:01 units: undefined THIS DATASET: 3 values per field, separated by ":" ID = order of fixes obtained Maxsnr = automatic GPS obtained information Angle = direction of GPS estimated location from the true location example: 201:0:86.16131174540 tag comments: Additional information about the tag that is not described by other reference data terms. example: custom-made Doppler shift Argos tag with a special altitude sensor 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 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 technical specification: Values for a tag-specific technical attribute. example: 8.31, YES units: undefined same as: tag tech. spec. THIS DATASET: Light sensor measurement interval (1 or 5 min) 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 sex: The sex of the biological individual(s) represented in the Occurrence. Values are from a controlled list: m: male f: female 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 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. ----------- Data Attributes for additional files. These definitions are specific to the original data files from the author. ConsistencyCheckLocations.csv Reference Location: Individual ID of reference location Northing_UTM_Nad83: UTM northing, Zone 11, NAD83 Easting_UTM_Nad83: UTM easting, Zone 11, NAD83 FSR_animaltests.csv RabbitID: unique rabbit ID Type: RF = Snapshot receivers; Trad = Traditional receivers Season: Season and year Sex: M/F LightSensor: 1 = Light sensor deployed at same time as GPS; 0 = no light sensor CollarStartDate: Date animal collared CollarRemoved: Date collar removed GPS_DeployedDuration: # days an animal was collared with a GPS GPS_End: date and time of last fix GPS_Duration: # days GPS collected data for ExpectedFixes: # Fixes expected for the GPS_Duration AcquiredFixes_All: # successful fixes acquired 3D_Fixes: # 3D fixes acquired FSR_All: # Acquired fixes/ Expected Fixes *100 FSR_3D: # 3D fixes/ Expected Fixes * 100 Predated: 1=Animal predated; 0 = animal lived Status_End: description of why GPS failed RFdata_stattests.csv Individual: Individual ID number for each stationary test Pair: Used to determine which GPS devices were ran at the same time at the same place Type: RF = Snapshot receivers; Trad = Traditional receivers Site: Stationary Test reference location GPSID: unique GPS ID DateTime_MTC: Mountain Time FixOrder: Order of fixes (1 = first fix in stationary test) SNR: Signal noise ratio HDOP: Horizontal dilution of precision VDOP: Vertical dilution of precision SVs_in_Use: # Satellites used to generate location Fix: Type of Fix LE: Location error (m). Distance between GPS estimated location and reference location Burrow: 0 = above ground; 1 = in burrow Success: 0 = no location estimated; 1 = successful location Success3D: 0 = no 3D fix estimated; 1 = 3D fix estimated BurrOrientation BurrEntrance STTest_Veg.csv Site: name of reference location X: Easting (UTM, NAD 27) Y: Northing (UTM, NAD 27) ACFish2015: Canopy Closure measured in 2015 with fish eye ACFish2016: Canopy Closure measured in 2016 with fish eye lens field_ShrubHt: Average shrub height 1 m surrounding the reference locations -- only measured shrubs > 8 cm UAVCan1: UAV derived canopy closure data 1 m (radius) around reference UAVCan6: UAV derived canopy closure data 6 m (radius) around reference UAVCan12.5: UAV derived canopy closure data 12.5 m (radius) around reference UAVCan25: UAV derived canopy closure data 25 m (radius) around reference UAV_ShrubHt1: UAV derived shrub height 1 m (radius) around reference UAV_ShrubHt6: UAV derived shrub height 6 m radius UAV_ShrubHt12.5: UAV derived shrub height 12.5 m radius UAV_ShruhHt25: UAV derived shrub height 25 m radius Volume1: Shrub voume 1 m around reference: used UAV height Volume 6: Shrub volume 6 m around reference Vol1_field: Shrub volume measured using shrub height from field measurements Tdata_stattests.csv Individual: Individual ID number for each stationary test Pair: Used to determine which GPS devices were ran at the same time at the same place Type: RF = Snapshot receivers; Trad = Traditional receivers Site: Stationary Test reference location GPSID: unique GPS ID DateTime_MTC: Mountain Time FixOrder: Order of fixes (1 = first fix in stationary test) TTF: Time to fix (seconds) SNR: Signal noise ratio HDOP: Horizontal dilution of precision SVs_in_Use: # Satellites used to generate location Fix: Type of Fix LE: Location error (m). Distance between GPS estimated location and reference location Burrow: 0 = above ground; 1 = in burrow Success: 0 = no location estimated; 1 = successful location Success3D: 0 = no 3D fix estimated; 1 = 3D fix estimated BurrOrientation BurrEntrance ----------- 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.