Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:72882 | 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 Light Detection and Ranging (LiDAR) dataset is a survey of the NRCS Christian Co Ill LiDAR Survey and encompasses 715 square miles. The LiDAR point cloud was flown at a nominal post spacing of 0.5 meters for un-obscured areas. The LiDAR data and derivative products produced are in compliance with the U.S. Geological Survey National Geospatial Program Guidelines and Base Specifications, Version 1.0 The flight lines were acquired by Digital Aerial Solutions, LLC. between Dec. 2014 and March 2015. Derivative products from the aerial acquisition include: Raw point cloud data in LAS v1.2, classified point cloud data in LAS v1.2, bare earth surface tiles (raster DEM GeoTIFF format), bare earth surface DEMs mosaic (raster ESRI float GRID format), Intensity images (8 bit tif format with world files), control points, project report, and FGDC compliant XML metadata.
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:
This data was collected by Digital Aerial Solutions for the Natural Resources Conservation Service (NRCS) and the U.S. Geological Survey (USGS). The data were made available for download by USGS. The NOAA Office for Coastal Management (OCM) downloaded the data to make the data available for custom download from the NOAA OCM Digital Coast Data Access Viewer (DAV) and for bulk download from AWS S3.
Process Steps:
- 2015-03-31 00:00:00 - The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey, laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collected by receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 40 km radius from the flight survey area.
- 2015-04-28 00:00:00 - The ABGPS, IMU, and raw scans are integrated using proprietary software developed by Leica Geosystems called IPAS Pro (Version 1.35). These LiDAR data are then output to a ASPRS Version 1.2 LAS binary format using Leica Geosystems ALSPP post-processing software (Release 2.75 Build #25 ) The LAS version 1.2 file format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return number, intensity value, xyz, etc.). The header file for each dataset is complete as defined by the LAS 1.0 specification.
- 2014-05-15 00:00:00 - The unedited data are classified to facilitate the application of the appropriate feature extraction filters. Combinations of proprietary filters are applied as appropriate for the production of bare earth digital elevation models (DEMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The data was classified as follows: Class 1 =Processed, but unclassified Class 2 = Bare-earth ground Class 3 = Low Vegetation is 0-5 feet Class 4 = Medium Vegetation is 5-20 feet Class 5 = High Vegetation is 20 feet or more Class 6 = Buildings, bridges, other manmade structures Class 7 = Noise (low or high, manually identified, if needed Class 9 = Water Class 10 Ignored Ground (Breakline Proximity) Class 14 = Ground Overlap Class 15 = Defualt Overlap Class 17 = Bridge Decks
- 2015-06-20 00:00:00 - Filtered and edited data are subjected to rigorous QA/QC, A series of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is established by DAS and GPS-derived ground control points (GCPs) in various areas of dominant and prescribed land cover. These points are coded according to land cover, surface material, and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment, as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error, and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA), according to Federal Geographic Data Committee (FGDC) specifications.
- 2024-06-05 00:00:00 - The Office for Coastal Management (OCM) downloaded 775 laz files from the USGS rockyweb site for the NRCS_Christian_County_IL dataset. The data were in IL State Plane West, NAD83 HARN, US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The points were classified as 1- Unclassified, 2 - Ground, 3 - Low Vegetation (0 - 5 ft), 4 - Medium Vegetation (5 - 20 ft), 5 - High Vegetation (20 ft or more), 6 - Buildings, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 14 - Overlap Ground, 15 - Overlap Unclassified, 17 - Bridge Deck. The class 14 points were reclassified to 22 and the class 15 points were reclassified to 21. All points were processed to the NOAA Digital Coast Data Access Viewer (DAV) for data provisioning. The classes available on DAV are: 1,2,3,4,5,6,7,9,10,17,21,22. 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 14 points to 22 (Overlap Ground) and the Class 15 points to 21 (Overlap Unclassified) b. Convert from orthometric (NAVD88) elevations in feet to NAD83 (2011) ellipsoid elevations in meters using the Geoid12B model c. Convert the laz files from IL State Plane West, NAD83 HARN, US survey feet coordinates to geographic coordinates d. Assign the geokeys, sort the data by gps time and zip the data to database
(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/geoid18/10123/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.