Slide Menu
Search Help Show/Hide Menu
Short Citation:
Office for Coastal Management, 2022: 2005 Oahu/Maui Lidar Mapping Project, https://www.fisheries.noaa.gov/inport/item/48186.

Item Identification

Title: 2005 Oahu/Maui Lidar Mapping Project
Short Name: hi2005_m24_metadata
Status: Completed
Publication Date: 2006-10-18
Abstract:

LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. 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 over a portion of Maui and Oahu, Hawaii with a Leica ALS-40 Aerial Lidar Sensor. Multiple returns were recorded for

each pulse in addition to an intensity value.

Original contact information:

Contact Org: NOAA Office for Coastal Management

Phone: 843-740-1202

Email: coastal.info@noaa.gov

Purpose:

The purpose of this mapping project is to create and deliver digital terrain models (DTM), to support the environmental,

social, and economic well being of the coast by linking people, information, and technology. The data will support the local

Coastal Zone Managers in their decision-making processes.

Notes:

10209

Supplemental Information:

The 2003-2005 Hawaii Lidar Data Validation Report may be viewed at:

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

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
UNCONTROLLED
EDI Thesaurus Bathymetry/Topography
EDI Thesaurus DEM
EDI Thesaurus Digital Elevation Model
EDI Thesaurus Digital Terrain Model
EDI Thesaurus DTM
EDI Thesaurus Elevation and derived products
EDI Thesaurus Elevation model
EDI Thesaurus LIDAR
EDI Thesaurus Lidar Point Cloud
EDI Thesaurus Surface model

Spatial Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Location Keywords
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > HAWAII
Global Change Master Directory (GCMD) Location Keywords
OCEAN > PACIFIC OCEAN > CENTRAL PACIFIC OCEAN > HAWAIIAN ISLANDS > MAUI
Global Change Master Directory (GCMD) Location Keywords
OCEAN > PACIFIC OCEAN > CENTRAL PACIFIC OCEAN > HAWAIIAN ISLANDS > OAHU
UNCONTROLLED
Geographic Names Information System Hawaii
Geographic Names Information System Honolulu
Geographic Names Information System Maui
Geographic Names Information System Oahu
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: Unknown
Data Presentation Form: Model
Distribution Liability:

Any conclusions drawn from analysis of this information are not the responsibility of NOAA or the Office for Coastal Management or its partners.

Support Roles

Data Steward

CC ID: 624027
Date Effective From: 2006-10-18
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: 624029
Date Effective From: 2006-10-18
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: 624030
Date Effective From: 2006-10-18
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: 624028
Date Effective From: 2006-10-18
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: 1133835
W° Bound: -158.138
E° Bound: -156.565
N° Bound: 21.4
S° Bound: 20.769

Extent Group 1 / Time Frame 1

CC ID: 1133834
Time Frame Type: Range
Start: 2005-02-20
End: 2005-03-24

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

Simple download of data files.

URLs

URL 1

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

URL 2

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

Activity Log

Activity Log 1

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

Date that the source FGDC record was last modified.

Activity Log 2

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

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 743857
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 based upon NOAA CO-OPS tide predictions for the nearest tidal station.

3. Lidar data accuracy is in accordance with the National Standard for Spatial Accuracy (NSSDA). When compared to 63 GPS static

survey points in open non-vegetated areas, at least 95% of the positions have an error less than or equal to 31.8 cm

(equivalent to root mean square error of 16.2 cm).

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 63 GPS static survey points in open non-vegetated areas,

at least 95% of the positions have an error less than or equal to 31.8 cm (equivalent to root mean square error of 16.2 cm).

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 Maui, HI

CC ID: 1133826
Publish Date: 2005-03-24
Extent Type: Range
Extent Start Date/Time: 2005-03-16
Extent End Date/Time: 2005-03-24
Source Contribution:

EarthData Aviation was contracted by EarthData International to collect ALS-40 Lidar data over the west coast

of Maui, Hawaii. The project site was flown on March 16th and 24th of 2005, using aircraft N806CP. 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 762 meters (2,500 feet) above mean terrain, at an average airspeed of 130 knots. Sensor pulse rate was set at 20,000 Hz

with a field of view of 25 degrees and a rate of 17 Hz. Average swath width of the collected raw lines is 337 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 Kahului Airport. The control point with designation OGG ARP 2 and PID AA3608, is "A" Order horizontal with

Third Order Class II ellipsoid height. 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. An adjustment was made to the ellipsoid

height of the published point by Terrasurv to reflect Local Tidal Elevation. 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

Aerial Lidar Acquisition over Oahu, HI

CC ID: 1133827
Publish Date: 2005-03-13
Extent Type: Range
Extent Start Date/Time: 2005-02-20
Extent End Date/Time: 2005-03-13
Source Contribution:

EarthData Aviation was contracted by EarthData International to collect ALS-40 Lidar data over the coastal

area of Oahu, Hawaii. The project site was flown on February 20 and March 2, 3, 6, 12, 13 using its aircraft with tail number

N806CP. 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 762meters (2,500 feet) above mean terrain, at an average airspeed of 130

knots. Sensor pulse rate was set at 20,000 Hz with a field of view of 25 degrees and a scan rate of 17 Hz. Average swath width

of the collected raw lines is 338 meters. Point spacing was 2 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 Honolulu Airport. The

coordinate value for temporary control point "PHNL" was determined by a network adjustment to CORS stations EHN1 and HNLC,

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. An adjustment was made

to the ellipsoid height of the published point by Terrasurv to reflect Local Tidal Elevation. 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 - Maui, Hawaii

CC ID: 1133828
Publish Date: 2003-11-06
Extent Type: Discrete
Extent Start Date/Time: 2003-11-06
Source Contribution:

Kevin Chappell, of Terrasurv and under contract to EarthData International established 6 ground control points.

The points were surveyed using GPS for both vertical and horizontal coordinate values. The horizontal datum used was the North

American Datum of 1983 (Pacific Plate Fixed Realization, epoch 2002.0). The vertical datum used was a Local Tidal Datum.

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

Report of Survey - Oahu, Hawaii

CC ID: 1133829
Publish Date: 2003-11-05
Extent Type: Range
Extent Start Date/Time: 2003-11-04
Extent End Date/Time: 2003-11-05
Source Contribution:

Kevin Chappell, of Terrasurv and under contract to EarthData International established 30 ground control

points along the coastline of the island of Oahu and within a blocked area around Honolulu where the 2005 flight was flown.

The points were surveyed using GPS for both vertical and horizontal coordinate values. The horizontal datum used was the North

American Datum of 1983(Pacific Plate Fixed Realization, epoch 2002.0). The vertical datum used was a Local Tidal Datum.

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

Process Steps

Process Step 1

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

7. The final DEM was written to an ESRI grid format (.flt).

8. The point cloud data were also delivered in LAS format.

Process Date/Time: 2005-09-02 00:00:00

Process Step 2

CC ID: 1133831
Description:

The NOAA Office for Coastal Management (OCM) received LAS files containing the point cloud elevation data from

Earth Data, Inc. OCM performed the following processing on the data to make it available within the Lidar Data Retrieval

Tool (LDART):

1. Variable length header records were added to the LAS files to identify projection, datum and sort order.

2. The LAS files were sorted by latitude.

Process Date/Time: 2005-09-27 00:00:00

Process Step 3

CC ID: 1133832
Description:

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

ellipsoid elevations using Geoid 99.

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

Catalog Details

Catalog Item ID: 48186
GUID: gov.noaa.nmfs.inport:48186
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: 2022-08-09 17:11+0000
Metadata Record Published: 2022-03-16
Owner Org: OCM
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