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
The State of Alaska Division of Geological & Geophysical Surveys (DGGS) produced airborne lidar-derived elevation data for Sitka, Alaska. Airborne and ground surveys occurred between the 27th and 30th of April, 2018. These data were produced to assess bare earth slope conditions as part of an overarching, multi-hazard risk analysis for the study area, coordinated through the Federal Emergency Management Agency (FEMA) Cooperating Technical Partners (CTP) program. The project was initiated in response to a tragic debris flow incident that took three Alaskans' lives in 2015. This data collection is released as a Raw Data File with an open end-user license. All files can be downloaded free of charge from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/30531).
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 263. During processing, OCM noted that there are points that fall on water bodies and buildings that are classified as ground.
In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data 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):
The data were collected for the Alaska Division of Geological and Geophysical Surveys (DGGS) and made available on the AK DGGS Elevation Portal (https://elevation.alaska.gov/). The NOAA Office for Coastal Management (OCM) downloaded the data from this site to make the data available for custom downloads from the NOAA Digital Coast Data Access Viewer and for bulk downloads from the AWS S3 bucket.
- 2018-04-30 00:00:00 - Airborne survey - The lidar survey was conducted with a Riegl VUX1-LR lidar scanner with an integrated GNSS and Northrop Grumman IMU system. The integration was designed by Phoenix LiDAR systems. This survey was flown with a pulse rate between 200,000-400,000 pulses/second and at a scan rate between 80 and 150 revolutions/second. This survey was flown with an average elevation of 400 m above ground level and a ground speed of approximately 40 m/s with a fixed-wing Cessna 185 aircraft. The scan angle was set from 55 to 305 degrees, centered normal to the aircraft's bottom. The accompanying report provides additional detail regarding flight conditions.
- 2018-04-30 00:00:00 - Ground survey - Trimble R8 and R9 RTK GPS systems were used to collect 195 survey points, 100 of which were used as control points and 95 of which were used as checkpoints. Points were gathered by vehicle along the road system and by boat along the coastline. Points were adjusted for accuracy according to OPUS corrections in Trimble Business Center.
- 2019-01-01 00:00:00 - Lidar dataset processing - SDCImport software was used to apply range thresholding, reflectance thresholding, and missed-time-around (MTA) disambiguation for preliminary point cloud noise filtering. In-flight IMU and GNSS data were coupled using Inertial Explorer software to produce the trajectory data. Spatial Explorer software was used to couple the trajectory data with the point cloud. The point cloud data were calibrated using tielines for roll, pitch, and yaw of the aircraft during the survey. This process was first run using all points, then on a per-flightline basis for additional accuracy. Interswath fluctuations in ground points were identified using overlapping tielines to further calibrate the data. The point cloud was classified in accordance with American Society for Photogrammetry and Remote Sensing (ASPRS) guidelines using project-tailored macros. Misclassified points were manually reclassified in post-processing QA/QC. The point cloud was converted from ellipsoidal to orthometric heights using geoid 12B, then uniformly adjusted to maintain a mean offset of 0 with collected ground control. Calibration, classification, and height adjustments were all executed in TerraSolid. Derived products were processed in ArcMap. DTM and DSM were produced using point triangulation with nearest-neighbor interpolation. The DTM was derived from all returns for ground classified points, while the DSM used first returns for all non-noise classes. The CHM was created by subtracting DTM height values from DSM height values. A lidar intensity image was created from first returns of all classes using mean binning.
- 2022-10-19 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 263 laz files from the Alaska Division of Geological and Geophysical Surveys Elevation Portal (https://elevation.alaska.gov/). The files contained classified elevation and intensity measurements for the 2018 Sitka Alaska project. The data were in UTM Zone 8 NAD83 (2011), meters coordinates and NAVD88 (GEOID12B) elevations in meters. During processing, OCM noted that there are points that fall on water bodies and buildings that are classified as ground. The data had the following classifications: 1 - Unclassified, 2 - Ground, 3- Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Building, 7 - Noise. OCM processed all points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from UTM Zone 8 NAD83 (2011), meters coordinates to geographic coordinates, to convert from NAVD88 elevations to ellipsoid elevations using the GEOID12B model, to assign the geokeys, to sort the data by gps time, zip the data to database, and to create Cloud Optimized Point Cloud (COPC) version laz files that are available from the AWS S3 bucket.
(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.