ISO Table View View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

Metadata Identifier: gov.noaa.csc.maps:wa2011_pslc_quinault_m2603

Aggregation Info | Bands | Citations | Constraints | Coverage Descriptions | Dimensions | Extents | Formats | Geographic Bounding Box
Georectified Information | Georeferenceable Information | Identifiers | Instruments | Mediums | OnlineResources | Operations
Platforms | Process Steps | Range Elements | Reference Systems | Responsible Parties | Series | Sources | Spatial Grids | Temporal Extents

MD_DataIdentification

Count Component Title Abstract
1 2011 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Quinault River Basin Watershed Sciences, Inc. (WSI) collected Light Detection and Ranging (LiDAR) data on the Quinault River Basin survey area for the Puget Sound LiDAR Consortium and the Quinault Indian Nation. Delivery 1 of the survey area was collected on April 16th, 29th, 30th, and May 1st, 2011 and delivered on June 14th, 2011. Delivery 2 of the survey area was collected on November 6th -19th, and December 1st - 4th, 2011. This report documents the data acquisition, processing methods, accuracy assessment, and deliverables for the first 91,162 acres of Delivery 1 data and the final 144,033 acres of Delivery 2 data for a total of 234,394 acres. The requested area was expanded to include a 100m buffer to ensure complete coverage and adequate point densities around survey area boundaries. The 2012 Quinault River Basin data (Delivery 2) were integrated with overlapping portions of the 2011 data (Delivery 1) to provide seamless models.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2011 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Quinault River Basin
  • 2013-12-05
1 Lidar Dataset Supplemental Information
    1 None
      1 North American Datum 1983
      • 2007-01-19
      1 none
        Top

        CI_Series

        none found
        Top

        CI_ResponsibleParty

        Count Component Individual Organization Position Email Role Linkage
        1 resourceProvider http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269
        1 Citation URL ftp://csc.noaa.gov/pub/DigitalCoast/lidar1_z/geoid12a/data/2603/supplemental/
        1 NOAA CSC (originator) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov originator http://coast.noaa.gov
        1 NOAA CSC (publisher) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov publisher http://coast.noaa.gov
        1 NOAA CSC(distributor) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov distributor http://coast.noaa.gov
        1 NOAA CSC (processor) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce coastal.info@noaa.gov processor http://coast.noaa.gov
        1 Diana Martinez - originator - Puget Sound Lidar Consortium (PSLC) Diana Martinez Puget Sound Lidar Consortium (PSLC) Senior GIS Analyst, Puget Sound Regional Council dmartinez@psrc.org originator
        1 Diana Martinez - pointOfContact - Puget Sound Lidar Consortium (PSLC) Diana Martinez Puget Sound Lidar Consortium (PSLC) Senior GIS Analyst, Puget Sound Regional Council dmartinez@psrc.org pointOfContact
        1 EPSG Registry European Petroleum Survey Group publisher http://www.epsg-registry.org/
        1 Mike Sutherland(author) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov author
        1 Mike Sutherland Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov distributor
        1 Mike Sutherland (processor) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov processor
        Top

        CI_OnlineResource

        Count Component Linkage Name Description Function
        1 ftp://csc.noaa.gov/pub/DigitalCoast/lidar1_z/geoid12a/data/2603/supplemental/ Where they exist, the supplemental information folder will include acquisition and QA/QC reports, breaklines, a footprint of the spatial extent of the data and other relevant related information information
        4 http://coast.noaa.gov
        1 http://www.epsg-registry.org/ European Petroleum Survey Group Geodetic Parameter Registry Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. search
        1 http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 NAD83 Link to Geographic Markup Language (GML) description of reference system. information
        Top

        MD_Identifier or RS_Identifier

        Count Component Code
        1 Ellipsoid in Meters
        1 urn:ogc:def:crs:EPSG::4269
        Top

        EX_Extent

        Bounding Box Temporal Extent
        Count Component Description West East North South Start End
        1 -124.36281791 -123.78635155 47.74485454 47.24383491 2011-11-06 2011-12-01 2011-11-19 2011-12-04
        Top

        EX_GeographicBoundingBox

        Count Component West East North South
        1 -124.36281791 -123.78635155 47.74485454 47.24383491
        Top

        EX_TemporalExtent

        Count Component Start End
        4
        1 2011-11-06 2011-11-19
        1 2011-12-01 2011-12-04
        Top

        MD_Format

        Count Component Name Version specification
        1 LAZ
        Top

        MD_Medium

        none found
        Top

        MD_Constraints

        Count Component Use Limitation
        1 Lidar Use Limitation These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
        Top

        MD_ReferenceSystem

        Count Component Code Authority Title
        1 Ellipsoid Ellipsoid in Meters
        1 NAD83 urn:ogc:def:crs:EPSG::4269 North American Datum 1983
        Top

        MD_GridSpatialRepresentation

        none found
        Top

        MD_Georeferenceable or MI_Georeferenceable

        none found
        Top

        MD_Georectified or MI_Georectified

        none found
        Top

        MD_Dimension

        none found
        Top

        MD_CoverageDescription or MI_CoverageDescription

        none found
        Top

        MD_Band or MI_Band

        none found
        Top

        MI_RangeElementDescription

        none found
        Top

        MD_AggregateInformation

        Count Component Title Code Association Type Code
        1 Lidar Dataset Supplemental Information crossReference
        Top

        LE_Source or LI_Source

        none found
        Top

        LE_ProcessStep or LI_ProcessStep

        Count Component DateTime Description
        1 Acquisition. The LiDAR survey utilized a Leica ALS50-II sensor in a Cessna Caravan 208B. Depending on acquisition day, weather, and terrain, the Leica systems were set to acquire 105,000 laser pulses per second (i.e.105 kHz pulse rate) and flown at 900 meters above ground level (AGL), capturing a scan angle of +/- 14 degrees from nadir. These settings were developed to yield points with an average native pulse density of 8 pulses per square meter over terrestrial surfaces. It is not uncommon for some types of surfaces to return fewer pulses than the laser originally emitted. These discrepancies between ?native? and ?delivered? density will vary depending on terrain, land cover, and the prevalence of water bodies. All areas were surveyed with an opposing flight line side-lap of more than 60% (less than 100% overlap) to reduce laser shadowing and increase surface laser painting. The Leica laser systems allow up to four range measurements (returns) per pulse, and all discernable laser returns were processed for the output dataset. To accurately solve for laser point position (geographic coordinates x, y, z) the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Aircraft position was measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft/sensor position and attitude data are indexed by GPS time.
        1 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 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. Software - ALS Post Processing Software v.2.74, Corpscon 6 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. Data were then converted to orthometric elevations (NAVD88) by applying a Geoid03 correction. Software: TerraScan v.12.004, TerraModeler v.12.002 7. 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
        1 2013-12-04T00:00:00 The NOAA Coastal Services Center (CSC) downloaded topographic files in LAZ format from PSLC's website. The files contained lidar easting, northing, elevation, intensity, return number, class, scan angle and GPS time measurements; the data was received in state plane Washington (in feet) and vertical coordinates were referenced to NAVD88 in feet using the Geoid03 model. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The All-Return LAZ files were checked for bad elevations 2. The laz files were converted from a Projected Coordinate System (SP 4602) to a Geographic Coordinate system (NAD83) 3. The laz files were then converted to ellipsoidal vertical units in meters using the geoid03 conversion.
        1 2013-12-31T00:00:00 The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.
        Top

        MI_Operation

        none found
        Top

        MI_Platform

        none found
        Top

        MI_Instrument

        none found
        Top