Search Help Show/Hide Menu
Summary
Item Identification
Keywords
Physical Location
Data Set Info
Support Roles
Extents
Spatial Info
Access Info
Distribution Info
URLs
Activity Log
Data Quality
Lineage
Catalog Details

Summary

Short Citation
OCM Partners, 2025: 2012 USACE NCMP Topobathy Lidar: Lake Michigan (IL,IN,MI,WI), https://www.fisheries.noaa.gov/inport/item/73327.
Full Citation Examples

Abstract

Original Data:

These files contain classified topographic and bathymetric lidar data as unclassified valid topographic data (1), valid topographic data classified as ground (2), invalid topographic data classified as low points (7), water (9), points that fall in topographic areas that were acquired with the bathymetric sensor (21), valid bathymetric data (29). Classes 1,2,7,9 are defined in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards, while classes 21 and 29 are classes specific to the data collection. These data were collected with a RIEGL VQ-480 and a Coastal Zone Mapping and Imaging Lidar (CZMIL) airborne lidar system along the Lake Michigan shoreline. The VQ-480 sensor has a pulse repetition rate of 150 kHz at near infrared laser wavelength. CZMIL integrates a lidar sensor with topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities.

Data coverage generally extends along the shoreline from the waterline to 500 meters onshore. Native lidar data are not generally in a format accessible to most Geographical Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be exported to standard formats and imported into GIS software for visualization and further analysis. Horizontal positions, provided in UTM Zone 16N coordinates in meters, are referenced to the NAD83 (2011) Epoch 2010 datum. Vertical elevations in meters are also referenced to this datum (GRS80 ellipsoidal height). The 3-D position data are sub-divided into a series of LAS files, each derived from a single flightline. The National Geodetic Survey's (NGS) GEOID03 model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). Once converted to orthometric heights, the data are then converted to the International Great Lakes Datum of 1985 (IGLD85) using the VDatum program from NOAA (National Oceanic and Atmospheric Administration). The 3-D position data are sub-divided into a series of LAS files, each covering approximately 5 kilometers of shoreline. The format of the file is LAS version 1.2.

In addition to the lidar point data, the topobathy bare earth Digital Elevation Models (DEMs) at a 1 meter grid spacing, created from the lidar point data, are also available from the NOAA Digital Coast Data Access Viewer (DAV). A link to the bare earth 1 meter DEM data is provided in the URL section of this metadata record. DEMs at a 1 meter grid spacing, created from all classifications, are available by request at coastal.info@noaa.gov.

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, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum.

Access Constraints:

The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch/JALBTCX be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form.

Use Constraints:

These data depict the heights at the time of the survey and are only accurate for that time. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.

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. These data depict the heights at the time of the survey and are only accurate for that time.

Controlled Theme Keywords

COASTAL BATHYMETRY, 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

Geographic Area 1

-87.9458693° W, -84.6843231741° E, 46.1156698822° N, 41.5996674° S

Time Frame 1
2012-09-02
Time Frame 2
2012-09-03
Time Frame 3
2012-09-07
Time Frame 4
2012-09-08
Time Frame 5
2012-09-09
Time Frame 6
2012-09-10
Time Frame 7
2012-09-12
Time Frame 8
2012-09-13
Time Frame 9
2012-09-14
Time Frame 10
2012-09-23
Time Frame 11
2012-09-25
Time Frame 12
2012-09-26
Time Frame 13
2012-09-27
Time Frame 14
2012-09-28
Time Frame 15
2012-09-29
Time Frame 16
2012-10-01
Time Frame 17
2012-10-02
Time Frame 18
2012-10-03
Time Frame 19
2012-10-06
Time Frame 20
2012-10-15
Time Frame 21
2012-10-16
Time Frame 22
2012-10-17
Time Frame 23
2012-10-18
Time Frame 24
2012-10-19
Time Frame 25
2013-11-05
Time Frame 26
2013-11-06
Time Frame 27
2013-11-11
Time Frame 28
2013-11-18
Time Frame 29
2013-11-26

Item Identification

Title: 2012 USACE NCMP Topobathy Lidar: Lake Michigan (IL,IN,MI,WI)
Short Name: usace2012_lake_mich_m10170_metadata
Status: Completed
Creation Date: 2012
Publication Date: 2014
Abstract:

Original Data:

These files contain classified topographic and bathymetric lidar data as unclassified valid topographic data (1), valid topographic data classified as ground (2), invalid topographic data classified as low points (7), water (9), points that fall in topographic areas that were acquired with the bathymetric sensor (21), valid bathymetric data (29). Classes 1,2,7,9 are defined in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards, while classes 21 and 29 are classes specific to the data collection. These data were collected with a RIEGL VQ-480 and a Coastal Zone Mapping and Imaging Lidar (CZMIL) airborne lidar system along the Lake Michigan shoreline. The VQ-480 sensor has a pulse repetition rate of 150 kHz at near infrared laser wavelength. CZMIL integrates a lidar sensor with topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities.

Data coverage generally extends along the shoreline from the waterline to 500 meters onshore. Native lidar data are not generally in a format accessible to most Geographical Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be exported to standard formats and imported into GIS software for visualization and further analysis. Horizontal positions, provided in UTM Zone 16N coordinates in meters, are referenced to the NAD83 (2011) Epoch 2010 datum. Vertical elevations in meters are also referenced to this datum (GRS80 ellipsoidal height). The 3-D position data are sub-divided into a series of LAS files, each derived from a single flightline. The National Geodetic Survey's (NGS) GEOID03 model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). Once converted to orthometric heights, the data are then converted to the International Great Lakes Datum of 1985 (IGLD85) using the VDatum program from NOAA (National Oceanic and Atmospheric Administration). The 3-D position data are sub-divided into a series of LAS files, each covering approximately 5 kilometers of shoreline. The format of the file is LAS version 1.2.

In addition to the lidar point data, the topobathy bare earth Digital Elevation Models (DEMs) at a 1 meter grid spacing, created from the lidar point data, are also available from the NOAA Digital Coast Data Access Viewer (DAV). A link to the bare earth 1 meter DEM data is provided in the URL section of this metadata record. DEMs at a 1 meter grid spacing, created from all classifications, are available by request at coastal.info@noaa.gov.

Purpose:

These data were collected as a part of the NCMP to depict the elevations above and below the water for Lake Michigan in the Illinois, Indiana, Michigan, and Wisconsin coastal zone.

Notes:

10381

Keywords

Theme Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Science Keywords
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
Global Change Master Directory (GCMD) Science Keywords
EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY > COASTAL BATHYMETRY
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 > ILLINOIS
Global Change Master Directory (GCMD) Location Keywords
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > INDIANA
Global Change Master Directory (GCMD) Location Keywords
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MICHIGAN
Global Change Master Directory (GCMD) Location Keywords
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > WISCONSIN

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)
Entity Attribute Detail Citation:

none

Distribution Liability:

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

Data Set Credit: Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products.

Support Roles

Data Steward

CC ID: 1346247
Date Effective From: 2014-07-02
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

CC ID: 1346249
Date Effective From: 2014-07-02
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

Metadata Contact

CC ID: 1346250
Date Effective From: 2014-07-02
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

CC ID: 1346248
Date Effective From: 2014-07-02
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

CC ID: 1346294
W° Bound: -87.9458693
E° Bound: -84.6843231741
N° Bound: 46.1156698822
S° Bound: 41.5996674

Extent Group 1 / Time Frame 1

CC ID: 1346265
Time Frame Type: Discrete
Start: 2012-09-02

Extent Group 1 / Time Frame 2

CC ID: 1346266
Time Frame Type: Discrete
Start: 2012-09-03

Extent Group 1 / Time Frame 3

CC ID: 1346267
Time Frame Type: Discrete
Start: 2012-09-07

Extent Group 1 / Time Frame 4

CC ID: 1346268
Time Frame Type: Discrete
Start: 2012-09-08

Extent Group 1 / Time Frame 5

CC ID: 1346269
Time Frame Type: Discrete
Start: 2012-09-09

Extent Group 1 / Time Frame 6

CC ID: 1346270
Time Frame Type: Discrete
Start: 2012-09-10

Extent Group 1 / Time Frame 7

CC ID: 1346271
Time Frame Type: Discrete
Start: 2012-09-12

Extent Group 1 / Time Frame 8

CC ID: 1346272
Time Frame Type: Discrete
Start: 2012-09-13

Extent Group 1 / Time Frame 9

CC ID: 1346273
Time Frame Type: Discrete
Start: 2012-09-14

Extent Group 1 / Time Frame 10

CC ID: 1346274
Time Frame Type: Discrete
Start: 2012-09-23

Extent Group 1 / Time Frame 11

CC ID: 1346275
Time Frame Type: Discrete
Start: 2012-09-25

Extent Group 1 / Time Frame 12

CC ID: 1346276
Time Frame Type: Discrete
Start: 2012-09-26

Extent Group 1 / Time Frame 13

CC ID: 1346277
Time Frame Type: Discrete
Start: 2012-09-27

Extent Group 1 / Time Frame 14

CC ID: 1346278
Time Frame Type: Discrete
Start: 2012-09-28

Extent Group 1 / Time Frame 15

CC ID: 1346279
Time Frame Type: Discrete
Start: 2012-09-29

Extent Group 1 / Time Frame 16

CC ID: 1346280
Time Frame Type: Discrete
Start: 2012-10-01

Extent Group 1 / Time Frame 17

CC ID: 1346281
Time Frame Type: Discrete
Start: 2012-10-02

Extent Group 1 / Time Frame 18

CC ID: 1346282
Time Frame Type: Discrete
Start: 2012-10-03

Extent Group 1 / Time Frame 19

CC ID: 1346283
Time Frame Type: Discrete
Start: 2012-10-06

Extent Group 1 / Time Frame 20

CC ID: 1346284
Time Frame Type: Discrete
Start: 2012-10-15

Extent Group 1 / Time Frame 21

CC ID: 1346285
Time Frame Type: Discrete
Start: 2012-10-16

Extent Group 1 / Time Frame 22

CC ID: 1346286
Time Frame Type: Discrete
Start: 2012-10-17

Extent Group 1 / Time Frame 23

CC ID: 1346287
Time Frame Type: Discrete
Start: 2012-10-18

Extent Group 1 / Time Frame 24

CC ID: 1346288
Time Frame Type: Discrete
Start: 2012-10-19

Extent Group 1 / Time Frame 25

CC ID: 1346289
Time Frame Type: Discrete
Start: 2013-11-05

Extent Group 1 / Time Frame 26

CC ID: 1346290
Time Frame Type: Discrete
Start: 2013-11-06

Extent Group 1 / Time Frame 27

CC ID: 1346291
Time Frame Type: Discrete
Start: 2013-11-11

Extent Group 1 / Time Frame 28

CC ID: 1346292
Time Frame Type: Discrete
Start: 2013-11-18

Extent Group 1 / Time Frame 29

CC ID: 1346293
Time Frame Type: Discrete
Start: 2013-11-26

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Reference Systems

Reference System 1

CC ID: 1346302

Coordinate Reference System

CRS Type: Geographic 3D
EPSG Code: EPSG:6319
EPSG Name: NAD83(2011)
See Full Coordinate Reference System Information

Access Information

Security Class: Unclassified
Data Access Procedure:

Data is available for bulk and custom downloads.

Data Access Constraints:

The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch/JALBTCX be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form.

Data Use Constraints:

These data depict the heights at the time of the survey and are only accurate for that time. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.

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. These data depict the heights at the time of the survey and are only accurate for that time.

Distribution Information

Distribution 1

CC ID: 1346251
Start Date: 2014
End Date: Present
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10170/details/10170
Distributor: NOAA Office for Coastal Management (NOAA/OCM) (2014-07-02 - 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

CC ID: 1346252
Start Date: 2014
End Date: Present
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10170/index.html
Distributor: NOAA Office for Coastal Management (NOAA/OCM) (2014-07-02 - Present)
File Name: Bulk Download
Description:

Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum.

Distribution Format: LAS/LAZ - LASer
Compression: LAZ

URLs

URL 1

CC ID: 1346253
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

CC ID: 1346254
URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10167/details/10167
Name: Custom DEM Download
URL Type:
Online Resource
File Resource Format: Zip
Description:

Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) data that were created from this lidar data set.

URL 3

CC ID: 1346255
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10170/ept.json
Name: 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 4

CC ID: 1346397
URL: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10170/ept.json
Name: Potree 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.

Activity Log

Activity Log 1

CC ID: 1346257
Activity Date/Time: 2016-05-23
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 1346256
Activity Date/Time: 2017-11-14
Description:

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 1346258
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 1346259
Activity Date/Time: 2018-03-13
Description:

Partial upload to move data access links to Distribution Info.

Data Quality

Horizontal Positional Accuracy:

VQ-480

The data point positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than +/- 0.50 m RMSE

CZMIL

Topo data - Compiled to meet 1 m @ 95% confidence level. Bathy data - compiled to meet 3.5 + 0.05*d meters @ 95% confidence level (d is depth).

Vertical Positional Accuracy:

VQ-480

The data point positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than +/- 0.15 m RMSE

Differences between a DEM created from the lidar data representing bare ground and the ground truth point data is unbiased and within +/- 15 cm (RMSE) in flat terrain and within +/-30 cm (RMSE) in hilly terrain.

CZMIL

Topo data - 19.6 cm @ 95% confidence level (10 cm RMSE). Bathy shallow FOV data - SQRT((0.25^2)+((0.0075d)^2)) meters at @ 95% confidence level. Bathy deep FOV data - SQRT((0.30^2)+((0.013d)^2)) meters @ 95% confidence level (d is depth).

Completeness Measure:

This data set covers the spatial extent of bathymetric and topographic lidar data obtained during this survey.

Completeness Report:

This data set covers the spatial extent of bathymetric and topographic lidar data obtained during this survey.

Conceptual Consistency:

Differences between a DEM created from the lidar data representing bare ground and the ground truth point data is unbiased and within +/- 15 cm (RMSE) in flat terrain and within +/-30 cm(RMSE) in hilly terrain.

Lineage

Lineage Statement:

The NOAA Office for Coastal Management (OCM) received the data from the USACE Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX). NOAA OCM processed the data to the NOAA Digital Coast Data Access Viewer (DAV) to make the data publicly available for bulk and custom downloads.

Sources

USACE JALBTCX

CC ID: 1346398
Contact Role Type: Originator
Contact Type: Organization
Contact Name: USACE JALBTCX

Process Steps

Process Step 1

CC ID: 1346262
Description:

VQ-480

These data were collected using the RIEGL VQ-480 lidar system, operated by Fugro Pelagos through contract. The system collects topographic lidar data at maximum pulse rate of 150 kHz in a wavelength near infrared. Aircraft position, velocity and acceleration information are collected a POS AV 510 equipment. All logged raw data were transferred to the office and processed in RiPROCESS software. Aircraft position data are processed using POSPac software and the results combined with the lidar data to produce 3-D positions for each lidar shot. Upon processing and export to LAS format, QA/QC is performed with Fledermaus and FPI Workbench tools. Data are classified as 0 (valid topographic data), 21 (points that fall in topographic areas that were acquired with the bathymetric sensor), 29 (valid bathymetric data). The data are then shifted vertically to the International Great Lakes Datum of 1985 (IGLD85) using the VDatum program from NOAA (National Oceanic and Atmospheric Administration).

CZMIL

These data were collected using the CZMIL system. It is owned and operated by the U.S. Army Corps of Engineers (USACE). The system collects lidar data at 20 kHz and RGB imagery at 2 Hz. A CASI-1500 hyperspectral line scanner is integrated with the system as well. Aircraft position, velocity and acceleration information are collected through a combination of Novatel and POS A/V 510 equipment. All raw data streams are transferred to the office for downloading and processing in CZMILs Hydro Fusion software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QA/QC in the software packages Fledermaus and PFM_ABE, anomalous data are flagged as invalid. NOAA's VDatum software then converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID12A model and exports valid lidar data as a series of unclassified LAS files.

Process Step 2

CC ID: 1346263
Description:

VQ-480

The flightline LAS files are imported into GeoCue [V7.0.3.5], which is a geospatial workflow production and management software tool employed by JALBTCX to perform and monitor production of data products. Upon import into GeoCue, the flightline LAS files are divided into a series of boxes, each of which are 1500 meters in length and width. A customized classification macro, built upon the TerraScan [V11] module within Microstation V8i, classifies valid topographic data as ground points (2) and unclassified points (1). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithm's ground surface instead of manually reclassifying those points. The final classification results are comprised of individual lidar points with classifications of ground (2) or unclassified (1). They are partitioned into a series of 5km delivery boxes, one Classified LAS file per box. The format of the file is LAS version [1.2]. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), 21 (points that fall in topographic areas that were acquired with the bathymetric sensor), 29 (valid bathymetric data).

CZMIL

LAS files are imported into GeoCue V2012.1.27.7, which is a geospatial workflow production and management software tool employed by JALBTCX to perform and monitor production of data products. Upon import into GeoCue, A customized classification macro, built upon the TerraScan V13 module within Microstation V8i, classifies valid topographic data as ground points (2), valid bathymetric data as bathy (29), and unclassified points (1). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithms ground surface instead of manually reclassifying those points. The final classification results are comprised of individual lidar points with classifications of ground (2) or unclassified (1). They are partitioned into a series of 5km or quarter quad delivery boxes, one Classified LAS file per box. The format of the file is LAS version 1.2. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), 29 (valid bathymetric data).

Process Step 3

CC ID: 1346399
Description:

The NOAA Office for Coastal Management (OCM) received laz files from USACE JALBTCX for the Lake Michigan coastline. The lidar data had elevation and intensity measurements. The data were in geographic (NAD83 2011) coordinates and IGLD85 elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Noise, 9 - Water, 21 - points that fall in topographic areas that were acquired with the bathymetric sensor, 29 - Bathymetric Point. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 21, 29.

OCM performed the following processing on the data for Digital Coast storage and provisioning purposes:

1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges.

2. The LAZ files were converted from IGLD85 elevations to NAD83 (GRS80) ellipsoidal heights using the GEOID 03 model.

3. Internal OCM scripts were run on the laz files to assign the geokeys, to sort the data by gps time and zip the data to database and to AWS S3.

Process Date/Time: 2024-08-23 00:00:00
Process Contact: Office for Coastal Management (OCM)

Catalog Details

Catalog Item ID: 73327
GUID: gov.noaa.nmfs.inport:73327
Metadata Record Created By: Rebecca Mataosky
Metadata Record Created: 2024-08-26 20:37+0000
Metadata Record Last Modified By: Rebecca Mataosky
Metadata Record Last Modified: 2024-08-27 14:15+0000
Metadata Record Published: 2024-08-27
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16