| 2009 Oregon Parks and Recreation Department Lidar: Columbia River | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49910 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset 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-08-09T17:11:37 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(NSRS2007) 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/4759/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4759 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 identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2009 Oregon Parks and Recreation Department Lidar: Columbia River alternateTitle: or2009_opr_columbia_river_m1079_metadata date: (CI_Date) date: 2011-11 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49910 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49910 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 protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource 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: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) abstract: The data set represents the lidar elevations along the Columbia River corridor in Oregon, including portions of the following counties: Gilliam, Hood River, Multnomah, Sherman, Umatilla, Wasco. The area includes portions of the Columbia River Gorge, as well as three smaller areas east of Hood River, OR. This data set covers 27,577 acres and was collected between December 7, 2009 and February 22, 2010. This data is part of a larger LiDAR survey effort by the US Army Corps of Engineers along the entire Columbia River. The lidar data are multiple return and are classified as unclassified and bare earth. The LiDAR survey used Leica ALS50 Phase II and ALS60 laser systems. The sensor scan angle was +/- 14 degrees from nadir with a pulse rate designed to yield an average native density (number of pulses emitted by the laser system) of > or = 8 points per square meter over terrestrial surfaces. In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. Elevation values for open water surfaces are not valid elevation values because few LiDAR points are returned from water surfaces. Watershed Sciences, Inc. collected the LiDAR and created this data set for Oregon Parks and Recreation Department. Original contact information: Contact Name: Brady Callahan Contact Org: Oregon Parks and Recreation Phone: 503-986-0783 Email: brady.callahan@state.or.us This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: Provide high resolution elevation data. credit: Oregon Parks and Recreation Department 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 Jul 01, 2023 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: Bare earth keyword: Bare ground keyword: High-resolution keyword: Light Detection and Ranging keyword: Oregon Parks and Recreation Department 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]: 2009 Oregon Parks and Recreation Department Lidar: Columbia River [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49910. 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 the Oregon Parks and Recreation Department, 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: 49910 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49910.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.336769 eastBoundLongitude: -119.134347 southBoundLatitude: 45.516912 northBoundLatitude: 45.919502 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2009-12-07 endPosition: 2010-02-22 supplementalInformation: The Lidar Report for this data set may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1079/supplemental/OPRD_ColumbiaRiver_LiDAR_Report.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1079/supplemental/2009_Oregon_Parks_and_Rec_Columbia_River.kmz return to top distributionInfo: (MD_Distribution) 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=1079 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. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1079/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. 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: Not provided result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The Root Mean Square Error (RMSE) of the data set is 0.14 feet (4.2 cm). Accuracy was assessed using 4293 ground survey RTK (real time kinematic) points. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Flightlines and LiDAR data were reviewed to ensure complete coverage of the survey area and positional accuracy of the laser points. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Not provided result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Acquisition This LiDAR survey used Leica ALS50 Phase II and ALS60 laser systems. The sensor scan angle was +/- 14 degrees from nadir with a pulse rate designed to yield an average native density (number of pulses emitted by the laser system) of greater than or equal to 8 points per square meter over terrestrial surfaces. It is not uncommon for some types of surfaces (e.g. water) to return fewer pulses than the laser originally emitted. These discrepancies between 'native' and 'delivered' density will vary depending on the terrain, land cover, and the prevalence of water bodies. All areas were surveyed with an opposing flight line side-lap of greater than or equal to 60% (greater than or equal to 100% overlap) to reduce laser shadowing and increase surface laser painting. The Leica laser systems allow up to four range measurements (returns) per pulse, and all discernible laser returns were processed for the output data set. To accurately solve for laser point position (geographic coordinates x,y,z) the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Aircraft position was measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll, and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft/sensor position and attitude data were indexed to GPS time. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: Processing 1. Laser point coordinates were computed using the IPAS and ALS Post Processor software suites based on independent data from the LiDAR system (pulse time, scan angle), and aircraft trajectory data (SBET). Laser point returns (first through fourth) were assigned an associated (x,y,z) coordinate along with unique intensity values (0-255). The data were output into large LAS v1.2 files; each point maintains the corresponding scan angle, return number (echo), intensity, and x,y,z (easting, northing, and elevation) information. 2. These initial laser point files were too large for subsequent processing. To facilitate laser point processing, bins (polygons) were created to divide the data set into manageable sizes (< 500 MB). Flightlines and LiDAR data were then reviewed to ensure complete coverage of the survey area and positional accuracy of the laser points. 3. Laser point data were imported into processing bins in TerraScan and manual calibration was performed to assess the system offsets for pitch, roll, heading, and scale (mirror flex). Using a geometric relationship developed by Watershed Sciences, each of these offsets were resolved and corrected if necessary. 4. LiDAR points were then filtered for noise, pits (artificial low points) and birds (true birds, as well as erroneously high points) by screening for absolute elevation limits, isolated points, and height above ground. Each bin was then manually inspected for remaining pits and birds and spurious points were removed. In a bin containing approximately 7.5 - 9.0 million points, an average of 50 - 100 points are typically found to be artificially low or high. Common sources of non-terrestrial returns are clouds, birds, vapor, haze, decks, brush piles, etc. 5. Internal calibration was refined using TerraMatch. Points from overlapping lines were tested for internal consistency and final adjustments were made for system misalignments (i.e., pitch, roll, heading offsets and scale). Automated sensor attitude and scale corrections yielded 3 - 5 cm improvements in the relative accuracy. Once system misalignments were corrected, vertical GPS drift was then resolved and removed per flight line, yielding a slight improvement (< 1 cm) in relative accuracy. 6. The TerraScan software suite is designed specifically for classifying near ground points (Soininen, 2004). The processing sequence began by removing all points that were not near the earth based on geometric constraints used to evaluate multi-return points. The resulting bare earth (ground) model was visually inspected and additional ground point modeling was performed in site-specific areas to improve ground detail. This manual editing of ground often occurs in areas with known ground modeling deficiencies such as: bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation. In some cases, automated ground point classification erroneously included known vegetation (i.e., understory, low/dense shrubs, etc.). These points were manually reclassified as non-grounds. Ground surface rasters were developed from triangulated irregular networks (TINs) of ground points. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained lidar elevation and intensity measurements. The data was in Lambert Conformal Conic projection and NAVD88 Geoid 09 vertical datum. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from Lambert Conformal Conic coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in international feet to GRS80 (ellipsoid) heights in meters using Geoid 09. 3. The data were filtered to remove outliers. 4. The LAS data were sorted by latitude and the headers were updated. dateTime: DateTime: 2011-10-01T00:00:00 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-07-01T05:38:30 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |