2018 OLC Lidar DEM: Morrow County, OR | referenceSystemInfo|
---|---|
(MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:58240 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2019-11-21T10:41:44 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::5703 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::6339 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::6340 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2018 OLC Lidar DEM: Morrow County, OR alternateTitle: or2018_morrow_dem_m8933_metadata date: (CI_Date) date: 2019-04-05 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 58240 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: NOAA's Office for Coastal Management (OCM) website description: Information on the NOAA Office for Coastal Management (OCM) function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8932 protocol: WWW:LINK-1.0-http--link name: Citation URL 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/htdata/lidar3_z/geoid12b/data/8932/supplemental/OLC_Morrow_County_3DEP_Data_Report_2018.pdf protocol: WWW:LINK-1.0-http--link name: Data set report description: Link to the data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid12b/data/8932/breaklines/ protocol: WWW:LINK-1.0-http--link name: Citation URL description: Link to the hydro breaklines. 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 for this data set. This record was created by the NOAA Office for Coastal Management (OCM) using information from the 3DEP Hydroflattened DEM metadata and making a minor adjustment to Process Step 3. This GIS dataset contains Bare Earth (BE) raster grids depicting lidar-derived elevation data for Oregon Lidar Consortium (OLC) Morrow County project area. The BE raster dataset encompasses 801,116 acres within Morrow County County in Oregon. The nominal pulse density is eight pulses per square meter. The bare earth (BE) digital elevation model (DEM) raster grid cell size is 1 meter. The native projection was UTM Zones 10 and 11, units are in meters. The native horizontal datum is NAD83(2011) and the native vertical datum is NAVD88 (Geoid 12B). Quantum Spatial Inc. collected the lidar and created this data set in partnership with the Oregon Department of Geology and Mineral Industries (DOGAMI). In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, and the hydro breaklines are also available. These data are available for download at the link provided in the URL section of this metadata record. purpose: This data set provides high resolution elevation data that is used to produce three-dimensional models of the earth surface for the purpose of managing natural resources and mapping natural hazards. credit: Quantum Spatial, Inc. 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: 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian graphicOverview: (MD_BrowseGraphic) fileName: https://coast.noaa.gov/htdata/lidar3_z/geoid12b/data/8932/supplemental/or2018_morrow_m8932.kmz fileDescription: This graphic displays the footprint for this lidar data set. descriptiveKeywords: (MD_Keywords) keyword: Earth Science > Land Surface > Topography > Terrain Elevation keyword: elevation type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: bare earth keyword: digital elevation model (DEM) keyword: hillshade keyword: lidar keyword: quadrangle keyword: topography type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Oregon Geospatial Enterprise Office Metadata Keyword Thesaurus date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America > Oregon 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: Gilliam County keyword: Grant County keyword: Morrow County keyword: North America keyword: Oregon keyword: Sherman County keyword: Umatilla County keyword: USA type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Oregon Geospatial Enterprise Office Metadata Keyword Thesaurus 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. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Quantum Spatial, Inc, the Oregon Lidar Consortium (OLC), DOGAMI, NOAA, the Office for Coastal Management or its partners. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) language: eng; US topicCategory: (MD_TopicCategoryCode) elevation topicCategory: (MD_TopicCategoryCode) geoscientificInformation environmentDescription: LiDAR Mapping Suite 2.4, Applanix PosPac 7.1, Microstation Version 8.0, TerraScan Version 16, TerraModeler Version 16, TerraMatch Version 16, ESRI ArcGIS 10.3.1, Windows 7 Operating System extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -120.569414 eastBoundLongitude: -119.048421 southBoundLatitude: 44.546486 northBoundLatitude: 45.923056 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2018-10-03 endPosition: 2018-11-15 supplementalInformation: CONTRACTOR: Quantum Spatial, Inc. All ground survey data, Lidar data acquisition, calibration, and follow-on processing were completed by the prime contractor, Quantum Spatial, Inc. 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: 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=8933 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, map projection, file format, 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/raster2/elevation/OLC_Morrow_DEM_2018_8933 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in the original coordinate system. 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: The project specifications require that only Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA (i.e., based on RMSE of 10 cm in the "bare earth" and "urban" land cover classes). The Raw Swath NVA was tested with 66 checkpoints located in bare earth and urban (non-vegetated) areas. These checkpoints were not used in the calibration or post processing of the lidar point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. The project specifications require the accuracy (ACCz) of the derived DEM be calculated and reported in two ways: 1. The required NVA is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the "bare earth" and "urban" land cover classes. This is a required accuracy. The Bare Earth DEM NVA was tested with 63 checkpoints located in bare earth and urban (non-vegetated) areas; the 2. Vegetated Vertical Accuracy (VVA): VVA is reported for "forested", "shrub", and "tall grass" land cover classes. The target VVA is: 29.4 cm at the 95th percentile, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for Lidar Data, i.e., based on the 95th percentile error in all vegetated land cover classes combined. This is a target accuracy. The VVA was tested with 63 checkpoints located in vegetated areas. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. Tested 0.076 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the raw lidar point cloud swath files was calculated against TINs derived from the final calibrated and controlled swath data using 66 independent checkpoints located in Bare Earth and Urban land cover classes. Tested 0.081 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the DEM was calculated using 66 independent checkpoints located in the Bare Earth and Urban land cover categories. Tested 0.152 meters VVA was calculated using 63 checkpoints located in vegetated land cover categories at the 95th percentile, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for Lidar Data. Tested against the DEM. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data covers the entire area specified for this project. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Lidar data acquisition occured between October 3, 2018, and November 15, 2018. The survey utilized the Riegl 1560i laser systems mounted in a Piper Navajo. Near nadir scan angles were used to increase penetration of vegetation to ground surfaces. Ground level GPS and aircraft IMU were collected during the flight. Processing.1. Airborne GPS and IMU data were merged to develop a Single Best Estimate (SBET) of the lidar system trajectory for each flight line. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Laser point return coordinates were computed using ALS Post Processor software and IPAS Pro GPS/INS software, based on independent data from the LiDAR system, IMU, and aircraft. 3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate. 4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment. 5. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency. 6. Noise (e.g., pits and birds) was filtered using ALS postprocessing software, based on known elevation ranges and included the removal of any cycle slips. 7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area. 8. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical and horizontal accuracies. 9. Points were output as laser points, TINed and GRIDed surfaces. dateTime: DateTime: 2018-11-16T00:00:00 processStep: (LI_ProcessStep) description: Lidar Post-Processing: The calibrated and controlled lidar swaths were processed using automatic point classification routines in proprietary software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Data were then distributed as virtual tiles to experienced lidar analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags were stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project were calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified lidar swath files were delivered to the client. dateTime: DateTime: 2018-11-16T00:00:00 processStep: (LI_ProcessStep) description: Raster DEM Processing: Class 2 (Ground) LiDAR points were used to create a 1-meter raster DEM. Using automated scripting routines within ArcMap, an ESRI GRID file was created for each tile. Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface. dateTime: DateTime: 2018-11-16T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received 71 raster DEM files (UTM10 - 10 files, UTM11 - 61 files) in ESRI ArcGrid format from DOGAMI. The data were in UTM Zones 10 and 11, NAD83(2011), meters coordinates and NAVD88 (Geoid12b) elevations in meters. The bare earth raster files were at a 1 m grid spacing. No metadata record was provided for this data set. This record was created by the NOAA Office for Coastal Management (OCM) using information from the 3DEP Hydroflattened DEM metadata and making a minor adjustment (removal of use of hydro breaklines to hydroflatten) to Process Step 3. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal script to assign the EPSG codes (horizontal - 6339 for UTM10 files and 6340 for UTM11 files, vertical - 5703) and convert to GeoTiff format. 2. Copied to the files to https. dateTime: DateTime: 2019-11-15T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: This data was used, along with GPS/IMU data, to georeference LIDAR point cloud data. sourceCitation: (CI_Citation) title: See the survey report PDF for this project area. date: (CI_Date) date: 2019-04-05 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial, Inc. contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://quantumspatial.com/ protocol: WWW:LINK-1.0-http--link name: Source Citation URL description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-11-16 source: (LI_Source) description: Source Contribution: These data was used to classify LiDAR point cloud data. scaleDenominator: (MD_RepresentativeFraction) denominator: 50 sourceCitation: (CI_Citation) title: See the survey report PDF for this project area. date: (CI_Date) date: 2019-04-05 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial, Inc. role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-11-16 source: (LI_Source) description: Source Contribution: These data were used to assess the vertical accuracy of the LiDAR point cloud data. sourceCitation: (CI_Citation) title: See the survey report PDF for this project area. date: (CI_Date) date: 2019-04-05 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial, Inc. role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2018-10-03 endPosition: 2018-11-15 |