Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2024: 2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Tulalip Partnership, https://www.fisheries.noaa.gov/inport/item/50174.

Item Identification

Title: 2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Tulalip Partnership
Short Name: wa2013_pslc_tulalip_m2614_metadata
Status: Completed
Publication Date: 2014-01-14
Abstract:

In October 2012, WSI (Watershed Sciences, Inc.) was contracted by the Puget Sound LiDAR Consortium (PSLC)to collect Light Detection and Ranging (LiDAR) data on a 5-year cycle for sites in Washington. The Tulalipsite in northwestern Washington is one of these sites. Unclassified (1), Ground (2) and Snow (14).

Purpose:

Provide high resolution terrain elevation and land cover elevation data. Data were collected to aidin assessing stream and forest habitat.

Notes:

10818

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/2614/supplemental/wa2013_pslc_tulalip_m2614.KMZ

Reports explaining collection and quality assurance is available at:https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2614/supplemental/wa2013_pslc_tulalip_m2614_lidarreport.pdf

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
None LAZ

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 LAZ format (ASPRS Classes 1,2)

Entity Attribute Detail Citation:

none

Distribution Liability:

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

Data Set Credit: Please credit the Puget Sound LiDAR Consortium (PSLC) for these data. The PSLC is supported by the Puget Sound Regional Council,the National Aeronautical and Space Administration (NASA), the United States Geological Survey (USGS) and numerous partners inlocal, state, and tribal government.

Support Roles

Data Steward

CC ID: 693150
Date Effective From: 2014-01-14
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: 693152
Date Effective From: 2014-01-14
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: 693153
Date Effective From: 2014-01-14
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: 693151
Date Effective From: 2014-01-14
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: 1135105
W° Bound: -123.5796125
E° Bound: -122.9079181
N° Bound: 48.4311248
S° Bound: 47.7515734

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=2614;

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 datamay no longer represent actual surface conditions. Users should not use this data for critical applications without a fullawareness 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

CC ID: 743455
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2614
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: 743456
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2614/index.html
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

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

URL 2

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

URL 3

CC ID: 743460
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2614/supplemental/wa2013_pslc_tulalip_m2614.KMZ
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz
Description:

This graphic shows the 2013 lidar coverage for the Tulalip Partnership lidar collection.

Activity Log

Activity Log 1

CC ID: 693200
Activity Date/Time: 2016-05-23
Description:

Date that the source FGDC record was last modified.

Activity Log 2

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

Partial upload of Positional Accuracy fields only.

Activity Log 4

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

Partial upload to move data access links to Distribution Info.

Data Quality

Horizontal Positional Accuracy:

Horizontal positional accuracy for LiDAR is dependent upon the quality ofthe GPS/INS solution, sensor calibration and ground conditions at the time of data capture.The standard system results for horizontal accuracy are less than 1 meter.Not reported, assumed as 1.0 m. Laser horizontal errors are a function of flight altitudeabove ground (i.e., +/- 1/3000th AGL flight altitude). Relative errors for the position mustbe less than 1.5 cm horizontal and 2.0 cm vertical in order to be accepted.; Quantitative Value: 1.0 meters, Test that produced the value: See Lidar report.

Vertical Positional Accuracy:

Upon the LiDAR data's arrival to the office, WSI processing staff initiates a suite ofautomated and manual techniques to process the data into the requested deliverables.Processing tasks include GPS control computations, smoothed best estimate trajectory(SBET) calculations, kinematic corrections, calculation of laser point position,calibration for optimal relative and absolute accuracy, and classification ofground and non-ground points.; Quantitative Value: 0.054 meters, Test that produced the value: Vertical absolute accuracy was primarily assessed from RTK ground check point (GCP)data collected on open, bare earth surfaces with level slope (less than 20 degrees).Fundamental Vertical Accuracy (FVA) reporting is designed to meet guidelinespresented in the National Standard for Spatial Data Accuracy (FGDC, 1998). FVAcompares known RTK ground survey check points to the triangulated ground surfacegenerated by the LiDAR points. FVA is a measure of the accuracy of LiDAR point datain open areas where the LiDAR system has a "very high probability" of measuring theground surface and is evaluated at the 95% confidence interval (1.96 sigma).Vertical accuracy was calculated at 2-sigma to 0.178 ft (5.4 cm).

Completeness Report:

LiDAR data has been collected and processed for all areas within the project study area.

Conceptual Consistency:

The accuracy of the LiDAR data collection can be described in terms of absolute accuracy (the consistency ofthe data with external data sources) and relative accuracy (the consistency of the dataset with itself). SeeAppendix A in the lidar report for further information on sources of error and operational measures used toimprove relative accuracy.

Lineage

Process Steps

Process Step 1

CC ID: 1135101
Description:

Planning.In preparation for data collection, WSI reviewed the project area using Google Earth,and flightlines were developed using a combination of specialized software. Carefulplanning by acquisition staff entailed adapting the pulse rate, flight altitude, scanangle, and ground speed to ensure complete coverage of the study area at thetarget point density of 11.43 points per square meter (ground points only were calculated at0.83 points per square meter). Efforts are taken to optimize flight paths by minimizingflight times while meeting all accuracy specifications.Factors such as satellite constellation availability and weather windows mustbe considered during the planning stage. Any weather hazards or conditions affectingthe flight were continuously monitored due to their potential impact on the dailysuccess of airborne and ground operations. In addition, a variety of logisticalconsiderations required review including private property access, potential airspace restrictions, and availability of company resources (both staff andequipment).Special care was taken to acquire the tidal flats at low tide wherepossible.

Process Step 2

CC ID: 1135102
Description:

LiDAR Processing Steps:1. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPSand static ground GPS data.Software - Waypoint GPS v.8.3 Trimble Business Center v.3.00 Geographic Calculator 20132. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processedaircraft position with attitude data. Sensor head position and attitude are calculatedthroughout the survey. The SBET data are used extensively for laser point processing.Software - IPAS TC v.3.13. Calculate laser point position by associating SBET position to each laser point returntime, scan angle, intensity, etc. Create raw laser point cloud data for the entire surveyin *.las (ASPRS v. 1.2) format. Data are converted to orthometric elevations (NAVD88) byapplying a Geoid12 correction.Software - ALS Post Processing Software v.2.744. Import raw laser points into manageable blocks (less than 500 MB) to perform manualrelative accuracy calibration and filter erroneous points. Ground points are thenclassified for individual flight lines (to be used for relative accuracy testingand calibration).Software - TerraScan v.13.0085. Using ground classified points per each flight line, the relative accuracy is tested.Automated line-to-line calibrations are then performed for system attitude parameters(pitch, roll, heading), mirror flex (scale) and GPS/IMU drift.Calibrations are calculated on ground classified points from paired flight lines andresults are applied to all points in a flight line. Every flight line is used forrelative accuracy calibration.Software - TerraMatch v.13.0026. Classify resulting data to ground and other client designated ASPRSclassifications (Table 7). Assess statistical absolute accuracy via direct comparisonsof ground classified points to ground RTK survey data.Software - TerraScan v.13.008 TerraModeler v.13.0027. Generate bare earth models as triangulated surfaces. Highest hit models were createdas a surface expression of all classified points (excluding the noise and withheldclasses). All surface models were exported as ESRI grids at a 3-foot pixel resolution.Software - TerraScan v.13.008 ArcMap v. 10.1 TerraModeler v.13.002

Process Step 3

CC ID: 1135103
Description:

The NOAA Office for Coastal Management (OCM) downloaded topographic files in LAZ format from PSLC's website.The files contained lidar easting, northing, elevation, intensity, return number, class, scan angleand GPS time measurements. Entiat data were received in Washington State Plane North, 4601 (feet) andreferenced to NAVD88 (feet).OCM performed the following processing for data storage and Digital Coast provisioning purposes:1. The All-Return LAZ files were cleared of variable lengths records.2. The All-Return LAZ files were converted from a Projected Coordinate System (State Plane 4601)to a Geographic Coordinate system (NAD83).3. The All-Return LAZ files were converted from NAVD88 to ellipsoidal heights using Geoid03.

Process Date/Time: 2014-01-14 00:00:00

Catalog Details

Catalog Item ID: 50174
GUID: gov.noaa.nmfs.inport:50174
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:24+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