Data Management Plan
GUID: gov.noaa.nmfs.inport:49650 | 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 Diablo Canyon Power Plant (DCPP) LiDAR and Imagery datasets are comprised of three separate LiDAR surveys: Diablo Canyon (2010), Los Osos (2011), and San Simeon (2013). The DCPP San Simeon project study area is located primarily in San Luis Obispo County, California, encompasses approximately 195,000 acres (801 km2), and measures 75 miles in length. Watershed Sciences, Inc. (WSI) collected Light Detection and Ranging (LiDAR) data and orthophotography across the DCPP San Simeon survey area from 29 January 2013 to 25 February 2013. For optimal capture of the intertidal zone, WSI acquired LiDAR data of the coastline during seasonal low tides between 7 February 2013 and 10 February 2013. The LiDAR survey utilized a Leica ALS70 sensor in a Cessna Caravan, and an Optech Orion sensor in a Bell Long Ranger. The Leica system was used for acquisition of the inland portion of the study area. It was set to acquire 240,000 laser pulses per second (i.e., 240 kHz pulse rate) and flown at 1,100 meters above ground level (AGL), capturing a scan angle of +/- 15 degrees from nadir. The Orion system was used to acquire the intertidal portion of the study area. It was set to acquire 175,000 laser pulses per second and flown at 300 meters AGL; capturing a scan angle of +/- 13 degrees from nadir. Both laser systems were programmed to yield an average native pulse density of more than 8 pulses per sq meter over terrestrial surfaces. Digital orthophotos were collected using a 260 megapixel ultra large format digital aerial camera. Image radiometric values were calibrated to specific gain and exposure settings associated with each capture using Microsoft's UltraMap software suite. The calibrated images were saved in TIFF format for input to subsequent processes. Photo position and orientation were calculated by linking the time of image capture, the corresponding aircraft position and attitude, and the smoothed best estimate of trajectory (SBET) data in POSPAC. Within the Inpho software suite, automated aerial triangulation was performed to tie images together and to align with ground control. The orthophotos were delivered in 0.375 USGS tiles with a 3 inch pixel resolution. This survey was flown in conjunction with the DCPP Senior Seismic Hazard Analysis Committee (SSHAC) Level 3 process and as part of the DCPP Long-Term Seismic Program (LTSP). In addition to aerial LiDAR data, DEM and orthophotography raster data are available for this area: San Simeon DEMs and Orthophotos.
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):
Process Steps:
- Classify ground-level features and create the ground model. After the ground model has been created and examined for correctness, vegetation points above 8 feet are then classified using a combination of automated and manual techniques. Once vegetation is classified in the LiDAR point cloud, automated techniques are used to delineate individual units of vegetation. These automated techniques utilize the unique point geometry of vegetation to segment the individual units of vegetation and create crown polygons representing them. The polygons representing individual units of vegetation (crown) are then aggregated with adjacent polygons to produce polygons representing stands. Classify remaining points as default and check for accuracy before finalizing the point classification portion of the project.
- 2014-05-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in laz format via download from the OpenTopography online repository. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 10, NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from UTM 10 coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 12A. 3. The LAS data were sorted by latitude and the headers were updated.
(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.6. Type(s) of data
- 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.
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/geoid18/3652/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3652
The data set is dynamically generated based on user-specified parameters.;
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.