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 are a derived product of the NOAA VDatum tool and they extend the tool's Mean Higher High Water (MHHW) tidal datum conversion inland beyond its original extent.
VDatum was designed to vertically transform geospatial data among a variety of tidal, orthometric and ellipsoidal vertical datums - allowing users to convert their data from different horizontal/vertical references into a common system and enabling the fusion of diverse geospatial data in desired reference levels (http://vdatum.noaa.gov/). However, VDatum's conversion extent does not completely cover tidally-influenced areas along the coast. For more information on why VDatum does not provide tidal datums inland, see http://vdatum.noaa.gov/docs/faqs.html.
Because of the extent limitation and since most inundation mapping activities use a tidal datum as the reference zero (i.e., 1 meter of sea level rise on top of Mean Higher High Water), the NOAA Office for Coastal Management created this dataset for the purpose of extending the MHHW tidal datum beyond the areas covered by VDatum. The data do not replace VDatum, nor do they supersede the valid datum transformations VDatum provides. However, the data are based on VDatum's underlying transformation data and do provide an approximation of MHHW where VDatum does not provide one. In addition, the data are in a GIS-friendly format and represent MHHW in NAVD88, which is the vertical datum by which most topographic data are referenced.
Data are in the UTM NAD83 projection. Horizontal resolution varies by VDatum region, but is either 50m or 100m. Data are vertically referenced to NAVD88 meters.
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):
- 2016-01-01 00:00:00 - Buffered Census Counties offshore by 6km. Source VDatum .gtx files were shifted from positive east longitude values to negative west values. The tss grid was subtracted from the MHHW tidal grid. This step resulted in the MHHW tidal datum referenced to an orthometric datum, specifically NAVD88. Each region's orthometric-referenced tidal grid was converted to a point file, where each cell's centroid is a point containing the value of the cell. The point data were then clipped to county boundaries that extend ~6 km offshore to limit the number of points in the interpolation below. 10 and 12-digit hydrologic unit code (HUC) watershed boundaries that intersect the point data were selected. Where VDatum regions overlapped for an area, the VDatum bounding polygons were used to remove points outside of these areas. Where there was still overlap, points from either the higher resolution region or regions covering bays and estuaries were used. Using the Inverse Distance Weighted interpolation method, the point data were used to interpolate the NAVD88-based tidal surface inland, using the selected HUC boundaries as barriers to interpolation. This approach uses only points within the watershed and limits the interpolation to areas only within the watershed. This process was done for both 10 and 12-digit HUC watersheds. The resulting interpolated surfaces were then nested or mosaicked, where the HUC 12 interpolated surface was the primary raster and the HUC 10 surface the secondary. A Euclidean Allocation approach was then used to extend the conversion further inland to areas where the HUC 10 watersheds did not cover the study area. County boundaries were used as the inland limit instead of watersheds since most topographic data are collected and/or available on a county basis.
(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.6. Type(s) of data
- 1.7. Data collection method(s)
- 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.
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.