Data Management Plan
GUID: gov.noaa.nmfs.inport:72181 | Published / External
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
Lidar-derived elevation data for Kipnuk, Southwest Alaska, collected August 18, 2021, Raw Data File 2023-20, provides lidar derived classified point cloud data, a digital surface model (DSM), a digital terrain model (DTM), and an intensity model of Kipnuk, Southwest Alaska. The survey was flown during leaf-on ground conditions. The survey provides snow-free surface elevation data for assessing coastal erosion and flooding hazards. Ground control data and aerial lidar data were collected on August 18, 2021, and subsequently processed using a suite of geospatial processing software. All files can be downloaded from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/31036).
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV).
The NOAA Office for Coastal Management (OCM) downloaded 21 laz point data files from the AK DGGS (Alaska Division of Geological and Geophysical Surveys) website (https://dggs.alaska.gov/webpubs/data/rdf2023_020_kipnuk_classified_points.zip). The data were processed to the NOAA Digital Coast Data Access Viewer (DAV) to make the data available for bulk and custom downloads. 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.
4. Resources
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):
Lineage Statement:
Data were collected by the Alaska Division of Geological and Geophysical Surveys (AK DGGS). The data were downloaded by the NOAA Office for Coastal Management (OCM) and processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from AWS S3.
Process Steps:
- 2021-08-18 00:00:00 - Ground survey - We collected ground control and checkpoints on August 18, 2021. We deployed a Trimble R10 GNSS receiver at benchmark IIK-A near the Kipnuk Airport. It provided a base station occupation and real-time kinematic (RTK) corrections to points we surveyed with a rover Trimble R8 GNSS receiver (internal antenna). We collected 45 ground control and checkpoints for calibration and to assess the vertical accuracy of the point cloud. All points were collected on bare earth surfaces. We processed and delivered all data in NAD83 (2011) UTM3N and vertical datum NAVD88 GEOID12B.
- 2021-08-18 00:00:00 - Aerial photogrammetric survey - DGGS used a Riegl VUX1-LR laser scanner integrated with a global navigation satellite system (GNSS) and Northrop Grumman LN-200C inertial measurement unit (IMU). Phoenix LiDAR Systems designed the lidar integration system. The sensor can collect up to 820,000 points per second at a range of up to 150 m. The scanner operated with a pulse refresh rate of 400,000 pulses per second at a scan rate of 200 lines per second. We used a Cessna 180 fixed-wing platform to survey from an elevation of about 200 m above ground level, at a ground speed of about 40 m/s, and with a scan angle set from 80 to 280 degrees. The total survey area covers about 20 km2. We flew the aerial survey on August 18, 2021, departing at 2:30 pm from Kipnuk, Alaska Airport, and landing back at Kipnuk at 3:10 pm. The weather throughout the survey was clear with no wind.
- 2022-01-01 00:00:00 - Lidar dataset processing - We processed point data in SDCimport software for initial filtering and multiple-time-around (MTA) disambiguation. MTA errors, corrected in this process, result from ambiguous interpretations of received pulse time intervals and occur more frequently with higher pulse refresh rates. We processed IMU and GNSS data in Inertial Explorer and we used Spatial Explorer software to integrate flightline information with the point cloud. We calibrated the point data at an incrementally precise scale of sensor movement and behavior, incorporating sensor velocity, roll, pitch, and yaw fluctuations throughout the survey. We created macros in Terrasolid software and classified points following the American Society for Photogrammetry and Remote Sensing (ASPRS) 2019 guidelines. Once classified, we applied a geometric transformation and converted the points from ellipsoidal heights to GEOID12B (Alaska) orthometric heights.We used ArcGIS Pro to derive raster products from the point cloud. The DSM was interpolated from maximum return values from the ground, vegetation, bridge deck, and building classes using a binning method. The DTM was interpolated from all ground class returns, also using a binning method and minimum values. In ArcGIS Pro, we produced an intensity image by binning and averaging ground, vegetation, building, and bridge deck classes.
- 2024-03-05 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 21 laz point data files from the Alaska Division of Geological and Geophysical Surveys (AK DGGS). The data were in UTM Zone 3 (NAD83 2011), meters coordinates and NAVD88 (Geoid12b) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 3 - Low Vegetation (0.05 - 0.2 m), 4 - Medium Vegetation (0.2 - 3 m), 5 - High Vegetation (3 - 40 m), 6 - Building, 7 - Low Noise, 10 - Hard Surface, 17 - Bridge Decks, 18 - High Noise. There were also points that were classified as 20 and 31 that were not listed in either the lidar report or in the provided metadata. OCM confirmed with AK DGGS the following: 1. Classes 20 and 31 should be considered High Noise 2. Class 10 points were found by AK DGGS using the Hard Surface macro and used as a temporary class to help differentiate between ground points and boardwalks/ramps (which are common in Kipnuk and easily misclassified as grounds). Some of the Class 10 points were later converted to Class 2 ground points, and some to Class 17 bridge deck points, but many could not be sorted into either of those two categories. So, Class 10 points were kept as Class 10 points so that bridge decks would not be misclassified as ground points. Class 10 points were excluded from the digital terrain model, but kept in the digital surface model. OCM re-classified the Class 20 and 31 points to 18 - High Noise and the Class 10 points to 1 - Unclassified Also, during processing to the DAV, it was noted that there are points that fall on ponds/lakes and streams/rivers that are classified as ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV), the classes available on the DAV are: 1, 2, 3, 4, 5, 6, 7, 17, 18. 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, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Re-classify the Class 20 and 31 points to 18 (High Noise) and the Class 10 points to 1 (Unclassified) b. Convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid12b model c. Convert the laz files from UTM Zone 3 (NAD83 2011), meters coordinates to geographic coordinates d. Assign the geokeys, sort the data by gps time and zip the data to database and to AWS S3.
(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.
Missing/invalid information:
- 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.
None
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.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/10074/index.html
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 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.