gov.noaa.nmfs.inport:50058
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)
NAD83(HARN)
2008-11-12
publication
European Petroleum Survey Group
https://apps.epsg.org/api/v1/CoordRefSystem/4152/export/?format=gml
urn:ogc:def:crs:EPSG:4152
6.18.3
North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters
North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters
https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml
North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters
Link to Geographic Markup Language (GML) description of reference system.
information
resourceProvider
European Petroleum Survey Group
https://www.epsg.org/
European Petroleum Survey Group Geodetic Parameter Registry
Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations.
search
publisher
vertical
OGP
2006-11-28
false
urn:ogc:def:cs:EPSG::6499
Vertical CS. Axis: height (H). Orientation: up. UoM: meter.
Used in vertical coordinate reference systems.
urn:ogc:def:axis:EPSG::114
H
up
urn:ogc:def:crs:EPSG::5703
2006 USACE Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI)
usace2006_gl_m40_metadata
2007-03-22
publication
NOAA/NMFS/EDM
50058
https://www.fisheries.noaa.gov/inport/item/50058
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
WWW:LINK-1.0-http--link
Citation URL
Online Resource
download
https://coast.noaa.gov/dataviewer
WWW:LINK-1.0-http--link
Citation URL
Online Resource
download
The U.S. Army Corps of Engineers collects and maintains LiDAR data including orthophotos in coastal areas of the United States and its territories. The Corps acquires this data in the course of performing its mission of Flood Control, Navigation, Environmental Engineering, and support for the Army and others. These data were collected along the Indiana, Michigan, Ohio and Pennsylvania coasts of the Great Lakes using the CHARTS (Compact Hydrographic Airborne Rapid Total Survey) system and industry based coastal mapping and charting systems.
Original contact information:
Contact Org: NOAA Office for Coastal Management
Phone: 843-740-1202
Email: coastal.info@noaa.gov
This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data.
The purpose of this survey was to collect topographic and hydrographic elevations to obtain the existing conditions
of the beach and near shore in support of the Joint Airborne LiDAR Bathymetric Technical Center of Expertise National
Coastal Mapping Program. However, depths were not attained in many areas due to water clarity.
Acknowledgment of JALBTCX would be appreciated in any publications or derived products.
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 Mar 01, 2024 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
June 2006
September 2006
temporal
Lidar - partner (no harvest)
project
InPort
otherRestrictions
Cite As: OCM Partners, [Date of Access]: 2006 USACE Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50058.
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
it's limitations.
otherRestrictions
Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of the US Army Corp of Engineers,
the Joint Airborne Lidar Bathymetry Center of Expertise(JALBTCX), NOAA, the Office for Coastal Management or it's partners.
unclassified
NOAA Data Management Plan (DMP)
NOAA/NMFS/EDM
50058
https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50058.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
-87.2
-79.98
41.37
44.08
| Currentness: Ground Condition
2006-06-14
2006-09-26
false
eng
false
none
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=40
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/40/index.html
WWW:LINK-1.0-http--link
Bulk Download
Simple download of data files.
download
dataset
Accuracy
N/A
Horizontal Positional Accuracy
The data has been collected and compiled to meet the +/- 3 m (2 sigma) accuracy specification.; Quantitative Value: 3.0 meters, Test that produced the value: Compiled to meet
Vertical Positional Accuracy
The data has been collected and compiled to meet the +/- 30 cm (2 sigma) accuracy specification.; Quantitative Value: 0.3 meters, Test that produced the value: Compiled to meet
Completeness Report
See Process Step
Conceptual Consistency
N/A
Acquisition - Data were acquired using a SHOALS-1000T. Sensor orientation was measured using a POS AV 410, while
images were acquired at 1Hz using a Duncantech DT4000 digital camera. Prior to survey PDOP was checked and missions
planned to avoid PDOP greater than 3.5. During survey the plane was always within 30km of a GPS ground control point,
to provide a good quality position solution. Final positions were determined using a post-processed inertially aided
Kinematic GPS (KGPS) solution. GPS ground control data were acquired at 1Hz.
Data received by the airborne system were continually monitored for data quality during acquisition operations. Display
windows showed coverage and information about the system status. In addition, center waveforms at 5Hz were shown. All
of this information allowed the airborne operator to assess the quality of data being collected.
The data were collected and processed in geographic coordinates and ellipsoid heights. The positions are
relative to NAD83 in decimal degrees of longitude and latitude. The heights were converted from ellipsoid
to geoid heights (NAVD88) using the Geoid03 model with the results in meters.
Data were processed in the field to verify coverage and data quality.
Processing - Data were processed using the SHOALS Ground Control System (GCS). The GCS includes links to Applanix POSPac
software for GPS and inertial processing, and IVS Fledermaus software for data visualization, 3D editing and tie-line
analysis. Data were processed in NAD83 horizontal and vertical datum. Data were later converted to the NAVD88 vertical
datum using the GEOID03 model. The date and time of each point are also MM:SS.SSSSSS.
Fugro in-house utilities were used to extract XYZ data from the native LiDAR files and split the data in to pre-defined
boxes, each covering approximately 5km of shoreline. ASCII files include: Longitude, Latitude, Elevation, Date, Time,
and Intensity.
Files converted to LDART LAS format (geographic coords, ellipsoid heights,using GEOID03),
sorted by latitude and filtered to eliminate outliers.
2007-06-15T00:00:00
Times had originally been stored as POSIX seconds when converted to LAS. This was switched to adjusted GPS time (GPS seconds - 1e9) to conform to the LAS 1.2 standard.
2014-01-09T00:00:00
NOAA OCM received the data in LAS v1.2 format. For data storage and Digital Coast provisioning purposes, the data were processed as follows:
1. Heights were converted Ellipsoid heights, horizontal coordinates were converted to geographic coordinates.
2. lastools's Lasground processed the all unclassifed points to have ground classified points as well.
3. LAS files were converted to LAZ and sorted.
2013-07-01T00:00:00
Source Contribution: Fugro Pelagos, Inc. | Type of Source Media: Electronic Mail System
2006 USACE National Coastal Mapping Program, Great Lakes Topo/Bathy LiDAR
2006-09-25
The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey.
Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org)
Processing notes:
2024-03-01T06:47:02
NOAA Office for Coastal Management
coastal.info@noaa.gov
processor