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 "Antarctic blue whales, east Antarctic sector of the Southern Ocean" (Movebank Study ID 2391441038). 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: Antarctic blue whales east Antarctic sector of the Southern Ocean.csv Antarctic blue whales east Antarctic sector of the Southern Ocean-reference-data.csv BDJ_ssm_2h_mpm.csv Data package citation: Andrews-Goff V, Bell EM, Miller BS, Wotherspoon SJ, Double MC. 2022. Data from: Satellite tag derived data from two Antarctic blue whales (Balaenoptera musculus intermedia) tagged in the east Antarctic sector of the Southern Ocean. Movebank Data Repository. https://doi.org/10.5441/001/1.vr276ns3 Another version of this dataset is published as Andrews-Goff V, Double M. 2022. Deployment details for satellite tags deployed on Antarctic blue whales during the Antarctic blue whale voyage 2013, Ver. 2. Australian Antarctic Data Centre. https://doi.org/10.26179/jd0n-va59, Accessed: 2022-10-31. https://data.aad.gov.au/s3/bucket/datasets/science/AAS_4102_sat_tag/2022%20Update These data are described in the following written publication: Andrews-Goff V, Bell EM, Miller BS, Wotherspoon SJ, Double MC. In press, 2022. Satellite tag derived data from two Antarctic blue whales (Balaenoptera musculus intermedia) tagged in the east Antarctic sector of the Southern Ocean. Biodivers Data J. ----------- 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 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'. Best practice is to define units in the values if needed (e.g. '2 years'). example: juvenile, adult units: none entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000018 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 animal taxon detail: A more specific name and/or reference for the taxon name provided by 'animal taxon'. This can be used, for example, to specify a subspecies or a taxon not supported by the ITIS. example: Calonectris diomedea borealis (Cory, 1881) units: none entity described: individual URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000025 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 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 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 location algorithm: The processing algorithm used by Argos to estimate locations using Doppler shift. If the location data represent model output rather than the original estimates from Argos, also use 'modelled'. Values are chosen from a controlled list: least squares = locations were calculated by Argos using a least-squares analysis; Kalman = locations were calculated by Argos using Kalman filtering. format: controlled list entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000278 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 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 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 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 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 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. Units and time zones should be defined in the remarks. example: 15-min fixes from 8:00-18:00 local time (0:00-10:00 UTC) units: none entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000086 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 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 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 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 units: none entity described: tag URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000179 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 model: The model of the tag. example: T61 units: none entity described: tag URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000185 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 BDJ_ssm_2h_mpm.csv This file contains state space model output at 2h time step with move persistence (gamma) value used to provide behavioural context to movement. ptt: the Argos PTT ID; same as 'tag-id' above track_segment: the individual identifier for each track segment - the first 6 digits are equal to PTT which is followed by an underscore and then a number to indicate the unique track segment belonging to that PTT date: the date and time (yyyy-MM-dd HH:mm:ss) in UTC lon: state space model predicted longitude in decimal degrees, WGS84 reference system lat: state space model predicted latitude in decimal degrees, WGS84 reference system g: Gamma value used as the behavioural index mode: The assigned behavioural mode. ARS is assigned where g < mean(g) and transit is assigned where g >= mean(g) patch: The assignment of each location in relation to an ARS patch. FALSE indicates outside of an ARS patch, TRUE indicates within an ARS patch. ----------- 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.