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 "Movements of free-ranging Maremma sheepdogs (data from Bommel and Johnson 2014)". 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: Movements of free-ranging Maremma sheepdogs (data from van Bommel and Johnson 2014).csv Movements of free-ranging Maremma sheepdogs (data from van Bommel and Johnson 2014)-reference data.csv tortuosity code from van Bommel and Johnson 2014.R These data are described in the following written publication: van Bommel L, Johnson CN (2014) Where do livestock guardian dogs go? Movement patterns of free-ranging Maremma sheepdogs. PLoS ONE 9(10), e111444. doi:10.1371/journal.pone.0111444 Data package citation van Bommel L, Johnson CN (2014) data from: Where do livestock guardian dogs go? Movement patterns of free-ranging Maremma sheepdogs: Movebank Data Repository. doi:10.5441/001/1.pv048q7v See below for additional information on attributes of the data files and instructions for running the R code. ----------- 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 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 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. animal reproductive condition: The reproductive condition of the animal at the beginning of the deployment. example: non-reproductive, pregnant 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 person: The name of the person/people who removed the tag from the animal and ended the deployment. example: J. Smith 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 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 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 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 latitude (UTM): The geographic longitude of the geographic center of a location along an animal track as estimated by the processed sensor data. example: 3628361.84012295 units: meters, WGS84 reference system same as: utm northing local timestamp: The date and time a sensor measurement was taken in the time zone of the study reference location. example: 2008-08-14 15:31:00.000 format: yyyy-MM-dd HH:mm:ss.sss units: specific to the study time zone same as: study local timestamp location accuracy comments: Comments about the location error estimate values provided using location error text and/or location error numerical. The percentile uncertainty can be provided using location error percentile. example: 1 standard deviation errors, assuming normal distribution, provided by the GPS unit 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 longitude (UTM): The geographic longitude of the geographic center of a location along an animal track as estimated by the processed sensor data. example: 756243.7836 units: meters, WGS84 reference system same as: utm easting 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 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. sensor type: The type of sensor with which data were collected. Values are chosen from a controlled list: Argos Doppler Shift: The sensor is using Argos Doppler shift for determining position. GPS: The sensor uses GPS to find location and stores these. solar geolocator: The sensor uses measure for sunset and sunrise for determining position. radio transmitter: The sensor is a classical radio transmitter. bird ring: The animal is identified by a ring that has a unique ID. natural mark: The animal is identified by a natural marking. acceleration: The sensor collects acceleration data. other: The sensor is a type other than those described above. sex: The sex of the biological individual(s) represented in the Occurrence. Values are from a controlled list: m: male f: female same as: animal-sex 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 time zone: The time zone at the study reference location. example: Mountain Standard Time units: none 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 voltage: The voltage as reported by the tag. example: 2895 units: millivolts (mV) 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 temperature external: The temperature measured by the tag (different from ambient temperature or internal body temperature of the animal). example: 32.1 units: degrees Celsius 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 UTM zone: The UTM zone, selected based on the location of each event, used to convert locations from decimal degrees to UTM. example: 14N units: none 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. ----------- Tortuosity code instructions Take the steps below to get your file ready to run through the r-code. ArcGIS can be used, but the Geospatial Modelling Environment is also very useful (freely available online). 1) Create a movement path out of all the GPS locations (so a file that consists of a single line going from point to point following the animal its relocations). 2) If you are measuring tortuosity in different zones (for example based on location in the home range, or within different vegetation types), cut your movement path up so that one path stops, and a new path starts, each time the animal crosses a boundary. Be careful that the tool you use to do this does not create one single path within each area; you want an X number of separate paths within each area, depending on how often the animal crossed into and out of this area. 3) The attribute table associated with your file should have a column named ‘location’, which should contain the information on which zone (from step 2) each line is in. 4) VERY IMPORTANT LAST STEP (without this the r-code will run, but will give faulty results). Use the ‘densify’ function in ArcMap to add vertices to all the lines in your file – the vertices should be 1m apart (So a 10 m line will have 9 vertices added etc). Now, for R. The things to do: 1) Install the packages that are listed at the top of the code, if you do not have them installed already. 2) In line 223 of the code, set your filepath 3) In line 256 add the files you would like to run. It can run multiple files at once. 4) In line 258 add the distances over which you want to calculate tortuosity. For example 100m, 250m, 500m and 1000m - can be anything you think might be useful. Let the whole thing run. It will create two types of output: one csv for each input file you give it. This will contain all the tortuosity measurements for that particular file. It will also create a summary file, containing summary data for all the files that it ran in one sitting. ----------- Data Attributes These definitions come from the Movebank Attribute Dictionary, available at www.movebank.org/node/2381. More Information For more information about this repository, see the FAQ at www.movebank.org/node/2220 or contact us at support@movebank.org.