Short Citation:
Office for Coastal Management, 2021: 2005 Hancock and Jackson Counties, Mississippi LiDAR, https://www.fisheries.noaa.gov/inport/item/48195.

Item Identification

Title: 2005 Hancock and Jackson Counties, Mississippi LiDAR
Short Name: ms2005_m26_metadata
Status: Completed
Publication Date: 2006-10-19
Abstract:

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

Purpose:

These data were originally collected to support flood plain mapping and other coastal management applications.

Notes:

10218

Supplemental Information:

The 2005 Hancock and Jackson Counties, MS LiDAR Data Validation Report may be viewed at:

https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/26/supplemental

Keywords

Theme Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Science Keywords Earth Science > Land Surface > Topography > Terrain Elevation > Topographical Relief Maps
Global Change Master Directory (GCMD) Science Keywords Earth Science > Oceans > Bathymetry/Seafloor Topography > Seafloor Topography
Global Change Master Directory (GCMD) Science Keywords Earth Science > Oceans > Coastal Processes > Coastal Elevation
ISO 19115 Topic Category elevation
None Bathymetry/Topography
None Beach
None DEM
None Digital elevation model
None Elevation
None Erosion
None Laser
None Lidar

Spatial Keywords

Thesaurus Keyword
Geographic Names Information System Hancock County
Geographic Names Information System Jackson County
Geographic Names Information System Mississippi
Geographic Names Information System US
Global Change Master Directory (GCMD) Location Keywords Continent > North America > United States Of America > Mississippi

Physical Location

Organization: Office for Coastal Management
City: Charleston
State/Province: SC

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: None Planned
Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the OCM or

its partners.

Support Roles

Data Steward

CC ID: 624380
Date Effective From: 2006-10-19
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Distributor

CC ID: 624382
Date Effective From: 2006-10-19
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Metadata Contact

CC ID: 624383
Date Effective From: 2006-10-19
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Point of Contact

CC ID: 624381
Date Effective From: 2006-10-19
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Extents

Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 624386
W° Bound: -89.695649
E° Bound: -88.388259
N° Bound: 30.740893
S° Bound: 30.169006

Extent Group 1 / Time Frame 1

CC ID: 624385
Time Frame Type: Range
Start: 2005-02-25
End: 2005-03-01

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer;

Data Access Constraints:

None

Data Use Constraints:

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.

Distribution Information

Distribution 1

CC ID: 743908
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=26
Distributor:
File Name: Customized Download
Description:

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

Distribution 2

CC ID: 743909
Download URL: https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/26
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

CC ID: 743911
URL: https://coast.noaa.gov/dataviewer
URL Type:
Online Resource

URL 2

CC ID: 743912
URL: https://coast.noaa.gov
URL Type:
Online Resource

Activity Log

Activity Log 1

CC ID: 624405
Activity Date/Time: 2016-05-23
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 624404
Activity Date/Time: 2017-11-14
Description:

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.

Activity Log 3

CC ID: 717904
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 743910
Activity Date/Time: 2018-03-13
Description:

Partial upload to move data access links to Distribution Info.

Data Quality

Accuracy:

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).

Horizontal Positional Accuracy:

The lidar data fully comply with FEMA guidance as published in Appendix A, February, 2002.

Vertical Positional Accuracy:

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.

Completeness Measure:

Cloud Cover: 0

Completeness Report:

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.

Conceptual Consistency:

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).

Lineage

Sources

Aerial Lidar Acquisition over Jackson County, MS

CC ID: 624370
Contact Name: EarthData Aviation, LLC
Publish Date: 2005-03-01
Extent Type: Range
Extent Start Date/Time: 2005-02-25
Extent End Date/Time: 2005-03-01
Source Contribution:

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

CC ID: 624368
Contact Name: EarthData International
Publish Date: 2005-11-04
Extent Type: Range
Extent Start Date/Time: 2005-03-01
Extent End Date/Time: 2005-11-01
Source Contribution:

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

CC ID: 624369
Contact Name: Kevin J. Chappell
Publish Date: 2005-06-23
Extent Type: Range
Extent Start Date/Time: 2005-03-01
Extent End Date/Time: 2005-06-22
Source Contribution:

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

Process Steps

Process Step 1

CC ID: 624371
Description:

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.

Process Date/Time: 2005-11-03 00:00:00

Process Step 2

CC ID: 624372
Description:

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.

Process Date/Time: 2006-11-02 00:00:00

Process Step 3

CC ID: 624373
Description:

For data management purposes, the Office for Coastal Management converted the data from NAVD88 elevations to ellipsoid

elevations using Geoid 03.

Process Date/Time: 2008-01-01 00:00:00

Catalog Details

Catalog Item ID: 48195
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-14 14:19+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2019-07-02 15:17+0000
Metadata Record Published: 2018-03-13
Owner Org: OCM
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2019-03-14