| 2019-2020 NOAA NGS Topobathy Lidar DEM: Coastal VA, NC, SC | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:66714 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: 2022-03-15T17:56:23 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::6347 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2019-2020 NOAA NGS Topobathy Lidar DEM: Coastal VA, NC, SC date: (CI_Date) date: 2022 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 66714 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/66714 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/9467/supplemental/NOAA_Hurricane_Florence_Topobathymetric_LiDAR_and_Shoreline_Mapping_Report_Rev1.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to lidar 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: NOAA Florence Topobathymetric Lidar data were collected by NV5 Geospatial (NV5) in 9 blocks from 20191126 - 20200825 using the follow sensors: Block01 -Riegl VQ880GII system Block02 - Riegl VQ-880-G and Riegl VQ-880-GII systems Block03 - Riegl VQ880G, Riegl VQ880GII, and Riegl VQ880GH systems Block04 - Riegl VQ880GII and Leica Chiroptera 4x systems Block05 - Riegl VQ880GII, Leica Chiroptera 4x and Hawkeye systems Block06 - Riegl VQ880GII, Leica Chiroptera 4x and Hawkeye systems Block07 - Riegl VQ880G, Riegl VQ880GII, and Leica Chiroptera 4x systems Block08 - Riegl VQ880G and Riegl VQ880GII systems Block09 - Riegl VQ880G and Riegl VQ880GII systems This dataset includes topobathymetric data in a LAS format 1.4, point data record format 6, with classifications in accordance with project specifications and the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards. This data set also includes LiDAR intensity values, number of returns, return number, time, and scan angle. The 100 meter buffered project area consists of approximately 3,075,010 acres along the Eastern coast of Virginia, North Carolina, and South Carolina. The delivered classified lidar data were then transformed from ellipsoid to geoidal height (Geoid18) and used to create topobathymetric DEMs in GeoTIFF format with 1m pixel resolution. 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 enable accurate and consistent measurement of the national shoreline. The CMP works to provide a regularly updated and consistent national shoreline to define America's marine territorial limits and manage coastal resources. credit: National Oceanic and Atmospheric Administration (NOAA), National Geodetic Survey (NGS), Remote Sensing Division (RSD), Coastal Mapping Program (CMP) 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/9467/supplemental/extent_ngs_postFlorence_topobathy_m9467.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 > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > DIGITAL ELEVATION/TERRAIN MODEL (DEM) keyword: EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY > COASTAL BATHYMETRY keyword: EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION keyword: EARTH SCIENCE > SPECTRAL/ENGINEERING > LIDAR type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > NORTH CAROLINA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > SOUTH CAROLINA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > VIRGINIA keyword: VERTICAL LOCATION > LAND SURFACE keyword: VERTICAL LOCATION > SEA FLOOR type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) 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) descriptiveKeywords: (MD_Keywords) keyword: AIRCRAFT type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) 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: Cite As: National Geodetic Survey, [Date of Access]: 2019-2020 NOAA NGS Topobathy Lidar DEM: Coastal VA, NC, SC [Data Date Range], https://www.fisheries.noaa.gov/inport/item/66714. 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 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: 66714 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ngs/dmp/pdf/66714.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: OS Independent extent: (EX_Extent) description: Block01 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -77.904502 eastBoundLongitude: -77.289632 southBoundLatitude: 34.12689 northBoundLatitude: 34.545077 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-11-26 endPosition: 2019-12-21 extent: (EX_Extent) description: Block02 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -77.510503 eastBoundLongitude: -76.4876 southBoundLatitude: 34.527625 northBoundLatitude: 34.877717 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-11-28 endPosition: 2020-03-18 extent: (EX_Extent) description: Block03 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -79.40181 eastBoundLongitude: -77.800145 southBoundLatitude: 33.16496 northBoundLatitude: 34.285932 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-11-26 endPosition: 2020-04-02 extent: (EX_Extent) description: Block04 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -76.592761 eastBoundLongitude: -75.933037 southBoundLatitude: 34.646674 northBoundLatitude: 35.203366 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-12-08 endPosition: 2020-08-25 extent: (EX_Extent) description: Block05 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -75.996936 eastBoundLongitude: -75.4444 southBoundLatitude: 35.10379 northBoundLatitude: 35.8734 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-12-10 endPosition: 2020-07-27 extent: (EX_Extent) description: Block06 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -76.1174 eastBoundLongitude: -75.55938 southBoundLatitude: 35.8646 northBoundLatitude: 36.945709 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-11-26 endPosition: 2020-06-22 extent: (EX_Extent) description: Block07 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -77.16282 eastBoundLongitude: -76.36149 southBoundLatitude: 34.81832 northBoundLatitude: 35.37506 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-12-07 endPosition: 2020-04-04 extent: (EX_Extent) description: Block08 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -77.147204 eastBoundLongitude: -75.65982 southBoundLatitude: 35.26935 northBoundLatitude: 35.82732 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-12-09 endPosition: 2020-04-28 extent: (EX_Extent) description: Block09 geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -76.782432 eastBoundLongitude: -75.661664 southBoundLatitude: 35.500726 northBoundLatitude: 36.45838 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-12-04 endPosition: 2020-05-30 supplementalInformation: This dataset includes all lidar returns. An automated grounding classification algorithm was used to determine bare earth and submerged topography point classification. The automated grounding was followed with manual editing. Depth values were adjusted per sensor to NOAA provided ground truth data. Bathymetric intensity values were normalized for water depth. Classes 2 (ground), 40 (submerged topography), and 43 (submerged object) were used to create the final DEMs. The full workflow used for this project will be documented in the NOAA Florence Topobathymetric Lidar final report, to be provided upon project completion. return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAZ 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: 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=9468 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://coast.noaa.gov/htdata/raster5/elevation/NGS_VAtoSC_Topobathy_DEM_2020_9468 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_QuantitativeAttributeAccuracy) nameOfMeasure: 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 (ACCr). Absolute accuracy was assessed using both Non-Vegetated Vertical Accuracy (NVA) and Vegetated Vertical Accuracy (VVA) survey methods. Survey checkpoints 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 derived gridded bare earth DEM. NVA is a measure of the accuracy of lidar point data in open areas 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*RMSE). Project specifications require NVA meet 0.196 m accuracy at the 95% confidence interval. Ground check points located in land cover categories other than bare earth, urban, or submerged topography were used to compute the Vegetated Vertical Accuracy (VVA). Project specifications require VVA meet 0.36 m based on the 95th percentile tested against the derived bare earth DEM. Submerged topography points were tested separately to calculate accuracy 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. Please refer to the NOAA Hurricane Florence Topobathymetric lidar final data report for final accuracies, to be provided upon project completion. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Block01: Based on a flying altitude of 400 meters, an IMU error of 0.002 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 1 area is 0.029 meters, with a ACCr of 0.05 meters at the 95% confidence level. Block02:Based on a flying altitude of 400 meters, an IMU error of 0.005 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 2 area is 0.064 meters, with a ACCr of 0.11 meters at the 95% confidence level. Block03:Based on a flying altitude of 400 meters, an IMU error of 0.006 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 3 area is 0.076 meters, with a ACCr of 0.13 meters at the 95% confidence level. The project specification requires horizontal positions to be accurate to 1.0m(RMSE). Block04:Based on a flying altitude of 400 meters, an IMU error of 0.003 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 4 area is 0.040 meters, with a ACCr of 0.07 meters at the 95% confidence level. Block05: Based on a flying altitude of 400 meters, an IMU error of 0.003 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 5 area is 0.040 meters, with a ACCr of 0.07 meters at the 95% confidence level. Block06: Based on a flying altitude of 400 meters, an IMU error of 0.005 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 6 area is 0.064 meters, with a ACCr of 0.11 meters at the 95% confidence level. Block07:Based on a flying altitude of 400 meters, an IMU error of 0.005 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 7 area is 0.064 meters, with a ACCr of 0.11 meters at the 95% confidence level. Block08: Based on a flying altitude of 400 meters, an IMU error of 0.005 decimal degrees, and a GNSS positional error of 0.015 meters, the RMSEr value for the Delivery 8 area is 0.064 meters, with a ACCr of 0.11 meters at the 95% confidence level. Block09: Based on a flying altitude of 400 meters, an IMU error of 0.006 decimal degrees, and a GNSS positional error of 0.023 meters, the RMSEr value for the Delivery 9 area is 0.078 meters, with a ACCr of 0.14 meters at the 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: All accuracy values are reported at 95% confidence level. Block01 dataset Non-Vegetated Vertical Accuracy (NVA) tested 0.049 m against the derived bare earth DEM in open terrain using 10 ground check points, based on RMSEz (0.025 m) x 1.9600. Vegetated Vertical Accuracy (VVA) tested 0.164 m at the 95th percentile against the derived bare earth DEM using 9 landclass points. Block01 tested 0.157 m against the derived topobathymetric bare earth DEM using 34 submerged check points, based on RMSEz (0.080 m) x 1.9600. Block02 dataset NVA tested 0.072 m against the derived bare earth DEM in open terrain using 14 ground check points, based on RMSEz (0.037 m) x 1.9600. VVA tested 0.154 m at the 95th percentile against the derived bare earth DEM using 14 landclass points. Block02 tested 0.116 m vertical accuracy against the derived topobathymetric bare earth DEM using 89 submerged check points, based on RMSEz (0.059 m) x 1.9600. Block03 dataset NVA tested 0.041 m against the derived bare earth DEM in open terrain using 19 ground check points, based on RMSEz (0.021 m) x 1.9600. VVA tested 0.123 m at the 95th percentile against the derived bare earth DEM using 20 landclass points. Block03 tested 0.174 m vertical accuracy against the derived topobathymetric bare earth DEM using 60 submerged check points, based on RMSEz (0.089 m) x 1.9600. Block04 dataset NVA tested 0.047 m against the derived bare earth DEM in open terrain using 8 ground check points, based on RMSEz (0.024 m) x 1.9600. VVA tested 0.089 m at the 95th percentile against the derived bare earth DEM using 3 landclass points. Block04 tested 0.140 m vertical accuracy against the derived topobathymetric bare earth DEM using 34 submerged check points, based on RMSEz (0.071 m) x 1.9600. Block05 dataset NVA tested 0.048 m against the derived bare earth DEM in open terrain using 27 ground check points, based on RMSEz (0.025 m) x 1.9600. VVA tested 0.093 m at the 95th percentile against the derived bare earth DEM using 3 landclass points. Block05 tested 0.160 m vertical accuracy against the derived topobathymetric bare earth DEM using 308 submerged check points, based on RMSEz (0.082 m) x 1.9600. Block06 dataset NVA tested 0.084 m against the derived bare earth DEM in open terrain using 27 ground check points, based on RMSEz (0.043 m) x 1.9600. VVA tested 0.242 m at the 95th percentile against the derived bare earth DEM using 14 landclass points. Block06 tested 0.195 m vertical accuracy against the derived topobathymetric bare earth DEM using 165 submerged check points, based on RMSEz (0.100 m) x 1.9600. Block07 dataset NVA tested 0.049 m against the derived bare earth DEM in open terrain using 24 ground check points, based on RMSEz (0.025 m) x 1.9600. VVA tested 0.195 m at the 95th percentile against the derived bare earth DEM using 17 landclass points. Block07 tested 0.144 m vertical accuracy against the derived topobathymetric bare earth DEM using 124 submerged check points, based on RMSEz (0.074 m) x 1.9600. Block08 dataset NVA tested 0.068 m against the derived bare earth DEM in open terrain using 23 ground check points, based on RMSEz (0.034 m) x 1.9600. VVA tested 0.197 m at the 95th percentile against the derived bare earth DEM using 22 landclass points. Block08 tested 0.135 m vertical accuracy against the derived topobathymetric bare earth DEM using 123 submerged check points, based on RMSEz (0.069 m) x 1.9600. Block09 dataset NVA tested 0.067 m against the derived bare earth DEM in open terrain using 34 ground check points, based on RMSEz (0.034 m) x 1.9600. VVA tested 0.159 m at the 95th percentile against the derived bare earth DEM using 18 landclass points. Block09 tested 0.244 m vertical accuracy against the derived topobathymetric bare earth DEM using 11 submerged check points, based on RMSEz (0.124 m) x 1.9600. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Measure evaluationMethodDescription: Block01 is comprised of 36 - 5000 m x 5000 m DEM tiles. Block02 is comprised of 77 - 5000 m x 5000 m DEM tiles. Block03 is comprised of 107 - 5000 m x 5000 m DEM tiles. Block04 is comprised of 61 - 5000 m x 5000 m DEM tiles. Block05 is comprised of 62 - 5000 m x 5000 m DEM tiles. Block06 is comprised of 79 - 5000 m x 5000 m DEM tiles. Block07 is comprised of 101 - 5000 m x 5000 m DEM tiles. Block08 is comprised of 126 - 5000 m x 5000 m DEM tiles.. Block09 is comprised of 175 - 5000 m x 5000 m DEM tiles.. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Not applicable result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Data for the NOAA Florence Topobathymetric Lidar project area was acquired by NV5 Geospatial (NV5). All derived DEMdata is referenced to: Horizontal Datum-NAD83(2011) epoch: 2010.00 Projection-UTM Zone 18N Horizontal Units-meters Vertical Datum-NAVD88 (Geoid18) Vertical Units-meters 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 in POSPAC MMS 8.3 SP3 and loaded into RiProcess which applies pre-calibrated angular misalignment corrections of scanner position to extract the raw point cloud into geo-referenced LAS files. These files were inspected for sensor malfunctions and then passed through automated raster generation using LAStools 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. 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. dateTime: DateTime: 2020-10-02T00:00:00 processor: (CI_ResponsibleParty) organisationName: NGS Communications and Outreach Branch contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (301) 713-3242 address: (CI_Address) electronicMailAddress: ngs.infocenter@noaa.gov role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: Following final SBET creation, NV5 used RiProcess 1.8.5 to calculate laser point positioning by associating SBET positions to each laser point return time, scan angle, and intensity. Terra 19 and LasTools were used to classify water surface and create a water surface model. They are created for single swaths to ensure temporal differences and wave or water surface height variations between flight lines do not impact the refraction of the bathymetric data. These models are used in NV5's LasMonkey refraction tool to determine the accurate positioning of bathymetric points. All lidar data below water surface models were classified as water column to be refracted. 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. Using raster-based QC methods, the output data is verified to ensure the refraction tool functioned properly. In addition, for Blocks 4 - 7, following final SBET creation for the Leica Chiroptera 4X and Hawkeye systems, 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: 2020-12-17T00: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 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. 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 delivered dataset used the following classification scheme for Block01, Block02, Block03, Block08 and Block09: 1 - Unclassified 2 - Ground 7 - Noise 40 - Bathymetric Bottom or Submerged Topography 41 - Water Surface 43 - Submerged feature 45 - Water Column 46 - Temporal Bathymetric Bottom 71 - Overlap Default 72 - Overlap Ground 81 - Overlap Water Surface 85 - Overlap Water Column 1-Overlap - Edge Clip The delivered dataset used the following classification scheme for Block04, Block05, Block06 and Block07: 1 - unclassified 2 - ground 7 - noise 40 - bathymetric bottom or submerged topography 41 - water surface 42 Synthetic- Chiroptera synthetic water surface 43 - submerged feature 45 - water column 46 - overlap bathy bottom - temporally different from a separate lift 71 - unclassified associated with areas of overlap bathy bottom/temporal bathymetric differences 72 - ground associated with areas of overlap bathy bottom/temporal bathymetric differences 81 - water surface associated with areas of overlap bathy bottom/temporal bathymetric differences 81 Synthetic - Chiroptera synthetic water surface associated with areas of overlap bathy bottom/temporal bathymetric differences 85 - water column associated with areas of overlap bathy bottom/temporal bathymetric differences 1 Overlap - edge clip 1 Withheld - unrefracted green data from Chiroptera sensor dateTime: DateTime: 2022-01-29T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: NV5 transformed the final LiDAR data from ellipsoid heights to orthometric heights referenced to NAVD88, Geoid 18 to create the final topobathymetric void clipped DEMs. The topobathymetric bare earth DEMs were output at 1 meter resolution in GeoTIFF format into 5000 m x 5000 m tiles. The rasters are clipped to the extent of the project boundary and named according to project specifications. A bathymetric void shapefile was created to indicate areas where there was a lack of bathymetric returns. This shape was created by triangulating bathymetric bottom points with an edge length maximum of 4.56m to identify all areas greater then 9 square meters without bathymetric returns. This shapefile was used to clip and exclude interpolated elevation data from these areas in the bathymetric void clipped topobathymetric bare earth model. dateTime: DateTime: 2020-10-02T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Acquisition and Processing date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: NV5 Geospatial, Inc role: (CI_RoleCode) originator | |