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

2010-2011 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) Topobathy Lidar: Oregon and Washington

browse graphicThis graphic shows the lidar coverage for the coasts of Oregon and Washington.
These files contain topographic and bathymetric lidar data collected with the Leica ALS60 (topo) and SHOALS-1000T (bathy) systems along the coasts of Oregon and Washington. Data coverage generally extends along the coastline from the waterline inland 500 meters and offshore 1000 meters or to laser extinction. The ALS60 topographic lidar sensor has a pulse repetition rate of 200 kHz at 1064 nm. The bathymetric lidar was collected by the SHOALS-1000T system along the coast. The SHOALS system 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, were referenced to the North American Datum of 1983 (NAD83). Vertical positions were referenced to the NAD83 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID09 model was used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The NOAA Coastal Services Center received the data and converted the topo and hydro files from orthometric heights to ellipsoid heights using GEOID09. These files were converted for data storage and Digital Coast provisioning purposes. The data are classified and available from the NOAA Digital Coast as follows: Unclassified = -1 Ground = 2 Water = 9 Bathymetry = 11 Overlap = 12 Listed below are the specific dates of collection for different parts of this data set: 2010 Oregon (Coos, Curry, and Douglas Counties) Bathymetry: Date of collection: 20100618-20100702 2010-2011 Oregon (Curry County) Bathymetry: Date of collection: 20100702-20110608 2010 Oregon (Coos, Douglas, and Lane Counties) Bathymetry Date of collection: 20100618-20100705 2010 Oregon (Coos and Curry Counties) Topography: Date of collection: 20100713 2010 Oregon (Coos and Douglas Counties) Topography: Date of collection: 20100714 2010 Washington Topography: Date of collection: 20100813 2011 Oregon (Curry County) Topography: Date of collection: 20110610

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: 2012-09-01
    Data Presentation Form: Digital image
    Dataset Progress Status Complete
    Data Update Frequency: As needed
    Purpose: These data were collected as a part of the National Coastal Mapping Program (NCMP) to depict the elevations above and below the water line in the Oregon and Washington 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: 2010-06-18  to  2011-06-10
    Spatial Reference System: urn:ogc:def:crs:EPSG::4269 Ellipsoid in Meters
    Spatial Bounding Box Coordinates:
    N: 48.402893
    S: 41.999017
    E: -123.928959
    W: -124.766602
    Spatial Coverage Map:
    Themes
    • Topography/Bathymetry
    • U.S. Army Corps of Engineers, Mobile District
    • JALBTCX
    • ALS60
    • Topography
    • Unclassified LAS
    • Lidar
    • oceans
    • Land use
    Places
    • United States
    • Oregon
    • Washington
    • Pacific
    Use Constraints No constraint information available
    Fees Fee information not available.
    Lineage Statement Lineage statement not available.
    Processor
    • Fugro Pelagos, Inc.
    • 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
    • Bathymetry: These data were collected using the SHOALS-1000T system. It is owned by Fugro Pelagos Inc. and operated through contract. The system collects bathymetric lidar at 1 kHz and RGB imagery at 1Hz. A CASI-2 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 package Fledermaus, anomalous data are flagged as invalid. FPI Workbench then converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID09 model and exports data as a series of bathymetry (H) ASCII files. The bathymetry files contain all of the returns form the bathymetric sensor which includes returns both above and below the water. Process date for this is unknown. Topography: These data were collected using the ALS60 lidar system. It is owned by Fugro EarthData and operated through contract. The system collects topographic lidar data at maximum pulse rate of 200 kHz in a wavelength of 1064 nm. A CASI-1500 hyperspectral line scanner integrated with the system. Aircraft position, velocity and acceleration information are collected by the onboard GPS/IMU system. Raw data were transferred to the office and processed in IPAS 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 processing, validation and QA/QC in the software packages GeoCue and TerraScan, anomalous data are flagged as invalid and necessary reflights are called. Fugro's proprietary software converts all valid data from ellipsoid to orthometric heights based on the NGS GEOID09 model and exports topographic data as a series of LAS files with a single file per flightline per 5 km box. Process date for this is unknown.
    • Topographic lidar had an additional process step. Outlined below is a representative description for all the topo data sets. 1. The raw lidar data was processed with Leica ALS Post Processor software to LAS format. 2. The processed flightlines were boresighted and block adjustment was performed to ensure flightlines match each other vertically and to the control points using TerraMatch and Fugro EarthData proprietary software. 3. The boresighted data was cut to work tiles in GeoCue and TerraScan classification macros were developed and applied to classify bare-earth points automatically. 4. Then the auto-filtered tiles were manually edited in TerraSolid software packages to correct misclassification errors. Editors used a combination of intensity data, profiles, and color shaded TIN surface to assist the manual editing. 5. All edited tiles were reviewed by the QC team to ensure consistency and accuracy of point classification. 6. Water body polygons were digitized based on the lidar data. The water body polygons were then used to classify the lidar points fall in water to Class 9 - Water using Fugro EarthData proprietary software. 7. Using GeoCue and Fugro EarthData proprietary software the work tiles were then re-cut and re-projected to delivery tiling scheme and projection/datum. 8. These tiles are then re-formatted to two delivery data sets ? Classified and Un-classified Point Cloud that meet the project specification. 9. The Un-classified lidar point cloud data were delivered tiled in LAS 1.2 format; Class 1 - Default.
    • The NOAA Coastal Services Center (CSC) received the topo files in LAS v1.2 format and the hydro files in ascii format. The files contained lidar elevation and intensity measurements. The topo data were received in geographic coordinates (NAD83) and vertically referenced to NAVD88 using the Geoid09 model. The vertical units of data were meters. The hydro files were received in geographic coordinates (NAD83) and vertically referenced to NAVD88. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. Both topo and hydro files were filtered for elevation outliers. 2. The topo las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09. 3. The hydro files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09 and points were classified as 11 (Bathymetry).
    • Times for the hydro files 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.
    • 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: 2014-03-14

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