gov.noaa.csc.maps:200610_SCRIPPS_m567 Southern California Beach Processes Study (SCBPS)/Coastal Data Information Program (CDIP) part of Scripps Institution of Oceanography (SIO) in cooperation with Bureau of Economic Geology, University of Texas at Austin. Department of Commerce (DOC), National Oceanographic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Coastal Services Center (CSC) 2011 Charleston, SC NOAA's Ocean Service, Coastal Services Center (CSC) http://csc-s-maps-q.csc.noaa.gov/dataviewer/viewer.html?missions=567&aoi=-118.000239599945,-117.246803100015,32.8243789997851,33.6588080001064 http://www.csc.noaa.gov/lidar http://www.csc.noaa.gov There was no metadata record provided along with this data set. Much of the information in this record, has been gleaned from the metadata record for a data set from this same project, for data collected in March of 2006. The minimal amount of known information that is specific to this data set has been included in this record where possible. This lidar point data set was collected during low tide conditions along an approximately 500-700 meter wide strip of the Southern California coastline within an area extending south from Long Beach to the US/Mexico border. Data were collected in Los Angeles, Orange and San Diego counties in October 2006. Data set features include water, beach, cliffs, and top of cliffs. The all points data set contains the complete point cloud of first and last return elevation and laser intensity measurements recorded during the fall 2006 airborne lidar survey conducted semi-annually by the University of Texas at Austin for the Southern California Beach Processes Study. Data represented is all points including terrain, vegetation, and structures. This data also contains returns from the water surface. No processing has been done to remove returns from terrain, vegetation, structures, or water surfaces. The data set was generated by the processing of laser range, scan angle, and aircraft attitude data collected using an Optech Inc. Airborne Laser Terrain Mapper (ALTM) 1225 in combination with geodetic quality Global Positioning System (GPS) airborne and ground-based receivers. The system was installed in a twin engine Partenavia P-68 (tail number N3832K) owned and operated by Aspen Helicopter, Inc. The lidar data set described by this document was collected in October of 2006. The 99d118 instrument settings for these flights were: laser pulse rate: 25 kHz scanner rate: 26 Hz, scan angle: +/- 20 deg beam divergence: narrow altitude: 300-600m AGL ground speed: 95-120kts The data described in this document will be compared with previous and forthcoming data sets to determine rates of shoreline change along the Southern California coastline. The SCBPS program is designed to improve the understanding of beach sand transport by waves and currents, thus improving local and regional coastal management. There was no metadata record provided along with this data set. Much of the information in this record, has been gleaned from the metadata record for a data set from this same project, for data collected in March of 2006. The minimal known information that is specific to this data set has been included in this record where possible. The ALTM 1225 (SN#99d118) lidar instrument has the following specifications: operating altitude = 410-2,000 m AGL; maximum laser pulse rate = 25 kHz; laser scan angle = variable from 0 to +/-20deg from nadir; scanning frequency = variable, 28 Hz at the 20deg scan angle; and beam divergence: narrow = 0.2 milliradian (half angle, 1/e). The ALTM 1225 does not digitize and record the waveform of the laser reflection, but records the range and backscatter intensity of the first and last laser reflection using a constant-fraction discriminator and two Timing Interval Meters (TIM). ALTM elevation points are computed using three sets of data: laser ranges and their associated scan angles, platform position and orientation information, and calibration data and mounting parameters (Wehr and Lohr, 1999). Global Positioning System (GPS) receivers in the aircraft and on the ground provide platform positioning. The GPS receivers record pseudo-range and phase information for post-processing. Platform orientation information comes from an Inertial Measurement Unit (IMU) containing three orthogonal accelerometers and gyroscopes. An aided-Inertial Navigation System (INS) solution for the aircraft's attitude is estimated from the IMU output and the GPS information. Wehr, A. and U. Lohr, 1999, Airborne laser scanning - an introduction and overview, ISPRS Journal of Photogrammetry and Remote Sensing, vol. 54, no.2-3, pp.68-82. A footprint of this data set may be viewed in Google Earth at: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ca/scripps/Scripps_October_2006_Lidar_Long_Beach_to_Mexico_Border.kmz 200610 ground condition Complete As needed -118.000240 -117.246803 33.658808 32.824379 ISO 19115 Topic Category elevation none Bathymetry/Topography shoreline beach lidar laser point file Latitude Longitude intensity none US California Los Angeles County Orange County San Diego County San Diego Pacific Ocean Huntington Beach Point La Jolla none 2006 October None 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. SCBPS/CDIP, Scripps Institution of Oceanography Julie Thomas/Randy Bucciarelli Project Managers mailing

9500 Gilman Drive

La Jolla CA 92093-0214 United States 858-534-3032 858-455-5575 0800-1700 PST Monday-Friday Also available at www.cdip.ucsd.edu SCBPS/CDIP is jointly funded by the US Army Corps of Engineers and the California Department of Boating and Waterways. The initial data are collected by Bureau of Economic Geology, the University of Texas at Austin: R. Gutierrez and T. Hepner. Center for Space Research, The University of Texas at Austin: A. Neuenschwander. Data are further classified and processed by the SCBPS group, located at the Scripps Institution of Oceanography. Not Applicable Data were edited by an automated method to remove obvious outliers above a threshold of 150m. There was no metadata record provided along with this data set, therefore the horizontal accuracy information is unknown. However, to provide some idea of the horizontal accuracy for a comparable data set, the horizontal accuracy information provided below, was gleaned from the metadata record for this same project, for data collected in March of 2006. The lidar data is estimated to have a horizontal error of less than or equal to 0.50 m from comparison between kinematic GPS road survey and a 1m resolution grey-scale image generated from the lidar backscatter intensity data. Kinematic GPS data were superimposed on the lidar backscatter image and examined for any mismatch between the horizontal position of the ground GPS and the corresponding features on the lidar image. Horizontal agreement between the ground kinematic GPS and the lidar was within the resolution of the 1m -resolution backscatter image. There was no metadata record provided along with this data set, therefore the vertical accuracy information is unknown. However, to provide some idea of the vertical accuracy for a comparable data set, the vertical accuracy information provided below, was gleaned from the metadata record for this same project, for data collected in March of 2006. The March 2006 lidar data were compared to the 1998 ATM LIDAR data to determine offsets in the vertical position. The ATM survey points were estimated to have a vertical accuracy of +/- 15 cm. The March 2006 lidar data set was sorted to find data points that fell within 0.5 m of an ATM LIDAR survey point along piers in the survey area. The mean elevation difference between the elevation differences between the March 2006 survey and the ATM survey were used to estimate and remove TIM1 and TIM2 elevation biases from each lidar flight. The standard deviation of these elevation differences provided estimates of the lidar precision. After bias adjustment the mean lidar elevations had a vertical accuracy of 0.10 m. GPS and XYZ-Point Data Processing There was no metadata record provided along with this data set, therefore the process description is unknown. However, to provide some idea of plausible processing, the information provided below, was gleaned from the metadata record for a data set from this same project, for data collected in March of 2006. Transfer raw ALTM 1225 flight data (laser ranges with associated scan angle information and IMU data), airborne GPS data collected at 1 Hz using Ashtech receiver, and ground-based GPS data collected at 1 Hz using Ashtech Z-12 receivers to processing computer. Generate decimated lidar point file from above three data sets using Optech's Realm 2.27 software. This is a 9-column ASCII data set with the following format: time tag; first pulse Easting, Northing, HAE; last pulse Easting, Northing, HAE; first pulse intensity; and last pulse intensity. View decimated lidar point file to check data coverage (i.e. sufficient overlap of flight lines and point spacing). Compute base station coordinates using National Geodetic Survey's PAGES-NT software. Compute aircraft trajectories from each base station GPS dataset using National Geodetic Survey's KINPOS software. Solutions for base stations coordinates and aircraft trajectories are in the International Terrestrial Reference Frame of 2000 (ITRF2000). A final aircraft trajectory was computed from a weighted average of the trajectories from the two base stations. Epoch-by-epoch weighting for the individual trajectories was inversely proportional to the baseline length (distance from base station) and solution RMS. Transformed trajectory solution from ITRF2000 to North American Datum of 1983 (NAD83) using the National Geodetic Survey's Horizontal Time Dependent Positioning software (http://www.ngs.noaa.gov/TOOLS/Htdp/Htdp.html). Input NAD83 trajectories and aircraft inertial measurement unit data into Applanix's POSProc version 2.1.4 to compute an optimal 50Hz inertial navigation solution (INS) and smoothed best estimate of trajectory (SBET). Substitute the INS and SBET into Realm 2.27. Generate a set of initial lidar instrument calibration parameters (pitch, roll, scale, and elevation bias) for each lidar flight, then incrementally improve parameters by iteratively comparing a subset of the lidar output to the GPS kinematic ground control. Once the instrument calibration parameters are sufficiently accurate, create the complete lidar point file (9-column ASCII file) for the entire survey area in UTM Zone 11 with elevations being heights above the GRS-80 reference ellipsoid (HAE). The output format from REALM 2.27 was a 9-column ASCII file containing: the second in the GPS week, easting, northing and HAE of the first lidar return, the easting, northing and HAE of the last lidar return, and the laser backscatter intensity of the first and last returns. Using the GEOID99 model, heights above the GRS80 ellipsoid were converted to orthometric heights with respect to the North American Vertical Datum of 1988 (NAVD88). Parse the 9-column lidar point file into 3.75-minute quarter-quadrangle components. Convert UTM Easting and Northing to geodetic latitude and longitude with respect to the GRS80 ellipsoid. The conversion was computed using the TMGEOD and TCONPC fortran subroutines written by T. Vincenty (NGS). Each record contains 9 columns of data: time tag (seconds in the GPS week), first return Latitude,first return Longitude, first return NAVD88, last return Latitude, last return Longitude, last return NAVD88, first return intensity, and last return intensity. In some cases either the first or last return values may be missing (5 columns). Latitude and longitude are in decimal degrees with nine significant digits to retain the 0.01m resolution of the UTM coordinates. West longitude is negative and north latitude is positive. The UTM quarter-quad files were re-organized into latitude delineated files. UTM quarter-quads files that were delineated by the same upper and lower latitude bounds were concatenated. The lat-long files were named by the month-year of the survey (e.g. mar06) and the lower latitude bounding the quarter-quad. GPS, LIDAR 2006 Bureau of Economic Geology, University of Texas at Austin Coastal Studies Group Member mailing

University Station, Box X

Austin Texas 78713-8924 United States 512-471-1534 512-471-0140 0800-1700 CT Monday-Friday also available at www.beg.utexas.edu Created initial metadata 20030418 Tiffany Hepner Bureau of Economic Geology, The University of Texas at Austin Research Scientist Associate mailing

University Station Box X

Austin Texas 78713 United States 512-475-9572 512-471-0140 tiffany.hepner@beg.utexas.edu The NOAA Coastal Services Center (CSC) received the lidar files in ASCII format. The files contained lidar intensity and elevation measurements. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. Data converted from UTM coordinates to geograhic coordinates. 2. Data converted from NAVD88 heights to ellipsoid heights using GEOID03. 3. Data converted from dual return xyz format to xyz text format with return numbers to las format. 4. The LAS data were sorted by latitude and the headers were updated. 201103 NOAA Coastal Services Center Clearinghouse Manager mailing and physical

2234 South Hobson Avenue

Charleston South Carolina 29405 843-740-1210 clearinghouse@noaa.gov The NOAA National Geophysical Data Center (NGDC) received Lidar data files by ftp. The data received compressed containing LiDAR data from the NOAA Coastal Services Center. The data are currently being served via Digital Coastl at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are provided in LAS format. LAS format is an industry standard for serving LiDAR data. The data are exclusively in geographic coordinates, however, the datums used vary. Most are NAD 83, however some are in ITRF. Vertical systems include both ellipsoid (ITRF and NAD 83) and NAVD 88. For NAVD 88 values, Geiod 03 is primarily used; however, data received in NAVD 88 prior to 2003 was processed using Geoid 99. 20111119 DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce Pamela Grothe Mailing and Physical Address

NOAA/NESDIS/NGDC E/GC1 325 Broadway

Boulder CO 80305-3328 USA (303) 497-6120 (303) 497-6958 (303) 497-6513 pamela.grothe@noaa.gov 7:30-5:00 Mountain Contact Data Center Point 0.0000001 0.0000001 Decimal degrees North American Datum of 1983 (NAD83) Geodetic Reference System 80 (GRS80) 6378137.000000 298.257222 Ellipsoid 0.01 meters Explicit elevation coordinate included with horizontal coordinates NOAA Coastal Services Center Clearinghouse Manager mailing and physical

2234 South Hobson Avenue

Charleston SC 29405-2413 843-740-1210 clearinghouse@noaa.gov Downloadable Data This data was collected in partnership with Scripps Institution of Oceanography, The University of California, San Diego. Any conclusions drawn from analysis of this information are not the responsibility of the Bureau of Economic Geology or the University of Texas at Austin, NOAA, the Coastal Services Center or its partners. This data can be obtained on-line at the following URL: http://www.csc.noaa.gov/lidar DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce Pamela Grothe Mailing and Physical Address

NOAA/NESDIS/NGDC E/GC1 325 Broadway

Boulder CO 80305-3328 USA (303) 497-6120 (303) 497-6958 (303) 497-6513 pamela.grothe@noaa.gov 7:30-5:00 Mountain Contact Data Center Disclaimer 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. 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. 20111119 20111119 20121119 NOAA Coastal Services Center Clearinghouse Manager mailing and physical Charleston SC 29405-2413 843-740-1210 clearinghouse@noaa.gov FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998