48195 ms2005_m26_metadata Data Set Published / External 37231 Lidar Project Completed 2006-10-19 This metadata record describes the topographic mapping of Hancock and Jackson Counties, Mississippi during 2005. Using a combination of laser rangefinding, 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. This data was collected at submeter resolution to provide nominal 5m spacing of collected points. Multiple returns were recorded for each pulse in addition to an intensity value using a Leica ALS-50 Aerial Lidar Sensor. Original contact information: Contact Org: NOAA Office for Coastal Management Phone: 843-740-1202 Email: coastal.info@noaa.gov These data were originally collected to support flood plain mapping and other coastal management applications. 10218 The 2005 Hancock and Jackson Counties, MS LiDAR Data Validation Report may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/26/supplemental/index.html Theme Global Change Master Directory (GCMD) Science Keywords EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > TOPOGRAPHICAL RELIEF MAPS Theme Global Change Master Directory (GCMD) Science Keywords EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > SEAFLOOR TOPOGRAPHY Theme Global Change Master Directory (GCMD) Science Keywords EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION Theme ISO 19115 Topic Category elevation Spatial Global Change Master Directory (GCMD) Location Keywords CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MISSISSIPPI Theme Beach Theme Erosion Spatial Geographic Names Information System Hancock County Spatial Geographic Names Information System Jackson County Spatial Geographic Names Information System Mississippi Spatial Geographic Names Information System US Office for Coastal Management Charleston SC Data Set None Planned Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the OCM or its partners. Data Steward 2006-10-19 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Distributor 2006-10-19 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Metadata Contact 2006-10-19 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Point of Contact 2006-10-19 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Ground Condition -89.695649 -88.388259 30.740893 30.169006 Range 2005-02-25 2005-03-01 Yes Unclassified This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer; None Any conclusions drawn from analysis of this information are not the responsibility of NOAA or the Office for Coastal Management. 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. https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=26 Customized Download Create custom data files by choosing data area, product type, map projection, file format, datum, etc. https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/26/index.html Bulk Download Simple download of data files. https://coast.noaa.gov Online Resource https://coast.noaa.gov/dataviewer Online Resource 2016-05-23 Date that the source FGDC record was last modified. 2017-11-14 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. 2018-02-08 Partial upload of Positional Accuracy fields only. 2018-03-13 Partial upload to move data access links to Distribution Info. 1. Lidar data was collected and processed in accordance with FEMA guidance as published in Appendix A, February, 2002. 2. Lidar data at the interface between the land and ocean was collected (when possible) during periods when tides were predicted to be below mean lower low water. 3. Lidar data accuracy is in accordance with the National Standard for Spatial Data Accuracy (NSSDA). When compared to GPS survey grade points in generally flat non-vegetated areas, at least 95% of the positions have an error less than or equal to 36.3 cm (equivalent to root mean square error of 18.5 cm if errors were normally distributed). The lidar data fully comply with FEMA guidance as published in Appendix A, February, 2002. The lidar data fully comply with FEMA guidance as published in Appendix A, February, 2002 and National Standard for Spatial Accuracy (NSSDA). The vertical accuracy was tested following the National Standards for Spatial Data Accuracy. Based on a total of 32 points the average error between the bare earth LiDAR coverage and the control was 0.004 m with a root mean square error (RMSE) of 0.120 m. Cloud Cover: 0 1. EarthData's proprietary software, Checkedb, for verification against ground survey points. 2. Terrascan, for verification of automated and manual editing and final QC of products. Compliance with the accuracy standard was ensured by the placement of GPS ground control prior to the acquisition of lidar data. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical boresight adjustment. 2. The DTM (Digital Terrain Model) data were checked against the project control. 3. Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). Aerial Lidar Acquisition over Jackson County, MS 2005-03-01 Range 2005-02-25 2005-03-01 EarthData Aviation was contracted by EarthData International to collect ALS-50 Lidar data over Hancock and Jackson Counties, Mississippi. The project site was flown on February 25 and March 1, 10, 11, and 12 using its aircraft with tail number N2636P. Lidar data was captured using an ALS-50 Lidar system, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. Lidar was obtained at an altitude of 3,658 meters (12,000 feet) above mean terrain, at an average airspeed of 145 knots. Sensor pulse rate was set at 29,900 Hz with a field of view of 45 degrees and a scan rate of 17 Hz. Average swath width of the collected raw lines is 3,100 meters. Point spacing was 5 meters. Lidar data was recorded in conjunction with airborne GPS and IMU; the stationary GPS receiver was positioned over a control point located at the airport. Recorded digital data was shipped via external hard drive to the production facility for processing. During airborne data collection, an additional GPS receiver was in constant operation over a published National Geodetic Survey (NGS) control point at KHSA (Stennis International) Airport. The coordinate value for temporary control point STENNIS (BH2999) was determined by a network adjustment to CORS stations MOB1 and NDBC, both of which were tied to the project control network. During the data acquisition, the receivers collected phase data at an epoch rate of 1 Hz. All GPS phase data was post processed with continuous kinematic survey techniques using "On the Fly" (OTF) integer ambiguity resolution. The GPS data was processed with forward and reverse processing algorithms. The results from each process, using the data collected at the airport, were combined to yield a single fixed integer phase differential solution of the aircraft trajectory. | Source Geospatial Form: Model | Type of Source Media: Firewire Drive Final lidar point cloud data in LAS format 2005-11-04 Range 2005-03-01 2005-11-01 EarthData International under contract to the NOAA Office for Coastal Management collected, processed and delivered lidar point cloud data for Hancock and Jackson counties in Mississippi. | Source Geospatial Form: Diagram | Type of Source Media: Firewire drive Report of Survey - Hancock & Jackson Counties Mississippi 2005-06-23 Range 2005-03-01 2005-06-22 Kevin Chappell, of Terrasurv and under contract to EarthData International established at total of 40 survey points within Jackson and Hancock Counties, MS. The survey was completed in two phases; the first phase consisted of 8 lidar control points in southern Jackson County. The second phase consisted of 12 additional lidar control points in Jackson County and 20 new lidar control points in Hancock County. | Source Geospatial Form: Diagram | Type of Source Media: Electronic mail system 1 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 step-by-step breakdown of the process. 1. Using the lidar data set provided by EarthData, the technician performs calibrations on the data set. 2. Using the lidar data set provided by EarthData, 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 layer 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. 6. The final DEM was written to an ESRI grid format (.flt). 7. The point cloud data were also delivered in LAS format. 8. Project data was clipped to a 500-meter buffer outside of the official project boundary. 2005-11-03T00:00:00 2 The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements. OCM performed the following processing on the data to make it available within the LiDAR Data Retrieval Tool (LDART) 1. The las files were converted from UTM coordinates to Geographic coordinates. 2. The las header fields were sorted by latitude and updated. 2006-11-02T00:00:00 3 For data management purposes, the Office for Coastal Management converted the data from NAVD88 elevations to ellipsoid elevations using Geoid 03. 2008-01-01T00:00:00 gov.noaa.nmfs.inport:48195 Anne Ball 2017-11-14T14:19:59 SysAdmin InPortAdmin 2022-08-09T17:11:32 2022-03-16 Office for Coastal Management OCM 1002 Public No No 2022-03-16 1 Year 2023-03-16