| 2012 OLC Bathymetric Lidar: Sandy River (OR) | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:55926 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: Office for Coastal Management Website description: Website listed for Office for Coastal Management function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2023-05-30T18:10:31 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(CORS96) 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/6783/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6783 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2012 OLC Bathymetric Lidar: Sandy River (OR) alternateTitle: 2012 OLC Bathy lidar sandy river m8694 date: (CI_Date) date: 2012 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2012 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 55926 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/55926 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/laz/geoid12b/8694/supplemental/Sandy_River_2012_Bathymetric_Survey_Delivery_LIDAR_QC_Report.pdf protocol: WWW:LINK-1.0-http--link name: QC report description: Online Resource 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/geoid12b/8694/supplemental/OLC_Sandy_River_Bathymetric_2012_Survey_Report.pdf protocol: WWW:LINK-1.0-http--link name: survey report description: Online Resource 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/geoid12b/8694/supplemental/Sandy_River_LiDAR_final.pdf protocol: WWW:LINK-1.0-http--link name: Technical Data Report description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Airborne topobathymetric lidar point cloud collected for the Sandy River, Oregon in 2012. The Sandy River flows through areas of steep terrain and dense tree canopy and is home to Chinook and Coho salmon and Steelhead trout. The Sandy River is further distinguished by the 2007 removal of the Marmot Dam (river mile 30) and has been the focus of ongoing monitoring to understand the impacts of dam removal on downstream morphology and fish habitat. The nature of the river makes it challenging for traditional transect or boat-based bathymetric surveys. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The data were collected to map channel and floodplain morphology and to evaluate the effectiveness of new topo-bathymetric LiDAR technology in a Pacific Northwest riverine environment. The project was conducted through the Oregon LiDAR Consortium (OLC) with contributions from DOGAMI, the Federal Emergency Management Agency (FEMA), and the Bureau of Land Management (BLM). credit: Oregon Lidar Consortium; Watershed Sciences, Inc; DOGAMI; FEMA; BLM 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 Aug 01, 2023 at https://coast.noaa.gov/dataviewer. 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: Office for Coastal Management Website description: Website listed for Office for Coastal Management function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8694/supplemental/2012_sandy_river_m8694.kmz fileDescription: graphic showing the extent of the data set. fileType: kmz 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) edition: 12.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA 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: 14.9 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 14.9 descriptiveKeywords: (MD_Keywords) keyword: Oregon type: (MD_KeywordTypeCode) theme 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: Cite As: OCM Partners, [Date of Access]: 2012 OLC Bathymetric Lidar: Sandy River (OR) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/55926. 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: 2012 OLC Bathymetric Lidar DEM: Sandy River (OR) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 56855 associationType: (DS_AssociationTypeCode) crossReference 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: 55926 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/55926.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) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -122.410523 eastBoundLongitude: -121.934087 southBoundLatitude: 45.336942 northBoundLatitude: 45.57894 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: Area includes the Sandy River and a buffer of land around it. temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-22 verticalElement: (EX_VerticalExtent) minimumValue: Real: 0 maximumValue: Real: 860 verticalCRS: NAD83(CORS96) return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Multiple formats version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAZ 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: Office for Coastal Management Website description: Website listed for Office for Coastal Management function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8694 protocol: WWW:LINK-1.0-http--link name: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8694 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8694/index.html protocol: WWW:LINK-1.0-http--link name: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8694/index.html description: Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. 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: Bare earth topography: 0.060 meters at 95% confidence High confidence bathymetry areas: 0.347 meters at 95% confidence Low confidence bathymetry areas: 0.779 meters at 95% confidence Low confidence areas have a low point density. See report for details. result: (missing) lineage: (LI_Lineage) statement: Lidar was flown from two instruments over the Sandy River in Oregon. Data were processed to point clouds and classified as ground or unclassified. 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 (Figure 2). 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: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: Lidar Survey: Two lidar instruments were flown. A Riegel VQ-820-Q for bathymetric collection and a Lieca ALS60 for topographic collection. The Riegl VQ-820-G uses a green-wavelength (μ = 532 nm) laser that, in addition to collecting vegetation and topography data, is able to penetrate the water surface with the 532-nm wavelength which provides for minimal spectral absorption. The sensor also collects both discrete returns (similar to the NIR data) and full-waveform data (every other pulse) for more rigorous feature extraction and evaluation of point returns. The recorded waveform enables range measurements for all discernible targets for a given pulse. The typical number of returns digitized from a single pulse ranged from 1 to 7 for the Sandy River project area. The Leica ALS60 uses a NIR wavelength (μ =1,064nm) laser that has been proven to provide high value terrestrial topography data. The NIR wavelengths do not penetrate the water column and thus provide water surface returns for received pulses off of water surface. The Leica system collects 8-bit intensity information and does not store waveform information. To accurately solve for laser point position (geographic coordinates x, y, and z), the positional coordinates of the airborne sensor and the attitude of the aircraft 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. 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. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: Lidar Processing: Prior to the mission, a boresight calibration flight was conducted in Corvallis, OR and processed by WSI to ensure accurate initial sensor alignment. An individual mission calibration was also performed on the Sandy River data set using Riegl’s RiProcess software. RiProcess was then used by WSI to further refine line-to-line calibration of the topo-bathymetric LiDAR dataset to match collected hard surface RTK control points. Upon completion of calibration, Dewberry processed the LiDAR returns with a combination of manual and automated techniques using both the Riegl software and in-house proprietary software to differentiate the bathymetric and terrestrial data. WSI processed NIR LiDAR and the orthorectified digital imagery, which were also used to facilitate the processing of the bathymetric returns. Once bathymetric points were differentiated, they were spatially corrected for refraction through the water column based on the angle of incidence of the laser. Dewberry refracted water column points and classified the resulting point cloud. The resulting data was sent back to WSI for further review and product creation. Figure 4 shows the various datasets used in the bathymetric analysis while Table 7 summarizes the steps used to process the bathymetric LiDAR data. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: Point Classification: As with standard NIR LiDAR data, bathymetric (green) LiDAR returns are classified into categories according to whether the points are considered above ground, ground, or water. Additional LiDAR classifications were created for bathymetric processing by adding categories for channel bottom, water surface, and water column points. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: Full Waveform Processing: Initial echo analysis is accomplished with Riegl’s online waveform processing. In online waveform processing, discrete returns are digitized from the echo signal based on the amplitude and pulse deviation of returning energy. To facilitate discrimination of ground points versus water column points and bathymetry points, the Riegl VQ-820-G uses the online waveform processing system that generates a discrete point cloud dataset at time of capture (“online”) from the full waveform signal. The system also records geo-referenced waveforms for a subsample of the data (configured for every other pulse). The waveforms are used in determining accurate bathymetry in shallow submerged environments. The separation of the water surface and bottom return in shallow depths requires further analysis and customized methods to ‘decompose’ or ‘deconvolve’ the waveform. Furthermore, certain parameters such as attenuation coefficients need to be set when processing data in various depth ranges and water column parameters. Information derived from the waveforms is used to set these parameters. The determination of the bottom return also needs to be corrected for the change in speed of light through the water column and the refraction of light at the air/water interface. The processed waveforms are used to validate the online digitization of the initial point cloud data. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management received the lidar data from the Oregon Lidar Consortium. There were two sets of point clouds. One set contained only the points within the river boundaries, but included points classified as water surface and water column. The other set contained points from the full survey area, but only contained points classified as ground or unclassified. The second set of data was ingested into the Digital Coast Data Access Viewer. Data were received in NAD83(CORS96) UTM zone 10 meters with vertical coordinates in NAVD88(GEOID09) meters. They were converted to geographic coordinates and ellipsoid heights for ingestion. Metadata was not delivered with the data. This metadata was created from the WSI report. dateTime: DateTime: 2019-03-22T00: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: Watershed Sciences Inc role: (CI_RoleCode) originator processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-08-01T06:39:10 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |