Data Management Plan
GUID: gov.noaa.nmfs.inport:53623 | 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
The University of Alaska Fairbanks, Geographic Information Network of Alaska (UAF/GINA) provided Aero-Metric, Inc. (AeroMetric) and Watershed Sciences, Inc. (WSI) with detailed specifications for this project in the spring of 2013. Planning and acquisition of airborne LiDAR data was carried out by WSI in early May of 2013.
This delivery contains point cloud data in LAS 1.2 format classified in the following manner:
Class 1: Unclassified
Class 2: Bare Earth Ground
Class 3: Low Vegetation (vegetation within 12 inches of the ground surface)
Class 4: Medium Vegetation (vegetation greater than 12 inches, but less than 36 inches above the ground surface)
Class 5: High Vegetation (vegetation greater than 36 inches above the ground surface)
Class 6: Buildings
Class 7: Noise
Class 8: Ground Model Keypoints
Class 9: Water
Class 10: Breakline Proximity
Class 14: Bridge Decks
The following are the collection parameters and equipment used to create these data sets:
Aircraft: Cessna Caravan (N604MD)
LiDAR System: Leica ALS60
Approximate Collection Altitude (Above Mean Terrain): 900 meters
Ground Speed: 160 kts
Pulse Rate Frequency: 98-106 kHz
Mirror Scan Frequency: 66 Hz
Scan Angle (+/-): 14 degrees
Accuracy statements are based on areas of moderate terrain, with points classified as ground. Diminished accuracies are to be expected in areas of extreme terrain and dense vegetation. The accuracy of each point is expected to meet the vertical accuracy standard, derived products may be less accurate in areas of extreme terrain and dense vegetation due to a lesser number of points defining the ground in these areas. Classified data sets such as this one may have varying posting due to some pulses not reaching the ground.
The NOAA Office for Coastal Management (OCM) downloaded this lidar data from the AK DGGS site (https://elevation.alaska.gov/) and processed the data to be available on the Digital Coast Data Access Viewer (DAV). OCM processed all points to the Digital Coast Data Access Viewer (DAV).
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):
- 2013-05-31 00:00:00 - WSI created a smoothed-best estimated trajectory (SBET) of the sensor at a rate of 200 Hz, by integrating the airborne GPS and IMU data The basis of the GPS coordinates were two dual frequency GPS receivers, collecting data at a rate of 2 Hz operated by Aero-Metric during the acquisition phase of this project, and were referenced to NAD83 (CORS96) ellipsoid heights.
- 2013-06-03 00:00:00 - WSI integrated SBET and raw laser data to produce point cloud data in LAS 1.2 format for each flight line.
- 2013-06-12 00:00:00 - WSI processed data calibration: An in-situ calibration was performed using the data collect for this project. The data was classified in each line separately for ground and other common features between lines, such as building roofs. This data was processed in TerraMatch 11.001 (TerraSolid, Ltd.), to compute corrections for roll, pitch, heading, and mirror scale. These corrections are applied in order to minimize discrepancies between flight lines.
- 2013-06-13 00:00:00 - WSI automated classification of the bare-earth data from the LiDAR point cloud using a series of algorithms customized for the types of terrain encountered in the project.
- 2013-06-20 00:00:00 - WSI manually classified any data which appears to be improperly classified using the automated methods.
- 2013-06-25 00:00:00 - WSI provided AeroMetric with calibrated, vertically adjusted, and classified LiDAR data in the Vallenar Bay area.
- AeroMetric completed a series of evaluations including verifying density requirements, confirming relative and absolute accuracies, reviewing coverage and classification's, and confirming the reproducibility of ranges within the LiDAR Data.
- 2013-09-09 00:00:00 - Due to tiling artifacts being identified in the low vegetation and high vegetations, using a automated method those classes were properly re-classified.
- Create point cloud data, by tile in LAS 1.2 format.
- 2018-09-10 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 32 laz files from the Alaska Division of Geological and Geophysical Surveys data Portal (https://elevation.alaska.gov/). The files contained classified elevation and intensity measurements for the 2013 Vallenar Bay data set. The data were in Alaska State Plane, Zone 5001 coordinates (NAD83 2011, US survey feet) and NAVD88 elevations (GEOID12A) in feet. The data were classified: Class 1: Unclassified, Class 2: Bare-earth ground, Class 3: Low vegetation, Class 4: Medium Vegetation, Class 5: High Vegetation, Class 6_ Buildings, Class 7: Noise, Class 8: Ground Model Keypoints, Class 9: Water, Class 10: Breakline Proximity, Class 14: Bridge Decks. Low vegetation is defined in the report as vegetation within 12 inches of the ground surface, medium vegetation as vegetation greater than 12 inches, but less than 36 inches above the ground surface and high vegetation as vegetation greater than 36 inches above the ground surface. 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. The LAStools software scripts lasinfo and lasvalidate were run on the laz files to check for errors. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps times and intensity ranges. 3. Internal OCM scripts were run on the laz files to convert from Alaska State Plane, Zone 5001 coordinates to geographic coordinates, to convert from NAVD88 elevations to ellipsoid elevations using the GEOID12A model, to convert from feet to meters, to assign the geokeys, to assign a lidar domain profile, to sort the data by gps time and zip the data to database and to http.
(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 and bulk 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.