Data Management Plan
GUID: gov.noaa.nmfs.inport:71418 | 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
This task order is for planning, acquisition, processing, and derivative products of lidar data for Starr Project number 400000096. FEMA Task Order number is HSFE05-11-J-0090. The area of data acquisition is for the entire county of Racine County in Wisconsin. The collection area consists of 332 square miles and was captured to the "Highest" vertical accuracy requirement.
Specifications listed below are based on FEMA Procedure Memorandum No. 61 Standards for LiDAR and Other High Quality Digital Topography. This collection specification is the equivalent of a 2 foot contour accuracy, and was collected with a nominal pulse spacing of 1.3 meters. The airborne GPS and IMU data were processed immediately following each mission. In addition, a sample of the LIDAR data was post-processed at the completion of each mission and the data was reviewed to ensure planned data quality and coverage.
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:
- 2013-12-20 00:00:00 - Ground based survey points were compared to the LiDAR airborne data points. Two hundred twenty-three survey points were collected throughout Racine County in various ground cover categories.
- 2013-12-21 00:00:00 - The LiDAR data was captured using Quantum Spatial's twin-engine AeroCommander 500 or a Cessna 320 with an Optech ALTM Gemini LiDAR system. This system consists of a Airborne Global Position System (ABGPS), inertial measurement unit (IMU), and laser sensor. The ABGPS collects XYZ coordinates of the laser sensor and the IMU calibrates the orientation of the aircraft. During flight, laser pulses are reflected from features on the surface and the system collects this data. The acquired LiDAR data receives a preliminary review to assure that complete coverage is obtained and to ensure the absence of data gaps. Acquisition parameters: 1. Scanner - Optech ALTM Gemini LIDAR 2. Flight Height - 1700 meters above ground level 3. Swath Width - 44 degrees 4. Sidelap - 55% 5. Nominal Point Spacing - 1.3m GPS and IMU processing parameters: 1. Processing Programs and version - Applanix POSPac, version 4.4 2. IMU processing monitored for consistency and smoothness - Yes.
- 2013-12-30 00:00:00 - Point Cloud Processing: 1. Program and version - Optech ASDA 2. Horizontal Datum - NAD83 3. Horizontal Coordinates - UTM zone 16N, in meters. 4. Vertical Datum - NAVD88 5. Geoid Model used to reduce satellite derived elevations to orthometric heights - Geoid09 (Meters). LIDAR Processing: 1. Processing Programs and versions - TerraSolid TerraScan (version 013.020), TerraModeler (version 013.005) and TerraMatch (version 013.009), Intergraph MicroStation (version 08.05.02.70), and GeoCue (version 2013.1.45.1) GlobalMapper (version 13.2.1). 2. Point Cloud data is imported to TerraScan in a Microstation V8 (V) CAD environment on a specified 1500m by 1500m tiling scheme 3. Analyze the data for overall completeness and consistency. This is to ensure that there are no voids in the data collection. 4. QC (Quality Control) for calibration errors in the dataset. This is accomplished by sampling the data collected accross all flight lines and classify the individual lines to ground. The software will use the ground-classified lines to compute corrections (Heading, Pitch, Roll, and Scale). 5. Orientation corrections (i.e. Calibration corrections) are then applied (if needed) to the entire dataset. 6. 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. 7. Quantum Spatial provided Quality Assurance and Quality Control (QAQC) data for this project. Quantum Spatial processed QA/QC points in 'open terrian' 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 QAQC 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 QAQC data, a bias adjustment was determined, and the results were applied to the LIDAR data. 8. Once the automatic processing and testing of LiDAR is complete, Quantum Spatial meticulously reviews the generated bare-earth surface data to insure that proper classification was achieved as part of a Quality Control process. Point classification follows the standard established by The American Society for Photogrammetry and Remote Sensing (ASPRS). Class 1 Unclassified Code 2 Ground Code 7 Low Points Code 8 Model Key Points Code 9 Water Code 10 Ignored Ground Code 12 Overlap 9. Linework is created of water bodies and drainage. A routine is used to drape line work following monotonic elevation change of drainage. 10. Final deliverables are generated and output to a client specified PLSS tiling scheme.
- 2023-11-16 00:00:00 - Data were retrieved from the Wisconsin View website in LAS format, NAD83(2007) UTM 16N projection with NAVD88 (Geoid09) vertical meters. The data were converted to geographic projection on the ellipsoid (EPSG:4893) in the cloud optimized point cloud (COPC) version of LAZ format and ingested into the Digital Coast Data Access Viewer. (Citation: Point cloud data)
(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://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9978/details/9978
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9978/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 or 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.