gov.noaa.nmfs.inport:49977
eng
UTF8
dataset
OCM Partners
resourceProvider
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
2024-02-29T00:00:00
ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data
ISO 19115-2:2009(E)
2009 SCDNR Berkeley County Lidar
sc2009_scdnr_berkeley_m3654_metadata
2014-06-09
publication
NOAA/NMFS/EDM
49977
https://www.fisheries.noaa.gov/inport/item/49977
WWW:LINK-1.0-http--link
Full Metadata Record
View the complete metadata record on InPort for more information about this dataset.
information
Sanborn Map Company completed the original classification of the multiple return LiDAR of Berkeley 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.
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).
Sanborn collected the data, Dewberry processed the data for redelivery, please acknowledge these firms for this dataset.
completed
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
custodian
As needed - Dewberry 2013-2014 (reprocessed, did not recollect data)
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3654/supplemental/sc2009_scdnr_berkeley_m3654.kmz
This graphic shows the lidar coverage for the 2006 SCDNR collection of Berkeley county in South Carolina. The 2009 dataset is a reprocessing and redelivery of this areas.
kmz
Bare earth
Surface
Terrain
theme
Lidar - partner (no harvest)
project
InPort
otherRestrictions
Cite As: OCM Partners, [Date of Access]: 2009 SCDNR Berkeley County Lidar [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49977.
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.
otherRestrictions
Access Constraints: none
otherRestrictions
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.
otherRestrictions
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.
unclassified
NOAA Data Management Plan (DMP)
NOAA/NMFS/EDM
49977
https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49977.pdf
WWW:LINK-1.0-http--link
NOAA Data Management Plan (DMP)
NOAA Data Management Plan for this record on InPort.
information
crossReference
vector
eng; US
elevation
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 10.0
-80.373467
-79.433067
32.809321
33.516439
| Currentness: Ground Condition
2009
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3654/supplemental/sc2009_scdnr_berkeley_m3654.kmz .
A report documenting project notes is available at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3654/supplemental/sc2009_scdnr_berkeley_lidarreport_m3654.pdf .
false
eng
false
none
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
distributor
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3654
WWW:LINK-1.0-http--link
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
download
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3654/index.html
WWW:LINK-1.0-http--link
Bulk Download
Simple download of data files.
download
dataset
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: 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 Berkeley 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. 0.6 ft = 18.3 cm
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.
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.
2009-01-01T00:00:00
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.
2009-01-01T00:00:00
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).
2009-01-01T00:00:00
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.
2014-01-01T00:00:00
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 coordinates to geographic coordinates.
2. Vertical values were converted from NAVD88 to ellipsoidal values using Geoid09.
2014-08-21T00:00:00