Data Management Plan
GUID: gov.noaa.nmfs.inport:68025 | 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 section provides the Simplified Geographic Description for each unit designated as Nassau Grouper Critical Habitat.The 20 Designated Critical Habitat Units for Nassau Grouper include: Navassa Island Unit. Waters surrounding Navassa Island. Area = 2.46 sq. km.Puerto Rico Unit 1 - Mona Island and Monito. Waters surrounding Mona Island and Monito to the 50m contour. Area = 30.65 sq. km.Puerto Rico Unit 2 - Desecheo Island. Waters surrounding the island to the 50m contour. Area = 4.28 sq. km.Puerto Rico Unit 3 - Southwest. Waters off the southwest coast of the Puerto Rico main island. Area = 112.39 sq. km.Puerto Rico Unit 4 - Northeast. Waters off the northeast coast of the Puerto Rico main island. Area = 48.75 sq. km.Puerto Rico Unit 5 - Vieques Island. Waters off the west and northeast, east, and southeast coasts of the island. Area = 9.49 sq. km.Puerto Rico Unit 6 - Culebra/Culebrita Islands. The Culebra area consists of waters off the southeastern Culebra coastline. The Culebrita area consists of waters off the western and southern coasts of the island. Area = 4.15 sq. km.United States Virgin Island Unit 1- St Thomas. Waters off the east coast of St. Thomas Island and waters off the southwest, south, and southeast coast of the Water Island. Area = 9.18 sq. km.United States Virgin Island Unit 2- St. John. Waters off the east coast of the island. Area = 6.55 sq. km.United States Virgin Island Unit 3- St. Croix. Waters off the east end of St. Croix Island and waters off the north coast of Buck Island. Area = 50.35 sq. km.Florida Unit 1 – Biscayne Bay/Key Largo. Waters south of Rickenbacker Causeway, including portions of waters from the coastline into Biscayne Bay, and waters off the eastern coastline to 80°29'21" W, 25° 01' 59" N. Area = 1,279.69 sq. km.Florida Unit 2 - Marathon. Waters off the southern shoreline approximately between Knights Key to 80°55'51"W, 24° 46' 26" N. Area = 172.38 sq. km.Florida Unit 3 - Big Pine Key to Geiger Key. Waters off the south side of coastline and US 1 from approximately Geiger Key to Big Pine Key. Area = 372.37 sq. km.Florida Unit 4 - Key West. Shoal waters south of Woman Key. Area = 127.09 sq. km.Florida Unit 5 - New Ground Shoal. New Ground Shoal waters. Area = 31.04 sq. km.Florida Unit 6 - Halfmoon Shoal. Halfmoon Shoal waters. Area = 33.62 sq. km.Florida Unit 7 - Dry Tortugas. Waters encompassing Loggerhead Key and waters surrounding Garden Key and Bush Key. Area = 4.43 sq. km.Spawning Site Unit 1 - Bajo de Sico. All waters encompassed by 100m isobath bounded in the Bajo de Sico spawning area bound within the following coordinates: A) 67°26’13â€W, 18°15’23â€N, B) 67°23’ 08â€W, 18°15’26â€N, C) 67°26’ 06â€W, 18°12’55â€N, and D) 67°26’ 13â€W, 18°12’56â€N. Area = 10.74 sq. km.Spawning Site Unit 2 - Grammanik Bank/Hind Bank. All waters which make up the Hind Bank and the Grammanik Bank, interconnecting waters between these banks, and waters extending out to the 200 fathom line directly south from Grammanik Bank. Area = 59.69 sq. km. Spawning Site Unit 3 - Riley's Hump. All waters encompassing Riley's Hump (centroid 83.1085642°W 24.4948905°N) out to the -35m isobath on the north, west, and east side of the hump, and extending out to the 50m isobath on the south side of the hump to include the escarpment on the southern face of the bank. Area=15.35 sq. km.Source of Base Data for Unit Boundaries: The shoreline was created using the existing Acropora critical habitat designation (from NOAA NCCOS Benthic Habitat Mapping 2000-2002 - land and mangrove attribute combined for shoreline). For PR and USVI units, shoreline data using The NCCOS Benthic Habitat Mapping program provides baseline data and maps at https://coastalscience.noaa.gov/project/benthic-habitat-mapping-puerto-rico-virgin-islands/. For the Continental US, this shoreline is consistent with the US Medium Resolution Shoreline. Contours were derived from the National Geophysical Data Center’s 2004 U.S. Coastal Relief Model https://www.ngdc.noaa.gov/mgg/coastal/crm.html. The NCCOS Benthic Habitat Mapping program provides data and maps at http://products.coastalscience.noaa.gov/collections/benthic/default.aspx, which was used to pull in substrate data. For the Florida Units, benthic substrate and bathymetry data were pulled from the FWC Florida Unified Reef Tract at https://myfwc.com/research/gis/fisheries/unified-reef-map/. Benthic data was also used from The Nature Conservancy and can be downloaded here: https://sites.google.com/view/caribbean-marine-maps. For Spawning Site Unit 3 - Riley's Hump, bathymetry contours (i.e. isobaths) were pulled from the NCEI's CUDEM, or Continuously Updated Digital Elevation Models. (https://noaa.maps.arcgis.com/home/item.html?id=bf72d32c6a00407bb67a285845a7fa32) The CUDEM Raster was downloaded (Global Mosaic Elevation Values) and clipped to the site in ArcPro. The Contour Tool was set to 5m intervals. The CUDEM is built in 10m increments, as noted using the 1/3 arcseconds. Did not use the 1/9 arc second model, which corresponds to 3 meter increments. The CUDEM uses LiDAR data and is an orthometric vertical datum, and compiles data from NGDC, NOS, USGS, NMFS, etc. For more information, please vist: https://www.ncei.noaa.gov/products/coastal-relief-model. Riley's Hump (the geographic feature, not the critical habitat unit) was identified as the fully enclosed -30m hump located at 83.1085642°W 24.4948905°N (centroid). Standardized metadata has been prepopulated for the Fields and Values and the standard spatial reference is the World Geodetic System 1984 geographic coordinate system (GCS_WGS_1984, EPSG well-known identifier 4326).Attribute Values:Shape = Feature Class, Polygon Data.ID = Species IDScientific Name = Genus speciesCommon Name = Common Name of speciesListing Status = Federal status of a taxon under the federal Endangered Species Act. Critical Habitat Status = Status of Critical Habitat Designation (i.e. Proposed or Designated)Unit = Location of Identified Critical HabitatTaxon = TaxonLead Office = NMFS Regional OfficeFederal Register Notice = Public official notice of RulePublication Date = Publication Date of Federal Register Notice Effective Date = Effective Date of RuleArea SqKm = Area of Unit in Square KilometersCreate Date = Last Date Polygon and Attribute Data were ModifiedNotes = notesInPort URL = MetaData URL Link (InPort)Habitat Type = general location of critical habitatseCFR = Electronic Code of Federal RegulationsShape_Length = dynamic geodatabase field. Automatically calculated in the units of the output coordinate system specified by the Spatial Reference parameter by ESRI. Shape_Area = dynamic geodatabase field. Automatically calculated in the units of the output coordinate system specified by the Spatial Reference parameter by ESRI.
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.
W: -83.135404, E: -64.562313, N: 25.7482, S: 17.686503
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):
(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)
- 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.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.
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.