www.bandedbirds.org; Shorebird Resighting Database: Banding Data Extraction

Metadata:

Frequently anticipated questions:

What does this data set describe?

Title:
www.bandedbirds.org; Shorebird Resighting Database: Banding Data Extraction
Abstract:
Since 2003, New Jersey and Delaware Divisions of Fish and Wildlife and NJ Audubon Society have captured and individually marked over 35,000 red knots, ruddy turnstones, sanderlings and semipalmated sandpipers with coded leg flags during spring migration stopovers in Delaware Bay. Banders in Argentina have utilized engraved markers for red knot since 2001. These markers are conspicuous to observers at a distance, which allows identification of individual birds. Internationally, many additional banding programs have implemented this practice of marking based on the success of resighting efforts. The aforementioned organizations initiated the developement of a website and web-based relational database, www.bandedbirds.org, that allows field observers to report resightings of these uniquely marked shorebirds via the web. The relational database maintains both capture data and resighting data. Large quantities of banding and resighting data can be formatted in Excel in a fashion similar to field collection sheets for bulk uploads. Custom programming creates and maintains the relationship of capture and resighting data, even when band changes are made to an individual, allowing the retrieval of data that details a bird’s recorded history.
Supplemental_Information:
Several research groups contribute data to the Shorebird Resighting Database. Data is stored on a secure server and is archived daily. Downloads of secure data are available to approved researchers. Look-ups for an individual bird's history for personal use only is available to the general public.
  1. How should this data set be cited?

    Multiple authors for several projects participating in the overall database. Refer to the "Other Citation Details" section for specifics and proper publication credit., 20090501, www.bandedbirds.org; Shorebird Resighting Database: Banding Data Extraction:, <http://www.bandedbirds.org>.

    Online Links:

    Other_Citation_Details:
    Publication Credit: Any form of publication using this data should credit: www.bandedbirds.org. In addition, each project contributing data to the dataset used should be individually credited. Please consult the metadata for each project for the correct citation(s). If metadata is not available, contact the database administrator for further information.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -166.0090
    East_Bounding_Coordinate: -53.92750
    North_Bounding_Coordinate: 70.27835
    South_Bounding_Coordinate: -52.57645
    Description_of_Geographic_Extent:
    While the majority of the data comes from the Eastern Coasts of North and South America, some data has been received from the Western shorelines, as well.

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: Unknown
    Ending_Date: Unknown
    Currentness_Reference: ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: database; spreadsheet

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      Indirect_Spatial_Reference:
      All resighting locations are identified by place. A code for a place relates to a table with a location name, generalized coordinates for the location area, state/province and country for that location.
      This is a Point data set.

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is World Geodetic System of 1984.
      The ellipsoid used is World Geodetic System of 1984.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.25722210088.

  7. How does the data set describe geographic features?

    Banding Data
    Location, bands, biometrics for birds caught by various methods. (Source: Producer defined.)

    Project
    The ID representing the group licensed for the catch and considered the owner of the data. (Source: none)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Method
    Code representing method of catching birds. (Source: none)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Capture Date
    Date and time of catch; time is not always included within this attribute. (Source: none)

    Range of values
    Minimum:none
    Maximum:none

    Country
    Country where bird was banded. (Source: none)

    ValueDefinition
    Country names are standardized in database reference table. 

    State/Province
    State or province where bird was banded. (Source: none)

    ValueDefinition
    State/Province names are standardized in database reference table. 

    Location
    Alphanumeric code to define the generalized geographic area of the catch. (Source: none)

    ValueDefinition
    Refer to the document Metadata Location Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Latitude
    Latitude of catch location in decimal degrees. (Source: none)

    Range of values
    Minimum:0
    Maximum:90

    Longitude
    Longitude in decimal degrees. (Source: none)

    Range of values
    Minimum:-180
    Maximum:180

    BirdID
    Unique number identifying an individual. (Source: none)

    Range of values
    Minimum:9401
    Maximum:ongoing

    Species
    Code representing the species of the bird. (Source: Derived from "The North American Bird Banding Manual (electronic version)".)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Metal In
    Metal band number on a retrapped bird upon capture. (Source: none)

    Band number issued by authoritative agencies.

    Flag Color In
    Code representing type of marker used as part of sequence to uniquely mark a bird. Marker present on retrapped bird upon capture. (Source: none)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 
    CBCB:Bands Only: No engraving or flag.

    Flag Code In
    Engraved code on marker on a retrapped bird upon capture. (Source: none)

    Engraved codes or letter sequences based on color band sequences.

    Upper Left In
    Colors recorded on a retrapped bird upon capture. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Lower Left In
    Colors recorded on a retrapped bird upon capture. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Upper Right In
    Colors recorded on a retrapped bird upon capture. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Lower Right In
    Colors recorded on a retrapped bird upon capture. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Metal Out
    Metal band number on a bird upon release. (Source: none)

    Band number issued by authoritative agencies.

    Flag Color Out
    Code representing type of marker used as part of sequence to uniquely mark a bird. Marker present upon release. (Source: none)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 
    CBCB:Bands Only: No engraving or flag.

    Flag Code Out
    Engraved code on marker on a bird upon release. (Source: none)

    Engraved codes or letter sequences based on color band sequences.

    Upper Left Out
    Colors recorded on a bird upon release. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Lower Left Out
    Colors recorded on a bird upon release. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Upper Right Out
    Colors recorded on a bird upon release. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Lower Right Out
    Colors recorded on a bird upon release. Colors are read top down for leg part. (Source: none)

    Free-form text.

    Disp
    One character code indicating condition of the metal band. (Source: Derived from "The North American Bird Banding Manual (electronic version)".)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Status
    Status of the bird at release. (Source: Derived from "The North American Bird Banding Manual (electronic version)".)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Age
    Code for age of bird based on calendar year. (Source: Derived from "The North American Bird Banding Manual (electronic version)".)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Sex
    Code for sex of bird. (Source: Derived from "The North American Bird Banding Manual (electronic version)".)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Culmen
    Length of bill. (Source: none)

    Range of values
    Minimum:none
    Maximum:none
    Units:mm

    Head
    Length of head + bill. (Source: none)

    Range of values
    Minimum:none
    Maximum:none
    Units:mm

    Wing
    Wing chord measurement. (Source: none)

    Range of values
    Minimum:none
    Maximum:none
    Units:mm

    Weight
    Weight of bird. (Source: none)

    Range of values
    Minimum:none
    Maximum:none
    Units:g

    Capture Time
    Time of capture in 24 hour time. Must be formatted with colons as per Microsoft protocol. (Source: none)

    Range of values
    Minimum:00:00
    Maximum:11:59
    Units:24 hour time

    Weight Time
    Time processed in 24 hour time. Must be formatted with colons as per Microsoft protocol. (Source: none)

    Range of values
    Minimum:00:00
    Maximum:11:59
    Units:24 hour time

    Lapsed Minutes
    Difference in minutes from time of capture to time processed. Must be in whole numbers. (Source: none)

    Range of values
    Minimum:0
    Maximum:1440

    Observations
    Comments regarding the bird. (Source: none)

    Free-form text.

    BMI Extent
    Code representing the amount of active body moult observed. (Source: none)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    BMI Stage
    Description of stage of body moult observed. (Source: none)

    A consistent form of reporting body moult stage could not be developed to fit historic and current record keeping by various projects. Metadata for individual projects should be consulted for methodology.

    BMI Plumage
    Code representing the extent of basic/alternate plumage. (Source: none)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Primary Stage 1 to 10
    Stage of growth for each primary feather. (Source: none)

    ValueDefinition
    Refer to the document Metadata Banding Supplement available in the metadata section of <http://report.bandedbirds.org/>. 

    Fat Score
    Representation of degree of fat observed on the bird. (Source: none)

    A coded system for fat score was not developed for this database. Metadata for individual projects should be consulted for methodology in scoring fat.

    Size Adj Mass
    Field reserved for projects recording fat scores and associated measurements or computations. (Source: Metadata for individual projects should be consulted for definition and methodology.)

    Range of values
    Minimum:none
    Maximum:none

    Fat Gram
    Field reserved for projects recording fat scores and associated measurements or computations. (Source: Metadata for individual projects should be consulted for definition and methodology.)

    Range of values
    Minimum:none
    Maximum:none

    Fat Adj Gram
    Field reserved for projects recording fat scores and associated measurements or computations. (Source: Metadata for individual projects should be consulted for definition and methodology.)

    Range of values
    Minimum:none
    Maximum:none

    Fat Mass Ratio
    Field reserved for projects recording fat scores and associated measurements or computations. (Source: Metadata for individual projects should be consulted for definition and methodology.)

    Metadata for individual projects should be consulted for methodology.

    Blood Sample Num
    Notation of labeling assigned to blood sample taken. (Source: none)

    Labeling sequence is at the discretion of the project.

    Entity_and_Attribute_Overview:
    Banding Data: The amount of biometric banding data maintained in this database is at the discretion of each participating research project. Each record will include at a minimum Project, Method, Capture Date, Country, State/Province, Location, Latitude, Longitude, BirdID, Species, Metal Out. All birds color marked as individuals will include Flag Color Out and Flag Code Out.
    Entity_and_Attribute_Detail_Citation: none

  8. What biological taxa does this data set concern?

    Taxonomy:
    Keywords/Taxon:
    Taxonomic_Keyword_Thesaurus: None
    Taxonomic_Keywords: multiple species
    Taxonomic_Keywords: birds
    Taxonomic_Keywords: shorebirds
    Taxonomic_Keywords: black-bellied plover
    Taxonomic_Keywords: Pluvialis squatarola
    Taxonomic_Keywords: dunlin
    Taxonomic_Keywords: Calidris alpina
    Taxonomic_Keywords: long-billed dowitcher
    Taxonomic_Keywords: Limnodromus scolopaceus
    Taxonomic_Keywords: least sandpiper
    Taxonomic_Keywords: Calidris minutilla
    Taxonomic_Keywords: Hudsonian godwit
    Taxonomic_Keywords: Limosa haemastica
    Taxonomic_Keywords: red knot
    Taxonomic_Keywords: Calidris canutus
    Taxonomic_Keywords: ruddy turnstone
    Taxonomic_Keywords: Arenaria interpres
    Taxonomic_Keywords: semipalmated sandpiper
    Taxonomic_Keywords: Calidris pusilla
    Taxonomic_Keywords: short-billed dowitcher
    Taxonomic_Keywords: Limnodromus griseus
    Taxonomic_Keywords: whimbrel
    Taxonomic_Keywords: Numenius phaeopus
    Taxonomic_System:
    Classification_System/Authority:
    Classification_System_Citation:
    Citation_Information:
    Originator: American Ornithologists' Union
    Publication_Date: 1998
    Title: Check-list of North American Birds
    Edition: Seventh
    Geospatial_Data_Presentation_Form: book, pdf
    Online_Linkage: <http://www.aou.org/checklist/north/>
    Classification_System_Modifications:
    Annual revisions by the American Ornithologists' Union are published in The Auk.
    Taxonomic_Procedures: Researchers have existing knowledge of bird identification.
    Taxonomic_Classification:
    Taxon_Rank_Name: Kingdom
    Taxon_Rank_Value: Animalia
    Applicable_Common_Name: animals
    Taxonomic_Classification:
    Taxon_Rank_Name: Phylum
    Taxon_Rank_Value: Chordata
    Applicable_Common_Name: chordates
    Taxonomic_Classification:
    Taxon_Rank_Name: Subphylum
    Taxon_Rank_Value: Vertebrata
    Applicable_Common_Name: vertebrates
    Taxonomic_Classification:
    Taxon_Rank_Name: Class
    Taxon_Rank_Value: Aves
    Applicable_Common_Name: birds
    Taxonomic_Classification:
    Taxon_Rank_Name: Order
    Taxon_Rank_Value: Charadriiformes

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    Sponsors for the creation and maintenance of the website and database: Clear into the Future: a DuPont Delaware Estuary Initiative, Conserve Wildlife Foundation of New Jersey, New Jersey Audubon Society, New Jersey Division of Fish and Wildlife, Delaware Division of Fish and Wildlife, U.S. Fish & Wildlife Service.

  3. To whom should users address questions about the data?

    Jeannine Parvin
    New Jersey Audubon Society: Research Dept.
    Database Administrator
    600 Route 47 North
    Cape May Court House, NJ 08210
    USA

    609-465-3056 (voice)
    bandedbirds@comcast.net

    Contact_Instructions: Best source of contact is email.

Why was the data set created?

Resightings of marked birds allow researchers to estimate adult survival, stopover duration and population size as well as examine patterns of migratory movement and timing. Survival is a critical metric to monitor trend and assess health of migratory shorebird populations. Maintenance of banding and resighting in relational database allows provision of data to meet researchers' analytical needs utilizing specialized queries.

How was the data set created?

  1. What methods were used to collect the data?

    Method 0 of 1
    Type: Field

    Birds are captured using a variety of methods, such as cannon, mist or whoosh netting. Birds are banded, often color marked/flagged and data such as species, age, weight, etc are collected. Metadata for a specific project should be consulted to determine the specifics of capture and data collected.

  2. From what previous works were the data drawn?

    (source 1 of 1)
    Multiple authors for several projects participating in the overall database., Unknown.

    Type_of_Source_Media: field notes
    Source_Contribution:
    All banding data are contributed by numerous research organizations/projects. A complete list of contributors can be found within the metadata section at <http://report.bandedbirds.org/>. Additionally, metadata for each contributor will be posted at this site as it becomes available.

  3. How were the data generated, processed, and modified?

    Date: May-2009 (process 1 of 1)
    The database and associated website went live May 1, 2009. All data collected since that date have been formatted according to database requirements.
    Data collected prior to May 1, 2009 had to be collated and formatted for the upload template. For some projects this required updating method of recording certain attributes to match coding of the database. Most common attributes affected by these changes were breeding plumage extent and body moult index.

    Person who carried out this activity:

    Jeannine Parvin

    bandedbirds@comcast.net

  4. What similar or related data should the user be aware of?

    Multiple authors for several projects participating in the overall database., 20090501, Shorebird Resighting Database: Resighting Data Extraction:, <http://www.bandedbirds.org>.

    Online Links:

    Other_Citation_Details:
    Related resightings to the banding data in the Shorebird Resighting Database.

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    Accuracy is the responsibility of the submitting organization. However, all banding data is proofed by the database administrator, as well, to provide additional error-checking. Any inaccuracies observed, other than obvious data entry errors, are reported to the submitting organization for correction. Specifically, the administrator checks for consistency of coordinates for stated location, adherence to character set for flagging codes, status correlation to banding disposition and comments, consistent use of age codes and correct entry of primary moult. Many attributes are related to a look-up table. The upload programming only allows correct codes. If incorrect codes are detected, the upload process ends and an error report is issued.
    As the data is used in analytical study, errors come to light. Any changes made to the banding data are logged in a report. This document is available for viewing/download by approved researchers.

  2. How accurate are the geographic locations?

    Latitude and longitude coordinates are required for each banding location. The accuracy of the coordinates may vary based on the reporting method. Some projects select a set of coordinates representing an area within which trapping takes place and some pinpoint the coordinates for a catch using Google Earth or a GPS unit. Metadata for a specific project should be consulted to determine the specifics.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    The database is updated as often as datasets are provided in the correct format. All participating projects have the historic banding data uploaded and are submitting data regularly post-field season/expedition. The time lag from field work to submission of data varies by project, but all do submit within a few months of field work.
    The basic biotics such as sex, age, and measurements are submitted by most projects. Completion of other data such as fat and moult varies greatly based on project goals and time of year.

  5. How consistent are the relationships among the observations, including topology?

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints:
Direct access to bulk data is limited to approved researchers. Approval for access is granted by the participating project leaders. Researchers may also request specialized downloads via the database administrator, who will seek the requisite permission from the appropriate project leaders.
The general public may look-up an individual bird's history after registration and acceptance of a Terms of Use agreement.
Use_Constraints:
Approved research users must agree that they will not reproduce, communicate, or otherwise make available the content to which they are permitted access to third parties. Use constraints for special requests are individualized between a researcher requesting data and the projects supplying data. To begin the process, the researcher should contact the database administrator by email. The email should include a personal introduction, the data the researcher is interested in accessing and the anticipated use of the data. The public history available for viewing on the website is for personal use only.

  1. Who distributes the data set? (Distributor 1 of 1)

    Jeannine Parvin
    Database Administrator

    bandedbirds@comcast.net

    Contact_Instructions: contact via email
  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    N/A

  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 28-Feb-2011
Metadata author:
Jeannine Parvin
Database Administrator

bandedbirds@comcast.net

Contact_Instructions: Best form of contact is email.
Metadata standard:
FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata (FGDC-STD-001.1-1999)

Generated by mp version 2.9.13 on Thu Mar 17 15:23:45 2011