gov.noaa.nmfs.inport:68798 eng UTF8 dataset Elevation OCM Partners resourceProvider NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact 2026-04-30T00:00:00 ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data ISO 19115-2:2009(E) NAD83(HARN) / UTM zone 15N2008-11-12publicationEuropean Petroleum Survey Grouphttps://apps.epsg.org/api/v1/CoordRefSystem/3745/export/?format=gmlurn:ogc:def:crs:EPSG:37456.18.3 2011 MN DNR Lidar: Twin Cities Metro (Minneapolis/St. Paul & Maple Grove), MN 2011 creation 2012 publication NOAA/NMFS/EDM 68798 https://www.fisheries.noaa.gov/inport/item/68798 WWW:LINK-1.0-http--link Full Metadata Record View the complete metadata record on InPort for more information about this dataset. information https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9681/ept.json WWW:LINK-1.0-http--link Entwine Point Tiles (EPT) 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. download https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?m=9681&g=geoid18 WWW:LINK-1.0-http--link NOAA Potree 3D View Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. download https://coast.noaa.gov/dataviewer/ WWW:LINK-1.0-http--link NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) 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. download https://resources.gisdata.mn.gov/pub/data/elevation/lidar/projects/metro/block_maple_grove/maple_grove_vertical_validation_report.pdf WWW:LINK-1.0-http--link MN DNR Maple Grove Vertical Validation Report The vertical validation report from the MN DNR. download https://resources.gisdata.mn.gov/pub/data/elevation/lidar/projects/metro/block_metro/metro_stpaul_minneapolis_vertical_validation_report.pdf WWW:LINK-1.0-http--link MN DNR Minneapolis/St. Paul Vertical Validation Report The vertical validation report from the MN DNR. download https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9681/supplemental/mn2011_minn_stp_mplgrv_m9681.kmz WWW:LINK-1.0-http--link Browse Graphic This graphic shows the lidar coverage for the 2011 lidar acquisition for Minneapolis/St. Paul and Maple Grove, MN. download 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 Minneapolis/St. Paul and Maple Grove blocks of the Twin Cities Metro data that are available from the NOAA Digital Coast Data Access Viewer (DAV). The NOAA Office for Coastal Management (OCM) downloaded 1776 laz point data files from these USGS sites: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MN_Phase4_Metro_Metro_2011_LAS_2016/laz/ (1536 laz files) https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MN_Phase4_Metro_MapleGrove_2011_LAS_2016/laz/ (240 laz files) The data were processed to the NOAA Digital Coast Data Access Viewer (DAV) to make the data available for custom downloads and to AWS S3 for bulk downloads. This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. 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 Fugro Horizons, Inc., and the Minnesota Department of Natural Resources The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed 2026-06-23 at https://coast.noaa.gov/dataviewer. completed NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information custodian asNeeded EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION theme Global Change Master Directory (GCMD) Science Keywords 23.3 CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MINNESOTA VERTICAL LOCATION > LAND SURFACE place Global Change Master Directory (GCMD) Location Keywords 23.3 LIDAR > Light Detection and Ranging instrument Global Change Master Directory (GCMD) Instrument Keywords 23.3 Airplane > Airplane platform Global Change Master Directory (GCMD) Platform Keywords 23.3 Lidar - partner (no harvest) project InPort otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-06-23 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2011 MN DNR Lidar: Twin Cities Metro (Minneapolis/St. Paul & Maple Grove), MN [Data Date Range], https://www.fisheries.noaa.gov/inport/item/68798. NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-06-23 from the NOAA system. Access Constraints: None otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-06-23 from the NOAA system. 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. otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-06-23 from the NOAA system. 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. unclassified 2011 MN DNR Lidar: Twin Cities Metro (Dakota Block), MN NOAA/NMFS/EDM 68740 crossReference 2011 MN DNR Lidar: Twin Cities Metro, MN NOAA/NMFS/EDM 68838 crossReference vector eng; US elevation -93.531701 -92.968891 44.812163 45.15633 | Currentness: Ground Condition 2011-11-02 2011-11-15 Twin Cities metropolitan region, Minnesota Zip Zip LAS/LAZ - LASer Zip NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information distributor https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9681/details/9681 WWW:LINK-1.0-http--link Customized Download 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. download https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9681/index.html WWW:LINK-1.0-http--link Bulk Download Simple download of data files. download dataset 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 Vertical Validation Reports for Minneapolis/St. Paul and Maple Grove at the links in the URL section of this metadata record. Completeness Report Complete Conceptual Consistency All deliverables were quality checked by MN DNR and passed inspection. Data were collected and processed by Fugro Horizons, Inc. and made available on the USGS ftp site. The data were downloaded from the USGS ftp site by the NOAA Office for Coastal Management (OCM) where the data were processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from AWS S3. 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. 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 The NOAA Office for Coastal Management (OCM) downloaded 1776 laz point data files from these USGS sites: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MN_Phase4_Metro_Metro_2011_LAS_2016/laz/ (1536 laz files) https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MN_Phase4_Metro_MapleGrove_2011_LAS_2016/laz/ (240 laz files) The data were in UTM Zone 15N NAD83 (HARN), meters coordinates and NAVD88 (Geoid09) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 3 - Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Buildings, 7 - Low Noise, 8 - Model Key Point, 9 - Water, 10 - Ignored Ground, 14 - Bridge Decks. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1,2,3,4,5,6,7,8,9,10,14. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid09 model b. Convert the laz files from UTM Zone 15N NAD83 (HARN) meters coordinates to geographic coordinates c. Assign the geokeys, sort the data by gps time and zip the data to database. 2022-12-14T00:00:00 Office for Coastal Management processor USGS USGS https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/ WWW:LINK-1.0-http--link USGS Rockyweb download site Source Citation URL information originator The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. 2026-06-23NOAA Office for Coastal Managementcoastal.info@noaa.govprocessor