Woolpert 20201209 Project level metadata Product: Processed, classified lidar point cloud tiles in LAS 1.4 format, 2.5-foot bare-earth digital elevation models (DEMs) in ERDAS IMG format, 2.5-foot intensity imagery tiles in GeoTIFF format, hydro-flattened lake and river breaklines in Esri file geodatabase format, bridges used for hydro-flattening in Esri shapefile format. Geographic Extent: Approximately 18,069 square miles across the following counties in western Indiana: Benton, Boone, Carroll, Clay, Clinton, Crawford, Daviess, Dubois, Fountain, Gibson, Greene, Hendricks, Jasper, Knox, Lake, LaPorte, Lawrence, Martin, Monroe, Montgomery, Morgan, Newton, Orange, Owen, Parke, Perry, Pike, Porter, Posey, Pulaski, Putnam, Spencer, Starke, Sullivan, Tippecanoe, Vanderburgh, Vermillion, Vigo, Warren, Warrick, White Dataset Description: The Indiana Statewide Lidar 2017 B17 West task called for the planning, acquisition, processing, and production of derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. The data was developed based on a horizontal datum/projection of NAD83 (HARN) State Plane Indiana West Zone (FIPS 1302), US Survey Feet, and a vertical datum of NAVD88 (GEOID12B), US Survey Feet. Lidar data was delivered as processed classified LAS 1.4 files formatted to 20,074 individual 5,000-foot x 5,000-foot tiles. Tiles were named according to the Indiana Statewide Ortho-Lidar tile index. Other lidar products include tiled intensity imagery and tiled bare-earth DEMs, all tiled to the same tiling schema. Ground Conditions: Lidar was collected from March 9, 2017 through April 11, 2020 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 234 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 724 independent accuracy checkpoints (417 NVA points and 307 VVA points), were collected and used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. This project will support the state of Indiana and the Natural Resources Conservation Service (NRCS) in Indiana. USGS Contract No. G16PC00022 Task Order No. G17PD00269 CONTRACTOR: Woolpert. USGS NGP Base Specifications v1.2 Leica ALS70 4 0.6 2.4 0.6 2.4 1981 150 40 46 272 5 2.5 1064 1 0.22 1442 25 GEOID12B USGS NGP Base Specifications v1.2 Leica ALS80 infinite 0.7 2.3 0.7 2.3 2377 150 40 35.5 346 5 2.5 1064 1 0.2 1731 25 GEOID12B USGS NGP Base Specifications v1.2 Optech Galaxy PRIME (2017) 8 0.7 2.36 0.7 2.36 1846 135 45 49.01 250 3 0.5 1064 1 0.25 1529 30 GEOID12B USGS NGP Base Specifications v1.2 Optech Galaxy PRIME (2020) 8 0.56 3.2 0.56 3.2 2133 150 40 70 450 3 0.5 1064 1 0.25 1553 30 GEOID12B USGS NGP Base Specifications v1.2 Riegl LMS-Q1560 (2018) 12 0.86 2.69 0.86 2.69 1722 150 58 172 600 3 0.3 1064 1 0.25 1930 20 GEOID12B USGS NGP Base Specifications v1.2 Riegl LMS-Q1560 (2019) 12 0.8 2.78 0.8 2.78 1981 145 58 172 600 3 0.3 1064 1 0.25 1442 25 GEOID12B 0 0 0 1.4 6 Geometrically unreliable points were identified using a combination of automated and manual techniques and subsequently classified as high or low noise and given the standard Withheld bit. Swath "overage" points were identified in these files using the standard LAS overlap bit. 16 1 Processed but not classified 2 Bare earth ground 7 Low Noise 9 Water 10 Ignored ground 17 Bridge Decks 18 High Noise 20170309 20200411 ground condition Complete None planned -88.174722 -86.195351 41.768459 37.755827 2655000 3195000 2375000 915000 None Project Level Lidar LAS Point Cloud Classified LAS Swath LAS Elevation Data Digital Elevation Model Remote Sensing None Indiana Benton County Boone County Carroll County Clay County Clinton County Crawford County Daviess County Dubois County Fountain County Gibson County Greene County Hendricks County Jasper County Knox County Lake County LaPorte County Lawrence County Martin County Monroe County Montgomery County Morgan County Newton County Orange County Owen County Parke County Perry County Pike County Porter County Posey County Pulaski County Putnam County Spencer County Starke County Sullivan County Tippecanoe County Vanderburgh County Vermillion County Vigo County Warren County Warrick County White County No restrictions apply to this dataset. None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data. Woolpert prepared the original data as set forth in the Scope of Services, in accordance with reasonable care and due diligence as set forth in this Agreement, however, due to the easily alterable nature of electronic media, files, documents, and other deliverables, Woolpert makes no warranties, either expressed or implied, with respect to the accuracy, completeness, merchantability, or fitness for any particular purpose, including, but not limited to, use of any/all data as described within this metadata file, by any user of this data. Any use will be at the end-user's sole risk. Microsoft Windows 10 Version 1803 (Build 17134.1304); ArcMap 10.7; ArcCatalog 10.7; TerraScan ver. 20; TerraModeler ver. 20; LP360 v2019.1.30.4. Data covers the entire area specified for this project. This dataset was validated using a combination of commercial lidar processing software, GIS software, and proprietary programs to ensure proper formatting and loading prior to delivery. The lidar data is visually inspected for completeness to ensure that are no void areas or missing data. This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. Woolpert 20201209 Lidar point cloud Dayton, OH Woolpert Digital data 20170305 20180421 ground condition Indiana Statewide Lidar 2017 B17 West - Lidar Point Cloud Data This dataset includes airborne lidar data point cloud data acquired as part of this task order. This data was used to create the required derivative lidar products. Woolpert 20201209 Vector digital data and tabular digital data Dayton, OH Woolpert Digital data 20170331 20170602 ground condition Indiana Statewide Lidar 2017 B17 West - Surveyed Control Points This dataset includes ground control and QA/QC checkpoints collected as part of this task order. These points were used in the calibration and accuracy testing of the lidar point cloud and DEM data. Woolpert 20201209 Vector digital data Dayton, OH Woolpert Digital data 20201209 ground condition Indiana Statewide Lidar 2017 B17 West - Breaklines This dataset includes hydro breaklines collected as part of this task order. Woolpert 20201209 Vector digital data Dayton, OH Woolpert Digital data 20201209 ground condition Indiana Statewide Lidar 2017 B17 West - Data Extent The data extent was created in shapefile format. Woolpert 20201209 Vector digital data Dayton, OH Woolpert Digital data 20201209 ground condition Indiana Statewide Lidar 2017 B17 West - Tile Index The tile index created in shapefile format. The tiles have a size of 5,000-feet x 5,000-feet. Tile names were derived from Indiana Statewide Ortho Lidar grid. This index was used to create the tiled deliverables for this project. Airborne Lidar Collection: Using Leica ALS70, Leica ALS80, Optech Galaxy PRIME, and Riegl LMS-Q1560 lidar sensors, high density data was collected at a nominal pulse spacing (NPS) of 0.7 meters. A total of seventy-four (74) total missions were flown. Multiple returns were recorded for each laser pulse along with an intensity value for each return. The survey crews were on-site, operating a Global Navigation Satellite System (GNSS) Base Station for the airborne GPS support. Specific information regarding latitude, longitude, and ellipsoid height to the L1 phase center is included in the lidar processing report. 20180421 Indiana Statewide Lidar 2017 B17 West - Lidar Point Cloud Data Control Point Collection: For this particular field effort, Woolpert field crews utilized Woolpert-owned, Trimble Navigation R series multi-frequency GPS receivers. Field personnel generated RTK vectors through the use of Sierra Wireless Raven XT Code Division Multiple Access (CDMA) modems and Trimble Navigation Continually Operating Reference Stations (CORS). Whenever possible, RTK observations were performed on all new lidar control points in order to collect data efficiently and accurately. The survey was conducted using a 1-second epoch rate, in a fixed solution RTK mode, with each observation lasting approximately 180 seconds. Each station was occupied twice to ensure the necessary horizontal and vertical accuracies were being met for this project. RTK surveys were performed where cellular data coverage was available and where baseline distance accuracy was maintained. Due to the usage of multiple RTK base stations, base stations with accompanying measurements were not contiguous. These stations were linked together via concurrent static observations, allowing for one contiguous network. CORS were also incorporated into the dataset to strengthen the overall baseline network. Data from observation sessions typically lasted several hours, with each session utilizing a 5-second sync rate. Static GPS was also utilized in areas in which cellular data coverage was limited. All static GPS observations were processed using Trimble Navigation's Trimble Business Center (TBC) 3.70 baseline processor with precise ephemeris. Both unconstrained and constrained adjustments were computed using trivial and nontrivial baselines. After an acceptable unconstrained least-squares adjustment was obtained, Woolpert performed a fully constrained least-squares adjustment by fixing the GPS network to existing NGS control stations with known coordinate data. Fixed solutions were obtained for all vector baselines. Indiana Statewide Lidar 2017 B17 West - Surveyed Control Points 20170602 After initial QC was completed, the mission's airborne GPS data was differentially processed using the GPS base station data, blended with the IMU data, and the integrity of the blended solution was verified. The blended GPS/IMU data was combined with the laser range data and instrument calibration parameters to produce raw swath files in the targeted project coordinate system. The use of current instrument calibration settings enabled the process to account for and correct all systematic sensor errors from the raw swath files for each mission. Ground control points are then imported and a check point report is produced. Once all ground control points are meeting spec, a ground control point report is exported. All lidar data files were delivered in EPSG: 2968 NAD83 (HARN) Indiana State Plane West, U.S. Survey Feet and NAVD88 GEOID12B, U.S. Survey Feet. Indiana Statewide Lidar 2017 B17 West - Lidar Point Cloud Data Indiana Statewide Lidar 2017 B17 West - Surveyed Control Points 20201209 Lidar Point Cloud Classification: 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 (Class 10), 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 1.14 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. Woolpert 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. Indiana Statewide Lidar 2017 B17 West - Lidar Point Cloud Indiana Statewide Lidar 2017 B17 West- Surveyed Control Points Indiana Statewide Lidar 2017 B17 West - Data Extent Indiana Statewide Lidar 2017 B17 West - Tile Index 20201209 Hydro Breaklines: Class 2 (ground) lidar points was used to create a bare-earth surface model. The compilation procedure included use of lidar intensity, bare-earth surface model, point cloud data, and open source imagery in an effort to compile hydrologic features in a 2-D environment. Elevation values were assigned to all inland ponds and lakes, inland pond and lake islands, and inland stream and river islands, using TerraModeler/LP360 functionality. All ground (Class 2) lidar data inside of the collected inland breaklines were then classified to water (Class 9) using TerraScan macro functionality. A buffer of 1.14 feet was also used around each hydro-flattened feature. These points were moved from ground (Class 2) to Ignored Ground (Class 10). Breaklines are reviewed against lidar intensity imagery and surface models to verify completeness of capture. The horizontal placement of breaklines is compared to terrain features and the breakline elevations are compared to lidar elevations to ensure all breaklines match the lidar within acceptable tolerances. Some deviation is expected between breakline and lidar elevations due to monotonicity, connectivity, and flattening rules that are enforced on the breaklines. Once completeness, horizontal placement, and vertical variance is reviewed, all breaklines are reviewed for topological consistency and data integrity using a combination of Esri Data Reviewer tools. The final lake and river hydrologic breakline products were delivered as polygon and polyline features classes in an Esri file geodatabase. Bridge breaklines were delivered as point features in Esri shapefile format. This breakline data was used in the processing of the DEM deliverable. Indiana Statewide Lidar 2017 B17 West - Lidar Point Cloud Indiana Statewide Lidar 2017 B17 West - Data Extent Indiana Statewide Lidar 2017 B17 West - Breaklines 20201209 Hydro-Flattened Digital Elevation Models (DEMs): Class 2 (ground) lidar points in conjunction with the hydro breaklines as well bridge breaklines were used to create a 2.5-foot, 32-bit floating point hydro-flattened bare-earth raster DEM. Using automated scripting routines within ArcMap, an ERDAS .IMG file was created for each tile. Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface. Indiana Statewide Lidar 2017 B17 West - Lidar Point Cloud Data Indiana Statewide Lidar 2017 B17 West - Surveyed Control Points Indiana Statewide Lidar 2017 B17 West - Breaklines Indiana Statewide Lidar 2017 B17 West - Data Extent Indiana Statewide Lidar 2017 B17 West - Tile Index 20201209 Intensity Imagery: TerraScan software was used to create the deliverable intensity images. All overlap classes were ignored during this process. This helps to ensure a more aesthetically pleasing image. Global Mapper software was then used to verify full project coverage as well. The lidar intensity image is a representation of the reflectivity of the collected lidar data. This data was provided as an 2.5-foot, 8-bit gray scale raster images of the reflective surface lidar intensity data in GeoTIFF format. A gridded raster file was created on a per tile basis. The task order projection information was applied to the final raster dataset. Prior to delivery, all raster files were visually reviewed to ensure coverage and reviewed using automated processes to ensure proper formatting. Indiana Statewide Lidar 2017 B17 West - Lidar Point Cloud Data Indiana Statewide Lidar 2017 B17 West - Data Extent Indiana Statewide Lidar 2017 B17 West - Tile Index 20201209 Point State Plane Coordinate System 1983 1302 0.99996667 -87.08333333 37.5 2952750.00000000 820208.33333333 coordinate pair 0.01 0.01 survey feet North American Datum of 1983 (HARN) Geodetic Reference System 80 6378137.0 298.257222101 North American Vertical Datum of 1988 0.01 feet Explicit elevation coordinate included with horizontal coordinates 20201209 Woolpert mailing and physical

4454 Idea Center Blvd

Dayton OH 45430 USA (937) 461-5660 FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998