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
The Endangered Species Act (ESA) requires the Federal government to designate critical habitat, areas of habitat essential to the species' conservation, for ESA listed species. This dataset is a compilation of the NOAA National Marine Fisheries Service and the U.S. Fish & Wildlife Service designated critical habitat in coastal areas of the United States. Critical habitat is defined as: (1) Specific areas within the geographical area occupied by the species at the time of listing that contain physical or biological features essential to conservation, which may require special management considerations or protection; and (2) specific areas outside the geographical area occupied by the species if the agency determines that the area itself is essential for conservation. See metadata for online linkages to reference full listings of proposed and final critical habitat areas.
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.
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.
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):
- 2018-07-26 00:00:00 - Go to http://ecos.fws.gov/ecp/report/table/critical-habitat.html and download (1) the zip file containing aggregated critical habitat shapes for all species, and (2) the zip file containing individual shapefiles and metadata for all species. Convert USFWS individual polygon shapefiles that are unique (not duplicated by the NMFS data) and that are located in coastal areas except Hawaii to single-part features, project into WGS 1984 World Mercator, and merge resulting features into a single feature class. Organize attributes to retain all information found in section 7 of this document and set the Authority attribute as USFWS.
- 2018-07-26 00:00:00 - Use USFWS and NMFS species websites to assign missing attribute information, where applicable. Check the USFWS ECOS website (https://ecos.fws.gov/ecp) for species listed as "proposed", and delete confirmed species.
- 2018-07-26 00:00:00 - For Hawaii, extract all features from the CRITHAB_POLY.shp located in the Hawaii and NWHI areas (except Hawaiian Monk Seal) and project into WGS 1984 World Mercator. Merge resulting single-part features into a single feature class and organize attributes to retain all information found in section 7 of this document and set Authority attribute to USFWS. Update species with shared common names or with "No Common Name".
- 2018-07-26 00:00:00 - Go to NOAA Fisheries website to view NMFS critical habitat maps and data. Download geospatial Critical Habitat data for any protected species with designated critical habitat. Convert NMFS shapefiles and KMZ files to single-part feature classes in a file geodatabase, then project into WGS 1984 World Mercator. Group feature classes based on location and work on each area at a time. For each area, merge features into a single feature class. Where necessary, convert unique line features (those that do not duplicate polygon features) by buffering by 500 feet and then merging resulting features into the working feature class. Organize attributes to retain all information found in section 7 of this document and set the Authority attribute as NMFS.
- 2018-07-26 00:00:00 - Merge NMFS, USFWS, and Hawaii feature classes into a single feature class, check geometry, and convert multi-part to single-part features.
(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.
- 1.7. Data collection method(s)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 3.1. Responsible Party for Data Management
- 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.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.2. Data storage facility prior to being sent to an archive facility
- 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.
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.
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.
North Charleston, SC
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.