Slide Menu
System Maintenance Notice, Monday, December 5, 2022 @ 1pm-5pm Eastern. The Operations Team will be performing system maintenance. During this scheduled downtime, InPort will not be available.
View All
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2022: 2009 SCDNR Horry County Lidar, https://www.fisheries.noaa.gov/inport/item/49980.

Item Identification

Title: 2009 SCDNR Horry County Lidar
Short Name: sc2009_scdnr_horry_m3656_metadata
Status: Completed
Publication Date: 2014-06-09
Abstract:

Sanborn Map Company completed the original classification of the multiple return LiDAR of Horry County, South Carolina in 2009. In 2013, Dewberry was tasked with reviewing and updating the original LiDAR product. The nominal point spacing for this project is 1.4 meters. Dewberry used proprietary procedures to update and reclassify the LAS according to updated project specifications: 1-Unclassified, 2-Ground, 7-Noise,8- Model Key Points, 9-Water, 10-Ignored Ground, 13- Points removed from bridges and culverts (class 13 were converted to class 15 to fit the OCM scheme)

Purpose:

The purpose of this LiDAR data was to produce high accuracy 3D elevation products, including tiled LiDAR in LAS 1.2 format, 3D breaklines, and ESRI grid raster format 10 ft cell size hydro flattened Digital Elevation Models (DEMs).

Notes:

10624

Supplemental Information:

A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3656/supplemental/sc2009_scdnr_horry_m3656.kmz . A report of the processing steps can be found here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3656/supplemental/sc2009_scdnr_horry_lidarreport_m3656.pdf

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
None Bare earth

Physical Location

Organization: Office for Coastal Management
City: Charleston
State/Province: SC

Data Set Information

Data Set Scope Code: Data Set
Maintenance Note:

As needed - Dewberry 2013-2014 (reprocessed, did not recollect data)

Data Presentation Form: LAS
Entity Attribute Overview:

LiDAR points in LAS 1.2 format

Entity Attribute Detail Citation:

none

Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of Dewberry, SCDNR, NOAA, the Office for Coastal Management or its partners.

Support Roles

Data Steward

CC ID: 685659
Date Effective From: 2014-06-09
Date Effective To:
Contact (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
URL: https://coast.noaa.gov

Distributor

CC ID: 685661
Date Effective From: 2014-06-09
Date Effective To:
Contact (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
URL: https://coast.noaa.gov

Metadata Contact

CC ID: 685662
Date Effective From: 2014-06-09
Date Effective To:
Contact (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
URL: https://coast.noaa.gov

Point of Contact

CC ID: 685660
Date Effective From: 2014-06-09
Date Effective To:
Contact (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
URL: https://coast.noaa.gov

Extents

Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1135577
W° Bound: -80.373467
E° Bound: -79.433067
N° Bound: 33.516439
S° Bound: 32.809321

Extent Group 1 / Time Frame 1

CC ID: 1135576
Time Frame Type: Discrete
Start: 2009

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3656

The data set is dynamically generated based on user-specified parameters.;

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. These data depict the heights at the time of the survey and are only accurate for that time.

Distribution Information

Distribution 1

CC ID: 742416
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3656
Distributor:
File Name: Customized Download
Description:

Create custom data files by choosing data area, product type, map projection, file format, datum, etc.

Distribution 2

CC ID: 742417
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3656/index.html
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

CC ID: 742419
URL: https://coast.noaa.gov/dataviewer
URL Type:
Online Resource

URL 2

CC ID: 742420
URL: https://coast.noaa.gov
URL Type:
Online Resource

URL 3

CC ID: 742421
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3656/supplemental/sc2009_scdnr_horry_m3656.kmz
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz
Description:

This graphic shows the lidar coverage for the 2009 SCDNR collection of Berkeley county in South Carolina. The 2013 dataset is a reprocessing and redelivery of this area.

Activity Log

Activity Log 1

CC ID: 685678
Activity Date/Time: 2016-05-23
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 685677
Activity Date/Time: 2017-11-14
Description:

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 718581
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 742418
Activity Date/Time: 2018-03-13
Description:

Partial upload to move data access links to Distribution Info.

Data Quality

Horizontal Positional Accuracy:

Lidar source compiled to meet 1 meter horizontal accuracy.; Quantitative Value: 1.0 meters, Test that produced the value: Dewberry does not perform independent horizontal accuracy testing on the LiDAR. LiDAR vendors perform calibrations on the LiDAR sensor and compare data to adjoining flight lines to ensure LiDAR meets the 1 meter horizontal accuracy standard at the 95% confidence level.

Vertical Positional Accuracy:

The vertical accuracy of the original LiDAR was tested by Dewberry in 2012 (or whenever we performed the original QAQC). Vertical Accuracy was not re-tested post updates performed in 2014.

The vertical accuracy of the of the full LiDAR project was tested by Dewberry with independent survey checkpoints. The survey checkpoints were evenly distributed throughout the project area and are located in areas of bare earth and open terrain, high grass, pavement, brush and low trees, and forest. The vertical accuracy is tested by comparing survey checkpoints to a triangulated irregular network (TIN) that is created from the LiDAR ground points. Checkpoints are always compared to interpolated surfaces created from the LiDAR point cloud because it is unlikely that a survey checkpoint will be located at the location of a discrete LiDAR point.

Checkpoints in open terrain were used to compute the Fundamental Vertical Accuracy (FVA). Project specifications required a FVA of 0.80 ft (24.5 cm) based on a RMSEz (0.41 ft/12.5 cm) x 1.9600. All checkpoints were used to compute the Consolidated Vertical Accuracy (CVA). Project specifications required a CVA of 1.19 ft (36.3 cm) based on the 95th percentile.; Quantitative Value: 0.183 meters, Test that produced the value: 0.6 ft (18.3cm) Based on the vertical accuracy testing conducted by Dewberry, using NSSDA and FEMA methodology, vertical accuracy at the 95% confidence level (called Accuracyz) is computed by the formula RMSEz x 1.9600. The dataset for Horry County, South Carolina satisfies the criteria:

Lidar dataset tested 0.32 ft vertical accuracy at 95% confidence level in open terrain, based on RMSEz (0.33 ft) x 1.9600.

Completeness Report:

A visual qualitative assessment was performed to ensure data completeness and bare earth data cleanliness. No void or missing data and data passes vertical accuracy specifications.

Conceptual Consistency:

Data covers the tile scheme provided for the project area.

Lineage

Process Steps

Process Step 1

CC ID: 1135570
Description:

The ABGPS, IMU, and raw Leica ALS-50 LiDAR data are integrated into the LEICA ALS post processor software. The resultant file is in a LAS binary file format. The LAS file version 1.2 formats can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the geodetic coordinates referenced to the NAD83 horizontal datum and GRS80 vertical datum. The date and time for each flight line can be determined using the Julian date and time.

Process Date/Time: 2009-01-01 00:00:00

Process Step 2

CC ID: 1135571
Description:

The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare earth digital terrain models (DTMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as define by the LAS 1.2 specification. In addition the following fields are included: Flight Date Julian, Year, and Class. The LAS files do not include overlap. The data was classified as follows: 1-Unclassified, 2-Ground, 7-Noise,8- Model Key Points, 9-Water, 10-Ignored Ground, 13- Points removed from bridges and culverts.

Process Date/Time: 2009-01-01 00:00:00

Process Step 3

CC ID: 1135572
Description:

Conversion from Geodetic coordinates NAD83 into State Plane coordinates (International Feet) NAD83 and conversion from ellipsoid heights (meters) into orthometric heights (U.S. Survey Feet).

Process Date/Time: 2009-01-01 00:00:00

Process Step 4

CC ID: 1135573
Description:

Dewberry updated the horizontal datum for the 2009 data from NAD83 to NAD83 (NSRS2007) and the vertical datum from NAVD88 (Geoid03) to NAVD88 (Geoid09). The projection and all units remain the same. Additionally, Dewberry updated the precision of the lidar data from 2 decimal places to 3 decimal places. Dewberry also reviewed the LiDAR data and removed gross artifacts and anomalies by re-classifying the LiDAR points to more appropriate classes.

Process Date/Time: 2014-01-01 00:00:00

Process Step 5

CC ID: 1135574
Description:

The NOAA Office for Coastal Management (OCM) received the files in laz format via hard drive from Dewberry. The data arrived referenced to the South Carolina State Plane (3900) and vertical reference to NAVD88 elevation in feet:

1. The data were converted from projected orthometric coordinates to geographic coordinates.

2. Vertical values were converted from NAVD88 to ellipsoidal values using Geoid09.

Process Date/Time: 2014-08-22 00:00:00

Catalog Details

Catalog Item ID: 49980
GUID: gov.noaa.nmfs.inport:49980
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:23+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2022-03-16
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16