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 "NYSDEC Raptor Tracking" (Movebank Study ID 2943485). 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: NYSDEC Raptor Tracking-argos.csv NYSDEC Raptor Tracking-gps.csv NYSDEC Raptor Tracking-reference-data.csv These data are described in the following written publications: Li Z, Han J, Ding B, Kays R (2012) Mining periodic behaviors of object movements for animal and biological sustainability studies. Data Mining and Knowledge Discovery 24(2): 355–386. doi:10.1007/s10618-011-0227-9 Nye P (2010) New York State bald eagle report 2010. New York State Department of Environmental Conservation, Albany, New York. 43 p. https://www.dec.ny.gov/docs/wildlife_pdf/baea2010.pdf Martell MS, Henny CJ, Nye PE, Solensky MJ (2001) Fall migration routes, timing, and wintering sites of North American ospreys as determined by satellite telemetry. The Condor 103: 715–724. doi:10.1650/0010-5422(2001)103[0715:FMRTAW]2.0.CO;2 Rodriguez F, Martell M, Nye P, Bildstein K (2001) Osprey migration through Cuba. In Bildstein K, Klem D, Jr (eds), Hawkwatching in the Americas: Proceedings of the 25th Anniversary Meeting of the Hawk Migration Association of North America, 8–11 June 2000. Hawk Migration Association of North America, North Wales, PA. p. 107–117. Bautz L and Nye P (1987) Spring movement of an adult bald eagle from southeastern New York to central Ontario. The Eyas 10(1): 32–33. Data package citation: Nye P, Hewitt G, Swenson T (2018) Data from: New York State bald eagle report 2010. Movebank Data Repository. doi:10.5441/001/1.s65q50j0 ----------- 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 ----------- Data Attributes These definitions come from the Movebank Attribute Dictionary, available at 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. THIS DATASET: The Douglas Argos Filter in Movebank was run in December 2018. Settings are Filter Method = Best Hybrid; keep_lc = 1; maxredun = 10; Duplicate record treatment = offset by one sec.; MRD filter advanced parameters = not enabled; minrate = 100; r_only = not enabled; ratecoef = 25; xmigrate = 10; xoverrun = 1.5; xdirect = 20; xangle = 150; xpercent = 20; testp_0a = 2; testp_bz = 3; Best of Day filter = not enabled. Values in Argos valid location manual, manually marked outlier, and manually marked valid were used to improve the results of the filter. animal comments: Additional information about the animal that is not described by other reference data terms. example: sibling of #1423 animal death comments: Comments about the death of the animal. example: hit by a car 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 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. Argos altitude: Altitude used for location calculation, Argos DIAG format file (definition from Argos User's Manual 2011) example: 27 units: meters Argos best level: Best signal strength, Argos DIAG format file (definition from Argos User's Manual 2011). example: -117 units: decibels (dB) Argos calculated frequency: Calculated frequency, Argos DIAG format file (definition from Argos User's Manual 2011). example: 401.6732709 units: hertz (Hz) same as: Argos calcul freq 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 DIAG format files (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 example: 68 units: none Argos lat1: Solution 1. platform latitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 19.493 units: decimal degrees, WGS84 reference system Argos lat2: Solution 2. platform latitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 14.773 units: decimal degrees, WGS84 reference system Argos LC: The location class retrieved from Argos. Allowed values are 0, 1, 2, 3, A, B, and Z (definition from Argos User's Manual 2011). example: A units: none Argos lon1: Solution 1. platform longitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 99.712 units: decimal degrees, WGS84 reference system Argos lon2: Solution 2. platform longitude in degrees and thousandths of degrees, Argos DIAG format file (definition from Argos User's Manual 2011). example: 120.286 units: decimal degrees, WGS84 reference system Argos nb mes: The number of messages received [to calculate location], Argos DIAG format file (definition from Argos User's Manual 2011). example: 8 units: none Argos nb mes 120: The number of messages received by the satellite at a signal strength greater than -120 decibels, Argos DIAG format file (definition from Argos User's Manual 2011). example: 2 units: none Argos NOPC: The number of plausibility checks successful (from 0-4), Argos DIAG format file (definition from Argos User's Manual 2011). example: 3 units: none Argos pass duration: Time elapsed between the first and last message received by the satellite, Argos DIAG format file (definition from Argos User's Manual 2011). example: 118 units: seconds Argos sensor 1: The value of the first Argos sensor, Argos DIAG format file (definition from Argos User's Manual 2011). example: 229 units: specific to the sensor Argos sensor 2: The value of the second Argos sensor, Argos DIAG format file (definition from Argos User's Manual 2011). example: 42 units: specific to the sensor Argos sensor 3: The value of the third Argos sensor, Argos DIAG format file (definition from Argos User's Manual 2011). example: 3 units: specific to the sensor Argos sensor 4: The value of the fourth Argos sensor, Argos DIAG format file (definition from Argos User's Manual 2011). example: 63 units: specific to the sensor 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. units: none Argos valid location manual: Indicates which of the two location estimates provided by Argos is the valid location as chosen by the user. Values override the results of Argos valid location algorithm. Allowed values are 1: The user has chosen the primary location (solution 1, lat1/lon1) as the valid location. 2: The user has chosen the alternate location (solution 2, lat2/lon2) as the valid location. units: none 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 beacon frequency: The frequency of the radio tag or tag retrieval beacon. example: 450.5 units: MHz same as: tag beacon frequency 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 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 end type: A categorical classification of the tag deployment end. Values are chosen from a controlled list: 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. equipment failure: The tag stopped working. fall off: The attachment of the tag to the animal failed, and it fell of accidentally. 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. unknown: The deployment ended by an unknown cause. 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 ground speed: The estimated ground speed provided by the sensor or calculated between consecutive locations. example: 7.22 units: meters per second heading: The direction in which the tag is moving, in decimal degrees clockwise from north, as provided by the sensor or calculated between consecutive locations. Values range from 0–360: 0 = north, 90 = east, 180 = south, 270 = west. example: 315.88 units: decimal degrees height raw: Raw values for the height of the tag above ellipsoid or mean sea level provided by the tag. Values are stored as raw text values because non-numeric characters are used or processing is required to derive the correct height estimate. example: 425, 2D fix units: undefined 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 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 comments: Additional comments about the way in which the animal was manipulated during the deployment. Use manipulation type to define the general type of manipulation. example: Relocated from breeding colony on Smithers Island to release location at 70.02E, 21.21S 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: Identifies events flagged manually as outliers, typically using the Event Editor in Movebank. Outliers have the value TRUE. 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. Records marked as valid have the value TRUE. 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. 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 processing type: Used to distinguish between data formats produced by different types of Microwave tags (currently not used). same as: processing type 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. 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 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.