Data Management Plan (Deprecated)

Product: These lidar data are processed Classified LAS 1.4 files, formatted to 5,230 individual 5,000 US Feet x 5,000 US Feet tiles in NAD83 (HARN), StatePlane Indiana East FIPS 1301, NAVD88 Geoid12B US Feet; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.

Geographic Extent: AOI is located in NE Indiana. The area of interest covers approximately 4,690 square miles.

Dataset Description: Indiana Statewide Lidar 2017 B17 Base Option Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.70 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 (HARN), StatePlane Indiana EastFIPS 1301, and vertical datum of NAVD88 (GEOID12B), US Feet. Lidar data was delivered as flightline-extent unclassified LAS swaths, as processed Classified LAS 1.4 files, formatted to 5,230 individual 5,000 US Feet x 5,000 US Feet tiles in NAD83 (HARN), StatePlane Indiana East FIPS 1301, US Feet as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 5,000 US Feet x 5,000 US Feet schema.

Ground Conditions: Lidar was collected in early 2017 by Woolpert, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Woolpert established a total of 265 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. Additional independent accuracy checkpoints were collected (84 NVA points and 64 VVA points) and 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.

Lineage Statement:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tiles (EPT) 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:

• 2017-03-08 00:00:00 - LAS Point Classification: The point classification is performed as described below. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" lidar returns. This process determined Processed, but unclassified (Class 1), Bare-earth ground (Class 2), Low Noise (Class 7), Water (Class 9), Ignored Ground (Class10), Bridge Decks (Class 17), and High Noise (Class 18). The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through a semi-automated process. All ground (Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (Class 9) using TerraScan/LP360 macro functionality. A buffer of 2.3 feet was also used around each hydro-flattened feature to classify these ground (Class 2) points to Ignored ground (Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Woolpert Inc. proprietary software and LP360 was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.
• 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 the vertical units were converted to meters (NAVD88 Geoid12B).
• 2023-01-20 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/IN_Statewide_B1_2017/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IN_Statewide_B2_2017/ept.json

Data is available online for bulk and custom downloads.

Data is backed up to tape and to cloud storage.