Data Management Plan

2012 USACE Great Lakes Topobathy Lidar: Lake Michigan

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 lowpoints (7), valid bathymetric data (11), and valid topographic data acquired with the bathymetric sensor (14). Classes 1, 2, and 7 are defined in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards, while classes 11 and 14 are classes specific to the NOAA Digital Coast Data Access Viewer (DAV).These data were collected with a RIEGL VQ-480 airborne lidar system along the Lake Michigan shoreline.

Data coverage generally extends along the shoreline from the waterline to 500 meters onshore. The VQ-480 sensor has a pulse repetition rate of 150 kHz at near infrared laser wavelength. 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 Geographic Coordinates in decimal degrees, 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. The National Geodetic Surveys (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). The 3-D position data are sub-divided into a series of LAS files, each covering approximately 5 kilometers of shoreline.

Note: The NOAA Office for Coastal Management was unable to determine the exact dates of collection due to corrupt GPS times in at least of the LAS files. Classifications listed from the original metadata above may have changed during processes at NOAA OCM.

One-time data collection

2012-09-02, 2012-09-03, 2012-09-07, 2012-09-08, 2012-09-09, 2012-09-10, 2012-09-12, 2012-09-13, 2012-09-14, 2012-09-23, 2012-09-25, 2012-09-26, 2012-09-27, 2012-09-28, 2012-09-29, 2012-10-01, 2012-10-02, 2012-10-03, 2012-10-06, 2012-10-15, 2012-10-16, 2012-10-17, 2012-10-18, 2012-10-19, 2013-11-05, 2013-11-06, 2013-11-11, 2013-11-18, 2013-11-26

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

las

No information found

NOAA Office for Coastal Management (NOAA/OCM)

Metadata Contact

NOAA Office for Coastal Management (NOAA/OCM)

coastal.info@noaa.gov

(843) 740-1202

No information found

Data Steward

No information found

No information found

Process Steps:

• 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 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 (valid topographic data acquired with the bathymetric sensor), 27 (invalid topographic and bathymetric data), 29 (valid bathymetric data)
• 2015-03-30 00:00:00 - The NOAA Office for Coastal Management (OCM) received the topographic/bathymetric files in LAS format from USACE. The files contained lidar easting, northing, elevation, intensity, return number, etc. Some GPS times in the LAS files appeared to be corrupt. the data was received in Geographic Coordinates (decimal degrees). The vertical coordinates were referenced to IGLD85 in meters. using the Geoid03 model. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. Class 29 points (bathymetry) were reclassified to Class 11 (bathymetry). 2. Class 21 points (green topography) were reclassified to Class 14 (green topography). 3. Tile '2012_NCMP_MI_Michigan_05_Geoclassified_IGLD' was found to have erroneous points outside of the header's bounding box. These points were removed using LAStools' lasclip software. 4. The LAS files were then converted from IGLD85 orthometric heights to NAD83 (GRS80) ellipsoidal heights using NOAA's VDatum v3.3. 5. On March 30, 2015 tiles were added from an additional delivery from USACE following the same process.

No information found

No

NMFS Office of Science and Technology

https://www.fisheries.noaa.gov/inport/item/49736

Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf

No information found

NOAA Office for Coastal Management (NOAA/OCM)

This data can be obtained on-line at the following URL:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2644;

No information found

No information found

Office for Coastal Management - Charleston, SC

No information found

No information found