Data Management Plan
GUID: gov.noaa.nmfs.inport:54796 | Published / External
Data Management Plan
DMP Template v2.0.1 (2015-01-01)
Please provide the following information, and submit to the NOAA DM Plan Repository.Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
This data set contains sensitive biological resource data for wading birds, shorebirds, waterfowl, raptors, diving birds, seabirds, passerine birds, and gulls and terns in Southwest Florida. Vector polygons in this data set represent bird nesting, migratory staging, wintering sites, and vulnerable occurrences. Vector points represent bird nesting sites. Species specific abundance, seasonality, status, life history, and source information are stored in relational data tables (described below) designed to be used in conjunction with this spatial data layer.
This data set comprises a portion of the ESI data for Southwest Florida. ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil. The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. See also the BIRDSPT data layer, part of the larger Southwest Florida ESI database, for additional bird information.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
This reflects the extent of all land and water features included in the overall Southwest Peninsular Florida ESI study region. The bounding box for this particular feature class may vary depending on occurrences identified and mapped.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
Lineage Statement:
Three main sources of data were used to depict bird distribution and seasonality for this data layer: 1) personal interviews with resource experts from Audubon Florida, U.S. Fish and Wildlife Service, Florida Fish and Wildlife Conservation Commission (FWC), Rookery Bay National Estuarine Research Reserve (NERR), Sanibel-Captiva Conservation Foundation, and National Park Service (NPS); 2) various digital data sets from the above agencies (including the Florida Natural Areas Inventory (FNAI) data set); and 3) published and unpublished reports and documents.
Process Steps:
- 2017-02-01 00:00:00 - BIRD Polygons: Shorebirds, diving birds, gulls and terns: Survey data on locations of breeding, migrating, and/or wintering shorebirds, diving birds, gulls, and terns were provided by various agencies via shapefiles, spreadsheets, primary literature, and expert local knowledge, and was supplemented with information from eBird. In general, data from the various data sources were compiled and either mapped to habitat, park or refuge, or specific locations, per expert recommendations. Mapping qualifiers reflect the type of survey data used to map the species. For example, a species from a wintering shorebird survey has a mapping qualifier of "Wintering", but that species may be present at other times of year as well, which would be reflected in the seasonality. Additional source information is provided in the data tables. Waterfowl: Waterfowl are not found in large numbers in Southwest Florida. Waterfowl were mapped on nearshore waters using expert knowledge from Audubon Florida and in Ten Thousand Islands NWR using survey data. Gulf of Mexico seabirds Species lists and seasonalities of nearshore and offshore seabirds in the Gulf of Mexico were provided by Audubon Florida. Raptors: Osprey are ubiquitous throughout the area, so they were mapped only where specific expert knowledge or survey data were available, although they can occur in appropriate habitats (coastal wetlands) throughout the study area. Swallow-tailed kite were mapped based on expert knowledge. Rare birds: Cape Sable seaside sparrow (FE, SE) subpopulation boundaries were provided by Everglades National Park, and they were mapped as polygons. Other rare bird occurrence data was provided by the FNAI data set. The above digital and/or hardcopy sources were compiled by the project biologist to create the BIRD Polygons data layer. Depending on the type of source data, three general approaches are used for compiling the data layer: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:24,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. See the Lineage section for additional information on the type of source data for this data layer. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the BIRD Polygons data layer are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
- 2017-02-01 00:00:00 - BIRD Points: Colonial waterbird nesting areas: The South Florida Wading Birds reports, Audubon FL, Charlotte Harbor Aquatic Preserve, Estero Bay Aquatic Preserve, Everglades National Park, and Rookery Bay NERR provided nesting data for colonial waterbirds from 2011 to 2015 (in some cases not all years were available for each site). Each nesting colony location was mapped as a nest point. The maximum number of nesting pairs observed for each species for each colony during the time period of available data was reported in the ESI. Overall, species mapped using colonial waterbird datasets include: anhinga, black-crowned night-heron, brown pelican, cattle egret, double-crested cormorant, glossy ibis, great blue heron, great egret, green heron, little blue heron, reddish egret, roseate spoonbill, snowy egret, tricolored heron, white ibis, wood stork, and yellow-crowned night-heron. Shorebirds, diving birds, gulls and terns: Survey data on locations of breeding shorebirds, diving birds, gulls, and terns were provided by various agencies via shapefiles, spreadsheets, primary literature, and expert local knowledge. Raptors: Bald eagle nest survey data (2015) were provided by FWC. Nest locations were mapped as points in the ESI. Osprey are ubiquitous throughout the area, so they were mapped only where specific expert knowledge or survey data were available, although they can occur in appropriate habitats (coastal wetlands) throughout the study area. The above digital and/or hardcopy sources were compiled by the project biologist to create the BIRD Points data layer. Depending on the type of source data, three general approaches are used for compiling the data layer: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:24,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. See the Lineage section for additional information on the type of source data for this data layer. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the BIRD Points data layer are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
Missing/invalid information:
- 1.7. Data collection method(s)
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
None
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.