NCEI (formerly NGDC)
EMMA logo
Back to Collection NOAA/NESDIS/NGDC/MGG/Lidar
View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2009-2010 USACE Vicksburg District Lidar: Mississippi River Delta Phase I

browse graphicThis kmz file shows the extent of coverage for the 2009-2010 USACE Vicksburg District Mississippi River Delta (Phase I) lidar data set.
LiDAR collected at 1.0 points per square meter (1.0m GSD) for the entire portion of the Mississippi River Delta in the Vicksburg District. This area was flown during snow free and leaf-off conditions.
Cite this dataset when used as a source.
Other Access Online access information not available.
Distribution Formats
  • LAZ
Distributor DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Dataset Point of Contact Elijah C. Hunt
U.S. Army Corps of Engineers, Vicksburg District
(601) 631-7040
Documentation links not available.
  • publication: 2013-09-19
Data Presentation Form: Digital image
Dataset Progress Status Complete
Data Update Frequency: Unknown
Purpose: Classified LAS files are used to show the manually reviewed bare earth surface. Any additional classification is provided via automated macro functionality from proprietary Photo Science TerraScan macros. These additional classifications include Class 4 - Medium Vegetation and Class 5 - High Vegeation. This allows the user to create Intensity Images, Break Lines, Raster DEM, and Triangular Irregular Networks.
Use Limitations
  • 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.
  • While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • United State Army Corps of Engineers (USACE) Vicksburg District
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Time Period: 2009-02-19 to 2010-08-02
Spatial Reference System: urn:ogc:def:crs:EPSG::4269
Spatial Bounding Box Coordinates:
N: 35.080157
S: 32.301454
E: -89.726308
W: -91.247151
Spatial Coverage Map:
Theme keywords none
  • Bathymetry/Topography
  • LiDAR
  • Light Detection and Ranging
  • Model
  • LiDAR
  • DEM
  • Raster
  • Breaklines
  • Contours
  • TIN
  • Remote Sensing
Place keywords None
  • Mississippi
  • Warren County
  • Issaquena County
  • Yazoo County
  • Sharkey County
  • Holmes County
  • Humphreys County
  • Washington County
  • Sunflower County
  • Leflore County
  • Carroll County
  • Bolivar County
  • Grenada County
  • Tallahatchie County
  • Yalobusha County
  • Coahoma County
  • Quitman County
  • Panola County
  • Tunica County
  • Tate County
  • DeSoto County
  • US
Use Constraints No constraint information available
Fees Fee information not available.
Lineage information for: dataset
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • DOC/NOAA/NESDIS/NCEI > National Centers of Environmental Information, NESDIS, NOAA, U.S. Department of Commerce
Processing Steps
  • 2010-01-01T00:00:00 - Applanix software was used in the post processing of the airborne GPS and inertial data that is critical to the positioning and orientation of the sensor during all flights. POSPac MMS provides the smoothed best estimate of trajectory (SBET) that is necessary for Optech's post processor to develop the point cloud from the LiDAR missions. The point cloud is the mathematical three dimensional collection of all returns from all laser pulses as determined from the aerial mission. At this point this data is ready for analysis, classification, and filtering to generate a bare earth surface model in which the above ground features are removed from the data set. The point cloud was manipulated within the Optech or Leica software; GeoCue, TerraScan, and TerraModeler software was used for the automated data classification, manual cleanup, and bare earth generation from this data. Project specific macros were used to classify the ground and to remove the side overlap between parallel flight lines. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Class 2 LIDAR was used to create a bare earth surface model. The surface model was then used to heads-up digitize 2D breaklines of inland streams and rivers with a 30 foot nominal width and Inland Ponds and Lakes of 0.25 acres or greater. Elevation values were assigned to all Inland Ponds and Lakes using TerraModeler functionality. Elevation values were assigned to all Inland streams and rivers using Photo Science proprietary software. All Class 2 LIDAR data inside of the collected breaklines were then classified to Class 9 using TerraScan macro functionality. The breakline files were then translated to ESRI Shapefile and ARC Generate format using ESRI conversion tools. Breaklines were used to reclassify lakes, ponds, and inland drains. Data was then run through additional macros to ensure deliverable classification levels matching LAS ASPRS Classification structure. GeoCue functionality was then used to ensure correct LAS Version. In house software was used as a final QA/QC check to provide LAS Analysis of the delivered tiles. Buffered LAS files were created in GeoCue to provide overedge to the DEM creation. These tiles were then run through automated scripting within ArcMap and were combined with the Hydro Flattened Breaklines to create the 5' DEM. Final DEM tiles were clipped to the tile boundary in order to provide a seamless dataset. A manual QA review of the tiles was completed in ArcMap to ensure full coverage with no gaps or slivers within the project area.
  • 2013-09-19T00:00:00 - The NOAA Coastal Services Center (CSC) received the files in laz format. The files contained LiDAR elevation and intensity measurements. The data were in Mississippi State Plane West (2301, feet) coordinates and NAVD88 (Geoid03) vertical datum (feet). CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane (2301) coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid03. 3. The data were cleaned of bad elevations above 150 m and below 0 m, assumed to be errors points/noise. 4. The data were sorted by time.
  • 2013-12-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 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 ( 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.
Last Modified: 2013-12-06
For questions about the information on this page, please email: