| 2019 WA DNR Lidar DEM: San Juan County, WA | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:67179 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: 2022-05-06T13:04:19 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) code: EPSG::6360 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::2926 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2019 WA DNR Lidar DEM: San Juan County, WA date: (CI_Date) date: 2019 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: (missing) dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 67179 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/67179 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://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9495/details/9495 protocol: WWW:LINK-1.0-http--link name: Custom Point Download description: Link to custom download, from the Data Access Viewer (DAV), the lidar point data from which these raster Digital Elevation Model (DEM) data were created. 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. Washington Department of Natural Resources (WA DNR) contracted with Quantum Spatial, Inc. (QSI) in January 2019 to collect Light Detection and Ranging (LiDAR) data for the 2019 San Juan County LiDAR study area. A total of 128,731 acres of 8 pulses per square meter (PPSM) LiDAR data were acquired and delivered to the client. The data were collected between March 2 and March 21, 2019 and delivered to Washington DNR on June 14, 2019. In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from are also available. These data are available for download at the link provided in the URL section of this metadata record. purpose: LiDAR data will be used by the County and distributed by DNR. credit: Quantum Spatial, Inc., Washington Dept. of Natural Resources 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 graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9495/supplemental/wa2019_sanjuan_m9495.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > DIGITAL ELEVATION/TERRAIN MODEL (DEM) type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 12.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA 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: 12.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: 10.3 descriptiveKeywords: (MD_Keywords) keyword: AIRCRAFT type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 10.3 descriptiveKeywords: (MD_Keywords) keyword: DEMs - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: OCM Partners, [Date of Access]: 2019 WA DNR Lidar DEM: San Juan County, WA [Data Date Range], https://www.fisheries.noaa.gov/inport/item/67179. 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 useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | 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. | 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: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 67179 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/67179.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) grid language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -123.238792 eastBoundLongitude: -122.740526 southBoundLatitude: 48.413671 northBoundLatitude: 48.790179 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-03-02 endPosition: 2019-03-04 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2019-03-21 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: GeoTIFF version: (missing) 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=9496/details/9496 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://coast.noaa.gov/htdata/raster5/elevation/WA_SanJuan_DEM_2019_9496 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in GeoTiff format, WA State Plane North NAD83(2011) US survey feet coordinates and orthometric heights in feet. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Vertical Accuracy reporting is designed to meet guidelines presented in the National Standard for Spatial Data Accuracy (NSSDA) (FGDC, 1998) and the ASPRS Guidelines for Vertical Accuracy Reporting for LiDAR Data v 1.0 (ASPRS, 2014). The statistical model compares known GSPs to the closest laser point. Vertical accuracy statistical analysis uses ground survey points in open areas where the LiDAR system has a very high probability that the sensor will measure the ground surface and is evaluated at the 95th percent confidence level. For the 2019 San Juan County LiDAR study area, a total of 1,528 GSPs were collected and used for calibration of the LiDAR data. An additional 81 reserved ground survey points were collected for independent verification. Reserved ground survey points were tested against final LiDAR data, resulting in an RMSE of 0.047 meters, and non-vegetated vertical accuracy (NVA) of 0.092 meters (derived according to NSSDA, using 0.047 m (RMSEz) x 1.96000). The vertical accuracy requirement for this project was 9 cm RMSE. Vegetated vertical accuracy (VVA) testing was required for the San Juan County project, though a VVA requirement was not specified. The VVA tested 0.292 m at the 95th percentile using National Digital Elevation Program (NDEP)/ASPRS Guidelines against the DEM using 9 VVA points. result: (missing) lineage: (LI_Lineage) statement: The NOAA Office for Coastal Management (OCM) downloaded the GeoTiff files from the Washington Lidar Portal. processStep: (LI_ProcessStep) description: Planning: Flightlines were developed using Mission Pro software. Careful planning of the pulse rate, flight altitude, and ground speed ensured that data quality and coverage conditions were met while optimizing flight paths and ensuring the necessary pulse density of greater than eight points per square meter. The known factors were prepared for, such as: GPS constellation availability, acquisition windows, and resource allocation. In addition, a variety of logistical barriers were anticipated, namely private property access and acquisition personnel logistics. Finally, weather hazards and conditions affecting flight were continuously monitored due to their impact on the daily success of airborne and ground operations. processStep: (LI_ProcessStep) description: Geospatial Corrections of Aircraft Positional Data PP-RTX To improve precision and accuracy of the aircraft trajectory, the latest generation of Global Navigation Satellite System (GNSS) satellites and recent advances in GNSS post-processing technology have made possible trajectory processing methods that do not require conventional base support: specifically, Trimble CenterPoint Post-Processed Real-Time Extended (PP-RTX). PP-RTX using Applanix POSPac MMS software leverages near real-time atmospheric models from Trimble's extensive worldwide network of continuously operating base stations to produce highly accurate trajectories. When utilized properly and sufficiently controlled by a ground survey during post-processing, PP-RTX has the following advantages over conventional collection methods: Agility: The airborne acquisition is untethered by access constraints of the ground survey team at the time of acquisition, particularly in remote areas that lack permanent base stations. Flexibility: The airborne acquisition team can instantly shift collection priorities based on weather and client needs without waiting for a ground survey team to relocate. Accuracy: If properly controlled with a ground survey and datum adjustment during post-processing, PP-RTX produces results at least as accurate as conventional methods utilizing base stations. processStep: (LI_ProcessStep) description: Ground Survey Points The ground survey for the WA DNR San Juan County project was conducted between March 10 and March 19, 2019. Ground survey data were used for data calibration and accuracy assessment purposes. Ground survey points (GSPs) were collected using real time kinematic (RTK), post-processed kinematic (PPK), and Fast Static (FS) techniques. For RTK surveys, a base receiver was positioned at a nearby monument to broadcast a kinematic correction to a roving receiver; for PPK and FS surveys, however, these corrections were post-processed. RTK and PPK surveys recorded observations for a minimum of five seconds on each GCP/GSP in order to support longer baselines for post-processing; FS surveys record observations for up to fifteen minutes on each point in order to support longer baselines for postprocessing. All GSP measurements were made during periods with a Position Dilution of Precision (PDOP) no greater than 3.0 and in view of at least six satellites for both receivers. Relative errors for the position were requred to be less than 1.5 centimeters horizontal and 2.0 centimeters vertical in order to be accepted. Base Stations Base stations were utilized for collection of GSPs and selected with consideration for satellite visibility, field crew safety, and optimal location for GSP coverage. A combination of Leica SmartNet Real-Time Network (RTN) base stations, Washington State Reference Network (WSRN) RTN base stations, and QSI-established monuments were utilized for this project. New monumentation was set using magnetic survey nails. processStep: (LI_ProcessStep) description: Airborne Survey All data for the 2019 San Juan County project area were flown between March 2 and March 21, 2019 utilizing a Riegl LMS -Q1560 sensor mounted in a Piper Navajo twin-engine turbine aircraft. The LiDAR system for Riegl LMS-Q1560 sensor was set to acquire greater than or equal to 800,000 laser pulses per second (i.e. 800 kHz pulse rate; 400 kHz per channel) and flown at 1400 meters above ground level (AGL), capturing a 58.5 degree field of view. These settings and flight parameters are developed to yield points with an average native density of greater than or equal to 8 over terrestrial surfaces. The native pulse density is the number of pulses emitted by the LiDAR system. Some types of surfaces (e.g., dense vegetation or water) may return fewer pulses than the laser originally emitted. Therefore, the delivered density can be less than the native density and vary according to distributions of terrain, land cover, and water bodies. The study area was surveyed with opposing flight line side-lap of greater than or equal to 60% (greater than or equal to 100% overlap) for Riegal LMS-Q1560 sensor to reduce laser shadowing and increase surface laser painting. The system allows for an unlimited number of LiDAR return measurements per pulse, and all discernible laser returns were processed for the output data set. The LiDAR sensor operators constantly monitored the data collection settings during acquisition of the data, including pulse rate, power setting, scan rate, gain, field of view, and pulse mode. For each flight the crew performed airborne calibration maneuvers designed to improve the calibration results during the data processing stage. The LiDAR coverage was completed with no data gaps or voids, barring non-reflective surfaces (e.g., open water, wet asphalt). All necessary measures were taken to acquire data under conditions (e.g., minimum cloud decks, no snow on the ground) and in a manner (e.g., adherence to flight plans) that prevented the possibility of data gaps. All QSI LiDAR systems are calibrated per the manufacturer and our own specifications, and tested by QSI for internal consistency among every mission using proprietary methods. To solve for laser point position, an accurate description of aircraft position and attitude is vital. Aircraft position is described as x, y, and z and was measured twice per second (two hertz) by an on-board differential GPS unit. Aircraft attitude is described as pitch, roll, and yaw (heading) and was measured 200 times per second (200 hertz) from an onboard inertial measurement unit (IMU). Weather conditions were constantly assessed in flight, as adverse conditions not only affect data quality, but can prove unsafe for flying. processStep: (LI_ProcessStep) description: Once the LiDAR data arrived in the laboratory, QSI employed a suite of automated and manual techniques for processing tasks. Processing tasks included: GPS, kinematic corrections, calculation of laser point position, relative accuracy testing, classification of ground and non-ground points, and assessments of statistical absolute accuracy. The general workflow for calibration of the LiDAR data was as follows: Resolve GNSS kinematic corrections for aircraft position data using kinematic aircraft GNSS (collected at 2Hz) and IMU (collected at 200Hz) data with Trimble CenterPoint PP-RTX methodologies. Used POSGNSS, PosPac MMS Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data. Sensor heading, position, and attitude are calculated throughout the survey. Used POSGNSS, PosPac MMS Calculate laser point position by associating SBET position to each laser point return time, with offsets relative to scan angle, intensity, etc. This process creates the raw laser point cloud data for the entire survey in *.las (ASPRS v 1.2) format, in which each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z information. These data are converted to orthometric elevation (NAVD88 & NGVD29) by applying a Geoid correction. Used RiProcess and RiWorld Test relative accuracy using ground classified points per each flight line. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale), and GNSS/IMU drift. Calibrations are performed on ground classified points from paired flight lines. Every flight line is used for relative accuracy calibration. Used TerraMatch, TerraScan, QSI Proprietary Software Assess NVA via direct comparisons of ground classified points to ground RTK survey data. Point classifications are assigned for features of interest via a combination of QSI custom algorithms and manual inspection. Used TerraScan, TerraMatch, Trimble Business Center processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded 15 raster DEM files in GeoTiff format from the Washington Lidar Portal. The data were in Washington State Plane North NAD83(2011), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The bare earth raster files were at a 3 feet grid spacing. No metadata record was provided with the data. This record is populated with information from the Quantum Geospatial, Inc. technical report downloaded from the Washington Dept. of Natural Resources Washington Lidar Portal. NOAA OCM noted that there is water surface data that extends out into the water bordering along the topographic data. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal an script to assign the EPSG codes (Horizontal EPSG: 2926 and Vertical EPSG: 6360) to the GeoTiff formatted files. 2. Copied the files to https. dateTime: DateTime: 2022-03-07T00:00:00 processor: (CI_ResponsibleParty) organisationName: 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) originator | |