2018 MN DNR Lidar: Lake County, MN
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:72334 | Updated: March 20, 2024 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2018 MN DNR Lidar: Lake County, MN, https://www.fisheries.noaa.gov/inport/item/72334.
Full Citation Examples
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 3041 individual 750 m x 750 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.
Geographic Extent: The central portion of Lake County in Minnesota, covering approximately 627 total square miles.
Dataset Description for the Original Data: The MNDNR Lake County 2018 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.236 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1.3. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM Zone 15N, Meter and vertical datum of NAVD88 GEOID12B, Meter. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 3041 individual 750 m x 750 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 750 m x 750 m schema. Continuous breaklines were produced in Esri file geodatabase format.
Ground Conditions: LiDAR was collected in fall 2018, 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, Quantum Spatial, Inc. utilized a total of 14 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 70 independent accuracy checkpoints, 40 in Bare Earth and Urban landcovers (40 NVA points), 30 in Tall Weeds categories (30 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.
Distribution Information
-
Not Applicable
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.
-
LAS/LAZ - LASer
Bulk download of data files in LAZ format, UTM Zone 15N NAD83 (2011) meters coordinates and orthometric (Geoid12b) elevations in meters.
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.
Controlled Theme Keywords
elevation, TERRAIN ELEVATION
Child Items
No Child Items for this record.
Contact Information
Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Extents
-91.8065675406° W,
-91.0088228212° E,
47.8790143692° N,
47.5408246016° S
2018-09-22 - 2018-10-22
Dates of collection for Lake County
Item Identification
Title: | 2018 MN DNR Lidar: Lake County, MN |
---|---|
Short Name: | mn2018_lake_m10101_metadata |
Status: | Completed |
Creation Date: | 2018 |
Publication Date: | 2019-01-31 |
Abstract: |
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 3041 individual 750 m x 750 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. Geographic Extent: The central portion of Lake County in Minnesota, covering approximately 627 total square miles. Dataset Description for the Original Data: The MNDNR Lake County 2018 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.236 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1.3. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM Zone 15N, Meter and vertical datum of NAVD88 GEOID12B, Meter. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 3041 individual 750 m x 750 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 750 m x 750 m schema. Continuous breaklines were produced in Esri file geodatabase format. Ground Conditions: LiDAR was collected in fall 2018, 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, Quantum Spatial, Inc. utilized a total of 14 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 70 independent accuracy checkpoints, 40 in Bare Earth and Urban landcovers (40 NVA points), 30 in Tall Weeds categories (30 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. |
Purpose: |
To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 0.3 meter cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. |
Supplemental Information: |
Contract No. I6AAP-17; CONTRACTOR: Quantum Spatial, Inc. The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "USGS-NGP Base Specification v1.3", "ldrsens" : "Riegl 1560i", "ldrmaxnr" : "unlimited", "ldrnps" : "0.236", "ldrdens" : "18.0", "ldranps" : "0.236", "ldradens" : "17.95", "ldrfltht" : "1306", "ldrfltsp" : "145", "ldrscana" : "29", "ldrscanr" : "41.5", "ldrpulsr" : "193", "ldrpulsd" : "3", "ldrpulsw" : "0.24", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.18", "ldrswatw" : "1448.0", "ldrswato" : "55", "ldrgeoid" : "GEOID 12B", "ldrcrs" : "NAD 1983 2011 UTM Zone 15N, Meter" }, "ldraccur" : {
"ldrchacc" : "0", "rawnva" : "0", "rawnvan" : "0", "clsnva" : "0", "clsnvan" : "0", "clsvva" : "0", "clsvvan" : "0" }, "lasinfo" : {
"lasver" : "1.4", "lasprf" : "6", "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.", "lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit.", "lasintr" : "16", "lasclass" : {
"clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : {
"clascode" : "2", "clasitem" : "Bare-Earth Ground" }, "lasclass" : {
"clascode" : "3", "clasitem" : "Low Vegetation" }, "lasclass" : {
"clascode" : "4", "clasitem" : "Medium Vegetation" }, "lasclass" : {
"clascode" : "5", "clasitem" : "High Vegetation" }, "lasclass" : {
"clascode" : "6", "clasitem" : "Buildings" }, "lasclass" : {
"clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : {
"clascode" : "8", "clasitem" : "Model Key Points" }, "lasclass" : {
"clascode" : "9", "clasitem" : "In-land Water" }, "lasclass" : {
"clascode" : "18", "clasitem" : "High Noise" }, "lasclass" : {
"clascode" : "20", "clasitem" : "Ignored Ground" } }} |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
|
ISO 19115 Topic Category |
elevation
|
Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA
|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MINNESOTA
|
Global Change Master Directory (GCMD) Location Keywords |
VERTICAL LOCATION > LAND SURFACE
|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords |
LIDAR > Light Detection and Ranging
|
Platform Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Platform Keywords |
Airplane > Airplane
|
Physical Location
Organization: | Office for Coastal Management |
---|---|
City: | Charleston |
State/Province: | SC |
Data Set Information
Data Set Scope Code: | Data Set |
---|---|
Data Set Type: | Elevation |
Maintenance Frequency: | None Planned |
Data Presentation Form: | Model (digital) |
Distribution Liability: |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
Data Set Credit: | Quantum Spatial, Inc., MN Dept. of Natural Resources |
Support Roles
Data Steward
Date Effective From: | 2024 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2024 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2019 |
---|---|
Date Effective To: | |
Contact (Organization): | U.S. Geological Survey |
Address: |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
URL: | USGS Home |
Metadata Contact
Date Effective From: | 2024 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Point of Contact
Date Effective From: | 2024 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Extents
Currentness Reference: | Ground Condition |
---|
Extent Group 1
Extent Group 1 / Geographic Area 1
W° Bound: | -91.8065675406 | |
---|---|---|
E° Bound: | -91.0088228212 | |
N° Bound: | 47.8790143692 | |
S° Bound: | 47.5408246016 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2018-09-22 |
End: | 2018-10-22 |
Description: |
Dates of collection for Lake County |
Spatial Information
Spatial Representation
Representations Used
Grid: | No |
---|---|
Vector: | Yes |
Text / Table: | No |
TIN: | No |
Stereo Model: | No |
Video: | No |
Vector Representation 1
Point Object Present?: | Yes |
---|---|
Point Object Count: | 98127054316 |
Reference Systems
Reference System 1
Coordinate Reference System |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Reference System 2
Coordinate Reference System |
|||||||||||||||||||||||
|
Access Information
Security Class: | Unclassified |
---|---|
Data Access Procedure: |
Data is available online for bulk and custom downloads. |
Data Access Constraints: |
None |
Data Use Constraints: |
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. |
Distribution Information
Distribution 1
Start Date: | 2024-03-20 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10101/details/10101 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2024 - Present) |
File Name: | Customized Download |
Description: |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. |
Distribution Format: | Not Applicable |
Compression: | Zip |
Distribution 2
Start Date: | 2019 |
---|---|
End Date: | Present |
Download URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/MN_LakeCounty_2018_C20/MN_LakeCounty_2018/LAZ/ |
Distributor: | U.S. Geological Survey (2019 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of data files in LAZ format, UTM Zone 15N NAD83 (2011) meters coordinates and orthometric (Geoid12b) elevations in meters. |
Distribution Format: | LAS/LAZ - LASer |
Compression: | LAZ |
URLs
URL 1
URL: | https://coast.noaa.gov/dataviewer/ |
---|---|
Name: | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type: |
Online Resource
|
File Resource Format: | HTML |
Description: |
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. |
URL 2
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/MN_LakeCounty_2018_C20/MN_LakeCounty_2018/reports/MNDNR_2018_LiDAR_ProjectReport.pdf |
---|---|
Name: | Lidar Report |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Quantum Spatial lidar project report. |
URL 3
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/MN_LakeCounty_2018_C20/MN_LakeCounty_2018_C20_Project_Report.pdf |
---|---|
Name: | USGS Project Report |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used. |
URL 4
URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/metadata/MN_LakeCounty_2018_C20/MN_LakeCounty_2018/ |
---|---|
Name: | USGS Additional Info |
URL Type: |
Online Resource
|
Description: |
Link to the reports, breaklines, metadata, and spatial metadata. |
URL 5
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MN_LakeCounty_2018/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 6
URL: | https://usgs.entwine.io/data/view.html?r=https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MN_LakeCounty_2018/ept.json |
---|---|
Name: | USGS 3D View |
URL Type: |
Online Resource
|
Description: |
Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer. |
Technical Environment
Description: |
MicroStation Version 8; TerraScan Version 18; TerraModeler Version 18; GeoCue Version 2017.1.14.1; Esri ArcGIS 10.3; Global Mapper 19; RiProcess 1.8.5; Windows 10 Operating System \\point_cloud\tilecls\*.las |
---|
Data Quality
Vertical Positional Accuracy: |
This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. USGS Determined Vertical Accuracy: Tested NVA RMSEz = 5.7 cm Tested 95th percentile value for VVA is : 21.76 cm For more information see the USGS project report and the lidar report. The links to these reports are provided in the URL section of this metadata record. |
---|---|
Completeness Report: |
These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and the data pass Non-Vegetated Vertical Accuracy specifications. |
Conceptual Consistency: |
Data cover the entire area specified for this project. |
Data Management
Have Resources for Management of these Data Been Identified?: | Yes |
---|---|
Approximate Percentage of Budget for these Data Devoted to Data Management: | Unknown |
Do these Data Comply with the Data Access Directive?: | Yes |
Actual or Planned Long-Term Data Archive Location: | NCEI-NC |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to cloud storage. |
Lineage
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. |
---|
Sources
USGS AWS Entwine Point Tile (EPT) - MN_LakeCounty_2018
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MN_LakeCounty_2018/ept.json |
Citation URL Name: | Entwine Point Tile (EPT) for MN_LakeCounty_2018 |
Process Steps
Process Step 1
Description: |
Raw Data and Boresight Processing: 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 Quantum Spatial, 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 technicians then analyzed the results and made any necessary additional adjustment until it was 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 matched 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 7 cm RMSEz within individual swaths and less than or equal to 10 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 checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. |
---|---|
Process Date/Time: | 2019-01-01 00:00:00 |
Process Step 2
Description: |
LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. 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 Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS 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. 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 through numerous conference calls and pilot study areas. All data were 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. Quantum Spatial, Inc. proprietary software 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. |
---|---|
Process Date/Time: | 2019-01-01 00:00:00 |
Process Step 3
Description: |
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 (NAVD88 GEOID12B meters). |
---|---|
Process Contact: | U.S. Geological Survey |
Process Step 4
Description: |
The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tiles (EPT) 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. This is the AWS URL being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MN_LakeCounty_2018/ept.json |
---|---|
Process Date/Time: | 2024-03-20 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Catalog Details
Catalog Item ID: | 72334 |
---|---|
GUID: | gov.noaa.nmfs.inport:72334 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2024-03-20 18:41+0000 |
Metadata Record Last Modified By: | Rebecca Mataosky |
Metadata Record Last Modified: | 2024-03-20 19:19+0000 |
Metadata Record Published: | 2024-03-20 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2024-03-20 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2025-03-20 |