National Geophysical Data Center (NGDC), NOAA Satellite and Information Service

View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2008 USACE Great Lakes Topo/Bathy Lidar: Wisconsin

browse graphicThis kmz file shows the extent of coverage for the 2008 USACE Wisconsin Lake Michigan Topo/Bathy lidar data set.
These files contain topographic and bathymetric lidar data collected by the Compact Hydrographic Airborne Rapid Total Survey (CHARTS) system along the coast of Wisconsin. 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). 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. 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). The 3-D position data are sub-divided into a series of ASCII file products, with each covering approximately 5 kilometers of shoreline. The file index is provided by the shape file, "wi_michigan.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_WI_Michigan_01_TL.xyz", where 2008 is the year of data collection, NCMP is the project under which data were collected, WI_Michigan is the area of data collection, 01 is the "Box" number and H, TF, or TL is the product type. The ASCII columns are Longitude, Latitude, UTM Zone, Easting, Northing, Elevation (orthometric), Elevation (ellipsoid), Date, Time, and Intensity.

Cite this dataset when used as a source.

Search and Download
    Distribution Formats
    • LAZ
    Distributor DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Point of Contact US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX)
    228-252-1131 228-252-1121
    JALBTCX@usace.army.mil
    Documentation links not available.
    Originator
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Originator
    • US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX)
    Publisher
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Date(s)
    • publication: 2008-01-01
    Data Presentation Form: Digital image
    Dataset Progress Status Complete
    Data Update Frequency: As needed
    Supplemental Information: High water turbidity in the survey area hindered the acquisition of bathymetric data in boxes 61, 62, and 64 and resulted in incomplete coverage.
    Purpose: These data were collected as a part of the NCMP to depict the elevations ABOVE AND/OR BELOW the water for the First Return OR Last Return OR Hydro in the Wisconsin coastal zone.
    Use Limitations
    • These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
    Time Period: 2008-09-01  to  2008-10-31
    Spatial Reference System: urn:ogc:def:crs:EPSG::4269 Ellipsoid in Meters
    Spatial Bounding Box Coordinates:
    N: 44.809625
    S: 42.493938
    E: -87.272186
    W: -87.927026
    Spatial Coverage Map:
    Themes
    • None
    • Lidar
    • elevation
    • U.S. Army Corps of Engineers, Mobile District
    • JALBTCX
    • CHARTS
    • SHOALS
    • Topography
    • Bathymetry
    • oceans
    Places
    • United States
    • Wisconsin
    • Door County
    • Kenosha County
    • Kewaunee County
    • Manitowoc County
    • Milwaukee County
    • Ozaukee County
    • Racine County
    • Sheboygan County
    Use Constraints No constraint information available
    Fees Fee information not available.
    Lineage Statement Lineage statement not available.
    Processor
    • US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX)
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    • DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
    Processing Steps
    • 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 NOAA Coastal Services Center (CSC) received unclassified files in ASCII format (GCS NAD83/NAVD88). The files contained LiDAR intensity and elevation measurements. CSC performed the following processing on the data for data storage and Digital Coast provisioning: 1. The data were converted from ASCII to LAS 1.2 format. 1. The data were converted from orthometric (NAVD88) to ellipsoidal heights (GRS80) using Geoid03. 2. All bathymetric data were reclassified from '0' to '11'. 3. The LAS header fields were sorted by latitude and updated.
    • The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.

    Metadata Last Modified: 2013-06-05

    For questions about the information on this page, please email: mike.sutherland@noaa.gov