| 2022 - 2023 DOGAMI/OLC Lidar: Jackson County, OR | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:79352 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: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2026-03-04T14:25: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 referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) / UTM zone 10N 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/6339/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6339 version: 6.18.3 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2022 - 2023 DOGAMI/OLC Lidar: Jackson County, OR alternateTitle: or2022_jackson_m14002_metadata date: (CI_Date) date: 2022 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2026 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 79352 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/79352 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/entwine/geoid18/14002/ept.json protocol: WWW:LINK-1.0-http--link name: Entwine Point Tile (EPT) description: Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. 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/geoid18/14002/supplemental/XXX.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the NV5 lidar report. 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/geoid18/14002/breaklines/index.html protocol: WWW:LINK-1.0-http--link name: Breaklines description: Link to the breaklines in Esri gdb and OGC GeoPackage formats. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/14002/ept.json protocol: WWW:LINK-1.0-http--link name: Potree 3D View description: Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. 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: Original Product: These lidar data are processed Classified LAS 1.4 files, formatted to 3000 ft x 3000 ft tiles; used to create intensity images, Bare Earth DEMs, and Highest Hit DSMs. Original Geographic Extent: Jackson County, Oregon, covering approximately 506,952 acres. Original Dataset Description: The OLC Jackson County 2023 Lidar project called for the planning, acquisition, processing and production of derivative products of the lidar data and was to be collected at a nominal pulse spacing (NPS) of 8 ppsm - 0.350 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Lidar Base Specification, Version 2022 rev. A. The native projection is Oregon Lambert Conic Conformal, units are in International feet. The native horizontal datum is NAD83(2011); the native vertical datum is NAVD88; (Geoid 18). Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 3000 ft x 3000 ft tiles, intensity images, bare earth DEMs, and highest hit DSMs; all tiled to the same 3000 ft x 3000 ft schema and mosaicked. Ground Conditions: Lidar was collected between November 14th, 2002 - November 22nd, 2002 and June 28th, 2023 - June 30th, 2023 while no snow was on the ground and the area was free of cloud cover. This data was provided to the NOAA Office for Coastal Management (OCM) by DOGAMI (Oregon Department of Geology and Mineral Industries), for the purpose of making the data publicly available for custom and bulk downloads from the NOAA Digital Coast Data Access Viewer. This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. 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: DOGAMI, NV5 Geospatial 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 2026-03-04 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: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 17.0 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA 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) edition: 20.8 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: 17.2 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 17.2 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: This data set was compiled dynamically. It will be removed 10 days after 2026-03-04 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2022 - 2023 DOGAMI/OLC Lidar: Jackson County, OR [Data Date Range], https://www.fisheries.noaa.gov/inport/item/79352. 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) useConstraints: (MD_RestrictionCode) license otherConstraints: Anchor: Universal (CC0 1.0) Public Domain Dedication To the extent possible under law, the U.S. Government has waived all copyright and related or neighboring rights to this dataset. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-03-04 from the NOAA system. Access Constraints: None resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-03-04 from the NOAA system. 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_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-03-04 from the NOAA system. 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. Acknowledgment 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: 2022 - 2023 DOGAMI/OLC Lidar DEM: Jackson County, OR date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 79359 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: 79352 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/79352.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: .25 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation topicCategory: (MD_TopicCategoryCode) geoscientificInformation environmentDescription: Bayes StripAlign v2.2, Applanix PosPac 8.7, Microstation Connect, TerraScan Version 19, TerraModeler Version 19, TerraMatch Version 19, ESRI ArcGIS 10.8.1, LAS Product Creator (NV5 Proprietary), LasMonkey (NV5 Proprietary), Windows 10 Operating System extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -123.254362 eastBoundLongitude: -122.403838 southBoundLatitude: 42.029055 northBoundLatitude: 42.803112 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2022-11-14 endPosition: 2023-06-30 supplementalInformation: CONTRACTOR: NV5 Geospatial All ground survey data, Lidar data acquisition, calibration, and follow-on processing were completed by the prime contractor, NV5 Geospatial. Ground points within hydro-flattening water's edge breaklines were re-classifed as water by DOGAMI The following are the USGS lidar fields in JSON: { "ldrinfo " :{ "ldrspec " :" U.S. Geological Survey National Geospatial Program Lidar Base Specification, Version 2022 rev. A ", "ldrsens " :" Riegl 1560iiS ", "ldrmaxnr " :" 15 ", "ldrnps " :" 0.35 ", "ldrdens " :" 8 ", "ldranps " :" 0.25 ", "ldradens " :" 15.92 ", "ldrfltht " :" 2,500 ", "ldrfltsp " :" 160 ", "ldrscana " :" 58.5 ", "ldrscanr " :" Uniform Point Spacing ", "ldrpulsr " :" 827 ", "ldrpulsd " :" 3 ", "ldrpulsw " :" 57.5 ", "ldrwavel " :" 1064 ", "ldrmpia " :" 1 ", "ldrbmdiv " :" 0.23 ", "ldrswatw " :" 2,800 ", "ldrswato " :" 55 ", "ldrgeoid " :" Geoid 18 " }, "ldraccur " :{ "ldrchacc " :" 0.273 ", "rawnva " :" 0.045 ", "rawnvan " :" 54 " }, "lasinfo " :{ "lasver " :" 1.4 ", "lasprf " :" 7 ", "laswheld " :" Withheld (ignore) points are identified in these files using the standard LAS Withheld bit. ", "lasolap " :" Not applicable ", "lasintr " :" 16 ", "lasclass " :{ "clascode " :" 1 ", "clasitem " :" Processed, but Unclassified " }, "lasclass " :{ "clascode " :" 2 ", "clasitem " :" Bare-Earth Ground " }, "lasclass " :{ "clascode " :" 7 ", "clasitem " :" Low Noise " }, "lasclass " :{ "clascode " :" 9 ", "clasitem " :" Water " }, "lasclass " :{ "clascode " :" 17 ", "clasitem " :" Bridge Decks " }, "lasclass " :{ "clascode " :" 18 ", "clasitem " :" High Noise " } } } return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: (inapplicable) version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: LAZ 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=14002 /details/14002 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. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14002/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download 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. They will be in an orthometric datum. 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: Lidar horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, flying altitude, and INS derived attitude error. The obtained RMSEr value is multiplied by a conversion factor of 1.7308 to yield the horizontal component of the National Standards for Spatial Data Accuracy (NSSDA) reporting standard where a theoretical point will fall within the obtained radius 95 percent of the time. Based on a flying altitude of 2500 meters, an IMU error of 0.002 decimal degrees, and a GNSS positional error of 0.023 meters, this project was produced to meet 0.896 feet (0.273 meters) horizontal accuracy at the 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. The specifications require that classified Non-vegetated Vertical Accuracy (NVA) be computed from the derived DEMs. The NVA was tested with 54 independent check points located in open terrain and distributed throughout the project as feasible. These check points were not used in the calibration or post processing of the lidar point cloud data. Specifications for this project require that the NVA be 0.196 meters or better AccuracyZ at 95% confidence level. Vegetated Vertical Accuracy (VVA) is also to be computed from the derived DEMS. The VVA was tested with 46 check points in Tall Grass, Forest, and Shrub land cover types. These check points were also withheld from the calibration and post processing of the lidar point cloud data and distributed throughout the project area as feasible. Specifications for this project require that the VVA be 0.300 meters or better AccuracyZ at the 95th percentile. The 54 independent NVA check points were surveyed using the closed level loop technique. Elevations of the derived bare earth DEMs were compared to the elevation values of the surveyed NVA check points. The RMSE was computed to be 0.075 feet (0.023 meters) resulting in an AccuracyZ of 0.146 feet (0.045 meters) at the 95% confidence level. NVA AccuracyZ has been tested and meets the required 0.196 meter NVA at 95% confidence level using (RMSEz * 1.9600) for the derived bare earth DEMs as defined by the National Standards for Spatial Data Accuracy (NSSDA) and herein reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. The 46 independent VVA check points were surveyed using the closed level loop technique. Elevations of the derived bare earth DEMs were compared to the elevation values of the surveyed VVA check points. The RMSE was computed to be 0.320 feet (0.098 meters) resulting in an AccuracyZ of 0.531 feet (0.162 meters) at the 95% confidence level. VVA AccuracyZ has been tested and meets the required 0.300 meter NVA at 95% confidence level using (RMSEz * 1.9600) for the derived bare earth DEMs as defined by the National Standards for Spatial Data Accuracy (NSSDA) and herein reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Classified LAS files were tested by NV5 Geospatial for vertical accuracy. All data is seamless from one tile to the next, no gaps or no data areas. result: (missing) lineage: (LI_Lineage) statement: This data was provided to the NOAA Office for Coastal Management (OCM) by the DOGAMI (Oregon Department of Geology and Mineral Industries), for the purpose of making the data publicly available for custom and bulk downloads from the NOAA Digital Coast Data Access Viewer. processStep: (LI_ProcessStep) description: Lidar Pre-Processing: 1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las format. Convert data to orthometric elevations by applying a Geoid 18 correction. 5. Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 6. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 7. Adjust the point cloud by comparing ground classified points to supplemental ground control points. dateTime: DateTime: 2023-11-14T00:00:00 processStep: (LI_ProcessStep) description: Lidar Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. After completion of classification and final QC approval, calculate final NVA, VVA, and density information for the project using ground control quality check points. 4. Ground points within water's edge breaklines reclassified as Class 9 by DOGAMI dateTime: DateTime: 2023-11-17T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received 2457 laz files from DOGAMI. The files were in OR Statewide Lambert NAD83(2011) international feet coordinates and the elevations were in NAVD88 (GEOID18) international feet. The LAZ files had these classifications: 1 = unclassified; 2 = ground (or Bare Earth); 7 = low noise; 17 = bridges; 18=high noise. NOAA OCM processed all of the point classes to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the LAZ files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the GEOID18 model b. Convert from OR Statewide Lambert NAD83(2011) international feet coordinates to geographic coordinates c. Convert from elevations in feet to elevations in meters d. Assign the geokeys, to sort the data by gps time and zip the data to database and to AWS S3. dateTime: DateTime: 2026-02-27T00:00:00 processor: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: LAZ Files date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Oregon Dept. of Geology and Mineral Industries (DOGAMI) role: (CI_RoleCode) originator processStep: (LI_ProcessStep) description: The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. dateTime: DateTime: 2026-03-04 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |