2011 MN DNR Lidar: Twin Cities Metro (Dakota Block), MN
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:68740 | Updated: October 17, 2023 | Published / External
Item Identification
Title: | 2011 MN DNR Lidar: Twin Cities Metro (Dakota Block), MN |
---|---|
Short Name: | mn2011_dakota_m9679_metadata |
Status: | Completed |
Creation Date: | 2011 |
Publication Date: | 2012 |
Abstract: |
Fugro Horizons Inc. acquired highly accurate Light Detection and Ranging (LiDAR) elevation data for the Twin Cities metropolitan region in east-central Minnesota in Spring and Fall 2011, with some reflights in Spring 2012. The data cover Anoka, Benton, Carver, Dakota, Goodhue, Hennepin, Isanti, Kanabec, Meeker, Mille Lacs, Morrison, Ramsey, Scott, Sherburne and Washington counties. Most of the data was collected at 1.5 points/square meter. Smaller areas were collected with 2 points/square meter and with 8 points/square meter: 1. 1.5 points/square meter covers Morrison, Mille Lacs, Benton, Isanti, Sherburne, Anoka, Meeker, Hennepin, Washington, Carver, Scott, and Goodhue counties. 2. 2 points/square meter covers the Dakota Block (southern 2/3 of Dakota County) 3. 8 points/square meter covers portions of Minneapolis/St. Paul and the City of Maple Grove See map of block boundaries: ftp://lidar.dnr.state.mn.us/documentation/status/metro_data_delivery_dates.pdf Data are in the UTM Zone 15 coordinate system, NAD83 NAVD88 Geoid09 meters. The tiling scheme is 16th USGS 1:24,000 quadrangle tiles. The vendor delivered the data to the Minnesota Department of Natural Resources (DNR) in several formats: 1. One-meter digital elevation model 2. Edge-of-water breaklines 3. Classified LAS formatted point cloud data DNR staff quality-checked the data and created two additional products: two-foot contours and building outlines. Note: The original metadata record was created at the Minnesota Geospatial Information Office using information supplied by the vendor and by DNR. Abstract Addendum, USGS National Geospatial Technical Operations Center (NGTOC), data edited November 2015: Data may have been modified from the original, delivered data by the NGTOC to correct issues such as breakline enforcement and hydro-flattening of water bodies, pits and spikes, and to remove edge tinning and other anomalies. End Abstract Addendum. This metadata record reflects the Dakota Block portion of the Twin Cities Metro data set and 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: |
The Minnesota Elevation Mapping Project was initiated to support the development of high accuracy land surface information for the purposes of improving water quality, flood emergency preparedness and response, floodplain mapping, transportation planning and design, recreational planning and design, urban planning and to provide more efficient and effective project planning and execution. This project was primarily funded by the Clean Water Fund of the Clean Water, Land and Legacy Amendment. For more about the Project, see: http://www.mngeo.state.mn.us/committee/elevation/mn_elev_mapping.html |
Supplemental Information: |
Twin Cities metropolitan region, Minnesota |
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: | As Needed |
Data Presentation Form: | Model (digital) |
Distribution Liability: |
1. Minnesota Department of Natural Resources General Geographic Data License Agreement 1) The Minnesota Department of Natural Resources (MNDNR) grants to you a non-exclusive, non-sublicensable, license to use these digital data. This License agreement applies to all digital data acquired from DNR staff, FTP sites, or other internet-based delivery systems. In the event that another license agreement issued by DNR staff is explicitly associated with a particular data set, the terms of the other license agreement prevail, and the terms expressed in this more general license agreement are nullified. 2) The MNDNR makes no representations about the suitability of these data for any purpose. The data are provided 'as is' without express or implied warranties, including warranties of merchantability and fitness for a particular purpose or non-infringement. 3) MNDNR is not obligated to provide updates to these data in the event that newer versions become available. MNDNR provides documentation when available through established distribution mechanisms. 4) The user relieves the MNDNR and its respective officers, agents, and employees of any liability for any and all damages resulting from use of mis-use of these data including, but not limited to: a. Incidental, consequential, special or indirect damages of any sort, whether arising in tort, contract or otherwise, even if MNDNR has been informed of the possibility of such damages, or b. For any claim by any other party. Furthermore, in States that do not allow the exclusion of limitation of incidental or consequential damages, you may not use these data. 5) When these data are used in the development of digital or analog (hardcopy) products, MNDNR must be acknowledged as having contributed data to the development of the product. 6) Although the use of these data are not restricted, they may not be sold commercially or privately without the written permission of MNDNR. 2. MnGeo's data disclaimer is online: http://www.mngeo.state.mn.us/chouse/disclaimer.html 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: | Fugro Horizons, Inc., and the Minnesota Department of Natural Resources |
Support Roles
Data Steward
Date Effective From: | 2022 |
---|---|
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: | 2022 |
---|---|
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: | 2011 |
---|---|
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: | 2022 |
---|---|
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: | 2022 |
---|---|
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: | -93.376249 | |
---|---|---|
E° Bound: | -92.682127 | |
N° Bound: | 44.83341 | |
S° Bound: | 44.455894 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2011-11-12 |
End: | 2011-11-15 |
Spatial Information
Spatial Representation
Representations Used
Grid: | No |
---|---|
Vector: | Yes |
Text / Table: | No |
TIN: | No |
Stereo Model: | No |
Video: | No |
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: | 2022-12-09 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9679/details/9679 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2022 - 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. |
File Type (Deprecated): | Zip |
Compression: | Zip |
Distribution 2
Start Date: | 2022-12-09 |
---|---|
End Date: | Present |
Download URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MN_Phase4_Metro_Dakota_2011_LAS_2016/ |
Distributor: | U.S. Geological Survey (2011 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of the Dakota block data files in LAZ format, based on a horizontal datum/projection of UTM Zone 15, NAD83, meters and a vertical datum of NAVD88 (GEOID09) and units in meters. This url links to the USGS copy of the files, from which the Entwine Point Tile files originated. These have not been reviewed by OCM and the link is provided here for convenience. |
File Type (Deprecated): | LAZ |
Distribution Format: | LAS/LAZ - LASer |
Compression: | Zip |
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://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MN_Phase4_Metro_Dakota_2011_LAS_2016%22 |
---|---|
Name: | USGS 3D Potree View |
URL Type: |
Online Resource
|
Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 3
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MN_Phase4_Metro_Dakota_2011_LAS_2016/ept.json |
---|---|
Name: | USGS Entwine Point Tiles (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. |
Data Quality
Horizontal Positional Accuracy: |
Meets or exceeds horizontal accuracy of 0.6m RMSE. |
---|---|
Vertical Positional Accuracy: |
REPORT FROM THE VENDOR: Vertical accuracy of the LiDAR data will be assessed and reported in accordance with the guidelines developed by the NDEP (National Digital Elevation Program) and subsequently adopted by the ASPRS (American Society for Photogrammetry and Remote Sensing). The complete guidelines may be found in Section 1.5 of the http://www.ndep.gov/NDEP_Elevation_Guidelines_Ver1_10May2004.pdf Vertical accuracy requirements using the NDEP/ASPRS: 1. 1.5 points/square meter areas: Sub-Project A 24.5cm ACCz, 95% (12.5cm RMSEz) 2. The higher density areas (Dakota Block, Metro Block and Maple Grove Block): 17.64cm ACCz 95% (9.0cm RMSEz) REPORTS FROM MINNESOTA DNR: True accuracy values: Metro Block - 5 cm Dakota Block - 10.8 cm Maple Grove Block - 8.3 cm See the complete Vertical Validation Reports in each folder on the data download FTP site; for example, the report for the Maple Grove Block is here: ftp://ftp.lmic.state.mn.us/pub/data/elevation/lidar/projects/metro/block_maple_grove/maple_grove_vertical_validation_report.pdf |
Completeness Report: |
Complete |
Conceptual Consistency: |
All deliverables were quality checked by MN DNR and passed inspection. |
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-CO |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to tape and to cloud storage. |
Lineage
Lineage Statement: |
The Dakota block of the Twin Cities Metro, MN lidar was ingested into the Data Access Viewer for custom product generation by leveraging USGS hosted Entwine Point Tiles. |
---|
Sources
Entwine Point Tiles on AWS
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://usgs.entwine.io/ |
Citation URL Name: | USGS Entwine Point Cloud |
Process Steps
Process Step 1
Description: |
VENDOR PROCESSING STEPS: (See map of block boundaries: ftp://lidar.dnr.state.mn.us/documentation/status/metro_data_delivery_dates.pdf ) 1. Specifications for Blocks A-H (1.5 points/square meter): The settings for the Leica sensor ALS50-II MPiA included acquisition at 6,600' AMT, 130 knots, pulse rate 99,500Hz, scan rate 27.28Hz, 40 degree field of view, 4,805ft swath width, maximum along track spacing (occurs at FOV edge) of 2.45m in overlap areas, maximum cross track spacing (occurs at Nadir) 1.24m, 3sigma post spacing of 1.4m and 3sigma point density of 0.65 points per square meter. This sensor was also equipped with IPAS inertial measuring unit (IMU) and a dual frequency airborne GPS receiver. These settings were used to meet or exceed the following accuracy specification in flat areas with minimal vegetation. 24.5cm ACCz, 95% (12.5cm RMSEz) 29.4cm ACCz, 95% (15.0cm RMSEz) 29.4cm ACCz 95% (15.0cm RMSEz). 2. Specifications for the Dakota Block (2 points/square meter): The settings for the FLI-MAP sensor included acquisition at 2,700' AMT, 145 knots, 30% sidelap, 150kHz, 60% degree field of View, 3,116ft swath to attain an approximate 8 points per square meter. This sensor was also equipped with an inertial measuring unit (IMU) and a dual frequency airborne GPS receiver. These settings were used to meet or exceed the following accuracy specification in flat areas with minimal vegetation. 17.64cm ACCz 95% (9.0cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz). 3. Specifications for the Metro Block and the Maple Grove Block (8 points/square meter): The settings for the FLI-MAP sensor included acquisition at 2,100' AMT, 130 knots, 60% sidelap, 200kHz, 60% degree field of View, 2,424ft swath to attain an approximate 8 points per square meter. This sensor was also equipped with an inertial measuring unit (IMU) and a dual frequency airborne GPS receiver. These settings were used to meet or exceed the following accuracy specification in flat areas with minimal vegetation 17.64cm ACCz 95% (9.0cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz) 24.5cm ACCz 95% (12.5cm RMSEz). The data set for each flight line was checked for project area coverage, data gaps between overlapping flight lines, and tension/compression areas (areas where data points are more or less dense that the average project specified post spacing). Using an iterative process that involves analyzing raster difference calculations the omega, phi, kappa angle corrections for the LiDAR instrument were determined. Corrections were applied to the LiDAR data set. Extensive comparisons were made of vertical and horizontal positional differences between points common to two or more LiDAR flight lines. An intensity raster for each flight line was generated and verified that intensity was recorded for each LiDAR point. LiDAR ground points were compared to independently surveyed and positioned ground control points in the project area. Based on the results of these comparisons, the LiDAR data was vertically biased to the ground. PRE-PROCESSING STAGE LiDAR, GPS and IMU data are processed together using LiDAR processing software. The LiDAR data set for each flight line is checked for project area coverage and LiDAR post spacing is checked to ensure it meets project specifications. The LiDAR collected at the calibration area is used to correct the rotational, atmospheric, and vertical elevation differences that are inherent to LiDAR data. Intensity raster is generated to verify that intensity was recorded for each LiDAR point. LiDAR data is transformed to the specified project coordinate system. By utilizing the ground survey data collected at the calibration site and project area, the LiDAR data is vertically biased to the ground. Comparisons between the biased LiDAR data and ground survey data within the project area are evaluated and a final RMSE value is generated to ensure the data meets project specifications. |
---|
Process Step 2
Description: |
VENDOR DELIVERABLES Deliverables for the LiDAR are in UTM15N NAD83/HARN NAVD88 Geiod09 meters. Each geodatabase is named for its respective USGS quarter-quarter quad name; there is a tiling scheme feature class in the elevation_data file geodatabase. Every geodatabase contains a feature dataset called "terrain_data". The terrain_data feature dataset contains up to two feature classes: Bare_Earth_Points and Hydro_Breaklines (when applicable). The Bare-Earth_Points feature class is comprised of MultipointZ shapefiles extracted from the Ground and KeyPoint LAS files. Both the Bare_Earth_Points and Hydro-Breaklines have been clipped to the USGS quarter-quarter quad extent. Each geodatabase also contains a DEM. The DEM was created from a terrain using bare-earth multipoint PointZ and hydro-breaklines. The Terrain was then converted to a Raster DEM using a 1-meter cell-size, then clipped to an adjusted, quarter-quarter quad minimum-bounding rectangle and buffered an additional 50 meters. The naming convention for all DEMs is "DEM01". LAS files are clipped to the provided USGS quarter-quarter quad. For the higher density blocks (Dakota Block; Metro Block; Maple Grove Block), the vendor tiled the las files further, breaking each standard tile into 16 additional tiles. They are simply appended an A,B,C, or D starting in the upper left and proceeding in a clockwise direction. A sample image ( http://www.mngeo.state.mn.us/chouse/elevation/16tile_naming_convention.jpg ) taken from the tile index map that is on the FTP site, shows a single tile with the sub-block lettering scheme. A sample tile name would be: 4243-02-30_a_a.laz Water edges were created using proprietary processes to create an accurate 3D representation of water features. Further hands-on evaluations are performed to ensure compliance with USGS V13 regarding Hydro-Flattening. Once the waterbodies are finalized, LAS bare-earth points within the extents of the water polygons are classified to Class 9 (Water). Bare-earth points within 1-meter of the water polygons are re-classified to Class 10 (Ignored Class). ADDITIONAL PRODUCTS GENERATED BY MINNESOTA DNR STAFF: These products are in the geodatabase for each of the tiles: 1. Two-foot contours were created by resampling the 1-meter DEM to 3 meters, then smoothing the 3-meter grid using a neighborhood average routine, and then creating contours from this surface using standard ArcGIS processing tools. 2. Building outlines were created by extracting from the LAS files those points with Classification 6 (buildings), then grouping those points within 3 meters of each other into a single cluster and then creating an outline around those points. This was done using standard ArcMap tools. 3. Hillshades were created from the one- and three-meter DEMs using standard ArcMap tools. Azimuth value = 215, Altitude = 45, Z-Factor = 1 |
---|
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 reprojected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical (NAVD88 GEOID09 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/USGS_LPC_MN_Phase4_Metro_Dakota_2011_LAS_2016/ept.json |
---|---|
Process Date/Time: | 2022-12-08 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Catalog Details
Catalog Item ID: | 68740 |
---|---|
GUID: | gov.noaa.nmfs.inport:68740 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2022-12-09 15:29+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2023-10-17 16:12+0000 |
Metadata Record Published: | 2022-12-09 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2022-12-09 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2023-12-09 |