README This data package 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 "King Eider Alaska (UAF / USGS)" (Movebank Study ID 213511247). 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: King Eider Alaska (UAF _ USGS).csv King Eider Alaska (UAF _ USGS)-reference-data.csv Data package citation: Phillips LM, Oppel S, McGuire R. 2024. Data from: Study "King Eider Alaska (UAF / USGS)". Movebank Data Repository. https://doi.org/10.5441/001/1.339 These data are described in the following written publications: Bentzen RL, Powell AN. 2015. Dispersal, movements and site fidelity of post-fledging King Eiders Somateria spectabilis and their attendant females. Ibis. 157(1):133-146. https://doi.org/10.1111/ibi.12217 Bentzen RL, Powell AN. 2012. Population dynamics of king eiders breeding in northern Alaska. J Wildlife Manage. 76(5):1011-1020. https://doi.org/10.1002/jwmg.335 Oppel S, Powell AN. 2010. Age-specific survival estimates of King Eiders derived from satellite telemetry. Condor. 112(2):323-330. https://doi.org/10.1525/cond.2010.090199 Schamber JL, Flint PL, Powell AN. 2010. Patterns of use and distribution of king eiders and black scoters during the annual cycle in northeastern Bristol Bay, Alaska. Mar Biol. 157:2169-2176. https://doi.org/10.1007/s00227-010-1481-x Oppel S, Dickson DL, Powell AN. 2009. International importance of the eastern Chukchi Sea as a staging area for migrating king eiders. Polar Biol. 32:775-783. https://doi.org/10.1007/s00300-008-0580-3 Oppel S, Powell AN. 2009. Does winter region affect spring arrival time and body mass of king eiders in northern Alaska? Polar Biol. 32:1203-1209. https://doi.org/10.1007/s00300-009-0618-1 Oppel S, Powell AN, Dickson DL. 2009. Using an algorithmic model to reveal individually variable movement decisions in a wintering sea duck. J Anim Ecol. 78(3):524-531. https://doi.org/10.1111/j.1365-2656.2008.01513.x Oppel S, Powell AN, Dickson DL. 2008. Timing and distance of King Eider migration and winter movements. Condor. 110(2):296-305. https://doi.org/10.1525/cond.2008.8502 Knoche ML, Powell AN, Quackenbush LT, Wooller MJ, Phillips LM. 2007. Further evidence for site fidelity to wing molt locations by King Eiders: integrating stable isotope analyses and satellite telemetry. Waterbirds. 30(1):52-57. https://doi.org/10.1675/1524-4695(2007)030[0052:FEFSFT]2.0.CO;2 Phillips LM, Powell AN, Taylor EJ, Rexstad EA. 2007. Use of the Beaufort Sea by King Eiders breeding on the North Slope of Alaska. J Wildlife Manage. 71(6):1892-1898. https://doi.org/10.2193/2005-636 Phillips LM, Powell AN, Rexstad EA. 2006. Large-scale movements and habitat characteristics of King Eiders throughout the nonbreeding period. Condor. 108(4):887-900. https://doi.org/10.1093/condor/108.4.887 ----------- 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. algorithm marked outlier: Identifies events marked as outliers using a user-selected filter algorithm in Movebank. Outliers have the value TRUE. Information about how outliers were defined can be provided in 'outlier comments'. Units: none Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000011 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 ring ID: A number or color scheme for a band or ring attached to the animal. Color bands and other markings can be stored in 'animal marker ID'. 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 taxon on which the tag was deployed, as defined by the Integrated Taxonomic Information System (ITIS). 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'. The values 'test' and 'calibration' identify events relevant to animal tracking studies that should not be associated with a taxon. Format: controlled list Entity described: individual Same as: individual taxon canonical name URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000024 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 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 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 valid location algorithm: Indicates which of the two location estimates provided by Argos is the valid location, using a user-selected filter algorithm in Movebank. Allowed values are 1 = The Argos filter algorithm has chosen the primary location (solution 1, lat1/lon1) as the valid location; 2 = The Argos filter algorithm has chosen the alternate location (solution 2, lat2/lon2) as the valid location. Format: controlled list Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000050 attachment body part: The body part to which the tag is attached. In some cases this can also be indicated by 'attachment type'. If the tag is not attached on the mid-line of the animal, specify the side of placement to assist interpretation of sensor data. Units: none Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000395 attachment type: The way a tag is attached to an animal. Details can be provided in 'attachment comments'. 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; ear-tag = The tag is attached to the animal's ear; 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; subcutaneous-anchor = The tag is attached using one or more anchors attached underneath the animal's skin; suction-cup = The tag is attached using one or more suction cups; sutures = The tag is attached by one or more sutures; 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 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_42818 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: 14328243575 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'. Changes in manipulation status during deployment can be identified using 'manipulation status'. 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 outlier comments: A description or reference for methods used to define outliers in 'manually marked outlier', 'algorithm marked outlier', 'import marked outlier' and/or 'manually marked valid'. If outliers were removed prior to import, this field can be used to describe which data were excluded. Example: Movebank value range filter set to flag records with "GPS HDOP" => 20, retaining records with null values. Units: none Entity described: deployment URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000374 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; derived = Information is derived from other sensor data; geolocation-api = The location is determined based on detection by nearby cell towers or other wireless network connectors using the World Wide Web Consortium Geolocation API Recommendation; gnss = The sensor uses one or more global navigation satellite systems to determine location; 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; proximity = The sensor identifies proximity to other tags; 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 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. Allowed values are TRUE or FALSE. 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. Units: none Entity described: event URI: http://vocab.nerc.ac.uk/collection/MVB/current/MVB000209 ----------- 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.