2010 King County (WA) Dept of Natural Resources and Parks Lidar: Cedar River
OCM Partners
Data Set
(DS)
| ID: 50161
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 50161
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2010 King County (WA) Dept of Natural Resources and Parks Lidar: Cedar River |
---|---|
Short Name | wa2010_kcdnrp_cedarriver_m2533_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2013-08-14 |
* » Abstract |
Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data and true-color orthophotographs of King County, WA from March 18 to March 20, 2010. The total area of combined study areas orthophotographs and LiDAR, including a 100 m buffer, is approximately 21,038 acres. Original contact information: Contact Name: Dan Eastman Contact Org: King County Dept. of Natural Resources and Parks Title: Senior Ecologist Phone: 206-263-6319 |
* Purpose |
More information can be obtained from the LiDAR report. The link to the report can be found here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2533/supplemental/wa2010_kingcountydnrp_cedarriver_LiDAR_Report.pdf |
Notes |
10805 |
Other Citation Details | |
• Supplemental Information |
Support of the FEMA's FIRM program. A footprint of this data may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2533/supplemental/wa2010_kingcountydnrp_cedarriver.KMZ A LiDAR Report from the vendor for this data set may be viewed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2533/supplemental/wa2010_kingcountydnrp_cedarriver_LiDAR_Report.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | TIN |
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 | Unknown |
Maintenance Note | |
» Data Presentation Form | |
• Entity Attribute Overview |
Lidar points in LAZ format Classed 1,2,7 |
Entity Attribute Detail Citation |
none |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of KC DNRP, WS, the Office for Coastal Management, or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2013-08-14 |
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 | 2013-08-14 |
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 | 2013-08-14 |
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 | 2013-08-14 |
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 | -122.21932256 |
---|---|
* » E° Bound | -121.9699449 |
* » N° Bound | 47.5011362 |
* » S° Bound | 47.3738203 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2010-05-18 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 2
* » Time Frame Type | Discrete |
---|---|
* » Start | 2010-05-19 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 3
* » Time Frame Type | Discrete |
---|---|
* » Start | 2010-05-20 |
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
* » 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 The 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2533 |
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 | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2533/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File 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 |
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 |
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/2533/supplemental/wa2010_kingcountydnrp_cedarriver.KMZ |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the King County Cedar River Topographic LiDAR Survey |
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 |
Attribute accuracy is tested in the LiDAR processing stage. After classification of the LiDAR data, the 'bald earth' point class is compared to ground control collected within the project area. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Horizontal positional accuracy for LiDAR is dependent upon the quality of the 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.; Quantitative Value: 1 meters, Test that produced the value: This value is computed by comparing ground control to an intensity based image derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area. |
Vertical Positional Accuracy |
Vertical positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The vertical accuracy for this project was tested with a resultant RMSE of 0.030 meter (0.099 feet).; Quantitative Value: 0.03 meters, Test that produced the value: This value is computed by comparing ground control elevation to the classified LiDAR ground surface and represents the RMSE of residuals on controls within the project area. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
LiDAR data is collected for the project area. Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums. The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes. Anomalous laser returns that occur infrequently are removed entirely from the data set. The ground class points are then compared to surveyed ground control to develop an accuracy measure of the laser terrain data. |
Conceptual Consistency |
LiDAR data is collected within the project area, processed and verified against control. |
» 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 |
Applications and Work Flow Overview: 1.Resolved kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Software: Waypoint GPS v.8.10, Trimble Geomatics Office v.1.62 2.Developed a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data Sensor head position and attitude were calculated throughout the survey. The SBET data were used extensively for laser point processing. Software: IPAS v.1.35 3.Calculated laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Created raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.2) format. Software: ALS Post Processing Software v.2.7 4.Imported raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter for pits/birds. Ground points were then classified for individual flight lines (to be used for relative accuracy testing and calibration). Software: TerraScan v.10.009 5.Using ground classified points per each flight line, the relative accuracy was tested. Automated line-to-line calibrations were then performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations were performed on ground classified points from paired flight lines. Every flight line was used for relative accuracy calibration. Software: TerraMatch v.10.006 6.Position and attitude data were imported. Resulting data were classified as ground and non-ground points. Statistical absolute accuracy was assessed via direct comparisons of ground classified points to ground RTK survey data. Data were then converted to orthometric elevations (NAVD88) by applying a Geoid03 correction. Ground models were created as a triangulated surface and exported as ArcInfo ASCII grids at a 1 -meter pixel resolution. Software: TerraScan v.10.009, ArcMap v. 9.3.1, TerraModeler v.10.004 7.Converted raw images to tif format, calibrating raw image pixels for gain and exposure settings of each image. Software: Leica Calibration Post Processing v.1.0.4 8.Calculated photo position and orientation by associating the SBET position (Step 3) to each image capture time. Software: IPASCO v.1.3 9.Orthorectified calibrated tiffs utilizing photo orientation information (Step 8) and the LiDAR-derived ground surface (Step 6). Software: Leica Photogrammetry Suite v.9.2 10.To correct light imbalances between overlapping images, radiometric global tilting adjustments were applied to the rectified images. Software: OrthoVista v.4.4. 11.The color corrected images were then mosaicked together for the survey area and subset into tiles to make the file size more manageable. Software: OrthoVista v.4.4. 12.Mosaicked tiles were inspected for misalignments introduced by automatic seam generation. Misalignments were corrected by manual adjustments to seams. Software: Adobe Photoshop 7.0, OrthoVista v.4.4. |
Process Date/Time | 2010-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
LiDAR data is processed using the GPS/INS solution. Data is classified to produce: Class 1: unclassified points Class 2: ground points Class 7: low point (noise) |
Process Date/Time | 2012-08-13 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» 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 GA State Plane coordinates and NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from WA State Plane North coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 03. 3. The data were filtered to remove outliers. 4. The LAS data were sorted by latitude and the headers were updated. |
Process Date/Time | 2013-08-12 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 | 50161 |
---|---|
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 |
---|