2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Entiat
OCM Partners
Data Set
(DS)
| ID: 50171
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 50171
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Entiat |
---|---|
Short Name | wa2013_pslc_entiat_m2613_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2014-01-10 |
* » Abstract |
In October 2012, WSI (Watershed Sciences, Inc.) was contracted by the Puget Sound LiDARConsortium (PSLC) to collect Light Detection and Ranging (LiDAR) data for the EntiatRiver site in central Washington. The area is adjacent to several other LiDAR projectscollected in the greater Wenatchee area since 2008. Data were collected to aid inassessing the topographic and geophysical properties of the study area to supportfault line and geologic instability within the area. The Entiat site covers 67,067 acres,collected June 23, 26, 28, 29 and 30, 2013. |
* Purpose |
Provide high resolution terrain elevation and land cover elevation data. |
Notes |
10815 |
Other Citation Details | |
• 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/2613/supplemental/wa2013_pslc_entiat_m2613.KMZ Reports explaining collection and quality assurance is available at:https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2613/supplemental/wa2013_pslc_entiat_m2613_lidarreport.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | LAZ |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | |
• Maintenance Frequency | As Needed |
Maintenance Note | |
» Data Presentation Form | las |
• Entity Attribute Overview |
LiDAR points in LAZ format (ASPRS Classes 1,2) |
Entity Attribute Detail Citation |
none |
Entity Attribute Detail URL | |
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
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2014-01-10 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2014-01-10 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2014-01-10 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2014-01-10 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -120.5446775 |
---|---|
* » E° Bound | -120.2568846 |
* » N° Bound | 47.74748427 |
* » S° Bound | 47.52317975 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame
* » Time Frame Type | |
---|---|
* » Start | |
End | |
Alternate Start as of Info | |
Alternate End as of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL:https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2613; |
• » 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2613 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2613/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2613/supplemental/wa2013_pslc_entiat_m2613.KMZ |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the areas near Entiat, Washington collected in 2013. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | 2016-05-23 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-11-14 |
---|---|
Activity Type | |
Responsible Party | |
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 Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | 2018-03-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload to move data access links to Distribution Info. |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
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.046 meters, Test that produced the value: Vertical absolute accuracy was primarily assessedfrom RTK ground check point (GCP) data collected on open, bare earth surfaces with levelslope (<20 degrees). Fundamental Vertical Accuracy (FVA) reporting is designed to meet guidelinespresented in the FGDC National Standard for Spatial Data Accuracy3. FVA compares known RTKground survey check points to the triangulated ground surface generated by the LiDAR points.FVA is a measure of the accuracy of LiDAR point data in open areas where the LiDAR system hasa "very high probability" of measuring the ground surface and is evaluated at the 95%confidence interval (1.96 sigma) calculated 0.152 ft (4.6 cm). |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
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. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» 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 =8 pulses per square meter (0.74 pulses/square foot).Efforts are taken to optimize flight paths by minimizing flight times whilemeeting 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). |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» 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 Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» 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 vertical 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-10 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 50171 |
---|---|
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 Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|