2016-2017 NOAA NGS Topobathy Lidar DEM: Coastal South Carolina
Office for Coastal Management
Data Set
(DS)
| ID: 53372
| Published / External
Created: 2018-08-17
|
Last Modified: 2024-01-10
Project (PRJ) | ID: 47844
ID: 53372
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2016-2017 NOAA NGS Topobathy Lidar DEM: Coastal South Carolina |
---|---|
Short Name | SC1601 |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2018-09-01 |
* » Abstract |
These data were collected by Quantum Spatial, Inc. (QSI) for the National Oceanic and Atmospheric Administration (NOAA), National Geodetic Survey (NGS), Remote Sensing Devision (RSD), Coastal Mapping Program (CMP) using a Riegl VQ880G system. The Delivery 1 and Delivery 2 (D1/D2) data were acquired from 20161203 - 20170301 in nine missions. The missions were flown on 20161203, 20161209, 20161210, 20161228, 20161229, 20161230, 20170105, 20170228, and 20170301. The Delivery 3 (D3) data were acquired from 20161002 - 20170219 in fifteen missions. Data acquired on 10/02, pre-Hurricane Matthew, was only used to fill a small gap in data entirely over water where no bathymetric coverage was achieved. The Delivery 4 (D4) data were acquired from 20161211 - 20170204 in thirteen missions. The Delivery 5 (D5) data were acquired from 20170112 - 20170204 in eleven missions. The Delivery 6 (D6) data were acquired from 20161203 - 20170301 in eleven missions. The Delivery 7 (D7) data were acquired from 20170212 - 20170221 in eight missions. The Delivery 8 (D8) data were acquired from 20170218 - 20170227 in six missions. |
* Purpose |
This lidar data (and digital camera imagery collected under the same task order) was required by National Oceanic and Atmospheric Administration (NOAA), 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. |
Notes | |
Other Citation Details | |
• Supplemental Information |
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) and 26 (submerged topography) were used to create the final DEMs. |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > TOPOGRAPHICAL RELIEF MAPS |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
CoRIS Discovery Thesaurus | Geographic Information > LiDAR |
CoRIS Theme Thesaurus | EARTH SCIENCE > Land Surface > Topography> Terrain Elevation |
CoRIS Theme Thesaurus | EARTH SCIENCE > Oceans > Bathymetry/Seafloor Topography > Bathymetry |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | 20161203 |
None | 20170301 |
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > SOUTH CAROLINA |
CoRIS Place Thesaurus | COUNTRY/TERRITORY > United States of America > South Carolina |
CoRIS Place Thesaurus | OCEAN BASIN > Atlantic Ocean > |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | Binary |
• Maintenance Frequency | None Planned |
Maintenance Note | |
» Data Presentation Form | Model (digital) |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
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. |
Data Set Credit | We request that you credit the National Oceanic and Atmospheric Administration (NOAA) when you use these data in a report, publication, or presentation. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2018-07-24 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2018-07-24 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2018-07-24 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2018-07-24 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -80.041115 |
---|---|
* » E° Bound | -79.986325 |
* » N° Bound | 32.714096 |
* » S° Bound | 32.578384 |
* » Description |
D1/D2 |
Extent Group 1 / Geographic Area 2
* » W° Bound | -80.575337 |
---|---|
* » E° Bound | -80.307752 |
* » N° Bound | 32.542629 |
* » S° Bound | 32.254916 |
* » Description |
D3 |
Extent Group 1 / Geographic Area 3
* » W° Bound | -80.893994 |
---|---|
* » E° Bound | -80.574798 |
* » N° Bound | 32.372078 |
* » S° Bound | 32.117508 |
* » Description |
D4 |
Extent Group 1 / Geographic Area 4
* » W° Bound | -81.092181 |
---|---|
* » E° Bound | -80.787823 |
* » N° Bound | 32.189411 |
* » S° Bound | 31.878403 |
* » Description |
D5 |
Extent Group 1 / Geographic Area 5
* » W° Bound | -79.933722 |
---|---|
* » E° Bound | -79.609965 |
* » N° Bound | 32.905082 |
* » S° Bound | 32.647866 |
* » Description |
D6 |
Extent Group 1 / Geographic Area 6
* » W° Bound | -79.717039 |
---|---|
* » E° Bound | -79.327277 |
* » N° Bound | 33.117057 |
* » S° Bound | 32.886564 |
* » Description |
D7 |
Extent Group 1 / Geographic Area 7
* » W° Bound | -79.428248 |
---|---|
* » E° Bound | -79.130611 |
* » N° Bound | 33.228379 |
* » S° Bound | 33.064631 |
* » Description |
D8 |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2016-12-12 |
End | 2017-03-03 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
|
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8585 |
» Data Access Procedure | |
• » Data Access Constraints |
None |
• Data 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8585 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/NGS_SC_Topobathy_DEM_2016_8585/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov/dataregistry |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8575/supplemental/sc2016_ngs_topobathy_m8575.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the DEM footprint for the 2016-2017 NOAA NGS topobathy lidar project of coastal South Carolina. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
OS Independent |
---|
Data Quality
Representativeness |
The DEMs are derived from the source LiDAR and inherit the accuracy of the source data. The DEMs are created using controlled and tested methods to limit the amount of error introduced during DEM production so that any differences identified between the source LiDAR and final DEMs can be attributed to interpolation differences. DEMs are created by averaging several LiDAR points within each pixel which may result in slightly different elevation values at a given location when compared to the source LAS, which does not average several LiDAR points together but may interpolate (linearly) between two or three points to derive an elevation value.
Absolute accuracy was assessed using both Non-Vegetated Vertical Accuracy (NVA) and Vegetated Vertical Accuracy (VVA) survey methods. Survey checkpoints were evenly distributed, as much as possible, 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 LiDAR points that were calibrated and post-processed. 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). QSI assessed three land cover categories: tall grass, brush and small trees, and forested. Overall the NOAA South Carolina D1/D2 area, 9 survey checkpoints were used to assess the vegetated vertical accuracy. Project specifications require VVA meet 0.36 m based on the 95th percentile. Submerged topography points were also tested separately. Project specifications require submerged topography to meet 0.49 m at the 95% confidence level based on RMSEz x 1.9600. Using NSSDA and FEMA methodology, the non-vegetated vertical accuracy (NVA) at the 95% confidence level (called Accuracyz) was computed by the formula RMSEz x 1.9600. Using NSSDA and FEMA methodology, bathymetric vertical accuracy at the 95% confidence level for submerged topography was computed by the formula RMSEz x 1.9600. |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy | |
Vertical Positional Accuracy |
The D1/D2 dataset tested 0.06 m non-vegetated vertical accuracy at 95% confidence level in open terrain using 23 ground check points, based on RMSEz (0.031 m) x 1.9600. The D3 dataset tested 0.068 m non-vegetated vertical accuracy at 95% confidence level in open terrain using 30 ground check points, based on RMSEz (0.035 m) x 1.9600. The D4 dataset tested 0.108 m non-vegetated vertical accuracy at 95% confidence level in open terrain using 21 ground check points, based on RMSEz (0.055 m) x 1.9600. The D5 dataset tested 0.035 m non-vegetated vertical accuracy at 95% confidence level in open terrain using 30 ground check points, based on RMSEz (0.018 m) x 1.9600. The D6 dataset tested 0.043 m non-vegetated vertical accuracy at 95% confidence level in open terrain using 64 ground check points, based on RMSEz (0.022 m) x 1.9600. The D7 dataset tested 0.047 m non-vegetated vertical accuracy at 95% confidence level in open terrain using 46 ground check points, based on RMSEz (0.024 m) x 1.9600 The bathymetric vertical accuracy of the D1/D2 Lidar dataset tested 0.231 m vertical accuracy at 95% confidence level in submerged topography using 38 submerged control points, based on RMSEz (0.118 m) x 1.9600. The D3 Lidar dataset tested 0.082 m vertical accuracy at 95% confidence level in submerged topography using 31 submerged control points, based on RMSEz (0.042 m) x 1.9600. The D5 Lidar dataset tested 0.073 m vertical accuracy at 95% confidence level in submerged topography using 8 submerged control points, based on RMSEz (0.035 m) x 1.9600. D6 Lidar dataset tested 0.062 m vertical accuracy at 95% confidence level in submerged topography using 15 submerged control points, based on RMSEz (0.031 m) x 1.9600. The D7 Lidar dataset tested 0.132 m vertical accuracy at 95% confidence level in submerged topography using 52 submerged control points, based on RMSEz (0.067 m) x 1.9600. Using NDEP and ASPRS methodology, vegetated vertical accuracy (VVA) was computed using the 95th percentile method. The D1/D2 dataset tested 0.301 m vegetated vertical accuracy at 95th percentile using 9 mixed landclass points. The D3 dataset tested 0.049 m vegetated vertical accuracy at 95th percentile using 2 mixed landclass points. The D4 dataset tested 0.108 m vertical accuracy at 95% confidence level in open terrain using 21 ground check points, based on RMSEz (0.055 m) x 1.9600. The D5 dataset tested 0.052 m vegetated vertical accuracy at 95th percentile using 3 mixed landclass points. The D6 dataset tested 0.294 m vegetated vertical accuracy at 95th percentile using 11 mixed landclass points. The D7 dataset tested 0.107 m vegetated vertical accuracy at 95th percentile using 8 mixed landclass points. Due to the predominately marshy terrain, no survey checkpoints, ground check points, or submerged topobathy checkpoints were able to be collected within the D8 delivery area. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report | |
Conceptual Consistency | |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
Data for the NOAA South Carolina Topobathymetric-Shoreline Mapping project was acquired by Quantum Spatial (QSI) using a Riegl VQ-880G Topobathy LiDAR system. All derived DEM data is referenced to: Horizontal Datum-NAD83 (2011) epoch: 2010 Projection-UTM Zone 17N Horizontal Units-meters Vertical Datum- NAVD88 (Geoid12b) Vertical Units-meters This D1/D2 dataset encompasses 987 500m x 500m tiles in eastern South Carolina. Green and NIR (for water surface model creation that is used during refraction of the green bathymetric data) LiDAR data were acquired with the Riegl sensor VQ-880G. QSI reviewed all acquired flight lines to ensure complete coverage and positional accuracy of the laser points. QSI creates an initial product call Quick Look Coverage Maps. These Quick Looks files are not fully processed data or final products. The collected LiDAR data is immediately processed in the field by QSI 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 is created in POSPAC MMS 7.1 and used in RiProcess which applies pre-calibrated angular misalignment corrections of scanner position to extract the raw point cloud into geo-referenced LAS files. These files are inspected for sensor malfunctions and then passed through automated classification routines (TerraScan) to develop an initial topo-bathymetric ground model. To correct the continuous onboard measurements of the aircraft position recorded throughout the missions, QSI concurrently conducted multiple static Global Navigation Satellite System (GNSS) ground surveys (1 Hz recording frequency) over each monument. After the airborne survey, the 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 monument were processed to confirm antenna height measurements and to refine position accuracy. QSI then resolved kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. A smoothed best estimate trajectory (SBET) was developed that blends post-processed aircraft position with attitude data. Sensor head position and attitude are calculated throughout the survey. The SBET data are used extensively for laser point processing. The software Trimble Business Center v.3.90, Blue Marble Geographic Calculator 2016, and PosPac MMS 8.0 are used for these processes. |
Process Date/Time | 2017-11-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Next, QSI used RiProcess 1.8.1 to calculate laser point positioning of the Riegl VQ-880G data by associating SBET positions to each laser point return time, scan angle, intensity, etc. A raw laser point cloud is created in Riegl data format. Erroneous points are filtered and then automated line-to-line calibrations are performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations are calculated on matching surfaces within and between each line and results are applied to all points in a flight line. Every flight line is used for relative accuracy calibration. Green data are calibrated using TerraScan, TerraModeler, and TerraMatch. Accuracy of the calibrated data is assessed using ground RTK survey data. All data are then exported to LAS 1.2 format and are ready for processing and editing. QSI verified complete coverage. Relative accuracy of the green swaths compared to overlapping and adjacent swaths and verified through the use Delta-Z (DZ) orthos created using QSI's DZ Ortho creator. QSI used the green water surface points and as needed NIR water surface points to create water surface models. These models are used in the refraction tool to determine the depth of bathymetric points and 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. All LiDAR data below water surface models were classified as water column. 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 travelled) and horizontal position (change of angle/direction) of the LiDAR data. Using statistics and limited manual review, the output data is verified to ensure the refraction tool functioned properly. Once all green data has been refracted by flight lines, all flight lines covering each tile are combined into a single 500 m x 500 m tile. QSI used algorithms in TerraScan to create the initial ground/submerged topography surface. QSI then performed manual editing to review and improve the final topobathy surface. All LiDAR data was peer-reviewed. All necessary edits were applied to the dataset. QSI'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.2 and point data record format 3. The final classification scheme is as follows: 1-Unclassified 2-Ground 7-Noise 19-Overlap Default 20-Overlap Ground 21-Overlap Water Column 22-Overlap Water Surface 25-Water Column 26-Bathymetric Bottom or Submerged Topography 27-Water Surface 29-Submerged feature 31-Temporal Bathymetric Bottom 129-Edge Clip |
Process Date/Time | 2017-11-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
QSI then transformed the ellipsoid heights of the final LiDAR data to into orthometric heights referenced to NAVD88 using Geoid 12B to create the DEMs. The topobathymetric DEM was output at 1 meter resolution in IMG format into 5000 m x 5000 m tiles. The D1/D2 raster is clipped to the extent of the tile grid and named according to project specifications. Interpolated DEM dataset-These DEMs represent a continuous surface with all void areas interpolated. No void layer was incorporated into this DEM and there are no areas of No Data, regardles of whether the LiDAR data fully penetrated to the submerged topography. Void DEM dataset- A 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 exclude interpolated elevation data from these areas. |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 53372 |
---|---|
Metadata Record Created By | Maryellen Sault |
Metadata Record Created | 2018-08-17 08:33+0000 |
Metadata Record Last Modified By | Kirk Waters |
» Metadata Record Last Modified | 2024-01-10 19:02+0000 |
Metadata Record Published | 2024-01-10 |
Owner Org | OCM |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|