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 point cloud data collected to support FEMA flood risk analysis and mapping in Ketchikan, Alaska. Point cloud is classified as ground (class 2) and other (class 1). The data was collected under a FEMA contract to the Strategic Alliance for Risk Reduction (STARR) with an accuracy requirement to support 2-foot contours. Original tasking indicates additional classes would be populated (7, 9, 10, 11), but they are not in the data set.
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):
Processed data were received from FEMA and ingested into the Digital Coast Data Access Viewer.
- 2014-09-30 00:00:00 - Terrain data used for flood risk analysis go through LiDAR preliminary processing and the unclassified point cloud data are tested as specified in the USGS National Geospatial Program Base LiDAR Specification Version 1.0. Where the Mapping Activity Statement (MAS) requires bare earth post-processing of the floodplain area of interest (AOI), the elevation data are tested and comply with both the Fundamental Vertical Accuracy (FVA) and Consolidated Vertical Accuracy (CVA) requirements. Where no bare earth post-processing is specified, only the FVA requirements apply for LiDAR preliminary processing.
- 2014-07-01 00:00:00 - Ground Survey: RTK GPS based surveys were utilized to support both processing and testing of LiDAR data within FEMA designated Areas of Interest (AOIs). Geographically distinct ground points were surveyed using GPS technology throughout the AOIs to provide support for three distinct tasks. Task 1: Ground control monuments utilized for the STARR Ketchikan LiDAR dataset. Ground control monuments are used to provide redundant control within 13 nautical miles of mission areas for LiDAR flights, as well as the collection of ground control points using real-time kinematic (RTK) survey techniques. The horizontal datum for this dataset is NAD83 (2011), the vertical datum is NAVD88, Geoid 12A, and the data is projected in Alaska State Plane Zone 1. Units are in US Survey Feet. Task 2: RTK (real time kinematic) ground control points collected for the STARR Ketchikan LiDAR dataset. RTK ground control points are used to correct and verify the vertical accuracy of the LiDAR data. The horizontal datum for this dataset is NAD83 (2011), the vertical datum is NAVD88, Geoid 12A, and the data is projected in Alaska State Plane Zone 1. Units are in US Survey Feet. Task 3: Land cover class ground check points collected for the STARR Ketchikan LiDAR dataset. Land class ground check points are used to assess the vertical accuracy of the LiDAR data and are collected using real time kinematic (RTK) survey techniques. The horizontal datum for this dataset is NAD83 (2011), the vertical datum is NAVD88, Geoid 12A, and the data is projected in Alaska State Plane Zone 1. Units are in US Survey Feet.
- 2014-07-13 00:00:00 - LiDAR Acquisition: General: LiDAR collection was collected using a Leica ALS70 system mounted in a Piper Navajo airplane. Yielded an average pulse density of >= 4 pulses/square meter over the Ketchikan Project Area. Swath Acquisition: This swath dataset represents the STARR Ketchikan LiDAR study area. This data is delineated in 4800x4800 ft tiles. Tile naming is derived from the 4 four digits of the easting and first four digits of the northing coordinates of the lower left corner. Data is unclassified (class 0). The horizontal datum for this dataset is NAD83 (2011), the vertical datum is NAVD88, Geoid 12A, and it is projected in Alaska State Plane Zone 1. Units are in US Survey Feet. Quantum Spatial collected the STARR Ketchikan LiDAR data for STARR on 07/12/2014 and 07/13/2014 further information is available in the Ketchikan Post-Flight Aerial Acquisition Report. All areas were surveyed with an opposing flight line side-lap of >=50% (=100% overlap) in order to reduce laser shadowing and increase surface laser painting. To accurately solve for laser point position (geographic coordinates x, y and z), the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Position of the aircraft was measured twice per second (2 Hz) by an onboard differential GPS unit, and aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll and yaw (heading) from an onboard inertial measurement unit (IMU). All swath data were classified as Class 0 or Unclassified. Leica ALS70 Instrument Parameters: Beam diameter: 37 cm cm, Pulse rate: 175 kHz, Maximum returns: 4, Speed: 150 knots, Overlap: 60 %, Laser power: 93.6 %, Field of view (FOV): 30 degrees, Beam wavelength: 1064 nm, Frequency of GPS sampling: 2 Hz, Frequency of IMU sampling: 200 Hz, Swath width: 857 m, AGL: 5207 - 5315 MSL m, Average pulse density: 4
- 2014-09-30 00:00:00 - Bare Earth Processing: QSI processing staff initiated a suite of automated and manual techniques to process the data into ASPRS Class 2 Bare Earth. The calibrated and filt ered LiDAR point cloud was hand checked for accuracy. Generate bare earth models as triangulated surfaces. The calibrated and filtered LiDAR point cloud was hand checked for accuracy. All points were placed in one of the following categories: 1 Unclassified, 2 Ground, 7 Noise, and 12 Overlap Points. Model Key points were then generated from the Ground points and placed in Category 8. Requested elevation values were evaluated for the Consolidated Vertical Accuracy (CVA) testing. Ketchikan Classified LiDAR ASPRS Classifications 1 Unclassified 2 Ground
- 2018-04-30 00:00:00 - Point cloud data were received from FEMA in LAS format, NAD83(2011) Alaska State Plane Zone 01 in US survey feet horizontally and vertically. The vertical datum was NAVD88 from Geoid12a. NOAA OCM reprojected to geographic coordinates and transformed the vertical coordinate system to height above the NAD83 ellipsoid in meters by reversing the Geoid12a model. Data were then ingested into the Digital Coast Data Access Viewer for distribution. Examination of the data indicated points were only in classes 1 and 2. (Citation: Ketchikan Ketchikan Classified Tiled Point Cloud)
(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.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.
Data is available online for 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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.