gov.noaa.nmfs.inport:50072
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 US Army Corps of Engineers (USACE) National Coastal Mapping Program Topobathy Lidar: Lake Michigan
usace2008_mi_m518_metadata
2009
publication
NOAA/NMFS/EDM
50072
https://www.fisheries.noaa.gov/inport/item/50072
WWW:LINK-1.0-http--link
Full Metadata Record
View the complete metadata record on InPort for more information about this dataset.
information
These files contain topographic and bathymetric lidar data collected by the Compact Hydrographic Airborne Rapid Total
Survey (CHARTS) system along the west coast of Michigan from Berrien County to Leelanau County, along the Lake Michigan
coastline from 28 July - 16 Sept 2008. Lidar intensity data was also collected.
CHARTS integrates topographic and bathymetric lidar sensors, a digital camera and a hyperspectral scanner on a
single remote sensing platform for use in coastal mapping and charting activities. Data coverage generally extends along the
coastline from the waterline inland 500 meters (topography) and offshore 1,000 meters or to laser extinction (bathymetry).
The topographic lidar sensor has a pulse repetition rate of 9 kHz at 1064 nm (near-infrared wavelength). The bathymetric lidar
sensor has a pulse repetition rate of 1 kHz at 532 nm (green wavelength). Native lidar data is 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 imported into GIS software for visualization and further analysis. Horizontal
positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83).
Vertical positions are referenced to the NAD83 ellipsoid and provided in meters.
Original contact information:
Contact Org: JALBTCX
Title: Data Production Manager
Phone: 228-252-1111
Email: shoals-info@sam.usace.army.mil
These data were collected as a part of the National Coastal Mapping Program to depict the elevations above the water for the First Return,
Last Return, or Hydro in the Michigan coastal zone.
Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any
publications or derived products.
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
ASCII XYZ
CHARTS
Intensity
JALBTCX
SHOALS
U.S. Army Corps of Engineers
theme
2008
August
July
September
temporal
Lidar - partner (no harvest)
project
InPort
otherRestrictions
Cite As: OCM Partners, [Date of Access]: 2008 US Army Corps of Engineers (USACE) National Coastal Mapping Program Topobathy Lidar: Lake Michigan [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50072.
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
50072
https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50072.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
-86.838156
-85.915215
41.748285
44.989667
| Currentness: Ground Condition
2008-07-28
2008-09-16
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=518
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/518/index.html
WWW:LINK-1.0-http--link
Bulk Download
Simple download of data files.
download
dataset
Accuracy
These data are not attributed. | Quantitative Value: N/A | Quantitative Test Explanation: These data are not attributed.
Horizontal Positional Accuracy
The data positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than +/- 0.75m.; Quantitative Value: 0.75 meters, Test that produced the value: 1 Sigma
Vertical Positional Accuracy
The data positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than +/- 0.20m.; Quantitative Value: 0.20 meters, Test that produced the value: 1 Sigma
Completeness Measure
Cloud Cover: Unknown
Completeness Report
Not provided
Conceptual Consistency
The data provided in this file were tested against ground truth data. At these locations the lidar data matched within 0.20 meters,
and different flight line data agreed within 0.20 meters.
These data were collected using the CHARTS system. It is owned by the Naval Oceanographic Office and operated through contract.
The system collects topographic lidar data at 9kHz, bathymetric lidar data at 1kHz and RGB imagery at 1Hz. 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 410 equipment. All raw data streams are transferred to the office for downloading and processing in
SHOALS GCS 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. PFM_ABE's chartsLAS module then converts all valid data from ellipsoid to orthometric heights based on
the NGS' GEOID03 model and exports data as a series of first return topography (TF), last return topography (TL) and bathymetry (H)
ASCII files. The bathymetry files contain all of the returns from the bathymetric sensor which include returns both above and below
the water.
The National Geodetic Survey's (NGS) GEOID03 model was 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 were sub-divided into a series of ASCII file
products, with each covering approximately 5 kilometers of shoreline. The file index was provided by the shape file,
"mi_michigan_boxes.shp", and the numbers used to identify files are in the "Box" field of the shape file. The data file naming
convention is based on the year, project, area name, "Box" number and product type (topographic or bathymetric). An example file
name is "2008_NCMP_MI_Michigan_07_ASCII", where 2008 is the year of data collection, NCMP is the project under which data were
collected, MI_Michigan is the area of data collection, 07 is the "Box" number and ASCII is the product type. The ASCII columns
are Longitude, Latitude, UTM Zone, Easting, Northing, Elevation (orthometric), Elevation (ellipsoid), Date, Time, and Intensity.
2009-01-01T00:00:00
The NOAA Office for Coastal Management (OCM) received topo and hydro files in ASCII format. 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. LASEdit was used to convert the ASCII formatted files to las format.
2. The hydro points classification was changed from 'never classified' to class 11, 'bathymetry'. The topo points classification remains
as class 0, 'never classified'.
3. The LAS data were sorted by latitude and the headers were updated.
2009-11-01T00:00:00