2007 USGS Lidar: Canyon Fire (CA)
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:49639 | Updated: August 9, 2022 | Published / External
Summary
Short Citation
OCM Partners, 2025: 2007 USGS Lidar: Canyon Fire (CA), https://www.fisheries.noaa.gov/inport/item/49639.
Full Citation Examples
This Southern California Light Detection and Ranging (LiDAR) data is to provide high accuracy LIDAR data. These datasets will be the initial acquisition to support FEMA and other Federal Response to the Southern California Wild Fires.
LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. By positioning laser range finding with the use of 1 second GPS with 100hz inertial measurement unit corrections; Terrapoint's LIDAR instruments are able to make highly detailed geospatial elevation products of the ground, man-made structures and vegetation. The LiDAR flightlines for this project were planned for a 55% acquisition overlap. The nominal resolution of this project without overlap is 0.57m. Four returns were recorded for each pulse in addition to an intensity value. GPS Week Time, Intensity, Flightline and number attributes were recorded for each LiDAR point. Positional values were recorded to the centimeter level, while GPS is recorded to a 10th of a millisecond. Scan angle was recorded to the nearest angle, Intensity is recorded as an 8 Bit integer value and echo is recorded as an integer valuefrom 1 to 4.
Data is provided as random points, in LAS v1.2 format, classified according to the following ASPRS Class Codes:
Class 1 Unclassified
Class 2 Ground
Class 7 Noise
Class 9 Water
Please note all LiDAR points outside of the task order area was classified as Unclassified (Class 1).
Distribution Information
-
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
-
Simple download of data files.
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. These data
depict the heights at the time of the survey and are only accurate for that time.
Controlled Theme Keywords
elevation
Child Items
No Child Items for this record.
Contact Information
Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Extents
-118.777719° W,
-118.764501° E,
34.040941° N,
34.029936° S
2007-12-02
Item Identification
Title: | 2007 USGS Lidar: Canyon Fire (CA) |
---|---|
Short Name: | ca2007_usgs_canyon_fire_m5028_metadata |
Status: | Completed |
Publication Date: | 2013-01 |
Abstract: |
This Southern California Light Detection and Ranging (LiDAR) data is to provide high accuracy LIDAR data. These datasets will be the initial acquisition to support FEMA and other Federal Response to the Southern California Wild Fires. LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. By positioning laser range finding with the use of 1 second GPS with 100hz inertial measurement unit corrections; Terrapoint's LIDAR instruments are able to make highly detailed geospatial elevation products of the ground, man-made structures and vegetation. The LiDAR flightlines for this project were planned for a 55% acquisition overlap. The nominal resolution of this project without overlap is 0.57m. Four returns were recorded for each pulse in addition to an intensity value. GPS Week Time, Intensity, Flightline and number attributes were recorded for each LiDAR point. Positional values were recorded to the centimeter level, while GPS is recorded to a 10th of a millisecond. Scan angle was recorded to the nearest angle, Intensity is recorded as an 8 Bit integer value and echo is recorded as an integer valuefrom 1 to 4. Data is provided as random points, in LAS v1.2 format, classified according to the following ASPRS Class Codes: Class 1 Unclassified Class 2 Ground Class 7 Noise Class 9 Water Please note all LiDAR points outside of the task order area was classified as Unclassified (Class 1). |
Purpose: |
This data was collected to support emergency relief for the wildfires in the Canyon (47.7 square kilometers), in Southern California, December, 2007 |
Notes: |
10283 |
Supplemental Information: |
A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5028/supplemental/ca2007_usgs_canyon_fire_m5028.kmz |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category |
elevation
|
Spatial Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
US DOC, 1987, Codes for Identification of the States, Wash, DC and outlying areas of US and associated areas, Fed Info Processing Standard (FIPS) 5-2: Wash, DC, NIST. | California |
US DOC, 1995, Countries, dependencies, areas of special sovereignty, and their principal admin divisions, Fed Info Processing Standard (FIPS) 10-4: Wash DC, NIST. | US |
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 |
Data Presentation Form: | las |
Entity Attribute Overview: |
LiDAR points in LAS 1.2 format |
Entity Attribute Detail Citation: |
none |
Distribution Liability: |
Any conclusions drawn from the analysis of this information are not the responsibility of Northrop Grumman, USGS, the Office for Coastal Management or its partners. |
Data Set Credit: | U.S. Geological Survey |
Support Roles
Data Steward
Date Effective From: | 2013-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
Date Effective From: | 2013-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
Date Effective From: | 2013-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
Date Effective From: | 2013-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: | Ground Condition |
---|
Extent Group 1
Extent Group 1 / Geographic Area 1
W° Bound: | -118.777719 | |
---|---|---|
E° Bound: | -118.764501 | |
N° Bound: | 34.040941 | |
S° Bound: | 34.029936 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Discrete |
---|---|
Start: | 2007-12-02 |
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/#/lidar/search/where:ID=5028; |
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. These data depict the heights at the time of the survey and are only accurate for that time. |
Distribution Information
Distribution 1
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5028 |
---|---|
Distributor: | |
File Name: | Customized Download |
Description: |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
Distribution 2
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5028/index.html |
---|---|
Distributor: | |
File Name: | Bulk Download |
Description: |
Simple download of data files. |
URLs
URL 1
URL: | https://coast.noaa.gov/dataviewer |
---|---|
URL Type: |
Online Resource
|
URL 2
URL: | https://coast.noaa.gov |
---|---|
URL Type: |
Online Resource
|
URL 3
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5028/supplemental/ca2007_usgs_canyon_fire_m5028.kmz |
---|---|
Name: | Browse Graphic |
URL Type: |
Browse Graphic
|
File Resource Format: | kmz |
Description: |
This graphic shows the lidar coverage of the canyon fire area in California from 2007. |
Activity Log
Activity Log 1
Activity Date/Time: | 2017-03-20 |
---|---|
Description: |
Date that the source FGDC record was last modified. |
Activity Log 2
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
Activity Date/Time: | 2018-02-08 |
---|---|
Description: |
Partial upload of Positional Accuracy fields only. |
Activity Log 4
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 3; ESRI ArcCatalog 9.3.1.4000 |
---|
Data Quality
Accuracy: |
According to Terrapoint standards; the following aspects of the LiDAR data was verified during the course of the project processing: -Data accuracy and errors -Anomaly checks through full-feature hillshades -Post automated classification Bare-earth verification -Final quality control of deliverable products ensuring integrity, graphical quality |
---|---|
Horizontal Positional Accuracy: |
Compiled to meet 1 meter horizontal accuracy at the 95 percent confidence level |
Vertical Positional Accuracy: |
Independent accuracy testing was performed by Dewberry using 8 high accuracy quality control checkpoints distributed throughout the project on near level open bare terrain, gravel roads, concrete pads, roads, parking lots. Dewberry used testing procedures consistent with those specified in the National Standard for Spatial Data Accuracy (NSSDA) resulting in a tested accuracy of 0.072 m at 95 percent confidence level. Terrapoint conducted a primary internal check that gave a vertical accuracy of 0.149 meters at 95 percent confidence level. ; Quantitative Value: 0.072 meters, Test that produced the value: This LiDAR dataset was tested to have an RMSEz of 0.072 m (calculated from a Fundamental Vertical Accuracy at 95 percent confidence). Consolidated Vertical Accuracy of 0.705 m (RMSEz (0.036 m) x 1.9600). |
Completeness Report: |
According to Terrapoint standards, data completeness and integrity was verified. Conformance to Terrapoint standards are met for all delivered products. |
Conceptual Consistency: |
All LAS formatted LIDAR data are validated to ensure that data on delivery media is in correct physical format and is readable and correctly georeferenced and projected. Note that LiDAR intensity is not calibrated or normalized. |
Lineage
Process Steps
Process Step 1
Description: |
- Airborne GPS Kinematic Airborne GPS kinematic data was processed on-site using GrafNav kinematic On-The-Fly (OTF) software. Flights were flown with a minimum of 6 satellites in view (13o above the horizon) and with a PDOP of better than 3.5. Distances from base station to aircraft (differential baselines) were kept to a maximum of 30 km while the mean is 6.8 km, to ensure a strong OTF (On-The-Fly) solution. For all flights, the GPS data can be classified as excellent, with GPS residuals of 5cm average but no larger than10 cm being recorded. - Generation and Calibration of laser points (raw data) The initial step of calibration is to verify availability and status of all needed GPS and Laser data against field notes and compile any data if not complete. Subsequently the mission points are output using Optech's Dashmap, initially with default values from Optech or the last mission calibrated for system. The initial point generation for each mission calibration is verified within Microstation/Terrascan for calibration errors. If a calibration error greater than specification is observed within the mission, the roll pitch and scanner scale corrections that need to be applied are calculated. The missions with the new calibration values are regenerated and validated internally once again to ensure quality. All missions are validated against the adjoining missions for relative vertical biases and collected GPS kinematic ground truthing points for absolute vertical accuracy purposes. On a project level, a coverage check is carried out to ensure no slivers are present. |
---|---|
Process Date/Time: | 2007-12-01 00:00:00 |
Process Step 2
Description: |
- Data Classification and Editing The data was processed using the software TerraScan, and following the methodology described herein. The initial step is the setup of the TerraScan project, which is done by importing client provided tile boundary index (converted to the native UTM zone for processing)encompassing the entire project areas. The 3D laser point clouds, in binary format, were imported into the TerraScan project and divided in 495 USGS DOQQ derived tiles in LAS 1.0 format. Once tiled, the laser points were classified using a proprietary routine in TerraScan. This routine removes any obvious outliers from the dataset following which the ground layer is extracted from the oint cloud. The ground extraction process encompassed in this routine takes place by building an iterative surface model. This surface model is generated using three main parameters: building size, iteration angle and iteration distance. The initial model is based on low points being selected by a "roaming window" with the assumption is that these are the ground points. The size of this roaming window is determined by the building size parameter. The low points are triangulated and the remaining points are evaluated and subsequently added to the model if they meet the iteration angle and distance constraints. This process is repeated until no additional points are added within an iteration. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain angle allowed within the classification model. The data is then manually quality controlled with the use of hillshading, cross-sections and profiles. Any points found to be of class vegetation, building or error during the quality control process, are removed from the ground model and placed on the appropriate layer. An integrity check is also performed simultaneously to verify that ground features such as rock cuts, elevated roads and crests are present. Once data has been cleaned and complete, it is then by a supervisor via manual inspection and through the use of a hillshade mosaic of the entire project area. - Deliverable Product Generation >Deliverable Tiling Scheme All files were converted to LAS 1.1, in the specified projection and units and were delivered in the client provided tiling scheme with a total of 128 tiles. >LAS 1.1 Files LiDAR point data in LAS 1.1 ASPRS classfication scheme Class 1 Non-ground Class 2 Ground Class 7 Noise Class 9 Water Contains the following fields of information: Class, GPS WeekTime, Easting, Northing, Elevation, Echo Number, Echo, Intensity, Flightline, Scan Angle All points outside project area were assigned to Class 1 - Non-Ground (Unclassified). |
---|---|
Process Date/Time: | 2007-12-01 00:00:00 |
Process Step 3
Description: |
The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in NAD83 UTM Zone 15 Coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 2. The LAS files were converted from UTM Zone 11 (meters) to Geographic coordinates (decimal degrees). 3. The LAS files were converted to Adjusted GPS time rather than the delivered GPS week seconds (1457). |
---|---|
Process Date/Time: | 2016-03-20 00:00:00 |
Catalog Details
Catalog Item ID: | 49639 |
---|---|
GUID: | gov.noaa.nmfs.inport:49639 |
Metadata Record Created By: | Anne Ball |
Metadata Record Created: | 2017-11-15 15:21+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 |