gov.noaa.nmfs.inport:50167
eng
UTF8
dataset
OCM Partners
resourceProvider
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
2024-02-29T00:00:00
ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data
ISO 19115-2:2009(E)
2012 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Jefferson and Clallam Counties, Washington
wa2012_pslc_jeffersonclallam_m2506_metadata
2013-06
publication
NOAA/NMFS/EDM
50167
https://www.fisheries.noaa.gov/inport/item/50167
WWW:LINK-1.0-http--link
Full Metadata Record
View the complete metadata record on InPort for more information about this dataset.
information
https://coast.noaa.gov/dataviewer
WWW:LINK-1.0-http--link
Citation URL
Online Resource
download
https://coast.noaa.gov
WWW:LINK-1.0-http--link
Citation URL
Online Resource
download
Watershed Sciences, Inc. (WSI) collected Light Detection and Ranging (LiDAR) data for the Jefferson/Clallam study area on March 23rd-25th, April 13th-15th,
and May 7th, 2012 for the Puget Sound LiDAR Consortium in partnership with the Federal Emergency Management Agency (FEMA). The requested area of 32,034
acres for the Jefferson/ Clallam AOI was expanded to include a 100m buffer to ensure complete coverage and adequate point densities around survey area
boundaries. The total acreage of this delivery is 42,038 buffered acres of LiDAR data.
The LiDAR survey utilized a Leica ALS50 Phase II in a Cessna Caravan 208B and a Leica ALS60 sensor in a Partenavia. See "Process Report" for detailed
information about airborne/ground survey methods.
This data set has a point spacing of 11.58 points per square meter.
The LAS files can be used to create DEMs and also to extract topographic data in software that does not support raster data. Other surface features
can also be extracted with custom applications. LiDAR data has a wide range of uses such as earthquake hazard studies, hydrologic modeling, forestry,
coastal engineering, roadway and pipeline engineering, flood plain mapping, wetland studies, geologic studies and a variety of analytical and
cartographic projects.
Please credit the Puget Sound LiDAR Consortium (PSLC) and FEMA 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 in local, state, and
tribal government.
completed
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
custodian
asNeeded
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2506/supplemental/wa2012_pslc_jeffersonclallam_footprint.KMZ
This graphic shows the lidar coverage for a section of Jefferson and Clallam Counties, Washington.
kmz
LAZ
theme
Lidar - partner (no harvest)
project
InPort
otherRestrictions
Cite As: OCM Partners, [Date of Access]: 2012 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Jefferson and Clallam Counties, Washington [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50167.
NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose.
otherRestrictions
Access Constraints: None
otherRestrictions
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.
otherRestrictions
Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility
of Watershed Sciences Inc., PSLC, FEMA, NOAA, the Office for Coastal Management or its partners.
unclassified
NOAA Data Management Plan (DMP)
NOAA/NMFS/EDM
50167
https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50167.pdf
WWW:LINK-1.0-http--link
NOAA Data Management Plan (DMP)
NOAA Data Management Plan for this record on InPort.
information
crossReference
vector
eng; US
elevation
-123.626848
-122.747177
47.934501
48.185893
| Currentness: Ground Condition
2012-03-23
2012-05-07
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2506/supplemental/wa2012_pslc_jeffersonclallam_footprint.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/2506/supplemental/wa2012_pslc_jeffersonclallam_lidarreport.pdf
false
eng
false
none
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
distributor
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2506
WWW:LINK-1.0-http--link
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
download
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2506/index.html
WWW:LINK-1.0-http--link
Bulk Download
Simple download of data files.
download
dataset
Accuracy
Elevations are recorded in floating-point meters and the vertical datum is ellipsoidal (GEOID03). There are no other attribute tables.
Horizontal Positional Accuracy
Not applicable for pure elevation data: every XY error has an associated Z error.
Vertical Positional Accuracy
See the "Project Report" above for a detailed accuracy report.; Quantitative Value: 0.024 meters, Test that produced the value:
Root mean square Z error in open, near-horizontal areas, as specified by contract. Units in meters. Accuracy may be significantly less in steep
areas and under heavy forest canopy.
Completeness Report
Elevation data has been collected for all areas inside project boundaries. The data set was flown with a 60% sidelap between flightlines and a 100 meter
buffer to ensure all areas are properly sampled.
Conceptual Consistency
Puget Sound Lidar Consortium evaluates logical consistency of high-resolution lidar elevation data with three tests: examination of file names,
file formats, and mean and extreme values within each file; internal consistency of measured Z values in areas where survey swaths overlap; and
visual inspection of shaded-relief images calculated from bare-earth models.
File names, formats, and values: All file naming convention and file formats are checked for consistency.
Visual inspection of bare earth surfaces were examined to find any obvious data errors such as blunders, border artifacts, gaps between data quads,
no-data gaps between flight lines, hillscarps, land shifting due to GPS time errors, etc.
1. Resolved kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data.
Software: Waypoint GPS v.8.10, Trimble Business Center v.2.6
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 TC v.3.1
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. Data were then converted to orthometric elevations (NAVD88) by applying a Geoid03
correction.
Software: ALS Post Processing Software v.2.74
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.12.004
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.12.001
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.
Software: TerraScan v.12.004, TerraModeler v.12.002
7. Final version of data was checked for duplicate points using TerraScan software. No duplicate points were found.
Software: TerraScan v.12.004, TerraModeler v.12.002
8. Bare Earth models were created as a triangulated surface and exported as ArcInfo ASCII grids at a 3-foot pixel resolution. Highest Hit models
were created for any class at 3-foot grid spacing and exported as ArcInfo ASCII grids.
Software: TerraScan v.12.004, ArcMap v. 10.0, TerraModeler v.12.002
2012-01-01T00:00:00
The NOAA Office for Coastal Management (OCM) downloaded topographic files in .LAZ format from PSLC's website. The files contained lidar elevation and
intensity measurements. The data were received in Washington State Plane South Zone 4602, NAD83 coordinates and were vertically referenced to
NAVD88 using the Geoid03 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast
provisioning purposes:
1. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03.
2. The topographic las files were converted from a Projected Coordinate System (WA SP South) to a Geographic Coordinate system (NAD83).
3. The topographic las files' vertical units were converted from feet to meters.
4. The topographic las files' horizontal units were converted from feet to decimal degrees.
2013-06-01T00:00:00