2010-2011 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) Topobathy Lidar: Oregon and WashingtonView 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 graphicThese 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

Get the Data
AccessFormat(s)Distributor(s) / Contact InfoInstructions / Constraints
LAZ
Format version: (version is unknown)
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
843-740-1200Mike Sutherland
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
303-497-6120
7:30am-5:00pm Mountain
Ordering Instructions
The National Geophysical Data Center serves as the archive for this LIDAR data. NGDC should only be contacted for this data if it cannot be obtained from NOAA Coastal Services Center.

The National Geophysical Data Center serves as the archive for this LIDAR dataset. NGDC should only be contacted for the data if it cannot be obtained from NOAA Coastal Services Center.

Use Limitation
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.

Legal Constraints