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
These data represent critical habitat proposed for designation (November 27, 2020, 85 FR 76302) under the Endangered Species Act for the lobed star coral (Orbicella annularis). Critical habitat is defined as all marine waters in the defined depth ranges relative to mean low water.Within the defined boundaries, critical habitat does not include: - areas subject to the 2014 Naval Air Station Key West Integrated Natural Resources Management Plan- areas where the essential feature (i.e., reproductive, recruitment, growth, and maturation habitat) does not occur- all managed areas that may contain natural hard substrate but do not provide the quality of substrate essential for the conservation of threatened corals, such as dredged navigation channels, shipping basins, vessel berths, and active anchorages. Specific federally-authorized channels and harbors not included in the designation are: St. Lucie Inlet, Palm Beach Harbor, Hillsboro Inlet, Port Everglades, Bakerâs Haulover Inlet, Miami Harbor, Key West Harbor, Arecibo Harbor, San Juan Harbor, Fajardo Harbor, Ponce Harbor, Mayaguez Harbor, St. Thomas Harbor, Christiansted Harbor.- artificial substrates such as fixed and floating structures, aids-to-navigation (AToNs), seawalls, wharves, boat ramps, fishpond walls, pipes, submarine cables, wrecks, mooring balls, docks, and aquaculture cages- the restricted area managed by the South Florida Ocean Measuring Facility.
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):
- Bathymetry source: NGDC Coastal Relief Model for Puerto Rico & U.S. Virgin Islands (Vol. 9), Florida and Eastern Gulf of Mexico (Vol. 3), and Central Gulf of Mexico (Vol. 4). Using ESRI's ArcGIS ArcMap software and Spatial Analyst extension, ran the focal statistics tool, which smoothed blocky contours. Then Surface >Contour tool with base contour set to 0.99999, which will also smooth some blockiness. Converted the polyline to a polygon. Deleted very small polygons/ or polys for depths +/- 1m. NOAA NCCOS provided bathymeric contours for Navassa based on sidescan sonar surveys.
- A detailed shoreline was used for Puerto Rico and the Virgin Islands from NOAA National Centers for Coastal Ocean Science (NCCOS), by selecting 'Land' and 'mangrove' polygons. Used NOAA medium resolution vector shoreline for Florida to create land polygon. Erased the bathymetry polygons with the land/mangrove polygons. For Florida shoreline, or shoreward side of the critical habitat polygon, used Florida Fish & Wildlife Commission (FWC) nearshore bathymetry (digitized from NOAA nautical charts), FWC 1:24,000 scale shoreline, COLREG lines, and intercouncil boundary between South Atlantic and Gulf of Mexico Fishery Management Councils at the mouths of bays and inlets, and information from the U.S. Navy for exclusions. In areas where shallow contours intersected the shoreline, the contours were edited so they would not overlap in the GIS layer and on the maps.
(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)
- 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.
St. Petersburg, FL
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.