| 2015 OLC Topobathy Lidar DEM (Interpolated): Middle Fork Willamette River, OR | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:62797 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: Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 2234 South Hobson Avenue city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://www.coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: Website description: Website listed for this contact function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2020-08-17T17:48:47 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::6318 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2015 OLC Topobathy Lidar DEM (Interpolated): Middle Fork Willamette River, OR date: (CI_Date) date: 2015 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2015 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 62797 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar4_z/geoid18/data/9168/supplemental/2015_Middle_Fork_Willamette_Topobathymetric_Data_Report.pdf protocol: WWW:LINK-1.0-http--link name: Data set report description: Report by WSI that formed the basis for this metadata. Contains additional information. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Airborne topobathymetric lidar-derived digital elevation model (DEM) with interpolated data in areas where no bathymetric points could be obtained, collected for the Middle Fork of Willamette River, Oregon in 2015. In September 2015, Quantum Spatial (QSI) was contracted by the Oregon LiDAR Consortium (OLC) to collect topobathymetric Light Detection and Ranging (LiDAR) data in the fall of 2015 for the Middle Fork Willamette River site in Oregon. The Middle Fork Willamette River area of interest stretches between Eugene/Springfield and Dexter Dam and Fall Creek below Fall Creek Dam. Traditional near-infrared (NIR) LiDAR was fully integrated with green wavelength return data (bathymetric) LiDAR in order to provide seamless and complete project mapping. purpose: Data were collected to aid OLC in providing a complete topobathymetric dataset to be used in analyses of the long term impacts associated with sediment deposition on downstream habitat and channel morphology. credit: Oregon Lidar Consortium; Quantum Spatial, Inc; DOGAMI status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 2234 South Hobson Avenue city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://www.coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: Website description: Website listed for this contact function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://coast.noaa.gov/htdata/lidar4_z/geoid18/data/9168/supplemental/extent_MiddleFork_Willamette_m9168.kmz fileDescription: graphic showing the extent of the data set. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America > Oregon type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Science > Land Surface > Topography > Terrain Elevation keyword: Earth Science > Oceans > Bathymetry/Seafloor Topography > Seafloor Topography type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America keyword: Continent > North America > United States Of America > Oregon > Eugene keyword: Continent > North America > United States Of America > Oregon > Springfield keyword: Vertical Location > Land Surface type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Remote Sensing Instruments > Active Remote Sensing > Profilers/Sounders > Lidar/Laser Sounders > LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aircraft > Aircraft type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: DEMs - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) 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. 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: 62797 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/62797.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 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -123.0368 eastBoundLongitude: -122.74759 southBoundLatitude: 43.9083 northBoundLatitude: 44.050142 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: Area includes the Middle Fork, Wilamette River and a buffer of land around it. temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: Collection dates of lidar | Currentness: Ground Condition beginPosition: 2015-09-14 endPosition: 2015-09-15 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Multiple formats version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: GeoTIFF version: (missing) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 2234 South Hobson Avenue city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://www.coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: Website description: Website listed for this contact function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9170 protocol: WWW:LINK-1.0-http--link name: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9170 description: Application to 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. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/raster5/elevation/OLC_willamette_river_topobathy_interp_2015_9170 protocol: WWW:LINK-1.0-http--link name: https://coast.noaa.gov/htdata/raster5/elevation/OLC_willamette_river_topobathy_interp_2015_9170 description: Bulk download of data files in original projection. 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: Absolute accuracy was assessed using Fundamental Vertical Accuracy (FVA) reporting designed to meet guidelines presented in the FGDC National Standard for Spatial Data Accuracy3. FVA compares known ground check point data collected on open, bare earth surfaces with level slope (<20°) to the triangulated surface generated by the LiDAR points. FVA 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 ground check 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 Middle Fork Willamette River survey, 30 ground check points were withheld in total resulting in a fundamental vertical accuracy of 0.060 meters at the 95% confidence interval (1.96 * RMSE). Additionally, 45 bathymetric (submerged or along the water’s edge) check points were also collected in order to assess the submerged surface vertical accuracy, resulting in an average absolute accuracy of 0.012 meters at the 95% confidence interval (1.96 * RMSE). QSI also assessed absolute accuracy using 555 ground control points. Although these points were used in the calibration and post-processing of the LiDAR point cloud, they may still provide a good indication of the overall accuracy of the LiDAR dataset, and therefore have been provided - please see the dataset report for more details. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The specified depth penetration range of the Riegl VQ-820-G sensor is one secchi depth; therefore, bathymetry data below one secchi depth at the time of acquisition is not to be expected. To assist in evaluating performance results of the sensor, a polygon layer was created to delineate areas where bathymetry was successfully mapped. This shapefile was used to control the extent of the delivered clipped topo-bathymetric model and to avoid false triangulation across areas in the water with no returns. Insufficiently mapped areas were identified by triangulating bathymetric bottom points with an edge length maximum of 4.56 meters. This ensured all areas of no returns (> 9 m2), were identified as data voids. Of the areas successfully mapped, 46.50% had a calculated depth of 0 – 0.5m, 38.00% had a calculated depth of 0.51 -1.0 m, 13.89% had a calculated depth of 1.01 – 1.5m, and the remaining 1.61% had a calculated depth between 1.51m and 6.5m (Table 9, project report). For this DEM, areas that did not have bathymetric bottom point data were interpolated to create a continuous surface, rather than one with voids in areas of no data. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Planning: The airborne survey was designed to collect a point density of 4-5 pulses/m2 for the topo-bathymetric LiDAR. The flight was planned with a scan angle of ±20o and 50% side-lap. The 50% side-lap was used to ensure uniform coverage and to minimize laser shadowing due to vegetation and terrain. The flights were conducted in the late fall during base flow conditions to maximize water clarity and ensure shallow depths. The flight lines were developed using ALTM-NAV Planner (v.3.0) software and Leica Mission Pro Flight Planning and Evaluation (FPES) software. Efforts were taken to optimize flight paths by minimizing flight times while meeting all accuracy specifications. The WSI acquisition staff considered all factors such as air space restrictions, private property access, and GPS quality in the planning of this mission. dateTime: DateTime: 2015-09-01T00:00:00 processStep: (LI_ProcessStep) description: Lidar Survey: The LiDAR survey was accomplished using a Leica ALS80 system dually mounted with a Riegl VQ-820-G topobathymetric sensor in a Cessna Caravan. The Riegl VQ-820-G uses a green wavelength (ʎ=532 nm) laser that is capable of collecting high resolution vegetation and topography data, as well as penetrating the water surface with minimal spectral absorption by water. The recorded waveform enables range measurements for all discernible targets for a given pulse. The Leica ALS80 laser system can record unlimited range measurements (returns) per pulse. 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. Table 3 (dataset report) summarizes the settings used to yield an average pulse densityof ≥4.0 points/m2 for green LiDAR returns, and ≥8.0 points/m2 for NIR LiDAR returns over the Middle Fork Willamette River project area. dateTime: DateTime: 2015-09-01T00:00:00 processStep: (LI_ProcessStep) description: Lidar Processing: Upon completion of data acquisition, QSI 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 (Table 7). Riegl’s RiProcess software was used to facilitate bathymetric return processing. Once bathymetric points were differentiated, they were spatially corrected for refraction through the water column based on the angle of incidence of the laser. QSI refracted water column points using QSI’s proprietary LAS processing software, LAS Monkey. The resulting point cloud data were classified using both manual and automated techniques. Processing methodologies were tailored for the landscape. dateTime: DateTime: 2015-09-30T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management received the lidar DEM data from the Oregon Lidar Consortium. Data were received in NAD83(2011) UTM zone 10 meters with vertical coordinates in NAVD88(GEOID 12A) meters. They were converted to geoTiff format with georeferencing added for ingest into the Data Access Viewer. Metadata was not delivered with the data. This metadata was created from the WSI report. dateTime: DateTime: 2020-08-14T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: lidar data date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial, Inc. role: (CI_RoleCode) originator | |