2009 SCDNR Charleston County Lidar

OCM Partners
Data Set (DS) | ID: 49978 | Published / External
Created: 2017-11-15   |   Last Modified: 2022-08-09

Parent: Lidar - partner (no harvest)
Project (PRJ) | ID: 49401

ID: 49978
Data Set (DS)

* Discovery
• First Pass
» Metadata Rubric

Item Identification

* » Title 2009 SCDNR Charleston County Lidar
Short Name sc2009_scdnr_charleston_m3653_metadata
* Status Completed
Creation Date  
Revision Date  
• Publication Date 2014-06
* » Abstract

Photoscience completed the original collection and classification of the multiple return LiDAR of Charleston County, South Carolina in the winter of 2006-2007. In 2009, Sanborn collected portions of Charleston County which were previously uncollected in 2006/7. In 2013, Dewberry was tasked with reviewing, updating and merging the original LiDAR products into one continuous data to include the 2006-2007 and 2009 separate projects. The 2006/2007 data was separated from the 2009 collected points in order to keep the 2 missions separate (collection dates, standards, data qualities, etc). The 2006-2007 data was removed by analyzing GPS time stamps of the LAS points in order to differentiate by collection year. The resulting LAS files left only the 2009 points which represent this project. The 2007 data already exists at OCM as part of a previous delivery. 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.
* 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

10622
Other Citation Details
• 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/3653/supplemental/sc2009_scdnr_charleston_m3653.kmz .

A report documenting project notes is available at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3653/supplemental/sc2009_scdnr_charleston_lidarreport_m3653.pdf .
DOI (Digital Object Identifier)  
DOI Registration Authority  
DOI Issue Date  

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category elevation
None Bare earth
   
   
   

Temporal Keywords

Thesaurus Keyword
   
   
   

* Spatial Keywords

Thesaurus Keyword
   
   
   

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  
• Maintenance Frequency  
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
Entity Attribute Detail URL  
Distribution Liability

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

Support Roles

» At least one Distributor Org, one Metadata Contact, one Point of Contact, and one Data Steward should be listed.
* » Support Role Data Steward
* » Date Effective From 2014-06
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 2014-06
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 2014-06
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 2014-06
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 Ground Condition

Extent Group 1

Extent Description

Extent Group 1 / Geographic Area 1

* » W° Bound -80.373467
* » E° Bound -79.433067
* » N° Bound 33.516439
* » S° Bound 32.809321
* » Description

Extent Group 1 / Vertical Extent

EPSG Code
Vertical Minimum
Vertical Maximum

Extent Group 1 / Time Frame 1

* » Time Frame Type Discrete
* » Start 2009
End  
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? Yes
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
Dimension Type
Size
Resolution
Resolution Units
Resolution Type
Description

Axis Dimension
Dimension Type
Size
Resolution
Resolution Units
Resolution Type
Description

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
Horizontal Encoding Method
Latitude Resolution
Longitude Resolution
Coordinate X Resolution
Coordinate Y Resolution
Row Resolution
Column Resolution
Horizontal Units
Distance Resolution
Distance Units
Bearing Resolution
Bearing Units
Reference Direction
Reference Meridian

Vertical Resolution
Vertical Encoding Method
Vertical Resolution
Vertical Units

Access Information

Data License  
Data License URL  
Data License Statement
* » Security Class Unclassified
* Security Classification System
Security Handling Description
• Data Access Policy
» Data Access Procedure

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

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.
Metadata Access Constraints
Metadata Use Constraints

Distribution Information

Start Date  
» Download URL https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3653
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.amazonaws.com/laz/geoid18/3653/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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3653/supplemental/sc2009_scdnr_charleston_m3653.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 Charleston county in South Carolina. Delivered with the Charleston 2006 data as one mission.
URL https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3653/supplemental/sc2009_scdnr_charleston_lidarreport_m3653.pdf
Name project report
URL Type Online Resource
File Resource Format pdf
Description

A report documenting project notes.
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 2016-05-23
Activity Type  
Responsible Party  
Description

Date that the source FGDC record was last modified.
Activity Time 2017-11-14
Activity Type  
Responsible Party  
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 Time 2018-02-08
Activity Type  
Responsible Party  
Description

Partial upload of Positional Accuracy fields only.
Activity Time 2018-03-13
Activity Type  
Responsible Party  
Description

Partial upload to move data access links to Distribution Info.
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

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 10.0

Data Quality

Representativeness
Accuracy
Analytical Accuracy
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.185 meters, Test that produced the value: Calculated FVA to 0.61 ft (18.5 cm). 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 (Charleston County had a RMSEz of 9.25 cm+). The dataset for the Charleston County, SC LiDAR project satisfies the criteria:

Lidar dataset tested 0.49 ft vertical accuracy at 95% confidence level in open terrain, based on RMSEz (0.33 ft) x 1.9600.
Quantitation Limits
Bias
Comparability
Completeness Measure
Precision
Analytical Precision
Field Precision
Sensitivity
Detection Limit
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.
» 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

JASPER COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Jasper County, South Carolina.

Data was collected in a total of 111 flightlines at a pulse rate of 75,000 points per second.

COLLETON COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Colleton County, South Carolina.

Data was collected in a total of 160 flightlines at a pulse rate of 75,000 points per second.

CHARLESTON COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Charleston County, South

Carolina. Data was collected in a total of 77 flightlines at a pulse rate of 75,000 points per second.

Originally collected from 20061227 through 20070323.
Process Date/Time 2007-03-23 00:00:00
Process Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number 2
» Description

Raw LiDAR data (collected as Process Step 1) was processed to create a bare ground surface. Process included

calibration of LiDAR data to remove systematic errors (utilizing Leica's ALS Processor software), adjustment of elevation data

to control positions (utilizing TerraScan software for control comparisons and adjustments), and both automatic and manual

editing to correctly classify ground and non-ground data (utilizing TerraScan and TerraModeler software). In addition, QC

steps were performed before and after processing. QC steps included line-to-line vertical comparisons and coverage checks,

and were performed with TerraScan and GeoCue software.
Process Date/Time 2007-10-30 00:00:00
Process Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number 3
» 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 Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number 4
» 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 Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number 5
» 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 Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number 6
» 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 Contact  
Phone (Voice)  
Email Address  
Source  
Process Step Number 7
» 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.

3. The 2006/2007 data was separated from the 2009 collected points in order to keep the 2 missions separate (collection dates, standards, data qualities, etc). The 2007 data was removed by analyzing time stamps for each point in the LAS files in order to differentiate collection year. The resulting LAS files showed only the 2009 points. The 2007 data already exists at OCM as part of a previous delivery.

4. The LAS data were stored as compressed LAZ data.
Process Date/Time 2014-06-02 00:00:00
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  
Identifier  
Identifier  
Identifier
Docucomp UUID
Description

Mounted Instruments
Identifier  
Identifier  
Identifier  
Identifier
Docucomp UUID
Description

Mounted Instruments
Identifier  
Identifier  
Identifier  

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 49978
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 Workflow State Published / External
Metadata Last Review Date 2022-03-16
Metadata Review Frequency 1 Year
Metadata Next Review Date 2023-03-16
Tags