Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2022: 2004 Harrison County, Mississippi Lidar Mapping, https://www.fisheries.noaa.gov/inport/item/49814.

Item Identification

Title: 2004 Harrison County, Mississippi Lidar Mapping
Short Name: ms2004_m39_metadata
Status: Completed
Publication Date: 2006-11-09
Abstract:

This metadata record describes the topographic mapping of Harrison County, Mississippi in March of 2004. Products

generated include lidar point clouds in .LAS format and lidar bare-earth elevation models in .LAS format using lidar collected

with a Leica ALS-40 Aerial Lidar Sensor.

Original contact information:

Contact Org: NOAA Office for Coastal Management

Phone: 843-740-1202

Email: coastal.info@noaa.gov

Purpose:

The mission of the Center is to support the environmental, social, and economic well being of the coast by linking people,

information, and technology. The data produced from this SOW are intended to support the local Coastal Zone Managers in their

decision-making processes. This data will be used for flood plain mapping and other coastal management applications.

Notes:

10458

Supplemental Information:

The Harrison County, MS LiDAR Quality Control Report may be viewed at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/39/supplemental/index.html

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
EDI Thesaurus Bathymetry/Topography
EDI Thesaurus Digital Elevation Model (DEM)
EDI Thesaurus Digital Terrain Model (DTM)
EDI Thesaurus Elevation and Derived Products
EDI Thesaurus Lidar
EDI Thesaurus Lidar Point Cloud
EDI Thesaurus Surface Model
EDI Thesaurus Terrain Model

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
Geographic Names Information System Harrison County
Geographic Names Information System Mississippi
Geographic Names Information System US

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: 678445
Date Effective From: 2006-11-09
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: 678447
Date Effective From: 2006-11-09
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: 678448
Date Effective From: 2006-11-09
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: 678446
Date Effective From: 2006-11-09
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: 1135946
W° Bound: -89.39
E° Bound: -88.81
N° Bound: 30.71
S° Bound: 30.28

Extent Group 1 / Time Frame 1

CC ID: 1135945
Time Frame Type: Range
Start: 2004-03-08
End: 2004-03-09

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:

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: 741493
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=39
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: 741494
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/39/index.html
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

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

URL 2

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

Activity Log

Activity Log 1

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

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 678464
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: 718386
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 741495
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). 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).

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

Harrison County, Mississippi, Lidar Acquisition Report

CC ID: 1135939
Publish Date: 2005-07-28
Extent Type: Range
Extent Start Date/Time: 2004-03-08
Extent End Date/Time: 2004-03-09
Source Contribution:

EarthData Aviation. was contracted by EarthData International to collect ALS-40 Lidar data over Harrison

County, Mississippi. The project site was flown on March 8th and 9th 2004 using a Horizons, Inc. aircraft with tail number

N97HC. Lidar data was captured using an ALS-40 Lidar system, including an inertial measuring unit (IMU) and a dual frequency

GPS receiver. Lidar was obtained at an altitude of 11,100 feet above mean terrain, at an average airspeed of 120 knots. Sensor

pulse rate was set at 20 kHz with a field of view of 45 degrees and a rate of 11.0 Hz. Average swath width of the collected

raw lines is 9,112.7 feet. 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 Gulfport airport. Recorded digital data was

shipped via external hard drive to the production facility for processing. During airborne data collection, an additional 46

GPS control points were established throughout the airport. 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

Report of Survey -Harrison County, Mississippi

CC ID: 1135940
Publish Date: 2005-01-27
Extent Type: Discrete
Extent Start Date/Time: 2005-01-24
Source Contribution:

Waggoner Engineering in contract to EarthData International established at total of 9 survey points within

Harrison County, MS.

| Source Geospatial Form: Diagram | Type of Source Media: Electronic mail system

Process Steps

Process Step 1

CC ID: 1135941
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 9001compliant 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 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-07-28 00:00:00

Process Step 2

CC ID: 1135942
Description:

The NOAA Office for Coastal Management (OCM) received LAS files containing the bared-earth elevation and intensity

data from URS. OCM performed the following processing on the data to make it available within the Lidar Data Retrieval Tool

(LDART):

1. The data were projected from MS State Plane coordinates to geographic decimal degrees using the General Cartographic

Transformation Package.

2. The data were sorted based on latitude.

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

Process Step 3

CC ID: 1135943
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: 49814
GUID: gov.noaa.nmfs.inport:49814
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:22+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2022-03-16
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16