Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:49642 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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), Diablo Canyon (2010), and San Simeon (2013).
The Diablo Canyon project study is located in San Luis Obispo County, California, and encompasses approximately 10,634 acres (43.03 square kilometers). Watershed Sciences, Inc. (WSI) collected Light Detection and Ranging (LiDAR) data on both the inland and intertidal land within the Diablo Canyon study area on 28 January 2010. For optimal capture of the intertidal zone, WSI acquired LiDAR data of the coastline during seasonal low tides (between 0.0 ft and peak low of around 1.5 ft) and in conjunction with a PDOP value of less than 3.0.
This LiDAR survey utilized a Leica ALS50 Phase II laser system. The sensor scan angle was +/- 13 from nadir with a pulse rate designed to yield an average native density of more than 8 pulses per square meter over terrestrial surfaces. The area of interest was surveyed with an opposing flight line side-lap of equal-to-or-more-than 50% (equal-to-or-more-than 100% overlap) to reduce laser shadowing and increase surface laser painting.
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:
- 1. Resolved kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Software: Waypoint GPS v.8.10, Trimble Geomatics Office v.1.62 2. Developed a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data Sensor head position and attitude were calculated throughout the survey. The SBET data were used extensively for laser point processing. Software: IPAS v.1.35 3. Calculated laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Created raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.2) format. Software: ALS Post Processing Software v.2.7 4. Imported raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter for pits/birds. Ground points were then classified for individual flight lines (to be used for relative accuracy testing and calibration). Software: TerraScan v.9.017 5. Using ground classified points per each flight line, the relative accuracy was tested. Automated line-to-line calibrations were then performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations were performed on ground classified points from paired flight lines. Every flight line was used for relative accuracy calibration. Software: TerraMatch v.9.004 6. Position and attitude data were imported. Resulting data were classified as ground and non-ground points. Statistical absolute accuracy was assessed via direct comparisons of ground classified points to ground RTK survey data. Data were then converted to orthometric elevations (NAVD88) by applying a Geoid03 correction. Ground models were created as a triangulated surface and exported as ArcInfo ASCII grids at a three-foot pixel resolution. Software: TerraScan v.9.017, ArcMap v. 9.3.1, TerraModeler v.9.003
- 2014-05-02 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 03. 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/3650/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=3650
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.