| 2018 OLC Lidar DEM: Harney County, OR | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:59006 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: 2020-03-09T12:28:15 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: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2018 OLC Lidar DEM: Harney County, OR date: (CI_Date) date: 2018-11-29 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 59006 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9044/supplemental/OLC_BAKER_COUNTY_3DEP_2017_REPORT.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to 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/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: This metadata record is for the Oregon Lidar Consortium (OLC) Harney 2018 area of interest (AOI) bare-earth, hydro-flattened DEM, which was produced in collaboration with the USGS 3DEP program. The defined project area (DPA) encompasses 128,891 acres, and the buffered project area (BPA) encompasses 133,051 acres. All data are in Harney County, Oregon. The nominal pulse density for the source lidar is eight pulses per square meter. The bare earth (BE) digital elevation model (DEM) raster grid cell size is 1 meter The native projection is Universal Transverse Mercator (UTM) Zone 11N, 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 dataset in partnership with the Oregon Department of Geology and Mineral Industries (DoGAMI). purpose: This dataset 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: OLC / DOGAMI, Quantum Spatial, Inc., USGS 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 resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9044/supplemental/extent_2018_OLC_Harney_m9044.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 > Oceans > Bathymetry/Seafloor Topography > Bathymetry > Coastal Bathymetry keyword: Earth Science > Oceans > Coastal Processes > Coastal 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: 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 keyword: Vertical Location > Land Surface keyword: Vertical Location > Seafloor type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America > Oregon keyword: Continent > North America > United States Of America > Oregon > Harney County 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: Users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, surveying, or site specific purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information. Acknowledgement of Oregon Department of Geology and Industries (DoGAMI) would be appreciated for products derived from these data. 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: 59006 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://inport.nmfs.noaa.gov/inport-metadata/NOAA/NOS/OCMP/dmp/pdf/59006.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 spatialResolution: (MD_Resolution) distance: Distance: 1 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation 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: -119.321982 eastBoundLongitude: -118.810761 southBoundLatitude: 43.520614 northBoundLatitude: 43.754523 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2018-08-03 endPosition: 2018-08-04 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 (.tif) 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=9048 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. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/raster2/elevation/OLC_harney_DEM_2018_9048 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 46 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 46 checkpoints located in bare earth and urban (non-vegetated) areas; the 2. Vegetated Vertical Accuracy (VVA): VVA is be reported for "forested", "brushland/trees", and "tall weeds/crops" 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 10 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.Quantitative value: 0.063 0.070 0.092, Test that produced the value: Tested 0.063 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 46 independent checkpoints located in Bare Earth and Urban land cover classes. (RMSE = 3.2 cm). Tested 0.070 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 46 independent checkpoints located in the Bare Earth and Urban land cover categories. Tested 0.092 meters VVA was calculated using 10 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 August 3 and 4, 2018. The survey utilized the Optech Galaxy Prime laser systems mounted in a Cessna Caravan 208B. 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: 2028-08-06T00: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-08-06T00:00:00 processStep: (LI_ProcessStep) description: Hydro-Flattened Raster DEM Processing: Class 2 (Ground) LiDAR points in conjunction with the hydro-breaklines were used to create a 1-meter hydro-flattened 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-08-06T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received 1,098 IMG files from the Oregon Lidar Consortium/ DOGAMI. The data were in UTM Zone 11N (NAD83 2011) coordinates in meters and NAVD88 (Geoid12b) elevations in meters, at 1-m spatial resolution. OCM converted the files from .IMG format to Geotiff format using gdal_warp. The files were then assigned the EPSG codes of 6340 (horizontal) and 5703 (vertical) and then copied to https for Digital Coast storage and provisioning purposes.ordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor 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: 2018-11-29 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial, Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-08-06 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: 2018-11-29 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial, Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2018-08-03 endPosition: 2018-08-04 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 reprot PDF for this project area. date: (CI_Date) date: 2018-11-29 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: Quantum Spatial description: Quantum Spatial's Website function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-08-06 | |