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 "Brown pelican data from Lamb et al. (2017)" (Movebank Study ID 296027617). 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: Brown pelican data from Lamb et al. (2017).csv Brown pelican data from Lamb et al. (2017)-reference-data.csv These data are described in the following written publication: Lamb JS, Satgé YG, Jodice PGR (2017) Influence of density-dependent competition on foraging and migratory behavior of a subtropical colonial seabird. Ecology and Evolution 7(13). doi:10.1002/ece3.3216 Data package citation: Lamb JS, Satgé YG, Jodice PGR (2017) Data from: Influence of density-dependent competition on foraging and migratory behavior of a subtropical colonial seabird. Movebank Data Repository. doi:10.5441/001/1.7856r086 ----------- 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 U.S. Geological Survey Disclaimer The authors of these data require that data users contact them regarding intended use and to assist with understanding limitations and interpretation. Unless otherwise stated, all data, metadata, and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. ----------- 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 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 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 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 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 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 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 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 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 ground speed: The estimated ground speed between consecutive locations. example: 7.22 units: meters per second heading: The direction in which the tag moved from this location to the subsequent location, calculated as the bearing between consecutive locations, in decimal degrees clockwise from north; for example, 0 = north, 90 = east, 180 = south. example: 315.88 units: decimal degrees 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. location error text: An estimate of the horizontal error of the location estimate, typically provided in the original data file, described using more than numbers. Units should be provided in the values. (If the values are purely numerical, use location error numerical.) These values can be described using location error percentile and location accuracy comments. example: > 25 ft units: defined in the values 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. ring ID: A number or color scheme for a band or ring attached to the animal. example: 26225 units: none same as: animal ring id 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 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 serial number: The serial number of the tag. example: MN93-33243 units: none same as: tag serial no, serial no 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 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. ----------- 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.