Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:75048 | Published / External
InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.
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
NOAA's Coastal Ocean Reanalysis (CORA) couples long-term water level observations with hydrodynamic modeling to create historical information between tide stations to bridge gaps in service and more equitably serve the Nation's coastal communities. CORA water levels are simulated with ADvanced CIRCulation (ADCIRC) for ocean circulation modeling and coupled with a phase-averaging model called Simulating WAves Nearshore (SWAN) to produce surface gravity wave spectra and account for time-averaged wave contributions. Coastal water level observations from NOAA's Center for Operational Oceanographic Products and Services (CO-OPS) National Water Level Observation Network (NWLON) are low-pass filtered and assimilated into the model to account for long-term sea level variability and to reduce model errors, and validate results. The domain of this reanalysis spans the Gulf of America, Atlantic (East), and Caribbean coastlines (or CORA-GEC).
The reanalysis (1979-2022) was performed through the partnership of NOAA National Ocean Service (NOS) and University of North Carolina's (UNC) Institute of Marine Sciences and Renaissance Computing Institute (RENCI). This modeled dataset is meant to have secondary derived datasets including but not limited to daily maximums (daily maxes), monthly means, extremes and month high tide flooding predictions. In addition, the domain of the analysis will be expanded to the Pacific and the dataset to be included when it becomes available.
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):
Lineage Statement:
Each year of the reanalysis is run independently to simplify overall simulation, staging, processing, and management of resources on HPC clusters. This also allows for concurrent simulation of multiple years.
Process Steps:
- Compute year-long prior/initial prediction of historical water levels is computed with the ADCIRC model using only tides and meteorological forcing
- Perform initial/ prior skill assessment by comparing Prior water levels to NWLON observations and establish prior error timeseries and statistics.
- Map errors onto ADCIRC grid by generating Dynamic Water Level Correction (DWLC) terms.
- Compute posterior prediction through ADCIRC forcing of astronomical tides, ERAS meteorology and error surfaces (DWLC).
- Perform final/ posterior skill assessment by comparing posterior water levels to NOWLON observations and establishing posterior error timeseries and statistics.
(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.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.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.
There are no constraints.
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://noaa-nos-cora-pds.s3.amazonaws.com/index.html
https://registry.opendata.aws/noaa-nos-cora/
https://tidesandcurrents.noaa.gov/cora.html
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.