ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2008_SC_Dillon_m502
MD_DataIdentification
| 1 |
|
2008 South Carolina Department of Natural Resources (SCDNR) South Carolina
Lidar - Dillon County
|
The project area is composed of 16 counties in the State of South Carolina
- Cherokee, Union, Laurens, Greenwood, Newberry, Chester, Fairfield, Lancaster, Chesterfield,
Marlboro, Darlington, Dillon, Marion, Williamsburg, Clarendon, and Orangeburg. The
project area consists of approximately 10,194 square miles including a buffer of 50
feet along the edges of the project area and an additional buffer in some areas. The
project design of the lidar data acquisition was developed to support a nominal post
spacing of 1.4 meters. The Fugro EarthData, Inc. acquisition team of Fugro Horizons,
Inc. and North West Group acquired 721 flight lines in 44 lifts from January 15, 2008
through February 10, 2008. The data was divided into 5000' by 5000' foot cells that
serve as the tiling scheme. Lidar data collection was performed with a Cessna 310
aircraft, utilizing a Leica ALS50-II MPiA sensor, collecting multiple return x, y,
and z data as well as intensity data. Lidar data was processed to achieve a bare ground
surface (Classes 2 and 8). Lidar data is remotely sensed high-resolution elevation
data collected by an airborne collection platform. Using a combination of laser range
finding, GPS positioning and inertial measurement technologies, lidar instruments
are able to make highly detailed Digital Elevation Models (DEMs) of the earth's terrain,
man-made structures, and vegetation.
|
SV_Identification
| 1 |
|
2008 South Carolina Department of Natural Resources (SCDNR) South Carolina Lidar -
Dillon County
|
|
|
| 1 |
|
Aerial Acquisition of Lidar Data for 16 counties in the State of South Carolina |
|
|
| 1 |
|
Dillon County, SC - Digital Orthophotography |
|
|
| 1 |
|
Lidar QA/QC Report |
|
|
| 2 |
|
None |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 1 |
|
South Carolina Lidar, Quality Control Surveys, 16 Counties |
|
|
| 1 |
|
|
|
|
|
resourceProvider |
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
| 1 |
|
|
|
Citation URL |
|
|
ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/sc/dillon/LiDAR_QAQC_Report_Dillon.pdf |
| 4 |
|
Becky Jordan |
Fugro EarthData, Inc. |
Project Manager |
bjordan@earthdata.com |
processor |
|
| 1 |
NOAA CSC (originator) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
originator |
|
| 1 |
NOAA CSC (publisher) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
publisher |
|
| 1 |
NOAA CSC(distributor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
distributor |
|
| 1 |
NOAA CSC (processor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
processor |
|
| 1 |
|
|
ESP Associates, P.A. (ESP) |
|
|
originator |
|
| 1 |
EPSG Registry |
|
European Petroleum Survey Group |
|
|
publisher |
http://www.epsg-registry.org/ |
| 1 |
|
|
Fugro EarthData, Inc. |
|
|
originator |
|
| 1 |
|
Jim Scurry |
South Carolina Department of Natural Resources |
Technology Development Program Director |
scurryj@dnr.sc.gov |
pointOfContact |
|
| 1 |
Mike Sutherland(author) |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
author |
|
| 1 |
Mike Sutherland |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
distributor |
|
| 1 |
|
Pamela Grothe |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
|
processor |
|
| 1 |
|
|
South Carolina Department of Natural Resources |
|
|
originator |
|
| 1 |
|
|
South Carolina Department of Natural Resources (SCDNR) |
|
|
originator |
|
| 1 |
|
ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/sc/dillon/LiDAR_QAQC_Report_Dillon.pdf |
Lidar QA/QC Report |
|
information |
| 1 |
|
http://www.epsg-registry.org/ |
European Petroleum Survey Group Geodetic Parameter Registry |
Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured
dataset of Coordinate Reference Systems and Coordinate Transformations.
|
search |
| 1 |
|
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
NAD83 |
Link to Geographic Markup Language (GML) description of reference system. |
information |
| 1 |
|
Ellipsoid in Meters |
| 1 |
|
urn:ogc:def:crs:EPSG::4269 |
|
Bounding Box |
Temporal Extent |
| 1 |
|
|
-79.642290 |
-79.070922 |
34.624716 |
34.229750 |
2008-01-15 |
2008-02-10 |
| 1 |
|
|
|
|
|
|
2008-01-15 |
2008-02-10 |
| 1 |
|
|
|
|
|
|
|
|
| 1 |
|
|
|
|
|
|
|
|
| 1 |
|
-79.642290 |
-79.070922 |
34.624716 |
34.229750 |
| 2 |
|
2008-01-15 |
2008-02-10 |
| 3 |
|
|
|
| 1 |
Lidar Use Limitation |
These data depict the elevations at the time of the survey and are only
accurate for that time. 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. Any conclusions
drawn from analysis of this information are not the responsibility of NOAA
or any of its partners. These data are NOT to be used for navigational purposes.
|
| 1 |
Ellipsoid |
Ellipsoid in Meters |
|
| 1 |
NAD83 |
urn:ogc:def:crs:EPSG::4269 |
North American Datum 1983 |
| 1 |
|
Lidar QA/QC Report |
|
crossReference |
| 1 |
|
Aerial Acquisition of Lidar Data for 16 counties in the State of South Carolina |
2008-02-15 |
Source Contribution: Aerial Lidar Acquisition. The Fugro EarthData,
Inc. acquisition team of Fugro Horizons, Inc. and North West Group collected ALS50-II
derived lidar over 16 counties in the State of South Carolina with a 1.4m, nominal
post spacing using a Cessna 310 aircraft. The collection for the entire project area
was accomplished from January 15, 2008 through February 10, 2008 (Flight dates were
January 15, 16, 18, 20, 21, 25, 27, 28, 29, 30, 31 and February 2, 3, 4, 7, 8, 10).
The collection was performed using a Leica ALS50-II MPiA lidar system, serial numbers
ALS039 and ALS064, including an inertial measuring unit (IMU) and a dual frequency
GPS receiver. This project required 44 lifts of flight lines to be collected. The
lines were flown at an average of 6,000 feet above mean terrain using a maximum pulse
rate frequency of 112,000 pulses per second. The planned maximum baseline length was
50 miles. Source Type: external hard drive
|
| 1 |
|
Dillon County, SC - Digital Orthophotography |
|
Source Contribution: Countywide Orthophotos. The State of South Carolina,
Department of Natural Resources provided digital orthophotography covering the project
area in support of this project. Source Type: external hard drive
|
| 1 |
|
South Carolina Lidar, Quality Control Surveys, 16 Counties |
2008-01-31 |
Source Contribution: Ground Control. ESP under contract to Fugro EarthData,
Inc. successfully established ground control for Dillon County, SC. A total of 9 ground
control points in Dillon County, SC were acquired. GPS was used to establish the control
network. The horizontal datum was the North American Datum of 1983, 2007 adjustment
(NAD83/2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88).
Source Type: electronic mail system
|
| 1 |
|
2008-05-08T00:00:00 |
1. Lidar, GPS, and IMU data was processed together using lidar processing
software. 2. The lidar data set for each flight line was checked for project area
coverage and lidar post spacing was checked to ensure it meets project specifications.
3. The lidar collected at the calibration area and project area were used to correct
the rotational, atmospheric, and vertical elevation differences that are inherent
to lidar data. 4. Intensity rasters were generated to verify that intensity was recorded
for each lidar point. 5. Lidar data was transformed to the specified project coordinate
system. 6. By utilizing the ground survey data collected at the calibration site and
project area, the lidar data was vertically biased to the ground. 7. Comparisons between
the biased lidar data and ground survey data within the project area were evaluated
and a final RMSE value was generated to ensure the data meets project specifications.
8. Lidar data in overlap areas of project flight lines were trimmed and data from
all swaths were merged into a single data set. 9. The data set was trimmed to the
digital project boundary including an additional buffer zone of 50 feet (buffer zone
assures adequate contour generation from the DEM). 10.The resulting data set is referred
to as the raw lidar data.
|
| 1 |
|
2008-11-02T00:00:00 |
1. The raw lidar data was processed through a minimum block mean algorithm,
and points were classified as either bare earth or non-bare earth. 2. User developed
"macros" that factor mean terrain angle and height from the ground were used to determine
bare earth point classification. 3. The next phase of the surfacing process was a
2D edit procedure that ensures the accuracy of the automated feature classification.
4. Editors used a combination of imagery, intensity of the lidar reflection, profiles,
and tin-editing software to assess points. 5. The lidar data was filtered, as necessary,
using a quadric error metric to remove redundant points. This method leaves points
where there is a change in the slope of surfaces (road ditches) and eliminates points
from evenly sloped terrain (flat field) where the points do not affect the surface.
6. The algorithms for filtering data were utilized within Fugro EarthData's proprietary
software and commercial software written by TerraSolid. 7. The flight line overlap
points were merged back into filtered data set for delivery product. 8. The point
cloud data were delivered tiled in LAS 1.1 format; class 12 - flight line overlap
points, class 9 - points in water, class 8 - model-key points, class 2 - ground points,
and class 1 - all other.
|
| 1 |
|
2008-11-05T00:00:00 |
Lidar intensity images were generated in TerraSolid software. The
images are then brought up in Photoshop to see if a curve is needed to modify the
radiometrics and to ensure they match from group to group. Along with looking for
missing coverage and clipping to the boundary, the following steps are run in Photoshop:
1. Flip 0 values to 1 2. Change 3-band images to 1 band 3. Restore GeoTIFF headers.
The intensity images were delivered in GeoTIFF format.
|
| 1 |
|
2008-11-06T00:00:00 |
Tiled lidar LAS datasets are imported into a single multipoint geodatabase
featureclass. Only Ground and Model-Keypoint are imported. An ArcGIS geodatabase terrain
feature class is created using the terrain creation dialogue provided through ArcCatalog.
The multipoint featureclass is imported as mass point features in the terrain. An
overall tile boundary for the county is input as a soft clip feature for the terrain.
The terrain pyramid level resolutions and scales are automatically calculated based
on the point coverage for the county.
|
| 1 |
|
2009-09-01T00:00:00 |
The NOAA Coastal Services Center (CSC) received files in LAS format.
The files contained LiDAR intensity and elevation measurements. CSC performed the
following processing on the data to make it available within Digital Coast: 1. The
data were converted from State Plane, SPCS Zone 3900 coordinates to geographic coordinates.
2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03.
3. The LAS header fields were sorted by latitude and updated.
|
| 1 |
|
2011-07-06T00:00:00 |
The NOAA National Geophysical Data Center (NGDC) received lidar data
files via ftp transfer from the NOAA Coastal Services Center. The data are
currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/.
The data can be used to re-populate the system. The data are archived in LAS
or LAZ format. The LAS format is an industry standard for LiDAR data developed by
the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless
compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The
data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data
are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for
the ability to apply the most up to date geoid model when transforming to orthometric
heights.
|
|
