Data Management Plan
GUID: gov.noaa.nmfs.inport:70314 | 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
Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 1000 meter x 1000 meter tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
Dataset Description: This lidar project called for the planning, acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing of 0.5 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011), Albers Equal Area, meters, and a vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles, as was tiled Intensity Imagery, and tiled bare earth DEMs; all tiled to the same 1000 m x 1000 m schema. The vegetation classes are: Low vegetation 0.5-5 feet, Medium vegetation 5-20 feet, High vegetation >20 feet. Building classified points only available in Champaign County. Vegetation classes may also include buildings or parts of buildings.
Geographic Extent: This dataset covers approximately 6367 square miles in northwestern and central Illinois and consists of 3 deliveries or blocks.
IL_8County_PlusChampaign_B1 (Work Unit 175710) - Champaign County covering approximately 1049 square miles.
IL_8County_PlusChampaign_B2 (Work Unit 176488) - Jo Daviess, Stephenson, Carroll, Ogle, Whiteside, Lee, Rock Island, and Henry counties covering approximately 5318 square miles.
IL_8County_PlusChampaign_B4 (Work Unit 216347) - Champaign County (buffer area). This block includes the area along the perimeter of IL_8County_PlusChampaign_B1 which did not extend out to the project boundary.
Ground Conditions: Lidar was collected in late 2019, early 2020 and late 2020 while no snow was on the ground, and rivers levels fluctuated.
Control Points and Checkpoints:
In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Subcontractor, Surveying and Mapping, LLC (SAM) established the following:
IL_8County_PlusChampaign_B1 and IL_8County_PlusChampaign_B4
A total of 34 ground control points that were used to calibrate the lidar to known ground locations established throughout the Champaign County, Illinois project area.
An additional 112 independent accuracy checkpoints, 64 in Bare Earth and Urban landcovers (64 NVA points), 48 in tall Grass/tall weeds/crops, Brush lands/short trees, Forested categories (48 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
IL_8County_PlusChampaign_B2
A total of 76 ground control points that were used to calibrate the lidar to known ground locations established throughout the Jo Daviess, Stephenson, Carroll, Ogle, Whiteside, Lee, Rock Island, and Henry counties project area.
An additional 219 independent accuracy checkpoints, 127 in Bare Earth and Urban landcovers (127 NVA points), 92 in tall Grass/tall weeds/crops, Brush lands/short trees, Forested categories (92 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.
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.
IL_8County_PlusChampaign_B1
W: -91.08, E: -88.92, N: 42.53, S: 41.13IL_8County_PlusChampaign_B2
W: -88.48, E: -87.92, N: 40.41, S: 39.87IL_8County_PlusChampaign_B4 (buffer area along perimeter of the IL_8County_PlusChampaign_B1 dataset that extends out to the project boundary).
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:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tile (EPT) files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.
Process Steps:
- 2021-02-12 00:00:00 - The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used Aerial Services Inc. proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.4, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.
- 2021-02-16 00:00:00 - LAS Point Classification QL2+: The point classification was performed as described below. Classification Filters were applied to aid in the definition of; terrain characteristics, vegetation attribution of low, medium or high and building roof tops. Filtering processes address aspects of the data such as: ground points, noise points, air points, low points, Low vegetation 0.5-5’, medium vegetation 5-20’, high vegetation >20’, manmade features, buildings, and overlap points. The Classified point cloud data was manually reviewed to ensure correct classification of; ground (ASPRS class 2). After the bare earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS class 2) lidar data inside of the Inland Ponds and Lakes, and Inland Streams and Rivers are classified to water (ASPRS class 9). A buffer of 2.5 feet was used around each hydro-flattened feature to classify ground (ASPRS class 2) to ignored ground (ASPRS class 20). Island features were checked to ensure that Ground point (ASPRS class 2) remained classified as Ground. Ground points (ASPRS class 2) within 2.5 feet of bridge breaklines, used to reduce triangulation between bridge decks were also classified to Ignored ground (ASPRS class 20). All bridge decks were classified to Bridge deck (ASPRS class 17). All remaining points were filtered, or manually classified to their respective point classification; processed (ASPRS class 1), low vegetation (ASPRS class 3), medium vegetation (ASPRS class 4), high vegetation (ASPRS class 5), low noise (ASPRS class 7), high noise (ASPRS class 18). TerraScan v019.008 was used to identify the overlap flag and bit set flags to LAS v1.4 specifications. LP360 64bit was used to deduce the Well Known Text (WKT) and an ASI proprietary software was used to format the LAS to the final LAS v1.4 Format 6 version. LAStools by rapidlasso GmbH, open source, lasvalidate (open source LGPL) and an ASI proprietary software was used to perform final analysis to checks on LAS header information, LAS point classes, and LAS timestamps.
- 2021-02-16 00:00:00 - Data was tested at 0.5 meter nominal pulse spacing and a 4 pulses per meter. The nominal pulse spacing was tested on classified tiled LAS using geometrically reliable first-return points. NPS was tested using Delaunay Triangulation that produced average point spacing between all nearest neighbors.
- Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical elevations in NAVD88 (GEOID12B).
- 2023-07-18 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. These are the AWS URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IL_8County_PlusChampaign_B1_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IL_8County_PlusChampaign_B2_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IL_8County_PlusChampaign_B4_2019/ept.json
(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://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/IL_8County_PlusChampaign_2019_B19/
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 tape and 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.