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 proposed critical habitat designation is based on the best available data and includes only in-water areas containing the essential features. Please see the attribute data, which describe the essential features are contained in each unit of critical habitat. The essential features are defined as follows:(1) Reproductive (North Atlantic, South Atlantic, Central North Pacific, Central South Pacific, and Central West Pacific DPSs). From the mean high water line to 20 m depth, sufficiently dark and unobstructed nearshore waters adjacent to nesting beaches designated as critical habitat by U.S. Fish and Wildlife Service (USFWS), to allow for the transit, mating, and internesting of reproductive individuals and the transit of post-hatchlings.(2) Migratory (North Atlantic and East Pacific DPSs). From the mean high water line to 20 m depth (North Atlantic DPS) or 10 km offshore (East Pacific DPS), sufficiently unobstructed waters that allow for unrestricted transit of reproductive individuals between benthic foraging/resting and reproductive areas.(3) Benthic foraging/resting (North Atlantic, South Atlantic, East Pacific, Central North Pacific, Central South Pacific, and Central West Pacific DPSs). From the mean high water line to 20 m depth, underwater refugia and food resources (i.e., seagrasses, macroalgae, and/or invertebrates) of sufficient condition, distribution, diversity, abundance, and density necessary to support survival, development, growth, and/or reproduction.(4) Surface-pelagic foraging/resting (North Atlantic DPS). Convergence zones, frontal zones, surface-water downwelling areas, the margins of major boundary currents, and other areas that result in concentrated components of the Sargassum-dominated drift community, as well as the currents which carry turtles to Sargassum-dominated drift communities, which provide sufficient food resources and refugia to support the survival, growth, and development of post-hatchlings and surface-pelagic juveniles, and which are located in sufficient water depth (at least 10 m) to ensure offshore transport via ocean currents to areas which meet forage and refugia requirements.Disclaimer: the spatial data provided here display an approximation of the boundaries for the essential features described above. For example, in some areas critical habitat occurs from the mean high water line to 20 m depth, and the spatial data approximate this area. Use of these data do not replace the ESA section 7 consultation process; however, these data may be a first step in determining whether a proposed federal action overlaps with proposed critical habitat.USE LIMITATIONS*** Attribution *** Whenever NMFS material is reproduced and re-disseminated, we request that users attribute the material appropriately. Pursuant to 17 U.S. C. 403, parties who produce copyrighted works consisting predominantly of material created by the Federal Government are encouraged to provide notice with such work(s) identifying the U.S. Government material incorporated and stating that such material is not subject to copyright protection. Please cite the this dataset as: NOAA Fisheries Service. Endangered Species Act Critical Habitat Geodatabase. Silver Spring, MD: National Oceanic and Atmospheric Administration (NOAA), National Marine Fisheries Service (NMFS), Office of Protected Resources (OPR). ***No Warranty*** The user assumes the entire risk related to its use of these data. NMFS is providing these data "as is," and NMFS disclaims any and all warranties, whether express or implied, including (without limitation) any implied warranties of merchantability or fitness for a particular purpose. No warranty expressed or implied is made regarding the accuracy or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. It is strongly recommended that careful attention be paid to the contents of the metadata file associated with these data to evaluate dataset limitations, restrictions or intended use. In no event will NMFS be liable to you or to any third party for any direct, indirect, incidental, consequential, special or exemplary damages or lost profit resulting from any use or misuse of this data. *** Proper Usage *** The information on government servers are in the public domain, unless specifically annotated otherwise, and may be used freely by the public. Before using information obtained from this server, special attention should be given to the date and time of the data and products being displayed. This information shall not be modified in content and then presented as official government material. The dataset should not be used to infer information regarding the existence or details of other marine features or resources, including, but not limited to, navigable waters, coastlines, bathymetry, submerged features, or man-made structures. Users assume responsibility for determining the appropriate use of this dataset. *** Shorelines/Bathymetry Layers *** The accuracy of this dataset is dependent upon the accuracy and resolution of the datasets (e.g. shoreline, hydrography, bathymetry, shared administrative boundaries) used in the creation process. Source datasets used are specified in the metadata. These data sources were selected for their suitability to a broad audience, and may not be suitable for specific uses requiring higher-resolution information. Coastlines and water body boundaries change. Unless otherwise noted, assume the boundary reaches the most current river, estuary, or coastal shoreline delineation available. It does not include land. For shorelines, we used NOAAâs Continually Updated Shoreline Product (CUSP), where available. Where not available, we used Coastal Change Analysis Program C-CAP shoreline data. For bathymetry, we used the following datasets:North Atlantic: USGS Bathymetric Contours for East Coast 2013South Atlantic: Depths used for the proposed critical habitat designation of the lobe star coral.East Pacific: California. Department of Fish and Game. Marine Resources Region 2001.Central Pacific: University of Hawaii Pacific Islands Benthic Habitat Mapping Center and depths used for the proposed critical habitat designation of the Pacific coral, Acropora globiceps.Standard spatial reference is the World Geodetic System 1984 geographic coordinate system (GCS_WGS_1984, EPSG well-known identifier 4326).
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):
(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.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the data
- 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.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
- 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.
Silver Spring, MD
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.