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 (SLR) 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: http://www.coast.noaa.gov/slr This metadata record describes the Honolulu Weather Forecast Office (HFO WFO) digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Sea Level Rise and Coastal Flooding Impacts Viewer described above. The DEMs created for this project were developed using the NOAA National Weather Service's Weather Forecast Office (WFO) boundaries. This DEM includes the best available lidar known to exist at the time of DEM creation that met project specifications for the Honolulu WFO, which includes the following islands in Hawaii: Kauai, Oahu, Molokai, Maui, Lanai, and Hawaii. The DEM is derived from multiple sources. 1. 2006 Hawaii FEMA Lidar - acquired by FEMA along south shores of islands 2. 2007 USACE Pacific Islands Lidar: Hawaiian Islands - acquired by USACE and Hawaii State Civil Defense along north and windward facing shores of islands Hydrographic breaklines were delineated from LiDAR intensity imagery generated from the LiDAR datasets. The final DEM is hydro flattened such that water elevations are less than or equal to -0.5 meters. The DEM is referenced vertically to the Local Mean Sea Level (LMSL) tidal datum with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is 3 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):
- 2012-01-01 00:00:00 - The following datasets were used to develop the DEM: 1. 2006 Hawaii FEMA Lidar 2. 2007 USACE Pacific Islands Lidar Hydrographic breaklines delineated from LiDAR intensity imagery generated from the LiDAR datasets.
- 2012-01-01 00:00:00 - GeoCue software was used to develop LiDAR intensity imagery from the LiDAR. The raster resolution was 1ft or 0.3 m.
- 2012-01-01 00:00:00 - LiDAR intensity images were viewed in 2-D in ArcMap. Hydrographic features were collected as 2D breaklines.
- 2012-01-01 00:00:00 - Class 2, ground LiDAR points are exported from the LAS files into an Arc Geodatabase (GDB) in multipoint format. Hydro breaklines are assigned an elevation of -0.5 meters and loaded into an Arc GDB. An ESRI Terrain is generated from these inputs.
- 2012-01-01 00:00:00 - The ESRI Terrain is converted to a DEM in Erdas image file format with a cell size of 3 meters. The DEM is reviewed in Global Mapper for incorrect elevations and artifacts that are introduced from source inputs or during the raster creation process. Corrections are applied to the DEMs and reprocessed for review.
- 2012-01-01 00:00:00 - All DEMs are loaded into Global Mapper for the last review. During this last review, an analyst checks to ensure full, complete coverage, no issues along DEM boundaries, DEMs seamlessly edge-match, and that there are no remaining processing artifacts in the dataset. Once approved, DEMs are re-projected to the NAD83 geographic coordinate system.
- 2012-01-01 00:00:00 - Re-projected DEMs are further assessed for quality and consistency using Global Mapper. Fine-scale features, including bridges over narrow water bodies and small islands, are assessed for accuracy and edited accordingly. Once the DEMs are polished, they are re-projected to the Universal Transverse Mercator coordinate system.
(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.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.