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
Bare Earth LiDAR point cloud data provided for this project is compliant with FEMA Guidelines and Specifications Procedure Memorandum 61.
LiDAR derived products for two areas of interest within the Cordova, Alaska area, consisting of 32 square miles, were developed to support coastal or riverine H&H analysis and floodplain boundary delineation.
The NOAA Office for Coastal Management (OCM) downloaded this data set from this AK DGGS site:
These files were processed to make the data available for custom and bulk download from the NOAA Digital Coast Data Access Viewer (DAV). The total number of files downloaded and processed was 1. No metadata record was provided with the data. This record is populated with information from the FEMA Starr technical and QA reports downloaded from the Alaska Dept. of Geological and Geophysical Surveys Elevation Portal.
In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
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):
Data were collected by Aerometric, Inc. for FEMA. OCM downloaded the data from the Alaska DGGS Elevation Portal and processed the data to be available for custom and bulk download from the NOAA Digital Coast Data Access Viewer (DAV).
- 2012-01-01 00:00:00 - Process Steps For products derived from Cordova, Alaska LiDAR Data: 1-Create Cordova, AK ESRI file geodatabase feature dataset with NAD_1983_UTM_Zone_6N projection. 2-Use ESRI 3D analyst tool LAS to multipoint and created bare earth multipoint featureclass stored within Cordova, AK file geodatabase feature dataset. 3-Use ESRI Arc Catalog to create an ESRI terrain dataset stored within Cordova, AK file geodatabase feature dataset. The multipoints were added to the terrain as mass points using the shape as the height source and the study area polygon was added to the terrain as a soft clip without any height source. 1 meter or 3.2808399 ft average point spacing used. This was determined from Cordova, AK acquisition metadata. 4-Create Bare Earth DEM file geodatabase for Cordova, AK 5-Use 3D analyst tool Terrain to raster to create 2 meter DEM and store within Cordova, AK Bare Earth DEM file geodatabase. 6-Create Raster Index Polygon 7-Using ERDAS Imagine split 2 meter AOI DEM into GeoTif Format based on raster index. 8-Using ArcCatalog converted GeoTif DEMs into Ascii raster format. 9-Create Cordova, AK Cartographic Contours and Analysis Contours file geodatabase feature datasets with NAD_1983_UTM_Zone_6N projection. 10-Use ESRI spatial analyst neighborhood tool focal statistics (mean statistic using circle with 3 cell radius) on each GeoTif bare earth DEM. 11-Use ESRI spatial analyst surface tool Contour to create 2ft contour from focal mean GeoTif DEMs and stored within Cordova, AK Cartographic Contours file geodatabase feature dataset. 12-Use ESRI spatial analyst neighborhood tool focal statistics (sum statistic using weighted kernel) on each GeoTif bare earth DEM. Weighted Kernel: 3 3 .005 .005 .005 .005 .960 .005 .005 .005 .005 13-Use ESRI spatial analyst surface tool Contour to create 2ft contour from focal sum GeoTif DEMs and stored within Cordova, AK Analysis Contours file geodatabase feature dataset.
- 2022-09-02 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 1 raster DEM file in GeoTiff format from the Alaska DGGS Elevation Portal. The data were in UTM Zone 6 NAD83, meters coordinates and NAVD88 (Geoid09) elevations in feet. The bare earth raster files were at a 1 meter grid spacing. No metadata record was provided with the data. This record is populated with information from the FEMA Starr technical and QA reports downloaded from the AK Dept. of Geological and Geophysical Surveys Elevation Portal. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal an script to assign the EPSG codes (Horizontal EPSG: 26906 and Vertical EPSG: 6360) to the GeoTiff formatted files. 2. Copied the files to https.
(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
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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.
Data is available online for bulk and custom downloads.
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
Data is backed up to tape and to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.