gov.noaa.nmfs.inport:49797
eng
UTF8
dataset
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
2024-02-29T00:00:00
ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data
ISO 19115-2:2009(E)
2008 USACE NCMP Topographic Lidar: Lake Superior
mi2008_usace_lakesuperior_m2517_metadata
2013-08-09
publication
NOAA/NMFS/EDM
49797
https://www.fisheries.noaa.gov/inport/item/49797
WWW:LINK-1.0-http--link
Full Metadata Record
View the complete metadata record on InPort for more information about this dataset.
information
https://coast.noaa.gov/dataviewer
WWW:LINK-1.0-http--link
Citation URL
Online Resource
download
https://coast.noaa.gov
WWW:LINK-1.0-http--link
Citation URL
Online Resource
download
Fugro Pelagos contracted BLOM Aerofilms Limited to carry out the bathymetric laser data acquisition and part
of the hyperspectral imagery capture for these 3 areas which totals approximately 240km2. This data was collected
using a Hawk Eye II hydrographic and topographic LiDAR sensor. Imagery was acquired using a uEye 2250-M/C USB2.0
CCD UXGA Camera. The laserdata was processed onsite using Coastal Survey Studio and POSpac software to check
for coverage and quality. The data was then processed at the Cheddar office using the Terrasolid OY software;
the necessary macros were applied and manual reclassification was performed. Each individual wave form
was analysed in Coastal Survey Studio and reflectance values were gained; these values were then combined
with the classified laser data A conversion tool was then used to give the correct projections (IGLD85 and
NAD83) and the data was exported in an ASCII format.
Original contact information:
Contact Org: JALBTCX
Title: Data Production Manager
Phone: 228-252-1111
Email: shoals-info@sam.usace.army.mil
The purpose of the survey is to collect data representing the existing conditions of the beach and near
shore area along the Great Lake shorelines in support of the US Army Corps of Engineers (USACE) National
Coastal Mapping Program executed by the Joint Airborne LiDAR Bathymetry Technical Center of Expertise (JALBTCX)
JALBTCX
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
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2517/supplemental/2008_USACE_Great_Lakes_TopoBathy_Lidar_MI_Lake_Superior.KMZ
This graphic shows the lidar coverage for Alger, Bayfield, Chippewa, Luce and Ontonagon counties in Wisconsin
kmz
ASCII XYZ
BLOM Aerofilms Ltd
CHARTS
Fugro Pelagos
Hawk Eye II
JALBTCX
SHOALS
U.S. Army Corps of Engineers
inlandWaters (for Great Lakes projects)
theme
2008
October
temporal
Lidar - partner (no harvest)
project
InPort
otherRestrictions
Cite As: OCM Partners, [Date of Access]: 2008 USACE NCMP Topographic Lidar: Lake Superior [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49797.
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
Access Constraints: None
otherRestrictions
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
Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of JALBTCX, the Office for Coastal Management or its partners.
unclassified
NOAA Data Management Plan (DMP)
NOAA/NMFS/EDM
49797
https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49797.pdf
WWW:LINK-1.0-http--link
NOAA Data Management Plan (DMP)
NOAA Data Management Plan for this record on InPort.
information
crossReference
vector
eng; US
elevation
Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.2.6.1500
-91.208258
-85.164464
46.536586
47.003618
| Currentness: Ground Condition
2008-11-03
2008-11-11
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2517/supplemental/2008_USACE_Great_Lakes_TopoBathy_Lidar_MI_Lake_Superior.KMZ
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=2517
WWW:LINK-1.0-http--link
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
download
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2517/index.html
WWW:LINK-1.0-http--link
Bulk Download
Simple download of data files.
download
dataset
Accuracy
The raw topographic LiDAR was compared to ground surveyed reference surfaces within the project. The xyz position of the surface points surveyed by RTK GPS was located in the .dgn file and the point cloud hits on the surface were assessed. The raw LiDAR z was compared to the surveyed z, to generate the values given above. The flight lines and trajectories were then matched and adjusted to remove systematic errors. This then ensured the data was to the required specification before the data was used for production of the deliverables. | Quantitative Value: N/A | Quantitative Test Explanation: These data are not attributed.
Horizontal Positional Accuracy
The data has been collected and compiled to meet the: Bathy data: +/- 2.50m rmse Topo data: +/- 0.50m rmse accuracy
specification. Confirmation of achieved accuracy was demonstrated in Ground Control Area comparisons with recorded data
; Quantitative Value: 0.75 meters, Test that produced the value: 1 Sigma
Vertical Positional Accuracy
The data has been collected and compiled to meet the +/- 0.25m rmse accuracy specification. Confirmation of the achieved
accuracy was demonstrated by Ground Control Area comparisons
; Quantitative Value: 0.25 meters, Test that produced the value: RMSE at 1sigma = 0.25m
Completeness Measure
Cloud Cover: Unknown
Completeness Report
Not provided
Conceptual Consistency
LiDAR Specifications: 400m above lake surface level flying height; 15-20 degree field of view, 220m average swath widths flown
with 30m side overlap; 64,000 pulses per second (land), 4,000 pulses per second (sea), 1.064 um wavelength (red, land) and 532
um wavelength (green, sea).,Up to 4 returns and one REFLECTANCE value per pulse. LiDAR flown with Hawk Eye Mark II LiDAR. The
flights consisted of generally of flight lines parallell with the shoreline, with further overlapping and transverse flight
lines to ensure coverage of the entire area as required. LiDAR data and camera calibration carried out as required on
commencement of survey, when cameras / laser heads were changed and at other periods as necessary. Acgusition: Hawk Eye II
is operated by Blom Aerofilms using one operator and one pilot in a small aeroplane (Rockwell Commander N-690CL). Data
were acquried using HawkEye II. Sensor orientation was measured using POS AV 410 with GPS running at 10Hz). Images were
acquired using uEye UCGA 2M Pixel digital camera.
The laser data was collected using the HawkEye Mk II airborne system, the Hawkeye MKII system consists of two
lasers scanners; one green (wavelength 532um) which is used for capturing the Bathymetric data and one red (wavelength
1.064um) for the Topographic data. The system emitted 64 000 pulses per second (topographic) and 4 000 pulses per
second (bathymetric) with up to 4 returns and one reflectance value per pulse. The laser data collected was flown
using a fixed wing platform mounted to the Rockwell Aero Commander 690 aircraft registration N690CL. The Aircraft
was crewed with one pilot and one operator who was responsible for flight line planning, mission planning and
aircraft control during the survey. The operator used the AHAB Airborne Operator Console software to do this
Sensor orientation was measured using POS AV 410 with GPS running at 10Hz. The aerial acquisition starting on
the 01st October 2008; the flying height for the survey was 400m (approx 1300ft) with a swathe of 220m and a
30m flightline overlap, with the flight speed some 150 knots (approx 290 km/h). A total of 145 flight-lines
were required and a total of 17 online hours to cover the 3 survey areas in order to achieve 100% coverage.
Area 1 required 88 lines and 11 online hours, Area 5 required 24 lines and 3 online hours and Area 6 required
33 lines and 3 online hours. The raw LiDAR data was checked for matching and coverage following each flight;
trajectory files were produced using POSpac v5.2 and the data was then processed using Coastal Survey Studio
(CSS) v2.1. A final check at the end of the acquisition period confirmed that all requirements had been met
and all the data acquired to specification. On completion of all the QC checks the laser data for each
flight line was exported as individual files for import into Terrascan for cleaning and classification.
Topographic and hydrographic data was processed to different criteria, however during processing all data
sets were kept together so it was possible to edit and visualise both datasets in the same environment
simultaneously. Both the topographic and hydrographic laser data was imported into the TerraSolid OY
software running in the MicroStation v8 environment. The laser data was passed through a number of automated
macros for classification. The topographic laser data was then checked with the imagery by an experienced
editor to remove any hits from the sea areas and to ensure that the ground was correctly classified.
To ensure the quality of the data it was compared with topographic land survey data and overlapping or
crossing flightlines are checked. The hydrographic laser data was "cleaned", removing any rogue points,
floating structures, deep points or null points with no bottom returns. Overlapping or crossing
flightlines were checked and comparison with topographic points took place to ensure quality. To gain
reflectance values, the wave form of each individual laser sounding was analyzed in CSS (Coastal Survey
Studio); the echo intensity was extracted and the data was corrected for several system biases. These
included 'receiver gain', 'flight altitude' and 'scanner angle'. Several clear sand areas with known
reflectance were used as a reference sample for the creation of a reflectance calibration model which
took both theoretical bias and environmental bias into account. This model was used to further correct
the data gained. An internal tool was then used to take those values and match them with the 'cleaned'
data set by time and position. The tool was used to change the projection of the points and produce a
hydrographic return ASCII file which contains data regarding longitude, latitude, UTM zone, easting,
northing, elevation(IGLD85), elevation (ellipsoid), date (YYYY.MM.DD), time (HH:MM:SS:ssssss) and Bottom
reflectance data relative to both NAD83 ellipsoid and International Great Lakes Datum 1985 (IGLD85).
2009-01-01T00:00:00
The laser data was collected using the HawkEye Mk II airborne system, the Hawkeye MKII system consists
of two lasers scanners; one green (wavelength 532um) which is used for capturing the Bathymetric data
and one red (wavelength 1.064um) for the Topographic data. The system emitted 64 000 pulses per second
(topographic) and 4 000 pulses per second (bathymetric) with up to 4 returns and one reflectance value
per pulse. The laser data collected was flown using a fixed wing platform mounted to the Rockwell
Aero Commander 690 aircraft registration N690CL. The Aircraft was crewed with one pilot and one operator
who was responsible for flight line planning, mission planning and aircraft control during the survey.
The operator used the AHAB Airborne Operator Console software to do this. Sensor orientation was
measured using POS AV 410 with GPS running at 10Hz.
The aerial acquisition starting on the 01st October 2008; the flying height for the survey was 400m
(approx 1300ft) with a swathe of 220m and a 30m flightline overlap, with the flight speed some 150
knots (approx 290 km/h). A total of 145 flight-lines were required and a total of 17 online hours to
cover the 3 survey areas in order to achieve 100% coverage. Area 1 required 88 lines and 11 online
hours, Area 5 required 24 lines and 3 online hours and Area 6 required 33 lines and 3 online hours.
The raw LiDAR data was checked for matching and coverage following each flight; trajectory files were
produced using POSpac v5.2 and the data was then processed using Coastal Survey Studio (CSS) v2.1. A final
check at the end of the acquisition period confirmed that all requirements had been met and all the data
acquired to specification. On completion of all the QC checks the laser data for each flight line was
exported as individual files for import into Terrascan for cleaning and classification.
Topographic and hydrographic data was processed to different criteria, however during processing
all data sets were kept together so it was possible to edit and visualise both datasets in the
same environment simultaneously.
Both the topographic and hydrographic laser data was imported into the TerraSolid OY software running
in the MicroStation v8 environment. The laser data was passed through a number of automated macros
for classification. The topographic laser data was then checked with the imagery by an experienced
editor to remove any hits from the sea areas and to ensure that the ground was correctly classified.
To ensure the quality of the data it was compared with topographic land survey data and overlapping
or crossing flightlines are checked.
The hydrographic laser data was "cleaned", removing any rogue points, floating structures, deep points
or null points with no bottom returns. Overlapping or crossing flightlines were checked and comparison
with topographic points took place to ensure quality. The data was then exported from Terrascan into
a conversion tool; this was used to change the projection of the points and produce ASCII files which
contain data relative to both NAD83 ellipsoid and International Great Lakes Datum 1985 (IGLD85). Four
ASCII tiles were produced for each 5km tile; topographic first return, topographic last return,
hydrographic return and a combined topographic last return and hydrographic return.
The topographic first return and topographic last return files were then reopened in Terrascan.
Using the trajectories produced by POSpac and deducing by time, all points were put into their
respective flightline. Each individual flightline was then exported in 5km tiles in LAS1.0 format.
2009-01-01T00:00:00
The NOAA Office for Coastal Management (OCM) received topo and hydro files in ASCII format. Topography data was
provided within GeoClassified LAS files and original LAS strips. The files contained LiDAR elevation and intensity
measurements. The points were classed as 'never classified.' The data were provided in Geographic coordinates and
ellipsoidal heights and in orthometric heights. OCM performed the following processing to the ellipsoidal height data to
make it available within the Digital Coast:
1. ASCII formatted files were converted to LAS files using LAStools. The ASCII files contained topography/bathymetry data.
Bathyemtric LAS files, along with provided GeoClassified LAS files and original LAS strips were processed to remove high and
and low error (or "air") points.
2. All points classified as 21 were reclassified to 17 to fit the defined a scheme for NOAA Data Access Viewer.
3. All LAS files were then shifted vertically using NOAA's Vdatum software algorithms from IGLD85 to NAVD88.
4. All LAS files were then shifted horizontally and shifted from NAD83, UTM zone 16 to Geographic decimal degrees.
5. Metadata were created, along with a KMZ for the project and ancillary information provided in metadata record.
6. Finally, since original provided were differentiated by data type (i.e. GeoClassified LAS files, LAS strips and ASCII txt files,
all data were compiled into one dataset.
7. Due to vertical and horizontal datum shifting in order to have ASCII, geoclassified and las strips to match NOAA OCM requirements,
the data has been reverted to all unclassified points, although data contains bathymetric and topographic points.
2013-08-08T00:00:00