| 2023 WA DNR Lidar: Asotin County, WA and Lewiston, ID | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:80034 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2026-06-25T22:21:06 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(HARN) / UTM zone 11N date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/3741/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:3741 version: 6.18.3 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2023 WA DNR Lidar: Asotin County, WA and Lewiston, ID alternateTitle: wa2023_asotin_m14583 date: (CI_Date) date: 2023 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2026 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 80034 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/80034 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/14583/ept.json protocol: WWW:LINK-1.0-http--link name: Entwine Point Tiles (EPT) description: Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14583/supplemental/ger_asotin_2023_lidar_report.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the NV5 Geospatial Technical Lidar Report function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14583/supplemental/WGS_QA_asotin_2023.pdf protocol: WWW:LINK-1.0-http--link name: Washington Geologic Survey QA Report description: Link to the Washington Geologic Survey QA Report function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?m=14583&g=geoid18 protocol: WWW:LINK-1.0-http--link name: Potree 3D View description: Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/ protocol: WWW:LINK-1.0-http--link name: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: No metadata record was provided with the data. This record is populated with information from the Quantum Spatial, Inc. technical report downloaded from the Washington Dept. of Natural Resources Washington Lidar Portal. The technical report is available for download from the link provided in the URL section of this metadata record. In February 2023, NV5 Geospatial (NV5) was contracted by Washington Department of Natural Resources (WADNR) to collect Light Detection and Ranging (lidar) data in the summer of 2023 for the Asotin County, Washington and Lewiston, Idaho. Data were collected to aid WADNR in assessing the topographic and geophysical properties of the study area. A total of 768,469 acres of 8 pulses per square meter (PPSM) LiDAR data were acquired and delivered to the client. The data were collected between March 18 and June 26, 2023 and delivered to Washington DNR on June 14, 2019. This data was downloaded by the NOAA Office for Coastal Management (OCM) from the Washington Lidar Portal for the purpose of making the data publicly available for custom and bulk downloads from the NOAA Digital Coast Data Access Viewer. This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. purpose: Data were collected to aid WADNR in assessing the topographic and geophysical properties of the study area. and will be distributed by DNR. credit: NV5 Geospatial, Inc., Washington Dept. of Natural Resources The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed 2026-07-20 at https://coast.noaa.gov/dataviewer. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 23.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > IDAHO keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > WASHINGTON keyword: VERTICAL LOCATION > LAND SURFACE type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 23.3 descriptiveKeywords: (MD_Keywords) keyword: LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) edition: 23.3 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 23.3 descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-07-20 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2023 WA DNR Lidar: Asotin County, WA and Lewiston, ID [Data Date Range], https://www.fisheries.noaa.gov/inport/item/80034. resourceConstraints: (MD_Constraints) useLimitation: 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. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-07-20 from the NOAA system. Access Constraints: None resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-07-20 from the NOAA system. 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. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-07-20 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: 2023 WA DNR Lidar DEM: Asotin County, WA and Lewiston, ID date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 80036 associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -118 eastBoundLongitude: -116.84 southBoundLatitude: 45.98 northBoundLatitude: 46.48 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-03-18 endPosition: 2023-06-26 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: Zip distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=14583/details/14583 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14583/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, in UTM coordinates and orthometric heights in meters. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Lidar horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, flying altitude, and INS derived attitude error. The obtained RMSEr value is multiplied by a conversion factor of 1.7308 to yield the horizontal component of the National Standards for Spatial Data Accuracy (NSSDA) reporting standard where a theoretical point will fall within the obtained radius 95 percent of the time. Based on a flying altitude of 2500 meters, an IMU error of 0.003 decimal degrees, and a GNSS positional error of 0.023 meters, this project was produced to meet 1.336 feet (0.407 m) horizontal accuracy at the 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Absolute accuracy was assessed using Non-Vegetated Vertical Accuracy (NVA) reporting designed to meet guidelines presented in the FGDC National Standard for Spatial Data Accuracy. NVA compares known ground check point data that were withheld from the calibration and post-processing of the lidar point cloud to the triangulated surface generated by the classified lidar point cloud as well as the derived gridded bare earth DEM. NVA is a measure of the accuracy of lidar point data in open areas where the lidar system has a high probability of measuring the ground surface and is evaluated at the 95% confidence interval (1.96 * RMSE). The mean and standard deviation (sigma) of divergence of the ground surface model from quality assurance point coordinates are also considered during accuracy assessment. These statistics assume the error for x, y, and z is normally distributed, and therefore the skew and kurtosis of distributions are also considered when evaluating error statistics. For the Asotin County, Washington and Lewiston, Idaho survey, 65 ground checkpoints were withheld from the calibration and post processing of the lidar point cloud, with resulting non-vegetated vertical accuracy of 0.181 feet (5.5 cm) or 0.292 ft (2.8 cm) RMSE as compared to classified LAS, and 0.216 feet (0.066 meters) as compared to the bare earth DEM, with 95% confidence. NV5 Geospatial also assessed vertical accuracy using Vegetated Vertical Accuracy (VVA) reporting. VVA compares known ground check point data collected over vegetated surfaces using land class descriptions to the triangulated ground surface generated by the ground classified lidar points. For the Asotin County, Washington and Lewiston, Idaho survey, 53 vegetated checkpoints were collected, with resulting vegetated vertical accuracy of 0.923 feet (0.281 meters) as compared to the classified LAS, and 0.901 feet (0.275 meters) as compared to the bare earth DEM evaluated at the 95th percentile. result: (missing) lineage: (LI_Lineage) statement: The NOAA Office for Coastal Management (OCM) downloaded the LAZ files from the Washington Lidar Portal. processStep: (LI_ProcessStep) description: Planning: In preparation for data collection, NV5 Geospatial reviewed the project area and developed a specialized flight plan to ensure complete coverage of the Asotin County, Washington and Lewiston, Idaho lidar study area at the target point density of greater than or equal to 8.0 points/m2 (0.74 points/ft2). Acquisition parameters including orientation relative to terrain, flight altitude, pulse rate, scan angle, and ground speed were adapted to optimize flight paths and flight times while meeting all contract specifications. Factors such as satellite constellation availability and weather windows must be considered during the planning stage. Any weather hazards or conditions affecting the flight were continuously monitored due to their potential impact on the daily success of airborne and ground operations. In addition, logistical considerations including private property access and potential air space restrictions were reviewed. processStep: (LI_ProcessStep) description: Ground Survey Ground control surveys, including monumentation and ground survey points (GSPs) were conducted to support the airborne acquisition. Ground control data were used to geospatially correct the aircraft positional coordinate data and to perform quality assurance checks on final lidar. Base Stations Base stations were utilized for collection of ground survey points using real time kinematic (RTK), fast static (FS), and total station (TS) survey techniques. Base station locations were selected with consideration for satellite visibility, field crew safety, and optimal location for GSP coverage. NV5 Geospatial utilized three permanent real-time network (RTN) base stations from the Washington State Reference Network (WSRN) for the Asotin County, Washington and Lewiston, Idaho Lidar project and one existing mag hub nail. NV5 Geospatial also established five new monuments using 6 inch mag hub nails with orange survey washers. NV5's professional land surveyor Steven Hyde (WAPLS#22028821, L-10235) oversaw and certified the ground survey. NV5 Geospatial utilized static Global Navigation Satellite System (GNSS) data collected at 1 Hz recording frequency for each base station. During post-processing, the static GNSS data were triangulated with nearby Continuously Operating Reference Stations (CORS) using the Online Positioning User Service (OPUS) for precise positioning. Multiple independent sessions over the same monument were processed to confirm antenna height measurements and to refine position accuracy. Monuments were established according to the national standard for geodetic control networks, as specified in the Federal Geographic Data Committee (FGDC) Geospatial Positioning Accuracy Standards for geodetic networks. This standard provides guidelines for classification of monument quality at the 95% confidence interval as a basis for comparing the quality of one control network to another. For the Asotin County, Washington and Lewiston, Idaho Lidar project, the monument coordinates contributed no more than 5.6 cm of positional error to the geolocation of the final ground survey points and lidar, with 95% confidence. processStep: (LI_ProcessStep) description: Ground Survey Points (GSPs) Ground survey points were collected using real time kinematic (RTK), fast-static (FS), and total station (TS) survey techniques. For RTK surveys, a roving receiver receives corrections from a nearby base station or Real-Time Network (RTN) via radio or cellular network, enabling rapid collection of points with relative errors less than 1.5 cm horizontal and 2.0 cm vertical. FS surveys compute these corrections during post-processing to achieve comparable accuracy. RTK surveys record data while stationary for at least five seconds, calculating the position using at least three one-second epochs, while FS surveys record observations for up to fifteen minutes on each GSP in order to support longer baselines. All GSP measurements were made during periods with a Position Dilution of Precision (PDOP) of less than or equal to 3.0 with at least six satellites in view of the stationary and roving receivers. Forested checkpoints are collected using total stations in order to measure positions under dense canopy. Total station backsight and setup points are established using GNSS survey techniques. GSPs were collected in areas where good satellite visibility was achieved on paved roads and other hard surfaces such as gravel or packed dirt roads. GSP measurements were not taken on highly reflective surfaces such as center line stripes or lane markings on roads due to the increased noise seen in the laser returns over these surfaces. GSPs were collected within as many flightlines as possible; however, the distribution of GSPs depended on ground access constraints and monument locations and may not be equably distributed throughout the study area. processStep: (LI_ProcessStep) description: Airborne Survey The lidar survey was accomplished using a Riegl VQ-1560ii-S system mounted in a Cessna Caravan. Table 4 summarizes the settings used to yield an average pulse density of greater than or equal to 8 pulses/m2 (greater than or equal to 0.74 pulses/ft2) over the Asotin County, Washington and Lewiston, Idaho project area. The Riegl VQ-1560ii-S laser system can record unlimited range measurements (returns) per pulse, however a maximum of 15 returns can be stored due to LAS v1.4 file limitations. The typical number of returns digitized from a single pulse range from 1 to 10 for the Asotin County, Washington and Lewiston, Idaho project area. It is not uncommon for some types of surfaces (e.g., dense vegetation or water) to return fewer pulses to the lidar sensor than the laser originally emitted. The discrepancy between first return and overall delivered density will vary depending on terrain, land cover, and the prevalence of water bodies. All discernible laser returns were processed for the output dataset. All areas were surveyed with an opposing flight line side-lap of greater than or equal to 55% (greater than or equal to 100% overlap) in order to reduce laser shadowing and increase surface laser painting. To accurately solve for laser point position (geographic coordinates x, y and z), the positional coordinates of the airborne sensor and the orientation of the aircraft to the horizon (attitude) were recorded continuously throughout the lidar data collection mission. Position of the aircraft was measured twice per second (2 Hz) by an onboard differential GPS unit, and 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 and sensor position and attitude data are indexed by GPS time. processStep: (LI_ProcessStep) description: Upon completion of data acquisition, NV5 Geospatial processing staff initiated a suite of automated and manual techniques to process the data into the requested deliverables. Processing tasks included GPS control computations, smoothed best estimate trajectory (SBET) calculations, kinematic corrections, calculation of laser point position, sensor and data calibration for optimal relative and absolute accuracy, and lidar point classification. Processing methodologies were tailored for the landscape. Brief descriptions of these tasks are shown below: Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.4) format. Convert data to orthometric elevations by applying a geoid correction. Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. Classify resulting data to ground and other client designated ASPRS classifications. Assess statistical absolute accuracy via direct comparisons of ground classified points to ground control survey data. processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded this data set from the Washington Lidar Portal. The total number of files downloaded and processed was 1860. No metadata record was provided with the data. This record is populated with information from the NV5 Geospatial technical report downloaded from the Washington Dept. of Natural Resources Washington Lidar Portal. The technical report is available for download from the Washington Lidar Portal. The link is provided in the URL section of this metadata record. The data were in Washington State Plane South (NAD83 HARN), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. From the provided report, the data were classified as: 1 - Unclassified, 2 - Ground, 7W - Low Noise, 9 - Water, 17 - Bridge Deck. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available in the DAV are: 1, 2, 7, 9, 17, 18W - High Noise, 20 - Ignored Ground, 22 - Temporal Exclusion. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert from Washington State Plane South (NAD83 HARN), US survey feet coordinates to geographic coordinates, and to convert from elevations in feet to meters. dateTime: DateTime: 2026-06-17T00:00:00 processor: (CI_ResponsibleParty) organisationName: Anchor: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Washington Dept of Natural Resources date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Washington Dept of Natural Resources contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://lidarportal.dnr.wa.gov/ protocol: WWW:LINK-1.0-http--link name: Washington Lidar Portal description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher processStep: (LI_ProcessStep) description: The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. dateTime: DateTime: 2026-07-20 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor return to top acquisitionInformation: (MI_AcquisitionInformation) instrument: (MI_Instrument) identifier: (MD_Identifier) code: Riegl VQ-1560 II-S type: Lidar Sensor description: The RIEGL VQ-1560 II-S system has a rotating mirror design and high-output dual laser technology, allowing for data collection at a higher altitude and faster speed on large-scale mapping projects and corridor work. This system provides more dense, high-precision data with uniform point distribution and faster acquisition. | |