Short Citation:
Office for Coastal Management, 2020: 2009 - 2011 CA Coastal Conservancy Coastal Lidar Project, https://www.fisheries.noaa.gov/inport/item/48166.

Item Identification

Title: 2009 - 2011 CA Coastal Conservancy Coastal Lidar Project
Short Name: ca2010_coastal_m1124_metadata
Status: Completed
Publication Date: 2012-01
Abstract:

Light Detection and Ranging (LiDAR) data is remotely sensed high-resolution elevation data collected by an airborne collection platform. This LiDAR dataset is a survey of Coastal California. The project area consists of approximately 2616 square miles. The project design of the LiDAR data acquisition was developed to support a nominal post spacing of 1 meter. Fugro EarthData, Inc. acquired 1546 flight lines in 108 lifts between October 2009 and August 2011. This collection was a joint effort by the NOAA Office for Coastal Management (OCM); the California State Coastal Conservancy (SCC) Ocean Protection Council (OPC); Scripps Institution of Oceanography; and the Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX). The data coverage extends landward 500 m from the shoreline, along the entire California coastline. The data collection was performed with two Piper Navajo twin engine aircrafts, utilizing a Leica ALS60 MPiA sensor; collecting multiple return x, y, and z as well as intensity data. The data were classified as Unclassified (1), Ground (2), Low Point (Noise) (7), Water (9), Mudflats (10), and 12 (Overlap). Only the Unclassified (1), Ground (2), Water (9), and Overlap (12) points are available for download from the NOAA OCM Digital Coast.

Original contact information:

Contact Org: NOAA Office for Coastal Management

Phone: 843-740-1202

Email: coastal.info@noaa.gov

Purpose:

These digital data are intended to support the local coastal zone managers in their decision-making processes, including applications such as sea level rise.

Notes:

10189

Supplemental Information:

The Aerial Acquisition and QA reports for this data set may be accessed at:

https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1124/supplemental/ca2009_2011_ca_coastal_conservancy_m1124_acquisitionreport.pdf

https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1124/supplemental/ca2009_2011_ca_coastal_conservancy_m1124_qareport.pdf

A footprint of this data set may be viewed in Google Earth at:

https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1124/supplemental/ca2009_2011_ca_coastal_conservancy_m1124.kmz

Keywords

Theme Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Science Keywords Earth Science > Land Surface > Topography > Terrain Elevation > Topographical Relief Maps
Global Change Master Directory (GCMD) Science Keywords Earth Science > Oceans > Bathymetry/Seafloor Topography > Seafloor Topography
Global Change Master Directory (GCMD) Science Keywords Earth Science > Oceans > Coastal Processes > Coastal Elevation
ISO 19115 Topic Category elevation
None Bathymetry/Topography
None Elevation
None LiDAR
None Model
None Surface
None Terrain

Spatial Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Location Keywords Continent > North America > United States Of America > California
None California
None United States

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
Entity Attribute Overview:

Leica ALS60 MPiA sensor; 1 m nominal post spacing

Entity Attribute Detail Citation:

see process steps within this record

Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.

Data Set Credit: Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office for Coastal Management (OCM); the California State Coastal Conservancy (SCC) Ocean Protection Council (OPC); Scripps Institution of Oceanography; and the Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX).

Support Roles

Data Steward

CC ID: 623229
Date Effective From: 2012-01
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: 623231
Date Effective From: 2012-01
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: 623232
Date Effective From: 2012-01
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: 623230
Date Effective From: 2012-01
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: Publication Date

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 623235
W° Bound: -124.44374
E° Bound: -116.267734
N° Bound: 42.012737
S° Bound: 32.521695

Extent Group 1 / Time Frame 1

CC ID: 623234
Time Frame Type: Range
Start: 2009-09
End: 2011-10

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Access Information

Security Class: Unclassified
Security Classification System:

None

Security Handling Description:

N/A

Data Access Procedure:

This data can be obtained on-line at the following URL:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1124

This data set is dynamically generated based on user-specified parameters.;

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: 743731
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1124
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: 743732
Download URL: https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1124
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

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

URL 2

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

URL 3

CC ID: 743736
URL: https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1124/supplemental/ca2009_2011_ca_coastal_conservancy_m1124.kmz
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz
Description:

This graphic shows the lidar coverage for the CA Coastal Conservancy Lidar Project.

URL 4

CC ID: 790564
URL: https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1124/supplemental/ca2009_2011_ca_coastal_conservancy_m1124_acquisitionreport.pdf
URL Type:
Online Resource
Description:

Link to the acquisition report.

URL 5

CC ID: 790565
URL: https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1124/supplemental/ca2009_2011_ca_coastal_conservancy_m1124_qareport.pdf
URL Type:
Online Resource
Description:

Link to the QC report.

Activity Log

Activity Log 1

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

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 623249
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: 717622
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

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

Partial upload to move data access links to Distribution Info.

Technical Environment

Description:

Microsoft Windows XP Version 5.1 (Build 2600) Service

Pack 2; ESRI ArcCatalog 9.2.6.1500

Data Quality

Accuracy:

During LiDAR data collection the airborne GPS receiver was collecting data at 2 Hz frequency and the Dilution of Precision (PDOP) was monitored. One GPS base station was also running at the operation airport and was recording data at 1 Hz. The airborne GPS data was post-processed in DGPS mode together with the base station data to provide high accuracy aircraft positions. The GPS trajectory then was combined with the IMU data using loosely coupled approach to yield high accuracy aircraft positions and attitude angles. Then the LiDAR data was processed using the aircraft trajectory and raw LiDAR data. After boresighting the LiDAR data, the ground control points were measured against the LiDAR data by technicians using TerraScan and proprietary software and the LiDAR data was adjusted vertically to the ground control. Independent ground control check points were used to ensure vertical accuracy of t he data. The horizontal datum for the control was the North American Datum of 1983 (NAD83, NSRS2007).The vertical datum was the North American Vertical Datum of 1988 (NAVD88). The vertical datum was realized through the use of the published/calculated ellipsoidal heights of the base station to process the aircraft trajectory and then later applying the GEOID09 model to the processed LiDAR data to obtain orthometric heights.

Horizontal Positional Accuracy:

The minimum expected horizontal accuracy was tested to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA). Horizontal accuracy is 50 cm RMSE or better.

Vertical Positional Accuracy:

The minimum expected vertical accuracy was tested to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA). When compared to GPS survey grade points in generally flat, non-vegetated areas, at least 95% of the positions had an error less than or equal to 9.4 cm (equivalent to root mean square error (rmse) of 4.8 cm if errors were normally distributed).

Completeness Measure:

Cloud Cover: 0

Completeness Report:

The following methods are used to ensure LiDAR data accuracy:

1) Use of a ground control network utilizing GPS survey techniques;

2) Use of airborne GPS and IMU in conjunction with the acquisition of LiDAR; and

3) Measurement of quality control ground survey points within the finished product.

The following software is used for the validation: 1) Terrascan and 2) Fugro EarthData Proprietary Software.

Conceptual Consistency:

Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of a GPS base station at the

operation airport. The following checks were performed:

1) The LiDAR data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior

to generating a digital terrain model (DTM) or other products.

2) LiDAR elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal).

Lineage

Sources

Aerial Acquisition of Coastal California LiDAR

CC ID: 623214
Contact Name: Fugro EarthData, Inc.
Publish Date: 2011-08-04
Extent Type: Range
Extent Start Date/Time: 2009-10-15
Extent End Date/Time: 2011-08-02
Source Contribution:

Fugro EarthData, Inc. collected ALS60-derived LiDAR over Coastal California with a 1 meter, nominal post spacing using two Piper Navajo twin engine aircrafts. The collection for the entire project area was accomplished between October 2009 and August 2011; 1,546 flight lines were acquired in 108 lifts. The lines were flown at an average of 6,244 feet above mean terrain using a pulse rate of 121,300 pulses per second. The collection was performed using Leica ALS60 MPiA LiDAR systems, serial numbers 113 and 142. | Type of Source Media: External hard drive

Report of Survey California Coast Ground Control for LiDAR

CC ID: 623215
Contact Name: TerraSurv
Publish Date: 2010-11-17
Extent Type: Range
Extent Start Date/Time: 2009-09-25
Extent End Date/Time: 2010-10-21
Source Contribution:

TerraSurv under contract to Fugro EarthData, Inc. successfully established ground control for Coastal California LiDAR. A total of 307 ground control points were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum of 1983 (NAD83, NSRS2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). | Type of Source Media: electronic mail system

Process Steps

Process Step 1

CC ID: 623216
Description:

All acquired LiDAR data went through a preliminary review to assure that complete coverage was obtained and that there were no gaps between flight lines before the flight crew left the project site. Once back in the office, the data is run through a complete iteration of processing to ensure that it is complete, uncorrupted, and that the entire project area has been covered without gaps between flight lines. There are essentially three steps to this processing: 1) GPS/IMU Processing - Airborne GPS and IMU data was immediately processed using the airport GPS base station data, which was available to the flight crew upon landing the plane. This ensured the integrity of all the mission data. These results were also used to perform the initial LiDAR system calibration test.

2) Raw LiDAR Data Processing - Technicians processed the raw data to LAS format flight lines with full resolution output before performing QC. A starting configuration file was used in this process, which contains the latest calibration parameters for the sensor. The technician also generated flight line trajectories for each of the flight lines during this process.

3) Verification of Coverage and Data Quality - Technicians checked flight line trajectory files to ensure completeness of acquisition for project flight lines, calibration lines, and cross flight lines. The intensity images were generated for the entire lift at the required post spacing for the project. The technician visually checked the intensity images against the project boundary to ensure full coverage. The intensity histogram was analyzed to ensure the quality of the intensity values. The technician also thoroughly reviewed the data for any gaps in project area. The technician generated a few sample TIN surfaces to ensure no anomalies were present in the data. Turbulence was inspected for and if it affected the quality of the data, the flight line was rejected and reflown. The technician also evaluated the achieved post spacing against project specified post spacing.

Process Date/Time: 2011-08-04 00:00:00

Process Step 2

CC ID: 623217
Description:

The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process:

1) Technician processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight.

2) Technician first used commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift- mini project. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the result and made any necessary additional adjustment until it is acceptable for the mini project.

3) Once the boresight angle calculation was done for the mini project, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technician utilized commercial and proprietary software packages to analyze the matching between flight line overlaps for the entire lift and adjusted as necessary until the results met the project specifications.

4) Once the boresight adjustment was completed for each lift individually, the technician ran a routine to check the vertical misalignment of all flight lines in the project and also compared data to ground truth. The entire dataset was then adjusted to ground control points.

5) The technician ran a final vertical accuracy check between the adjusted data and surveyed ground control points after the z correction. The result was analyzed against the project specified accuracy to make sure it meets the project requirements.

6) The flight lines collected under the following programs: National Coastal Mapping Program - JALBTCX and Coastal California LiDAR and Digital Imagery for NOAA OCM in partnership with the SCC were tied together in the boresight process. Control points are shared in both projects. The overlap between flight lines from both projects was compared for matching.

Process Date/Time: 2011-09-19 00:00:00

Process Step 3

CC ID: 623218
Description:

Once boresighting is complete for the project, the project was set up for classification. The LiDAR data was cut to production tiles.

The flight line overlap points, Noise points and Ground points were classified automatically in this process. Fugro EarthData, Inc. has developed a unique method for processing LiDAR data to identify and re-classify elevation points falling on vegetation, building, and other above ground structures into separate data layers. The steps are as follows:

1) Fugro EarthData, Inc. utilized commercial software as well as proprietary software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results.

2) The Automated Process typically re-classifies 90-98% of points falling on vegetation depending on terrain type. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was either run through a different filter or was corrected during the manual filtering process.

3) Interactive editing was completed in 3D visualization software which also provides manual and automatic point classification tools.

Fugro EarthData, Inc. used commercial and proprietary software for this process. Vegetation and artifacts remaining after automatic data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were automatically filtered out during the automatic filtering process were brought back into ground class during manual editing. Auto-filtering routines were utilized as much as possible within fenced areas during interactive editing for efficiency. The technician reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering.

4) All LAS tiles went through peer review after the first round of interactive editing was finished. This helps to catch misclassification that may have been missed by the interactive editing.

5) Upon the completion of peer review and finalization of bare earth filtering, the classified LiDAR point cloud work tiles went through a water classification routine based on the collected water polygons.

Process Date/Time: 2011-10-20 00:00:00

Process Step 4

CC ID: 623219
Description:

6) Upon the completion of finalization of the classified LiDAR point cloud work tiles, the topographic LiDAR classified point cloud data that was produced under the JALBTCX and NOAA OCM programs was merged. The following methodology was used:

a) due to the differences in deliverable specifications between the two projects, the technician re-projected the data covered by JALBTCX to UTM zones 10 and 11 north, NAD83 (NSRS2007), NAVD88, meters. Once complete, the JALBTCX data was reformatted to LAS 1.2 format in accordance with the NOAA OCM project requirements. The time stamps for all points that are stored in GPS Weekly Time were converted to Adjusted Standard GPS time using proprietary software developed by Fugro EarthData, Inc. The data collection date and the current GPS time stamp were used in calculating the Adjusted Standard GPS time. The technician applied the same time stamp conversion to the flight lines collected and processed for JALBTCX project that were used in NOAA OCM project; b) the technician clipped the NOAA OCM dataset to the inland 500 meter boundary line used in the JALBTCX project. There were not any gaps or overlap between the coverage from these two projects; c) once the process finished, the reformatted JALBTCX data and final NOAA OCM LiDAR classified point cloud data were packaged into NAD83 (NSRS2007), UTM zones 10 and 11 north, meters; NAVD88, meters, using GEOID09 together for delivery. The data was also cut to the approved 1500 meter by 1500 meter tile layout and clipped to the approved project boundary. The technician checked the output LAS files for coverage and format; d) the technician then QC'ed the merged dataset for quality assurance and enhanced the Bare Earth classification in the JALBTCX area for consistent data quality; e) these final LiDAR tiles were then used in the hydro flattening process. Water classification in some JALBTCX areas was modified in order to achieve the best hydro flattening result.

7) The classified LiDAR point cloud data were delivered in LAS 1.2 format: 1 unclassified, 2 ground, 7 low points, 9 water, 10 mudflats, and 12 overlap points.

Process Date/Time: 2011-10-20 00:00:00

Process Step 5

CC ID: 623220
Description:

The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained lidar elevation and intensity measurements. The data were in UTM Zones 10 and 11 coordinates and NAVD88 Geoid 09 vertical datum. Only points classified as Unclassified (1), Ground (2), Water (9), and Overlap (12) were made available for download. OCM performed the following processing for data storage and Digital Coast provisioning purposes:

1. The data were converted from UTM coordinates to geographic coordinates.

2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 09.

3. The data were filtered to remove outliers.

4. The LAS data were sorted by latitude and the headers were updated.

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

Catalog Details

Catalog Item ID: 48166
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-14 14:19+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2019-07-02 15:17+0000
Metadata Record Published: 2018-03-13
Owner Org: OCM
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2019-03-14