NCEI (formerly NGDC)
EMMA logo
Back to Collection NOAA/NESDIS/NGDC/MGG/Lidar
View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2007 USGS Topographic LiDAR: Valdez, Alaska

browse graphicThis kmz file shows the extent of coverage for the 2007 USGS Valdez, Alaska lidar data set.
This project was completed by Aerometric, Inc. under USGS Contract No. 07CRCN0002, Task Order No. 070020009. This delivery contains point cloud data in LAS 1.1 format, classified in the following manner. Class 1: Unclassified, Class 2: Ground, Class 7: Low Point (Noise), Class 9: Water, Class 10: High Point (Noise), Class 12: Overlap, and Class 17: Port The following are the collection parameters and equipment used to create these data sets. Aircraft: Cessna 320 (N3443Q) and Piper Navajo (N6GR) Lidar System: Optech ALTM Gemini (03SEN145) Approximate Collection Altitude (Above Mean Terrain): 1800 meters Ground Speed: 145 kts Pulse Rate Frequency: 70 kHz Mirror Scan Frequency: 62.6 Hz Scan Angle (+/-): 5.3 degrees Beam Divergence: Narrow (0.25 mrad) Accuracy statements are based on areas of moderate terrain, with points classified as ground. Diminished accuracies are to be expected in areas of extreme terrain and dense vegetation. The accuracy of each point is expected to meet the vertical accuracy standard. Derived products may be less accurate in areas of extreme terrain and dense vegetation due to a lesser number of points defining the ground in these areas. Classified data sets such as this one may have varying posting due to some pulses not reaching the ground.
Cite this dataset when used as a source.
Other Access Online access information not available.
Distribution Formats
  • LAZ
Distributor DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Dataset Point of Contact Jacques Cloutier
Senior Geodetic Surveyor
Aero-Metric, Inc.
(907) 272-4495
Documentation links not available.
  • publication: 2013-02-01
Data Presentation Form: Digital image
Dataset Progress Status Complete
Data Update Frequency: As needed
Purpose: The purpose of this data set is to provide processed lidar data over Valdez at a nominal point spacing of 0.3 meter.
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.
  • While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • DOI/USGS > United States Geological Survey, U.S. Department of the Interior
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Time Period: Unknown to Unknown
Spatial Reference System: urn:ogc:def:crs:EPSG::4269
Spatial Bounding Box Coordinates:
N: 61.158460
S: 61.036345
E: -145.913257
W: -146.641106
Spatial Coverage Map:
Theme keywords None
  • Topography/Bathymetry
  • Elevation
  • Topography
  • Remote Sensing
  • lidar
  • Laser
  • Terrain
Place keywords None
  • USA
  • Alaska
  • Valdez
Use Constraints No constraint information available
Fees Fee information not available.
Lineage information for: dataset
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • DOC/NOAA/NESDIS/NCEI > National Centers of Environmental Information, NESDIS, NOAA, U.S. Department of Commerce
Processing Steps
  • 2008-10-18T00:00:00 - System Calibration: Aero-Metric collected data over a previously surveyed area in Palmer, Alaska. Data was collected at the same settings as this project, using two intersecting perpendicular lines. Two GPS ground stations were operating on site in order to minimize GPS error. The data was classified in each line separately for ground and other common features between lines, such as building roofs. This data was processed in TerraMatch 8.001 (TerraSolid, Ltd.), to compute corrections for roll, pitch, heading, and mirror scale. These corrections were applied to the initial processing settings (.res file). The data was reprocessed to verify the corrections were applied properly. The corrected data was then compared to ground surveyed measurements in order to check for any consistent vertical bias. The final step in calibration verified there was minimal vertical noise due to changes in intensity. This was done by comparing elevations of points on the airport runway, one point on a runway stripe and another adjacent point on the pavement.
  • 2008-11-02T00:00:00 - Create a smoothed-best estimated trajectory (SBET) of the sensor at a rate of 200 Hz, by integrating the airborne GPS and IMU data. The basis of the GPS coordinates were computed using NGS OPUS, and were referenced to NAD83 (CORS96) with GEOID06 derived orthometric heights. The maximum baseline distance for this project was 30 km, the average base line length was 12 km. The mean GPS positional accuracy for this project was +/- 0.08 meters.
  • 2008-11-02T00:00:00 - Integrate SBET and raw laser data to produce point cloud data in LAS 1.1 format for each flight line.
  • 2009-01-15T00:00:00 - Compute the roll, pitch, heading, and mirror scale correction factors for each flight line, then apply corrections to the corresponding flight line.
  • 2009-01-16T00:00:00 - Automated classification of the bare-earth data from the lidar point cloud using a series of algorithms customized for the types of terrain encountered in the project.
  • 2009-03-20T00:00:00 - Manual classification of any data which appears to be bare-earth but was not properly classified using the automated methods.
  • 2009-05-25T00:00:00 - The shorelines of the lakes and port areas were determined using manual techniques, starting with digitized shorelines from the orthophotography of the project area. The lidar points then underwent an intensive manual edit to determine with greater accuracy the points which represented the water surface. For the final data products the mean elevation of the water on each lake was used to determine its fixed elevation. The port areas fixed elevation was determined using the highest water point in the port data set. This value was found to be 4.72 meters. All points below 4.72 meters in the port area were fixed to this elevation, as per the contract.
  • 2009-05-26T00:00:00 - Create point clouds in LAS 1.1 format for all returns.
  • 2009-05-27T00:00:00 - Data verified using survey control points, located throughout the area.
  • 2009-06-18T00:00:00 - The metadata was updated for Bounding coordinates, Spatial Reference info using FGDC template
  • 2013-02-01T00:00:00 - The NOAA Coastal Services Center (CSC) received topographic files in LAS 1.1 format. The files contained lidar elevation and intensity measurements. The data were received in projected coordinates of NAD83 UTM6N, meters and were vertically referenced to NAVD88 orthometric elevations using GEOID06(Alaska). The vertical units of the data were meters. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. LAS Classifications 11(first return only), 13(first of many returns), 14(second of many returns), 15(third of many returns), 16(last of many returns) were all placed into Class 1 (Unclassified) 2. The topographic las files were converted from Projected Coordinates (NAD83 UTM6N, meters) to Geographic Coordinates (NAD83, decimal degrees). 3. The topographic las files were vertically converted from orthometric elevations (NAVD88) to ellipsoidal elevations (NAD83) using GEOID06. 4. The data were converted to LAZ format.
  • 2013-04-25T00:00:00 - 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 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 ( 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.
Last Modified: 2013-04-25
For questions about the information on this page, please email: