Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:70135 | Published / External
This is an outdated version of the NOAA Data Management Plan template. 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. Please see the Data Management Plan Help Guide to learn more.
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
High tide flooding is the overflow or excess accumulation of water that covers typically dry coastal land and occurs during high tides. As relative sea levels rise, high tide flooding (HTF) is occurring more frequently, even on sunny days. HTF creates short term impacts like road closures, overflowing storm drains, and temporary business closures. Over the long term, recurrent HTF causes more severe impacts like damage to below-ground infrastructure and degraded wetlands.
Through NOAA's National Ocean Service (NOS), the Center for Operational Oceanographic Products and Services (CO-OPS) and its predecessors have gathered oceanographic data along our nation's coasts for over 200 years to protect life, property, and the environment. Serving both the public and other government agencies, CO-OPS is the authoritative source for accurate, reliable, and timely water-level and current measurements that support safe and efficient maritime commerce, sound coastal management, and recreation. As part of those roles, CO-OPS offers a suite of interactive products that helps communities understand when, where, and how often high tide flooding may occur along the coast to better inform their coastal flood planning and mitigation efforts. The suite includes a summary of historical HTF days as well as Monthly and Annual HTF Outlooks which are produced for specific stations.
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:
CO-OPS updates high tide flooding likelihoods monthly using a methodology based on Dusek et al. 2023 (see URL 1 above). Flooding likelihoods are derived from a probabilistic model that incorporates tide predictions, sea level rise trends, and seasonal changes in coastal sea level to predict the potential that a higher than normal high tide may exceed established NOS flood thresholds. During these periods, high tide flooding may occur in flood-prone areas.
Process Steps:
- Verified water level data from a water level station (the verified 6-minute data, and the secondary datasets of highs and lows (except for Great Lakes stations), hourly heights, daily means (Great Lakes stations only), and monthly means) are made available roughly one month after collection. This is a 2-step process where one person reviews the data, and if necessary, removes erroneous data or fills gaps by either using data from the station's back-up sensor, predictions for that station, or similar data from proximal stations. With exception of the corrected errors or filled gaps, most preliminary (raw) 6-minute data become the verified 6-minute data. Secondary datasets are also generated during this step. Then a second person reviews the work of the first, and when satisfied, marks the data in the database as "verified." The order in which the 300+ water level stations are processed each month is random, to prevent the same stations or geographical locations from always being first or last. Verified water level data are made available on a monthly basis for the previous month's data.
- Water level gauges mounted along the U.S. coastlines (including Pacific and Caribbean Islands) employ acoustic or microwave technology (with pressure sensors as the back-up sensor). Historic stations employed paper trace rolls (marigram and ADR rolls) until the late 1990's. The type of sensor used today depends on the station's environment. The lack of infrastructure may prevent the use of the desired sensor type at that location.
(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)
- 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.
None.
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://tidesandcurrents.noaa.gov/high-tide-flooding/monthly-outlook.html
https://github.com/NOAA-CO-OPS/Seasonal_High_Tide_Flooding_Prediction
https://api.tidesandcurrents.noaa.gov/dpapi/prod/
https://tidesandcurrents.noaa.gov/inundationdb/
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.