Oppel, S2013https://doi.org/10.82144/0c57670bOBIS-SEAMAP487https://seamap.env.duke.edu/dataset/487OBIS-SEAMAPVersion 1.0.1vector digital data King Eiders are large sea ducks that nest in Arctic ecosystems around the world and migrate and winter at sea. Since 2002, the University of Alaska Fairbanks has tracked the migration and movements of King Eiders from breeding grounds in northern Alaska. This dataset includes all the locations provided by satellite-tracked King Eiders between June 2002 and December 2008. King Eiders migrated from breeding grounds in northern Alaska to winter regions in the Bering Sea. Females returned to breeding grounds in Alaska, whereas males dispersed over 50% of the species global range in the summer after capture. This study examined the migration routes and spatial distribution of King Eiders breeding in northern Alaska throughout the annual cycle. Satellite transmitters provided information on migration timing, migration distances, location of important molt, winter, and staging areas, migratory connectivity between those areas, and estimates of annual survival for adult and juvenile King Eiders. The authors and field assistants captured adult and juvenile King Eiders with mist nets on breeding grounds in northern Alaska and equipped each bird with an implanted satellite transmitter (PTT 100, Microwave Telemetry Inc.). Satellite transmitters provided locations every 2-7 days for a time period of 10-20 months per individual. We used a filter program (PC-SAS Argos Filter v7.02, David Douglas, USGS Science Center) to remove implausible locations, and retained one location per duty cycle. The filter algorithm flags implausible locations based on two different filtering methods:<br> 1. Minimum Redundant Distance (MRD): a user-defined distance threshold for determining locational redundancy; and<br> 2. Distance, Angle and Rate (DAR): measurements that attempt to identify implausible locations based on the fact that most suspicious ARGOS locations cause an animal to incorrectly move a substantial distance and then return, resulting in a tracking-path that goes 'out-and-back' (and/or further validated by unrealistic movement rates, depending on the temporal frequency of the locations).<br><br> A hybridization of the MRD and DAR filtered results is used for the data in this dataset. The hybrid was specifically developed for avian tracking that includes relatively high-speed, directional, migratory events. Locations that passed the MRD filter are retained as ‘anchor points,’ then chronologically intervening DAR locations are evaluated to determine if they adhere to directional movement when compared to the vector formed by their preceding and subsequent MRD anchor locations. 2002 2003 2004 2005 2006 2007 2008 2002061220081231 ground condition Complete None planned Alaska 97.93 252.302 76.168 50.637 97.93252.30276.16850.637 NoneRadio transmittersAnimal movementsKing Eidermigratory connectivitybird migrationNoneAlaskaSiberiaarctic tundraPrudhoe BayBeaufort SeaChukchi SeaBering SeaArctic OceanVictoria IslandBanks IslandTaymyr Peninsula Integrated Taxonomic Information Systemhttp://www.itis.usda.gov/Downloaded April, 2004Refer to the contact information of the dataset Open public unless otherwise noted. See Use Constraints for details. 1. Not to use data obtained from OBIS-SEAMAP in any publication, product, or commercial application without proper attribution to the original data provider(s) and OBIS-SEAMAP unless the datasets are explicitly shown under the CC0 policy. Citations or credits are suggested as attribution. If the data you downloaded come from multiple datasets, a citation or credit to each of the datasets is required. Suggested citation for this dataset: Oppel, S. 2013. Satellite telemetry of King Eiders from northern Alaska 2002-2009. Version 1.0.1. Dataset published in OBIS-SEAMAP. https://doi.org/10.82144/0c57670b. Suggested citation for OBIS-SEAMAP: Halpin, P.N., A.J. Read, E. Fujioka, B.D. Best, B. Donnelly, L.J. Hazen, C. Kot, K. Urian, E. LaBrecque, A. Dimatteo, J. Cleary, C. Good, L.B. Crowder, and K.D. Hyrenbach. 2009. OBIS-SEAMAP: The world data center for marine mammal, sea bird, and sea turtle distributions. Oceanography 22(2):104-115 2. To forward the citation of any publication / report that made use of the data / tools provided by OBIS-SEAMAP for inclusion in our list of references. 3. Not to hold OBIS-SEAMAP or the original data providers liable for errors in the data. While we have made every effort to ensure the quality of the database, we cannot guarantee the accuracy of these datasets. 4. The burden for determining fitness for use of the downloaded data for any analyses lies entirely with the user. OBIS-SEAMAP or the original data providers do not support outcomes of your analyses that used the data you downloaded from OBIS-SEAMAP. 5. To consider inclusion of the accompanying transect (effort) dataset if available into the methodology of your analyses. 6. Not to redistribute the data you downloaded from OBIS-SEAMAP through any media without contect from OBIS-SEAMAP and the original data providers unless the datasets are explicitly shown under the CC0 policy. Steffen Oppel Department of Biology and Wildlife, University of Alaska Fairbanks mailing and physical address

211 Irving 1

211 Irving 1

University of Alaska Fairbanks

Fairbanks AK 99775-6100 USA 907-474-6051 steffen.oppel@gmail.com U.S. Geological Survey Outer Continental Shelf Program<br> U.S. Minerals Management Service<br> U.S. Geological Survey Alaska Cooperative Fish and Wildlife Research Unit<br> North Slope Borough<br> ConocoPhillips Alaska<br> Sea Duck Joint Venture<br> U.S. Fish and Wildlife Service<br> German Academic Exchange Service Satellite telemetry data were processed by Service Argos, and filtered using the Douglas Argos-Filter Algorithm. We set the algorithm parameters to the following values: %let minoffh = 36 ; %let maxredun = 5 ; %let minrate = 60 ; %let ratecoef = 15 ; %let gmtoffst = 0. ; %let latmin = -90. ; %let latmax = 90. ; %let lonmin = -180. ; %let lonmax = 180. ; %let r_only = 0 ; %let r_or_a = 1 ; %let keep_lc = 1 ; %let rankmeth = 2 ; %let keeplast = 0 ; %let pickday = 0 ; %let skiploc = 0 ; %let xmigrate = 20 ; %let xoverrun = 1.5 ; %let xdirect = 20 ; %let xangle = 150 ; %let xpercent = 80 ; %let testp_0a = 2 ; %let testp_bz = 3 ; %let crossval = 0 ; %let unixdata = 0 ; We used the pkbr60d5lc1.txt output that filtered the best location per duty cycle. Those locations are contained in the database described by the metadata here. http://alaska.usgs.gov/science/biology/spatial/douglas.html PURPOSE: Ingests any number of Argos DIAG files and reformats all information into ASCII comma-delimited files. Chooses the most plausible location between the ARGOS primary and alternate locations based on minimum distance from the previous chosen location. Flags implausible locations based on two different filtering methods: 1. Minimum Redundant Distance (MRD): a user-defined distance threshold for determining locational redundancy; 2. Distance, Angle and Rate (DAR): measurements that attempt to identify implausible locations based on the fact that most suspicious ARGOS locations cause an animal to incorrectly move a substantial distance and then return, resulting in a tracking-path that goes 'out-and-back' (and/or further validated by unrealistic movement rates, depending on the temporal frequency of the locations); A hybridization of the MRD and DAR filtered results is also created. The hybrid was specifically developed for avian tracking that includes relatively high-speed, directional, migratory events. Locations that passed the MRD filter are retained as ‘anchor points’, then chronologically intervening DAR locations are evaluated to determine if they adhere to directional movement when compared to the vector formed by their preceding and subsequent MRD anchor locations. REQUIREMENTS: A) PC BASE SAS – Version 7 or later. This SAS program requires PC SAS because it uses DOS commands to concatenate all your individual ARGOS DIAG files into a single file before ingestion. This concatenated file will be written into the same directory where your SAS program files reside, and will be named 'total.dia'. It can be considered a temporary file, which you may delete after the SAS program executes. B) All your Argos ASCII-format DIAG data files in ONE directory. The SAS program has been written to accept DIAG files from CD-ROM, Telnet, and/or ADS (e-mail), in both compressed and uncompressed formats. C) You must create an ASCII text-file that defines each of your ptt deployments. This file is comprised of IF-THEN-DO logic blocks relating each ptt-number to the respective animal upon which the ptt was deployed, and during what time interval. D) You must modify the SAS program 'generic_run702.sas' to supply several user-defined thresholds that establish minimum distances, maximum rate of movement, etc., which largely dictate how conservative or liberal the filtering will be implemented. You must also define several directory pathnames (specific to your computer) that define where your input data are stored, the name and location of your deployment definition file, and the directories where results will be written. CAUTIONS: If this program filters a location, it does not necessarily mean that the location was incorrect. Conversely, and more importantly, if this program does not filter a location, it does not necessarily mean the animal visited that precise location. The underlying premise for the MRD filtering logic is: 'Argos does not make a significant error in the same place twice, consecutively.' In reality, bad Argos locations sometimes do occur at the same locale, consecutively, but with a low probability of occurrence. In about 2000 control relocations, I witnessed 3 consecutive pairs of locations that would have passed typical MRD threshold criteria. So, if you encounter suspicious results from this program – then question those results. This program will quickly (and systematically) get about 95+% of your Argos data “cleaned-up” to your satisfaction, but you should definitely invest some QC time reviewing the results and getting any last anomalies taken care of before you make and publish biological interpretations. You control how conservatively the filters behave through user-defined thresholds. How conservative (or liberal) the program is allowed to behave should be commensurate with the study's spatial scale-of-interpretation. This program does not correct the inherent locational error of any single Argos location. The program strives to reduce the average error among all locations that pass the filtering criteria. David C. Douglas USGS Alaska Science Center David C. Douglas david_douglas@usgs.gov David C. Douglas Unknown v.7.02 model http://alaska.usgs.gov/science/biology/spatial/douglas.html ShapefileRelational databaseS. Oppel and A.N. Powell2009vector digital dataonline datasethttp://mercury.bio.uaf.edu/kingeiderOppel, S., A.N. Powell, and D.L. Dickson2008vector digital dataCondor110: 296-305http://mercury.bio.uaf.edu/%7Esteffen_oppel/kingeider/Oppel_Condor_2008.pdfPhillips, L. M., A.N. Powell, and E.A. Rexstad2006vector digital dataCondor108: 887-900http://mercury.bio.uaf.edu/~steffen_oppel/kingeider/Phillips_etal_2006.pdfHalpin, P.N., A.J. Read, E. Fujioka, B.D. Best, B. Donnelly, L.J. Hazen, C. Kot, K. Urian, E. LaBrecque, A. Dimatteo, J. Cleary, C. Good, L.B. Crowder, and K.D. Hyrenbach2009Oceanography22(2):104-115 The accuracy of satellite telemetry locations is assessed via the Argos System. The location accuracy category of each location is listed with the data. Permissible values for date and time and coordinates were validated by the data provider and the OBIS-SEAMAP data manager. Species identification by the data provider was matched with Integrated Taxonomic Information System. Satellite transmitters depend on satellites being in the overhead viewing range for transmission. During some transmission cycles it is possible that either no satellites are within immediate range, that cloud cover prevents communication between transmitter and satellite, or that insufficient satellites can be received. This leads to inaccurate locations which will be excluded by the filter algorithm if they are implausible. The dataset contains temporal data gaps for some individuals ranging from 6 days to 2 months during which no reliable locations were recorded. Data were put through the OBIS-SEAMAP data registration steps. 20250925 GCS_WGS_1984Decimal degrees0.0010.001D_WGS_1984WGS_19846378137.000000298.257224 Biogeographic dataBiogeographic dataNot applicablespeciesSpecies name recorded by providerData providerpttserial identification number of platform transmitting terminal (PTT)Data providersexsex of the bird, f=female, m=maleData providerageage of the bird: ad=adult, juv=bird marked in hatch-year as young duckling, (adult if unspecified)Data providerlatitudelatitudeData providerlongitudelongitudeData providerlc94Location quality provided by ARGOSData providerobs_dateDateData providerobs_timeTime. Seconds are not provided.Data providersp_tsnTaxonomic Serial Number by Integrated Taxonomic Information SystemData providerobs_countalways 1. Added by OBIS-SEAMAP.Data providergeomData provideroidUnique ID number (generated by SEAMAP)Data provider Locations of King Eiders equipped with a satellite transmitter between 2002-2009. University of Alaska Fairbanks and U. S. Geological Survey OBIS-SEAMAPNicholas School of Environment, Duke Univ.mailing and physical address

A328, LSRC

DurhamNC27708USA919-613-8021seamap-contact@duke.edu OBIS-SEAMAP Dataset ID 487 Not to hold OBIS-SEAMAP liable for errors in the data. While we have made every effort to ensure the quality of the database, we cannot guarantee the accuracy of these datasets. Also please refer to Use Constraints. Must be able to open Microsoft Excel 2003 file. FreeGo to the OBIS-SEAMAP web sitezipzipped shapefilehttp://seamap.env.duke.edu/dataset/487 20250929 Ei FujiokaDuke Universitymailing and physical address

LSRC A328

DurhamNCUSA27708efujioka@duke.edu919-613-8021 FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata FGDC-STD-001.1-1999 http://www.nbii.gov/Biological Data Profile20250929