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 were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the Sea Level Rise and Coastal Flooding Impacts Viewer. It depicts potential sea level rise and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at sea level rise and coastal flooding impacts. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The Sea Level Rise and Coastal Flooding Impacts Viewer may be accessed at: https://coast.noaa.gov/slr.
This metadata record describes the Marsh Migration data displayed in the SLR Viewer. These data represent the potential distribution of each wetland type based on their elevation and how frequently they may be inundated under potential future SLR scenarios, from 0 to 10ft of SLR. As sea level rises, higher elevations will become more frequently inundated, allowing for marsh migration landward. At the same time, some lower-lying areas will be so often inundated that the marshes will no longer be able to thrive, becoming lost to open water. These data are based on the assumption that specific wetland types exist within an established tidal elevation range, based on an accepted understanding of what types of vegetation can exist given varying frequency and time of inundation, as well as salinity impacts from such inundation.
The data were created using the NOAA OCM Coastal Change Analysis Program (CCAP) land cover data, the SLR Viewer's digital elevation models, and NOAA VDatum tidal surfaces.
The data are available in 0.5ft increments of net sea level change, from 0 to 10ft. To determine the appropriate level, the user must identify a SLR scenario and an applicable accretion rate for the area of interest. The easiest way to do this is to go into the SLR Viewer's Marsh Migration tab; select a location, SLR scenario, and timeframe; and identify the closest available 0.5ft increment to what the viewer shows. For more information, see the tutorial at https://coast.noaa.gov/elearning/marshmigration/.
Data are available for download at https://coast.noaa.gov/htdata/raster1/landcover/bulkdownload/slr_wetland/.
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):
- A tidal zones raster is created for each increment of sea level rise (SLR) using a 10m DEM of a state and tidal surfaces created from VDatum representing MLLW, MTL, and MHHW. In addition, tidal surfaces for MHHWS (MHHW Spring) and a freshwater wetland-upland transition boundary are created from the VDatum MHHW tidal surface. This zones layer is an integer raster where each zone (i.e., MTL to MHHW) is coded. Select upland classes in the land cover source data are recoded in preparation for the next steps, resulting in a modified land cover raster where: 0 = Background 2 = High Intensity Developed 3 = Medium Intensity Developed 4 = Low Intensity Developed 5 = Developed Open Space 8 = All Uplands 13 = Palustrine Forested Wetland 14 = Palustrine Scrub/Shrub Wetland 15 = Palustrine Emergent Wetland 17 = Brackish/Transition Wetland 18 = Estuarine Wetland 19 = Unconsolidated Shore 21 = Open Water The tidal zones raster for each SLR increment (0-10ft in 0.5ft increments) is then combined with the recoded land cover raster for the state to create a raster where pixels have both a tidal zone and a land cover code. Using a ruleset that says which land cover types exist in each tidal zone, the combined raster is recoded to a new land cover raster where the land cover class has changed based on the tidal zone. See https://coast.noaa.gov/data/digitalcoast/pdf/slr-marsh-migration-methods.pdf for more detailed information.
(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.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.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.