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 "Marbled Murrelet satellite tracking data from British Columbia, Canada 2014-2016" (Movebank Study ID 913538699). 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: Marbled Murrelet satellite tracking data from British Columbia Canada 2014-2016.csv Marbled Murrelet satellite tracking data from British Columbia Canada 2014-2016-reference-data.csv MarbledMurrelet_Sat_Bertram_isotope_data.csv ProcessArgosRawDIAG_SensorDataGraphs_MAMU.R Data package citation: Bertram DF, Janssen MH, Cragg JL, Macdonald CA, McAdie M, Wilson A, Woo K, Gross E, Maftei M, O'Hara PD, Davis SE, Greene R, Vincent P. 2022. Data from: Study "Marbled Murrelet satellite tracking data from British Columbia, Canada 2014-2016". Movebank Data Repository. https://doi.org/10.5441/001/1.j0d889f0 These data are described in the following written publications: Bertram DF, Jannsen MH, Cragg JL, Macdonald CA, McAdie M, Wilson A, Woo K, Gross E, Maftei M, O’Hara PD, Davis S, Green R, Vincent P. In review, November 2022. Conservation implications of movements by Canadian Marbled Murrelets to Alaska in summer. Bertram DF, Macdonald CA, O'Hara PD, Cragg JL, Janssen MH, McAdie M, Boyd WS. 2016. Marbled Murrelet Brachyramphus marmoratus movements and marine habitat use near proposed tanker routes to Kitimat, BC, Canada. Mar Ornithol. 44:3-9. url:http://www.marineornithology.org/content/get.cgi?rn=1148 Additional description: Marbled murrelets were captured in Wright Sound, near Hartley Bay, BC (53°15′10.8″N, 129°9′1.79″W) 17–20 April 2014. Adult birds were captured on the water between 22h00 and 05h00 local time using night-lighting. Birds were tagged using 5-g solar-powered satellite transmitters attached to the loose fold of skin of the dorsal neck with four simple, interrupted, transverse sutures. Birds were not anesthetized and were released within 1.5 h after the time of capture. Transmitters were programmed to signal for 10 h followed by a 48-h off cycle to optimize the discharge/recharge cycle of the battery. Prior to organizing this dataset in the study above, the Douglas Argos Filter in Movebank was run in February 2019. Settings are Filter Method = Best Hybrid; keep_lc = 1; maxredun = 15; Duplicate record treatment = filter; keeplast = not enabled; skiploc = not enabled; minrate = 150; r_only = enabled; ratecoef = 25; xmigrate = 2; xoverrun = 1.5; xdirect = 20; xangle = 150; xpercent = 20; testp_0a = 2; testp_bz = 3; Best of Day filter = not enabled; pickday = not enabled; minoffh = n/a; rankmeth = n/a. Deployment ends were defined based on a sudden drop in temperature or voltage from the Argos sensor data. The workflow involved in truncating movement was performed by Shanti Davis based on the document Migration Patterns of Pacific Sea Ducks, created by Jennifer Barrett, March 28th, 2015, which was a part of the Pacific Barrow’s Goldeneye tracking project. R code accompanied this document which processed the sensor output to yield appropriate temperature, voltage, and mortality values and create corresponding graphs. This analysis resulted in 12 of the 27 bird time ranges being truncated due to suspected death or equipment failure. After discussions on how to further challenge some of the determinations (e.g., unknown should be dead and at an earlier date), it was decided that an additional analysis may provide further insight into more accurate movement patterns and timeframes of these birds. For example, a bird might have died on land and maintained the impression of being alive and active due to summer temperatures and the error radius of the sensors. Please contact Doug Bertram, ECCC STB Wildlife Research Division, Institute of Ocean Sciences, Sidney, BC, Canada (doug.bertram@canada.ca) for more information. ----------- 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 comments: Additional information about the animal that is not described by other reference data terms.
example: sibling of #1423
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000012 animal ID: An individual identifier for the animal, provided by the data owner. Values are unique within the study. If the data owner does not provide an Animal ID, an internal Movebank animal identifier is sometimes shown. example: TUSC_CV5 units: none entity described: individual same as: individual local identifier URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000016 animal mass: The mass of the animal, typically at the beginning of the deployment.
example: 500
units: grams
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000019 animal nickname: An alternate identifier for the animal. Used as the display name for animals shown in the Animal Tracker App.
example: Ali
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000020 animal ring ID: A number or color scheme for a band or ring attached to the animal.
example: 26225
units: none
entity described: individual
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000022 animal sex: The sex of the animal. Allowed values are m = male; f = female; u = unknown. format: controlled list entity described: individual URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000023 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'. format: controlled list entity described: individual same as: individual taxon canonical name URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000024 Argos altitude: Altitude used for location calculation, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 27
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000026 Argos best level: Best signal strength, Argos diagnostic data (definition from Argos User's Manual 2011).
example: -117
units: dB
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000027 Argos calcul freq: Calculated frequency, Argos diagnostic data. It should be between 401.620 and 401.680 MHz (definition from Argos User's Manual 2011). The '401.' is sometimes missing from the source data and should be added to the values for correct intepretation.
example: 401.6732709
units: MHz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000028 Argos error radius: One standard deviation (sigma) of the estimated location error, assuming isotropic error, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 229
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000029 Argos GDOP: Geometric dilution of precision, a measure of the effect of the geometry of the satellite-beacon configuration on location accuracy, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 254
units: m/Hz
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000030 Argos IQ: This quality indicator gives information on the transmitter in terms of two digits, X and Y. X is the first digit and indicates residual error on the frequency calculation; Y is the second digit and indicates transmitter oscillator frequency drift between two satellite passes. Values provided in Argos diagnostic data (definition from Argos User's Manual 2011). Values obtained through some Argos channels do not include leading 0s, so 1-digit values indicate X = 0 and blank values or values of '0' indicate both X and Y = 0. Allowed values are
X = 0: No calculation of residual frequency error (fewer than four messages received);
X = 1,2,3: Unsatisfactory convergence of calculation;
X = 4: Residual frequency error > 1.5 Hz;
X = 5: 0.15 Hz < residual frequency error < 1.5 Hz;
X = 6: Residual frequency error < 0.15 Hz;
Y = 0: No check on transmit frequency drift, as the two results are more than 12 hours apart;
Y = 1: Frequency discrepancy > 400 Hz Probably due to transmit frequency discrepancy, change of oscillator, etc.;
Y = 2: Previous location is less than 1/2 hour old. Frequency discrepancy > 30 Hz, i.e. F/F (over 10 min) >2.5 E-8;
Y = 3: Frequency drift > 4 Hz/minute, i.e. F/F (10 min) > 1.10-7;
Y = 4: Frequency drift < 4 Hz/minute, i.e. F/F (10 min) < 1.10-7;
Y = 5: Frequency drift < 2 Hz/minute, i.e. F/F (10 min) < 5.10-8;
Y = 6: Frequency drift < 1 Hz/minute, i.e. F/F (10 min) < 2.5 . 10-8;
Y = 7: Frequency drift < 0.4 Hz/minute, i.e. F/F (10 min) < 1.10-8;
Y = 8: Frequency drift < 0.2 Hz/minute, i.e. F/F (10 min) < 5.10-9.
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000031 Argos lat1: Solution 1. platform latitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 19.493
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000032 Argos lat2: Solution 2. platform latitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 14.773
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000033 Argos LC: The location class retrieved from Argos, Argos diagnostic data. Classes are based on the type of location (Argos Doppler Shift or GPS) and the number of messages received during the satellite pass. Location classes in order of decreasing accuracy are G (GPS), 3, 2, 1, 0, A, B and Z (definition from Argos User's Manual V1.6.6, 2016)
format: controlled list
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000034 Argos lon1: Solution 1. platform longitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 99.712
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000035 Argos lon2: Solution 2. platform longitude in degrees and thousandths of degrees, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 120.286
units: decimal degrees, WGS84 reference system
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000036 Argos nb mes: The number of messages received [to calculate location], Argos diagnostic data (definition from Argos User's Manual 2011).
example: 8
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000037 Argos nb mes 120: The number of messages received by the satellite at a signal strength greater than -120 decibels, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 2
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000038 Argos NOPC: Number of plausibility checks successful (from 0-4), Argos diagnostic data (definition from Argos User's Manual 2011).
example: 3
units: count
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000039 Argos orientation: The orientation of the semi-major axis of the error elipse, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 83
units: degrees clockwise from north
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000040 Argos pass duration: Time elapsed between the first and last message received by the satellite, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 118
units: seconds
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000041 Argos sat ID: The satellite identifier, Argos diagnostic data (definition from Argos User's Manual 2011).
example: P
units: none
entity described: event
same as: Argos satellite ID
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000042 Argos semi major: Length of the semi-major axis of the error ellipse, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 300
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000043 Argos semi minor: Length of the semi-minor axis of the error ellipse, Argos diagnostic data (definition from Argos User's Manual 2011).
example: 175
units: meters
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000044 Argos sensor 1: The value of the first Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 229
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000045 Argos sensor 2: The value of the second Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 42
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000046 Argos sensor 3: The value of the third Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 3
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000047 Argos sensor 4: The value of the fourth Argos sensor, Argos diagnostic data (definition from Argos User's Manual 2011). Units are specific to the sensor.
example: 63
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000048 attachment type: The way a tag is attached to an animal. Values are chosen from a controlled list: backpack-harness = The tag is attached to the animal using a backpack-style harness; collar = The tag is attached by a collar around the animal's neck; fin mount = The tag is attached to the animal's fin; 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; leg-band = The tag is attached as a leg band or ring; leg-loop-harness = The tag is attached to the animal using a leg-loop-style harness; none = No tag was attached, e.g., for observations using natural markings; other = The tag is attached using another method; suction-cup = The tag is attached using one or more suction cups; tape = The tag is attached to the animal using tape. format: controlled list entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000052 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
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000069 deploy off timestamp: The timestamp when the tag deployment ended. Data records recorded after this day and time are not associated with the animal related to the deployment. Values are typically defined by the data owner, and in some cases are created automatically during data import. Further information can be provided in 'deployment end type' and 'deployment end comments'. 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000077 deploy on latitude: The geographic latitude of the location where the animal was released. Intended primarily for cases in which the animal release location has higher accuracy than that derived from sensor data.
example: 27.3516
units: decimal degrees, WGS84 reference system
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000078 deploy on longitude: The geographic longitude of the location where the animal was released. Intended primarily for cases in which the animal release location has higher accuracy than that derived from sensor data.
example: -97.3321
units: decimal degrees, WGS84 reference system
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000079 deploy on timestamp: The timestamp when the tag deployment started. Data records recorded before this day and time are not associated with the animal related to the deployment. Values are typically defined by the data owner, and in some cases are created automatically during data import. 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000081 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
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000082 deployment end comments: Additional information about the end of a tag deployment. Also see 'deployment end type', 'animal death comments', and 'tag failure comments'.
example: data transmission stopped after 108 days. Cause unknown
units: none
entity described: deployment
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000083 deployment end type: A categorical classification describing the end of the tag deployment on the animal. Best practice is to clarify how the 'deploy-off timestamp', if present, was chosen. Values are chosen from a controlled list: analysis-end = the end time represents the end of the period of interest; 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; dead/fall-off = The tag stopped moving, and it is not possible to determine whether it is due to death of the animal or unscheduled tag detachment; equipment-failure = The tag stopped working; fall-off = The attachment of the tag to the animal failed, and it fell of accidentally; other = 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; scheduled-detachment = The tag was programmed to detach from the animal; transmission-end = The tag stopped transmitting usable data; unknown = The cause of the end of data availability or transmission is unknown. format: controlled list entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000084 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000085 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000103 import marked outlier: Identifies events as outliers. Typically used to import a record of outliers that were identified by the data provider or owner with automated methods outside of Movebank. Outliers have the value TRUE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000133 location lat: The geographic latitude of the location as estimated by the sensor. example: -41.0982423 units: decimal degrees, WGS84 reference system entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000145 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000146 manipulation type: The way in which the animal was manipulated during the deployment. Additional information 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; domesticated = The animal is domesticated, for example, is a house pet or part of a managed herd; manipulated-other = The animal was manipulated in some other way, such as a physiological manipulation; none = The animal received no treatment other than tag attachment and related measurements and sampling (if applicable); reintroduction = The animal has been reintroduced as part of wildlife conservation or management efforts; relocated = The animal was released from a site other than the one at which it was captured. format: controlled list entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000155 manually marked valid: An event marked manually as valid to override the results of a Movebank data filter (stored in 'algorithm marked outlier'), typically using the Event Editor in Movebank. These values also override values in 'manually marked outlier' and 'import marked outlier'. Records marked as valid have the value TRUE.
units: none
entity described: event
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000157 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; acoustic telemetry = The sensor transmits an acoustic signal that is detected by receivers to determine location; Argos Doppler shift = The sensor location is estimated by Argos using Doppler shift; 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; gyroscope = The sensor records angular velocity; heart rate = The sensor records or is used to calculate heart rate; 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 transmits a radio signal that is detected by receivers to determine location; Sigfox geolocation = The sensor location is determined by Sigfox using the received signal strength indicator; 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000170 study name: The name of the study in Movebank. example: Coyotes, Kays and Bogan, Albany NY units: none entity described: study URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000173 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
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000175 tag ID: An identifier for the tag, provided by the data owner. Values are unique within the study. 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000181 tag manufacturer name: The company or person that produced the tag. example: Holohil units: none entity described: tag same as: manufacturer name URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000183 tag mass: The mass of the tag. example: 24 units: grams entity described: tag same as: weight URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000184 tag model: The model of the tag. example: T61 units: none entity described: tag URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000185 tag production date: The approximate date the tag was produced (can be a year, month, or day).
example: March 2011
units: none
entity described: tag
URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000187 tag readout method: The way the data are received from the tag. Values are chosen from a controlled list: ISS = Data are transferred via the International Space Station; LPWAN = Data are transferred through a low-power wide-area network, such as LoRa or Sigfox; multiple = Data are acquired using multiple methods; none = Data are obtained without use of an animal-borne tag, such as by observing a unique marking; other-wireless = Data are transferred via another form of wireless data transfer, such as a VHF transmitter/receiver; phone-network = Data are transferred via a phone network, such as GSM or AMPS; satellite = Data are transferred via satellite; tag-retrieval = The tag must be physically retrieved in order to obtain the data; telemetry-network = Data are obtained through a radio or acoustic telemetry network; Wi-Fi/Bluetooth = Data are transferred via a local Wi-Fi or Bluetooth system. format: controlled list entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000188 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000200 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 URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000209 ----------- File MarbledMurrelet_Sat_Bertram_isotope_data.csv This file contains results of stable isotope analysis from the study. Samples were taken at the time of tag attachment. It includes the following attributes: animal-id: same as ‘animal-id’ above ISO ID: the isotope sample ID N2 Beam Area: the beam area for nitrogen analysis d15N: the measured 15N:14N ratio in parts per thousand CO2 Beam Area: the beam area for CO2 analysis d13C: the measured 13C:12C ratio in parts per thousand tag-id: same as ‘tag-id’ above ----------- File ProcessArgosRawDIAG_SensorDataGraphs_MAMU.R This file contains R script used to process Argos DIAG data to review sensor output in order to evaluate data, in particular to assess movement patterns and define the end of the deployment and possible causes (e.g., death or equipment failure). ----------- More Information For more information about this repository, see www.movebank.org/cms/movebank-content/data-repository, the FAQ at https://www.datarepository.movebank.org/faq, or contact us at support@movebank.org.