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
When a species is proposed for listing as endangered or threatened under the Endangered Species Act, NOAA National Marine Fisheries Service and the U.S. Fish & Wildlife Service must to the maximum extent prudent and determinable propose and designate critical habitat. This dataset, last updated in April 2017, is a compilation of the proposed critical habitat areas from NOAA and USFWS listed species in coastal areas. To become officially designated as critical habitat, an area is published as a proposed Federal regulation in the Federal Register. After a period of public review, the comments are adjudicated and the final boundaries of the critical habitat area are published in the Federal Register. When areas are officially designated, they move into the Coastal Critical Habitat Designations layer on MarineCadastre.gov. Because MarineCadastre.gov updates data on a pre-defined cycle, it is possible that proposed layers have been adopted or removed prior to being reflected in this layer. It is important to keep in mind that maps published before May 31, 2012 were only for illustrative purposes and the Federal Register text descriptions should be used for authoritative purposes. For designations published after May 31, 2012, the maps (and any clarifying textual descriptions) are the definitive source for critical habitat boundaries. 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):
- 2017-03-01 00:00:00 - + Go to http://www.nmfs.noaa.gov/pr/species/criticalhabitat.htm and download all zip files referenced on the page + Convert shapefiles and kml files to feature classes and project into NAD83 into a file gdb + Group feature classes based on location and work on each area at a time + For each area, merge features into a single feature class and organize attributes to retain all information found in section 7 of this document and delete any superfluous attributes + Explode all features + Shorelines were then adjusted to fix miss-aligning features to the others in the same area + Merge these resulting feature classes into a single feature class and note in the attributes the authority as NMFS + For hawksbill turtle, green turtle, gulf sturgeon, leatherback turtle, and smalltooth sawfish, data will need to be converted from line to polygon, then added into the main feature class + Go to http://ecos.fws.gov/ecp/report/table/critical-habitat.html and download the two zip files at the top of the page + From the individual species zip, add all polygon shapefiles to a new map + Remove any shapefiles that are not in a coastal area, all shapefiles that are duplicated by the NMFS data, and all shapefiles located in Hawaii + For all that remain, export and project into NAD83 in a file gdb + Group feature classes based on location and work on each area at a time + For each area, merge features into a single feature class and organize attributes to retain all information found in section 7 of this document and delete any superfluous attributes + Explode all features + Merge these resulting feature classes into a single feature class and note in the attributes the authority as USFWS + For Hawaii, add the CRITHAB_POLY.shp to a map and select all features in the Hawaii and NWHI areas (except Hawaiian Monk Seal) and export into a file gdb and project into NAD83 + Merge features into a single feature class and organize attributes to retain all information found in section 7 of this document and delete any superfluous attributes + Explode all features and note in the attributes the authority as USFWS + For species in Hawaii, common names were updated for species where the common name was repeated over many species, or for those with "No Common Name" + Merge NMFS, USFWS, and Hawaii feature classes into a single feature class and explode all features + Fill out missing attribute information from USFWS and NMFS species websites + Delete all superfluous fields + Check geometry and project data into WGS 1984 Auxiliary Sphere + Double check status of species listed as "proposed" using https://ecos.fws.gov/ecp/ + Delete confirmed species that area "final"
(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.6. Type(s) of data
- 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.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.
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.