These files contain classified bathymetric and topographic lidar data classified as unclassified (1), ground (2), low/noise (7), water (9), NOAA OCM bathymetry (11), and overlap (12) in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards. The topographic data were collected with a Leica ALS60 system along the coast of California on the following dates: October 15,16,17,21,22,29,30,31 and November 1,2,3,6,11,14,16,17,18,19,20,29,30. Data coverage generally extends along the coastline from the waterline inland 500 meters (topography). The ALS60 topographic lidar sensor has a pulse repetition rate of 200 kHz at 1064nm. The bathymetric data were collected by the SHOALS-1000T system along the coast of California on the following dates: October 3,10,12,13,25,26,28, November 1,2,6,10,12,15,16,17,18,24,25,26 and December 3,4,5,6. Data coverage generally extends along the coastline from the waterline offshore 1,000 meters or to laser extinction. Exclusively in areas where Fugro Pelagos acquired or planned to acquire multibeam sonar data by December 31, 2009, data coverage extends from the shoreline either to the 10-m contour, the 20-m contour or the landward extend of the multibeam data plus an additional 100 m offshore. 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 processed 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 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). Upon receipt of the data, the NOAA Office for Coastal Management (OCM) converted the topographic las format data and the bathymetric ASCII format data to laz format and orthometric heights to ellipsoid heights using GEOID09. The topographic 3-D position data were sub-divided into a series of LAS files, each covering approximately 5 kilometers of shoreline. The LAS file naming convention is based on the year, project, area name, "Box," and line name. An example file name is "2009_NCMP_CA_001_(system_generated_file_name_for_flightline).las", where (2009) is the year of data collection, (NCMP) is the project under which data were collected, (CA) is the area of data collection, (001) is the "Box" number and (system_generated_file_name_for_flightline) is the line file name. The format of the file is LAS version 1.0. The bathymetric 3-D position data were sub-divided into a series of ASCII file products, with each covering approximately 5 kilometers of shoreline. The data file naming convention was based on the year, project, area name, "Box" number and product type (H - bathymetry). An example file name is "2009_NCMP_CA_001_H.xyz", where <2009> is the project year, is the project under which data were collected, is the area of data collection, <001> is the "Box" number and is the product type. The ASCII columns were Longitude, Latitude, UTM Zone, Easting, Northing, Elevation (orthometric), Elevation (ellipsoid), Date, and Time. Upon arrival to NOAA's Office for Coastal Management the data were converted to geographic coordinates and to GRS80 (ellipsoid) in meters. In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data.