2024 USGS Lidar DEM: Red River, MN

Original Product: These are the Digital Elevation Model (DEM) data for the 2023 Minnesota Red River project.

Original Geographic Extent: covering approximately 16,141 square miles in the state of Minnesota

MN_RedRiver_1 (Work Unit 300611) - covers approximately 4701 square miles in Norman, Clay, Otter Tail, Grant, Wilkin, Traverse, Polk, Mahnomen, Becker, Stevens, and Big Stone counties

MN_RedRiver_2 (Work Unit 300612) - covers approximately 5133 square miles in Kittson, Roseau, Marshall, Pennington, Red Lake, and Polk counties

MN_RedRiver_3 (Work Unit 300613) - covers approximately 3012 square miles in Roseau, Marshall, Pennington, Red Lake, Clearwater, and Polk counties

MN_RedRiver_4 (Work Unit 300614) - covers approximately 3295 square miles in Polk, Clearwater, Mahnomen, Becker, Otter Tail, Wadena, Todd, Grant, Douglas, Stevens, and Pope counties

Original Dataset Description: This Minnesota Red River project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at an aggregate nominal pulse spacing (ANPS) of 0.35 meters (8ppsm). Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification 2024 Rev A. The data was developed based on a horizontal projection/datum of NAD83 (2011), UTM14N (EPSG 6343) and UTM15N (EPSG 6344), meters and a vertical datum of NAVD88 (GEOID18), meters. Lidar data was delivered as classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles, and as tiled bare earth DEMs; all tiled to the same 1000 m x 1000 m schema. Swath separation images and maximum height surface rasters will be included in the final deliverables.

Ground Conditions: Lidar was collected in Spring of 2024, under cloud, fog, and snow free conditions, with no unusual flooding or inundation.

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 GeoTIFF files hosted by USGS on Amazon Web Services.

This lidar data will support the United States Geological Survey (USGS) initiatives.

USGS Contract No. 140G0221D0010 CONTRACTOR: Fugro Geospatial, Inc. SUBCONTRACTOR: Terrasurv, Inc. Ground control and checkpoints collected by Terrasurv, Inc. All processing was completed by the prime contractor.

DEM Raster File Type = GeoTIFF

Bit Depth/Pixel Type = 32-bit float

Raster Cell Size = 0.5 meter

Interpolation or Resampling Technique = Triangulated Irregular Network (TIN)

Network Required Vertical Accuracy = 10 cm NVA

Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.

To the extent possible under law, the U.S. Government has waived all copyright and related or neighboring rights to this dataset.

Data is available online for bulk and custom downloads.

None

Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.

This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data, Edition 2 (2023) for a 18.9 cm RMSEH horizontal positional accuracy class.

This data set was tested to meet ASPRS Positional Accuracy Standards for Digital

Geospatial Data, Edition 2 (2023) for a 10 (cm) RMSEV Vertical Accuracy Class.

USGS Determined DEM Vertical Accuracy:

Non-Vegetated Vertical Accuracy (NVA) = 2.63 cm RMSE

Vegetated Vertical Accuracy (VVA) = 7.32 cm at 95th Percentile

A complete iteration of processing (GPS/IMU Processing, Raw Lidar Data Processing, and Verification of Coverage and Data Quality) was performed to ensure that the acquired data was complete, uncorrupted, and that the entire project area had been covered without gaps between flight lines. No void areas or missing data exist. The raw point cloud is of good quality and data passes Vertical Accuracy requirements.

A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The point cloud is of good quality and data passes Vertical Accuracy requirements. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist.

The DEM raster files cover the entire project delivery boundary. The pixels that fall outside the project delivery boundary are set to Void with a unique NODATA value. The value is identified in the file headers. There are no void pixels inside the project boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The bare earth surface is of good quality and passes Vertical Accuracy requirements.

Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of GPS base stations in the project area. The following checks were performed: 1) The lidar data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior to generating a digital terrain model (DTM) or other products. 2) Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). The following software was used for the validation: 1) RiProcess 1.8.3, RiWorld 5.0.2, RiAnalyze 6.2, RiServer 1.99.5; and 2) Fugro proprietary software.

The NOAA Office for Coastal Management (OCM) ingested references to the USGS GeoTIFF files that are hosted on Amazon Web Services (AWS), into the Digital Coast Data Access Viewer (DAV). The DAV accesses the raster data as it resides on AWS.