Data Management Plan
GUID: gov.noaa.nmfs.inport:66106 | 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 Digital Elevation Model (DEM) created for the Ocean Reports application is a combination of the NCEI Coastal Relief Model (CRM) and the GEBCO (2014) 1 arc-minute 2-dimensional bathymetric datasets. All components of the two models were resampled to 3 arc-seconds (as needed) and then mosaicked together to form the final output grid. The CRM integrates offshore bathymetry with land topography into a seamless representation of the coast. The CRM has a 3 arc-second resolution, except Alaska (24 arc-seconds), and spans the U.S. East and West coasts, the northern coast of the Gulf of Mexico, Puerto Rico, Hawaii, and Alaska, reaching out to and beyond the continental slope. Land and water portions of the CRM were used to construct the final DEM. The GEBCO data has a 1 arc-minute resolution and was supplemented in deeper portions of the ocean where the CRM data are not available. Where overlap occurred, CRM data were given precedence over GEBCO data. It should be noted that these are the best available data at the spatial extent needed (the entire U.S. Exclusive Economic Zone), but higher-resolution digital elevation models may be available for local or regional 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.
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):
Process Steps:
- 2018-08-01 00:00:00 - (1) Bathymetry grids were downloaded from each of the data sources in NetCDF format. (2) The GEBCO and Alaska CRM grids were resample to 3 arc-seconds to match the remaining CRM regional grids. During resampling the GEBCO grid was broken up in to four equal parts (NE, NW, SE and SW) to reduce the memory load during processing. (3) CRM data that overlapped each of the four GEBCO parts were then blended on to the GEBCO data. CRM data was given priority over GEBCO data, where it was available. (4) The four sections (NE, NW, SE and SW) were then combined to create the final grid encompassing the region of interest. (5) File size: 12 GB (NetCDF received from Michael Coyne), converted to raster (40 gb), clipped to the EEZ and coastline file leaving a file size 16.4 gb in a file geodatabase for the US waters. However, these data must be converted to a GeoTiff for final delivery. (6) Projected data to WGS 1984 World Mercator (ID: 3395), and 7) Project to NAD83 GRS80 4269
(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.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)
- 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.
https://marinecadastre.gov/oceanreports/
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.
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.