National Geophysical Data Center (NGDC), NOAA Satellite and Information Service

View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2006 MDEQ Camp Shelby, MS Lidar Survey

browse graphicThis kmz file shows the extent of coverage for the 2006 MDEQ Camp Shelby, MS lidar data set.
This metadata record describes the acquisition and processing of bare earth lidar data, raw point cloud lidar data, lidar intensity data, and floodmap breaklines consisting of a total of 280 sheets for Camp Shelby, MS. The post-spacing for this project is 3-meter. This project was broken into 3 parts, Acquisition, Part A Processing, and Part B Processing. Acquisition was tasked by Mississippi Geographic Information, LLC (MGI); Work Order No. ED-5. Part A Processing was tasked by MGI; Work Order No. ED-7. Part B Processing was tasked by MGI; Work Order No. ED-8. EarthData International, Inc. (EarthData) is a member of MGI and was authorized to undertake this project in accordance with the terms and conditions of the Professional Services Agreement between MGI and the Mississippi Department of Environmental Quality (MDEQ), dated February 17, 2004, and in accordance with MGI Task Order No. 18a. This project is being delivered to the City of Hattiesburg, Camp Shelby, USGS, and MDEQ. Products developed for the City of Hattiesburg (City of 1. Final lidar data georeferenced to MS State Plane East Zone, NAD83, NAVD88, US Survey foot 2. Bare earth lidar data in ASCII format and LAS format 3. Raw point cloud lidar data in LAS format 4. Lidar intensity data in TIF format 5. Digital flight line index in ESRI-compatible format 6. Survey control report 7. Lidar processing report Products developed for Camp Shelby (Part A) include the 1. Final lidar data georeferenced to UTM Zone 16 North, NAD83, NAVD88, meters 2. Bare earth lidar data in ASCII format and LAS format 3. Raw point cloud lidar data in LAS format 4. Lidar intensity data in TIF format 5. Digital flight line index in ESRI-compatible format 6. Survey control report 7. Lidar processing report Products developed for USGS (Part A and Part B) include 1. Final lidar data georeferenced to MS State Plane East Zone, NAD83, NAVD88, US Survey foot 2. Bare earth lidar data in ASCII format and LAS format 3. Raw point cloud lidar data in LAS format 4. Lidar intensity data in TIF format 5. Digital flight line index in ESRI-compatible format 6. Survey control report 7. Lidar processing report Products developed for MDEQ (Part A and Part B) include 1. Final lidar data georeferenced to MS State Plane East Zone, NAD83, NAVD88, US Survey foot 2. Bare earth lidar data in ASCII format and LAS format 3. Raw point cloud lidar data in LAS format 4. Lidar intensity data in TIF format 5. Floodmap breaklines in ESRI shapefile format 6. Digital flight line index in ESRI-compatible format 7. Survey control report 8. Lidar processing report

Cite this dataset when used as a source.

Search and Download
    Distribution Formats
    • LAZ
    Distributor DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Point of Contact Mississippi Department of Environmental Quality
    601-961-5506
    Stephen_Champlin@deq.state.ms.us
    Associated Resources
    • Lidar Final Report
    Originator
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Originator
    • Mississippi Department of Environmental Quality
    Publisher
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Date(s)
    • publication: 2013-09-23
    Data Presentation Form: Digital image
    Dataset Progress Status Complete
    Data Update Frequency: Unknown
    Purpose: The acquisition, processing, and delivery of bare earth lidar data, raw point cloud lidar data, lidar intensity data, and floodmap breaklines covering Camp Shelby, MS was a coordinated effort between EarthData and MGI to support Mississippi Digital Earth Model (MDEM) and FEMA flood mapping requirements. Floodmap breaklines are intended to support DFIRM modeling and update only, and will be delivered to MDEQ for use on the DFIRM program.
    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.
    Time Period: 2006-03-26  to  2006-03-27
    Spatial Reference System: urn:ogc:def:crs:EPSG::4269 Ellipsoid in Meters
    Spatial Bounding Box Coordinates:
    N: 31.433926
    S: 30.648553
    E: -88.618893
    W: -89.654184
    Spatial Coverage Map:
    Themes
    • LiDAR
    • DEM
    • Topographic
    • bare earth
    • intensity image
    • LAS
    • Elevation
    • Model
    • LAZ
    • Remote Sensing
    Places
    • United States
    • Mississippi
    • Tupelo
    • Lamar County
    • Forrest County
    • Perry County
    • Stone County
    • Greene County
    • George County
    • Hattiesburg
    Use Constraints No constraint information available
    Fees Fee information not available.
    Source Datasets
    • Aerial Acquisition of Lidar Data for Camp Shelby, MS
      • Description of Source: Source Contribution: MGI requested the collection of lidar data over Camp Shelby, MS. In response EarthData acquired the data from March 21 to April 12, 2006 using its aircraft with tail number N62912. Lidar data was captured using an ALS50 lidar system, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. An additional GPS receiver was in constant operation over a National Geodetic Survey published point by EarthData at Hattiesburg- Bobby L. Chain Municipal Airport which was later tied into a local network by Waggoner Engineering, Inc. During the data acquisition, the receivers collected phase data at an epoch rate of 1 Hz. The solution from Camp Shelby, MS was found to be of high integrity and met the accuracy requirements for the project. These accuracy checks also verified that the data meets the guidelines outlined in FEMA's Guidelines. Source Type: DVD
      • Temporal extent used:  unknown  to 
    • Camp Shelby, Mississippi - Lidar Control
      • Description of Source: Source Contribution: Waggoner Engineering, Inc., under contract to EarthData successfully established ground control for Camp Shelby, MS. A total of 36 ground control points in Camp Shelby, MS were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum of 1983 (NAD83). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). Source Type: electronic mail system
      • Temporal extent used:  unknown  to 
    Lineage Statement Lineage statement not available.
    Processor
    • EarthData International, Inc.
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    • DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
    Processing Steps
    • EarthData has developed a unique method for processing lidar data to identify and remove elevation points falling on vegetation, buildings, and other aboveground structures. The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid. This software suite of tools provides efficient processing for small to large-scale, projects and has been incorporated into ISO 9001 compliant production work flows. The following is a 1. The technician performs calibrations on the data set. 2. The technician performed a visual inspection of the data to verify that the flight lines overlap correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the data set and inspected them where adjacent flight lines overlapped. These overlapping areas were merged and a process which utilizes 3-D Analyst and EarthData's proprietary software was run to detect and color code the differences in elevation values and profiles. The technician reviewed these plots and located the areas that contained systematic errors or distortions that were introduced by the lidar sensor. 3. Systematic distortions highlighted in step 2 were removed and the data was re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. 4. The lidar data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines. The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed. The lidar flight line data sets were then segmented into adjoining tiles for batch processing and data management. 5. The initial batch-processing run removed 95% of points falling on vegetation. The algorithm also removed the points that fell on the edge of hard features such as structures, elevated roadways and bridges. 6. The operator interactively processed the data using lidar editing tools. During this final phase the operator generated a TIN based on a desired thematic layers to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits. Geo-referenced images were toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification. 7. The final bare earth was written to an LAS 1.0 format and also converted to ASCII. 8. The point cloud data were delivered in LAS 1.0 format.
    • EarthData utilizes a combination of proprietary and COTS processes to generate intensity images from the lidar data. Intensity images are generated from the full points cloud (minus noise points) and the pixel width is typically matched to the post spacing of the lidar data to achieve the best resolution. The following steps are used to 1. Lidar point cloud is tiled to the deliverable tile layout. 2. All noise points, spikes, and wells are deleted out of the tiles. 3. An EarthData proprietary piece of software, EEBN2TIF is then used to process out the intensity values of the lidar. At this point, the pixel size is selected based on best fit or to match the client specification if noted in the SOW. 4. The software then generates TIF and TFW files for each tile. 5. ArcView is used to review and QC the tiles before delivery. 6. The lidar intensity data were delivered in TIF format.
    • The NOAA Coastal Services Center (CSC) received topographic files in .LAZ format. The files contained lidar elevation and intensity measurements. The data were received in Mississippi State Plane East (2301, feet) and NAVD88 vertical datum (feet). CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic laz files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09. 2. The topographic laz files were transformed from MS-SP 2301 to a Geographic Coordinate system (NAD83). 3. The topographic laz files were cleaned of high (460 m) and low (0 m) error points and variable length records (vlr) were removed. 4. The topographic las files' horizontal units were converted from feet to decimal degrees.
    • 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.

    Metadata Last Modified: 2013-10-17

    For questions about the information on this page, please email: mike.sutherland@noaa.gov