2009 SCDRN Lidar: Florence County

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

Simple download of data files.

This graphic shows the lidar coverage for the 2009 lidar project covering Florence County, SC.

Date that the source FGDC record was last modified.

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.

Partial upload of Positional Accuracy fields only.

Partial upload to move data access links to Distribution Info.

This data is based on the Lidar Bare earth surface which has a nominal point spacing of 1.4 meters. The data is provided in tiled format and used as need within the Proprietary production process.

Final post-processing of LiDAR data involves several steps. The airborne GPS data was post-processed using Waypoint's GravNAVTM software (version 7.5). A fixed-bias carrier phase solution was computed in both the forward and reverse chronological directions. The data was processed for both base stations and combined. In the event that the solution worsened as a result of the combination of both solutions the best of both solutions was used to yield more accurate data. LiDAR acquisition was limited to periods when the PDOP was less than 3.2.

The GPS trajectory was combined with the raw IMU data and post-processed using Applanix Inc.'s POSPROC (version 4.3) Kalman Filtering software. This results in a two-fold improvement in the attitude accuracies over the real-time INS data. The best estimated trajectory (BET) and refined attitude data are then re-introduced into the LEICA ALS post processor for the Leica system to compute the laser point-positions. The trajectory is then combined with the attitude data and laser range measurements to produce the 3-dimensional coordinates of the mass points.

All return values are produced within ALS Post processing software for the Leica system. The multi-return information is processed to obtain the "Bare Earth Dataset" as a deliverable. All LiDAR data is processed using the binary LAS format 1.2 file format.

LiDAR filtering was accomplished using TerraSolid, TerraScan LiDAR processing and modeling software. The filtering process reclassifies all the data into classes with in the LAS formatted file based scheme set using the LAS format 1.2 specifications or by the client. Once the data is classified, the entire data set is reviewed and manually edited for anomalies that are outside the required guidelines of the product specification or contract guidelines, whichever apply. Table 1 indicates the required product specifications.

The coordinate and datum transformations are then applied to the data set to reflect the required deliverable projection, coordinate and datum systems as provided in the contract.

The client required deliverables are then generated. At this time, a final QC process is undertaken to validate all deliverables for the project. Prior to release of data for delivery, Sanborn's quality control/quality assurance department reviews the data and then releases it for delivery.

Upon completion of the production process, the data is merged into a single feature class for data delivery.

The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in State Plane Zone 3900, NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes:

1. The data were converted from State Plane coordinates to geographic coordinates.

2. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 03.

3. The LAS data were sorted by latitude and the headers were updated.

4. Duplicate/erroneous points were removed.