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
This task order is for planning, acquisition, processing, and derivative products of LiDAR data to be collected for Nueces County, Texas. LiDAR data, and derivative products produced in compliance with this task order are part of the data to be obtained under the American Recovery and Reinvestment Act (ARRA) of 2009. Contract number G10PC00025. Specifications listed below are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 13. Tile names were slightly altered to meet particular naming conventions on NOAA OCM ftp. Dataset was titled 2010 but due to acquisition dates falling in 2011, the title has been updated.
Original contact information:
Contact Name: Patrick Emmett
Contact Org: USGS
Title: USGS NGTOC
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):
- 2011-08-24 00:00:00 - The LiDAR data was captured using AeroMetric's twin-engine Cessna 310, fixed wing aircraft equipped with a LiDAR system. The LiDAR system includes a differential GPS unit and inertial measurement system to provide superior positional accuracy. Acquisition parameters: 1. Flight Height - 2500 meters above mean terrain 2. Swath Width - 34 degrees 3. Sidelap - 30% 4. Nominal Post Spacing - 1.5 meters GPS and IMU processing parameters: 1. Maximum baseline length - Not greater than 90 kilometers. 2. Number of base stations during LiDAR collection - A minimum of 1. 3. Maximum positional RMS of trajectory during LiDAR collection - 0.07 meters 4. IMU processing monitored for consistency and smoothness - Yes. Point Cloud Processing: 1. Horizontal Datum - NAD83(NSRS2007) 2. Horizontal Coordinates - Universal Transverse Mercator, Zone 14, in meters. 3. Vertical Datum - NAVD88 4. Geoid Model used to reduce satellite derived elevations to orthometric heights - NGS Geoid09. LiDAR Processing: 1. Point Cloud data is imported via TerraScan in a Microstation V8 (V) CAD environment on a specified 1500 meter by 1500 meter tiling scheme. 2. Analyze the data for overall completeness and consistency. This is to ensure that there are no voids or anomalies in the data collection. 3. Inspect for calibration errors in the dataset using the TerraMatch software. This is accomplished by sampling the data collected across all flight lines and classify the individual lines to ground. The software will use the ground-classified points by flightline to compute corrections (Heading, Pitch, Roll, and Scale). 4. Orientation corrections (i.e. Calibration corrections) are applied (if needed) to the entire dataset. 5. Automatic ground classification is performed using algorithms with customized parameters to best fit the project area. Several areas of varying relief and planimetric features were inspected to verify the final ground surface. 6. AeroMetric, Inc. provided Quality Assurance and Quality Control (QA/QC) data for this project. AeroMetric captured QA/QC points in 'open terrain' land cover category that were used to test the accuracy of the LiDAR ground surface. TerraScan's Output Control Report (OCR) was used to compare the QA/QC data to the LiDAR data. This routine searches the LiDAR dataset by X and Y coordinate, finds the closest LiDAR point and compares the vertical (Z) values to the known data collected in the field. Based on the QA/QC data, a bias adjustment was determined, and the results were applied (if necessary) to the LiDAR data. A final OCR was performed with a resulting RMSE of 0.048 meters for the project. 7. Each tile is reviewed for accuracy and consistency of the macro ground classification. 8. Once the automatic processing and the testing of LiDAR is complete, AeroMetric meticulously reviews the generated bare-earth surface data to ensure that proper classification was achieved as part of a Quality Control process. 9. Final deliverables are generated and output to a client specified 1500 meters by 1500 meters tiling scheme.
- 2015-12-20 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded topographic files (point clouds) in LAZ format from an USGS ftp site. The data was received in UTM Zone 14 North (in meters) and vertical coordinates were referenced to NAVD88 in meters using the Geoid09 model. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The All-Return LAZ files were checked for erroneous outliers removed. 2. The LAZ files were converted from a UTM coordinates to Geographic Coordinates (decimal degrees), then converted to ellipsoidal vertical units in meters with respect to the Geoid09.
(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.
This data can be obtained on-line at the following URL:
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.