Slide Menu
System Maintenance Notice, Monday, December 5, 2022 @ 1pm-5pm Eastern. The Operations Team will be performing system maintenance. During this scheduled downtime, InPort will not be available.
View All
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2022: October 2006 Scripps Institute of Oceanography (SIO) Lidar of Southern California Coastline: Long Beach to US/Mexico Border, https://www.fisheries.noaa.gov/inport/item/50011.

Item Identification

Title: October 2006 Scripps Institute of Oceanography (SIO) Lidar of Southern California Coastline: Long Beach to US/Mexico Border
Short Name: scripps_200610_m567_metadata
Status: Completed
Publication Date: 2011
Abstract:

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

Original contact information:

Contact Name: Julie Thomas/Randy Bucciarelli

Contact Org: SCBPS/CDIP, Scripps Institution of Oceanography

Title: Project Managers

Phone: 858-534-3032

Purpose:

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.

Notes:

10655

Supplemental Information:

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:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/567/supplemental/Scripps_October_2006_Lidar_Long_Beach_to_Mexico_Border.kmz

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
None beach
None intensity
None Latitude
None Longitude
None point file
None shoreline

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None 2006
None October

Physical Location

Organization: Office for Coastal Management
City: Charleston
State/Province: SC

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: As Needed
Distribution Liability:

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 Office for Coastal Management or its partners.

Data Set Credit: 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.

Support Roles

Data Steward

CC ID: 686755
Date Effective From: 2011
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Distributor

CC ID: 686757
Date Effective From: 2011
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Metadata Contact

CC ID: 686758
Date Effective From: 2011
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Point of Contact

CC ID: 686756
Date Effective From: 2011
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Extents

Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1139114
W° Bound: -118.00024
E° Bound: -117.246803
N° Bound: 33.658808
S° Bound: 32.824379

Extent Group 1 / Time Frame 1

CC ID: 1139113
Time Frame Type: Discrete
Start: 2006-10

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer

;

Data Access Constraints:

None

Data Use Constraints:

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.

Distribution Information

Distribution 1

CC ID: 742592
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=567
Distributor:
File Name: Customized Download
Description:

Create custom data files by choosing data area, product type, map projection, file format, datum, etc.

Distribution 2

CC ID: 742593
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/567/index.html
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

CC ID: 742595
URL: https://coast.noaa.gov/dataviewer
URL Type:
Online Resource

URL 2

CC ID: 742596
URL: https://coast.noaa.gov
URL Type:
Online Resource

Activity Log

Activity Log 1

CC ID: 686784
Activity Date/Time: 2017-03-20
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 686783
Activity Date/Time: 2017-11-14
Description:

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 718612
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 742594
Activity Date/Time: 2018-03-13
Description:

Partial upload to move data access links to Distribution Info.

Data Quality

Horizontal Positional Accuracy:

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.

Vertical Positional Accuracy:

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.

Completeness Report:

Data were edited by an automated method to remove obvious outliers above a threshold of 150m.

Conceptual Consistency:

Not Applicable

Lineage

Process Steps

Process Step 1

CC ID: 1139108
Description:

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.

Process Date/Time: 2006-01-01 00:00:00

Process Step 2

CC ID: 1139109
Description:

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.

Process Date/Time: 2006-01-01 00:00:00

Process Step 3

CC ID: 1139110
Description:

Created initial metadata

Process Date/Time: 2003-04-18 00:00:00

Process Step 4

CC ID: 1139111
Description:

The NOAA Office for Coastal Management (OCM) received the lidar files in ASCII format. The files contained lidar intensity

and elevation measurements. OCM 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.

Process Date/Time: 2011-03-01 00:00:00

Catalog Details

Catalog Item ID: 50011
GUID: gov.noaa.nmfs.inport:50011
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:23+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2022-03-16
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16