| 2023-2024 NOAA NGS Topobathy Lidar: Ozarks area (Missouri, Arkansas and Oklahoma Rivers) | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:79259 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: National Geodetic Survey 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-04T19:17:27 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 14N 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/6343/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6343 version: 6.18.3 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2023-2024 NOAA NGS Topobathy Lidar: Ozarks area (Missouri, Arkansas and Oklahoma Rivers) date: (CI_Date) date: 2026 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: (missing) dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 79259 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/79259 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: National Geodetic Survey contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 1315 East-West Hwy city: Silver Spring administrativeArea: MD postalCode: 20910 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://geodesy.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: National Geodetic Survey Website description: Website listed for National Geodetic Survey function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) originator citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/13981/supplemental/MO2301_NOAA_Ozarks_Topobathy_Final_Report.pdf protocol: WWW:LINK-1.0-http--link name: Topobathy Lidar Data Report description: Topobathy Lidar Data Report function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: In July 2023, NV5 was contracted by the National Oceanic and Atmospheric Administration (NOAA) to collect topobathymetric Light Detection and Ranging (lidar) data from August 2023 to July 2024 for the NOAA Ozarks site. The NOAA Ozarks area of interest encompasses several river sections in Missouri, Arkansas, and Oklahoma. In total, the base project area of the NOAA Ozarks project encompasses approximately 745 square statute miles. The dataset includes topobathymetric data in a LAS format 1.4, point data record format 6, with the following classifications in accordance with project specifications and the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards: 1 - Unclassified 1 Withheld - Edge clip 1 Overlap Withheld - Unrefracted green data from Chiroptera sensor 2 - Ground 7 Withheld -Low noise 17 - Bridge Decks 18 Withheld - High noise 21 - Identifiable snow 22 - Temporal exclusion 40 - Bathymetric bottom or submerged topography 41 - Water surface 42 Synthetic- Chiroptera synthetic water surface 43 - Submerged feature 45 - Water column 64 - Submerged Aquatic Vegetation (SAV) 65 - overlap bathy bottom - temporally different from a separate lift The channel bits are mapped as the following: 0 - Chiroptera green shallow laser 1 - Chiroptera synthetic water surface 3 - Chiroptera NIR The user byte is mapped as the following: 10 - Chiroptera green shallow 11 - Chiroptera green shallow 4X 12 - Chiroptera green shallow synthetic 30 - Chiroptera NIR This dataset also includes lidar intensity values, number of returns, return number, time, and scan angle. The horizontal datum for the the provided LAS files is NAD83 (2011), projected in UTM 15. The vertical datum of the Ellipsoidal height LAS files is in GRS80 ellipsoid heights. 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 lidar data was required by National Oceanic and Atmospheric Administration (NOAA) and the National Geodetic Survey (NGS), Remote Sensing Division Coastal Mapping Program (CMP) to support national shoreline characterization along 29 river stretches in Missouri, Arkansas, and Oklahoma. Additionally, data will be utilized to enable accurate and consistent hydrologic flood and weather monitoring in support of the National Water Center's modeling efforts. credit: We request that you credit the National Oceanic and Atmospheric Administration (NOAA) when you use these data in a report, publication, or presentation. 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-05 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) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/13981/supplemental/extent_OzarksTopobathy_m13981.kmz fileDescription: This graphic shows the lidar footprint for this dataset. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > BIOSPHERE > ECOSYSTEMS > FRESHWATER ECOSYSTEMS > RIVERS/STREAM keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > TOPOGRAPHICAL RELIEF MAPS 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 > ARKANSAS keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MISSOURI keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > OKLAHOMA 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: DOC/NOAA/NOS/NGS > National Geodetic Survey, National Ocean Service, NOAA, U.S. Department of Commerce type: (MD_KeywordTypeCode) dataCentre thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Data Center Keywords date: (CI_Date) date: 2017-04-24 dateType: (CI_DateTypeCode) publication edition: 8.5 citedResponsibleParty: GCMD Landing Page descriptiveKeywords: (MD_Keywords) keyword: NGS Lidar 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-05 from the NOAA system. Cite As: National Geodetic Survey, [Date of Access]: 2023-2024 NOAA NGS Topobathy Lidar: Ozarks area (Missouri, Arkansas and Oklahoma Rivers) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/79259. 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: CC0-1.0 These data were produced by NOAA and are not subject to copyright protection in the United States. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0-1.0). otherConstraints: Anchor: CC0-1.0 SPDX License: Creative Commons Zero v1.0 Universal (CC0-1.0) resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-03-05 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-05 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. Data set is not for use in litigation. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-03-05 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the National Geodetic Survey, 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: 2023-2024 NOAA NGS Topobathy Lidar DEM: Ozarks area (Missouri, Arkansas and Oklahoma Rivers) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 79263 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: 79259 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ngs/dmp/pdf/79259.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 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: OS Independent extent: (EX_Extent) description: Block04_K geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -91.39 eastBoundLongitude: -90.32 southBoundLatitude: 37.95 northBoundLatitude: 38.57 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-10-02 endPosition: 2024-07-24 extent: (EX_Extent) description: Block04_M geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -93.69 eastBoundLongitude: -93.22 southBoundLatitude: 34.85 northBoundLatitude: 34.96 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-11-24 endPosition: 2024-08-04 extent: (EX_Extent) description: Block04_N geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -93.89 eastBoundLongitude: -93.58 southBoundLatitude: 35.36 northBoundLatitude: 35.48 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-12-08 endPosition: 2023-12-10 extent: (EX_Extent) description: Block02_ E geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -94.04 eastBoundLongitude: -93.77 southBoundLatitude: 38.32 northBoundLatitude: 38.57 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-09-08 endPosition: 2023-09-18 extent: (EX_Extent) description: Block02_ F geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -91.49 eastBoundLongitude: -90.73 southBoundLatitude: 36.39 northBoundLatitude: 37.19 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-09-08 endPosition: 2023-09-25 extent: (EX_Extent) description: Block02_ G geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -90.82 eastBoundLongitude: -90.31 southBoundLatitude: 36.72 northBoundLatitude: 37.36 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-10-02 endPosition: 2023-10-09 extent: (EX_Extent) description: Block03_L geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -92.74 eastBoundLongitude: -92.347 southBoundLatitude: 38.87 northBoundLatitude: 39.13 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-09-12 endPosition: 2023-09-17 extent: (EX_Extent) description: Block04_J geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -92.48 eastBoundLongitude: -91.54 southBoundLatitude: 37.72 northBoundLatitude: 38.68 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-09-10 endPosition: 2024-09-04 extent: (EX_Extent) description: Block01_B geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -92.79 eastBoundLongitude: -92.4 southBoundLatitude: 35.97 northBoundLatitude: 36.17 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-08-21 endPosition: 2023-08-29 extent: (EX_Extent) description: Block01_ C geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -91.52 eastBoundLongitude: -91.06 southBoundLatitude: 36.14 northBoundLatitude: 36.39 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-09-25 endPosition: 2023-10-02 extent: (EX_Extent) description: Block01_ D geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -93.94 eastBoundLongitude: -93.71 southBoundLatitude: 37.83 northBoundLatitude: 38.02 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-08-28 endPosition: 2023-09-08 extent: (EX_Extent) description: Block02_H geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -90.53 eastBoundLongitude: -90.2 southBoundLatitude: 36.81 northBoundLatitude: 37.22 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-10-09 endPosition: 2023-10-11 extent: (EX_Extent) description: Block03_I geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -92.62 eastBoundLongitude: -91.94 southBoundLatitude: 38.18 northBoundLatitude: 38.6 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-09-13 endPosition: 2023-09-27 extent: (EX_Extent) description: Block04_P geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -94.95 eastBoundLongitude: -94.54 southBoundLatitude: 35.78 northBoundLatitude: 36.17 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2024-07-11 endPosition: 2024-08-30 extent: (EX_Extent) description: Block04_Q geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -96.25 eastBoundLongitude: -94.98 southBoundLatitude: 35.37 northBoundLatitude: 36.18 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-12-13 endPosition: 2024-12-06 extent: (EX_Extent) description: Block04_R geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -94.11 eastBoundLongitude: -93.42 southBoundLatitude: 35.48 northBoundLatitude: 35.85 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2024-08-13 endPosition: 2024-08-28 extent: (EX_Extent) description: Block04_S geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -93.56 eastBoundLongitude: -93.42 southBoundLatitude: 36.61 northBoundLatitude: 36.84 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-08-14 endPosition: 2024-09-02 extent: (EX_Extent) description: Block01_A geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -93.66 eastBoundLongitude: -93.56 southBoundLatitude: 36.38 northBoundLatitude: 36.49 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-08-19 endPosition: 2023-08-21 extent: (EX_Extent) description: Block04_O geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -93.44 eastBoundLongitude: -92.38 southBoundLatitude: 34.81 northBoundLatitude: 35.25 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2023-10-24 endPosition: 2024-09-03 supplementalInformation: The NOAA Ozarks Topbathymetric Lidar data includes all lidar returns within the project's buffered boundary. An automated grounding classification algorithm was used to determine bare earth and submerged topography point classification. The automated grounding was followed with manual editing. Classes 2 (ground), 40 (submerged topography), and 43 (submerged object) were used to create the final DEMs. The full workflow used for this project is documented in the NOAA Ozarks Topobathymetric Lidar final report. return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureTypes: LocalName: Other featureCatalogueCitation: https://www.fisheries.noaa.gov/inport/item/79262 (CI_Citation) title: NOAA NGS Topobathy Lidar Class Scheme: Ozarks Area date: (CI_Date) date: 2026-02-25 dateType: (CI_DateTypeCode) publication return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: ZIP 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=13981 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/13981/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_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: HORIZONTAL ACCURACY - Lidar horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, flying altitude, and INS derived attitude error. VERTICAL ACCURACY - Absolute accuracy was assessed using Non-Vegetated Vertical Accuracy (NVA) survey methods. Survey check points were evenly distributed as feasible throughout the project area. NVA compares known ground check point data that were withheld from the calibration and post-processing of the lidar point cloud to the triangulated surface generated by the ground classified lidar point cloud. Project specifications require NVA meet 0.196 m accuracy at the 95% confidence interval. Submerged topography points were tested separately and usually occurred in depths up to 1m. Project specifications require submerged topography shall meet a vertical RMSE of QL2b specified in the Draft National Coastal Mapping strategy 1.0 which is equivalent to 0.30 m RMSE at a depth of 1 m. result: (missing) report: (DQ_QuantitativeAttributeAccuracy) nameOfMeasure: Analytical Accuracy evaluationMethodDescription: HORIZONTAL ACCURACY - 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 (ACCr) . VERTICAL ACCURACY - Non-Vegetated Vertical Accuracy (NVA) is a measure of the accuracy of lidar point data in open areas (classified LAS) with level slope (less than 20 degrees) where the lidar system has a high probability of measuring the ground surface and is evaluated at the 95% confidence interval (1.96*RMSEz). result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Blocks A, B, D, E, F, G, H, J, K, M, N, Q, and S - RMSEr is 0.026 meters, with a ACCr of 0.045 meters at the 95% confidence level Block C- RMSEr is 0.013 meters, with a ACCr of 0.023 meters at the 95% confidence level. Blocks I, L, and O- RMSEr is 0.025 meters, with a ACCr of 0.044 meters at the 95% confidence level. Block P- RMSEr is 0.038 meters, with a ACCr of 0.066 meters at the 95% confidence level. Block R- RMSEr is 0.025-0.038 meters, with an ACCr of 0.044-0.065 meters at the 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The cumulative NVA compared to classified LAS for blocks A-S is 0.031 m RMSE, and 0.060 m 95% CL using 56 check points. The cumulative submerged topography accuracy for blocks A-S is 0.069 m RMSE and 0.134 m 95% CL using 3,409 check points. Please refer to the NOAA Ozarks Topobathymetric Lidar final data report for NVA and submerged topography accuracy assessment results for each block. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Data for the NOAA Ozarks Topbathymetric Lidar Delivery 1 Block A area was acquired by NV5 Geospatial (NV5) using a Leica Chiroptera Hawkeye 4X topobathymetric lidar system. All derived Ellipsoidal height LAS data is referenced to: Horizontal Datum-NAD83(2011) epoch: 2010.00 Projection-UTM Zone 15N Horizontal Units-meters Vertical Datums-GRS80 Ellipsoid Vertical Units-meters NOAA provided NV5 Geospatial with a project boundary for the NOAA Ozarks Topobathymetric Lidar project. Using a 25 meter buffered boundary, NV5 created an airborne lidar acquisition plan. The collected lidar data were immediately processed in the field by NV5 to a level that will allow QA\QC measures to determine if the sensor is functioning properly and assess the coverage of submerged topography. An initial SBET was created using Waypoint Inertial Explorer 8.90, and the raw data were extracted into geo-referenced LAS files using Lidar Survey Studio 3.0 with pre-calculated scanner misalignment angles determined through a boresight protocol. These files were inspected for errors and then passed through an automated workflow, producing rasters to develop an initial assessment of bathymetric coverage. NV5 reviewed all acquired flight lines to ensure complete coverage and positional accuracy of the laser points. These rasters were also used to create an initial product in Quick Look Coverage Maps. These Quick Look files are not fully processed data or final products but provide rapid assessment of approximate coverage and depth penetration. dateTime: DateTime: 2024-02-07T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: NV5 resolved kinematic corrections for aircraft position data using aircraft GNSS and Applanix's proprietary PP-RTX solution. When PP-RTX was not used NV5 conducted static Global Navigation Satellite System (GNSS) ground surveys (1 Hz recording frequency) using base stations over known monument locations during flights. After the airborne survey, static GPS data were triangulated with nearby Continuously Operating Reference Stations (CORS) using the Online Positioning User Service (OPUS) for precise positioning. Multiple independent sessions over the same base station were performed to confirm antenna height measurements and to refine position accuracy. This data was used to correct the continuous on board measurements of the aircraft position recorded throughout the flight. A final smoothed best estimate trajectory (SBET) was developed that blends post-processed aircraft position with attitude data. Using the SBETs, sensor head position and attitude were then calculated throughout the survey. Trimble Business Center v.3.90, Blue Marble Geographic Calculator 2019, and PosPac MMS 8.3 SP3 were used for these processes. Following the final SBET creation, NV5 used Leica Lidar Survey Studio (LSS) to calculate laser point positioning by associating SBET positions to each laser point return time, scan angle, and intensity. Leica LSS was used to derive a synthetic water surface to create a water surface model. Light travels at different speeds in air versus water and its direction of travel or angle is changed or refracted when entering the water column. The refraction tool corrects for this difference by adjusting the depth (distance traveled) and horizontal positioning (change of angle/direction) of the lidar data. All lidar data below water surface models were classified as water column to correct for refraction. Using raster-based QC methods, the output data is verified to ensure the refraction tool functioned properly. dateTime: DateTime: 2024-02-07T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: Once all data was refracted by flight line, the data was exported to LAS 1.4 format and combined into 500 m x 500 m tiles. Data were then further calibrated using TerraMatch. NV5 used custom algorithms in TerraScan to classify the initial ground/submerged topography surface points. Relative accuracy of overlapping swaths was compared and verified through the use Delta-Z (DZ) orthos created using NV5's Las Product Creator. Absolute vertical accuracy of the calibrated data was assessed using ground survey data and complete coverage was again verified. dateTime: DateTime: 2024-11-15T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: Post automated classification NV5 then performed manual editing to review all classification and improve the final topobathymetric surface. NV5's LasMonkey was used to update LAS header information, including all projection and coordinate reference system information. The final lidar data are in LAS format 1.4 and point data record format 6. The final classification scheme is as follows: 1 - Unclassified 1 Withheld - Edge clip 1 Overlap Withheld - Unrefracted green data from Chiroptera sensor 2 - Ground 7 Withheld -Low noise 17 - Bridge Decks 18 Withheld - High noise 21 - Identifiable snow 22 - Temporal exclusion 40 - Bathymetric bottom or submerged topography 41 - Water surface 42 Synthetic- Chiroptera synthetic water surface 43 - Submerged feature 45 - Water column 64 - Submerged Aquatic Vegetation (SAV) 65 - overlap bathy bottom - temporally different from a separate lift dateTime: DateTime: 2024-02-07T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received files in laz format. The files contain lidar elevation and intensity measurements. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Converted from UTM to geographic coordinates 2. Sorted by gps time dateTime: DateTime: 2026-03-01T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Acquisition and Processing date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: NV5 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-05 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |