Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2023: 2010 FEMA Lidar: Ozaukee County (WI),

Item Identification

Title: 2010 FEMA Lidar: Ozaukee County (WI)
Short Name: wi2010_fema_ozaukee_m5042_metadata
Status: Completed
Publication Date: 2011-01-31

The Ozaukee AOI consists of one area encompassing the entire county. Ground Control is collected throughout the AOI for use in the processing of LiDAR data to ensure data accurately represents the ground surface. QA/QC checkpoints, (FVA and CVA - see Ground Control process step for further information) also collected throughout the AOI, are used for independent quality checks of the processed LiDAR data.

LiDAR acquisition products include Pre- and Post- flight reports which contain information on the flightlines, equipment parameters, and other pertinent acquisition details. The LiDAR Point Cloud product consists of tiles of LAS points which are partially classified such that the bare earth points can be calibrated to the ground surface and tested via the independent QC to ensure the ground surface is accurately represented.

The LiDAR processing product consists of LAS points which are fully classified with the bare earth points tested via the independent QC to ensure the ground surface is accurately represented.


Provide high resolution terrain elevation and land cover elevation data. Terrain data is used to represent the topography of a watershed and/or floodplain environment and to extract useful information for hydraulic and hydrologic models.



Supplemental Information:

A footprint of this data set may be viewed in Google Earth at:

The preflight report of this data set may be viewed in Google Earth at:

The acquisition report of this data set may be viewed in Google Earth at:

The project report of this data set may be viewed in Google Earth at:

The survey report of this data set may be viewed in Google Earth at:


Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
None Land Surface

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
Data Presentation Form: las
Entity Attribute Overview:

LiDAR point data in LAS 1.2 format

Entity Attribute Detail Citation:


Distribution Liability:

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

Support Roles

Data Steward

CC ID: 693854
Date Effective From: 2011-01-31
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202


CC ID: 693856
Date Effective From: 2011-01-31
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202

Metadata Contact

CC ID: 693857
Date Effective From: 2011-01-31
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202

Point of Contact

CC ID: 693855
Date Effective From: 2011-01-31
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202


Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1137902
W° Bound: -88.060711
E° Bound: -87.787129
N° Bound: 43.547961
S° Bound: 43.190498

Extent Group 1 / Time Frame 1

CC ID: 1137901
Time Frame Type: Range
Start: 2010-10-31
End: 2010-11-23

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:;

Data Access Constraints:


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. These data depict the heights at the time of the survey and are only accurate for that time.

Acknowledgement of FEMA would be appreciated in products derived from these data. This digital data is produced for the purposes of updating/creating a DFIRM database.

Distribution Information

Distribution 1

CC ID: 743555
Download URL:
File Name: Customized Download

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

Distribution 2

CC ID: 743556
Download URL:
File Name: Bulk Download

Simple download of data files.



CC ID: 743558
URL Type:
Online Resource


CC ID: 743559
URL Type:
Online Resource


CC ID: 743560
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz

This graphic shows the lidar coverage for the 2010 project for the coastal region of Wisconsin in Ozaukee County.

Activity Log

Activity Log 1

CC ID: 693871
Activity Date/Time: 2017-05-24

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 693870
Activity Date/Time: 2017-11-14

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using '' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 718803
Activity Date/Time: 2018-02-08

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 743557
Activity Date/Time: 2018-03-13

Partial upload to move data access links to Distribution Info.

Data Quality

Vertical Positional Accuracy:

Deliverables were tested by for both vertical and horizontal accuracy. The vertical unit of the data file is in meters with 2-decimal point precision.; Quantitative Value: 0.051 meters, Test that produced the value: Calculated RMSEz from 21 RTK bare-earth points. See last page of the lidar report for clarity.; Quantitative Value: 0.223 meters, Test that produced the value: Consolidated Vertical Accuracy (CVA) equal to the 95th Percentile confidence level (RMSE[z] x 1.9600) calculated against the bare earth surface in all ground cover classes. Reported in meters.

Completeness Report:

Survey data have been checked for completeness, points have been collected in correct vegetation units, and distributed throughout the AOI. The terrain data have been checked for completeness against AOI polygons. No gaps as defined by FEMA Procedural Memo No. 61 are known to exist within the dataset.

Conceptual Consistency:

Survey data have been confirmed to be in proper units, coordinate systems and format. The terrain data have been confirmed as complete LAS format data files. Header files are in proper LAS format with content as specified by FEMA Procedural Memo No. 61.


Process Steps

Process Step 1

CC ID: 1137894

GPS based surveys were utilized to support both processing and testing of LiDAR data within FEMA designated Areas of Interest (AOIs). Geographically distinct ground points were surveyed using GPS technology throughout the AOIs to provide support for three distinct tasks.

Task 1 was to provide Vertical Ground Control to support the aerial acquisition and subsequent bare earth model processing. To accomplish this, survey-grade Trimble R-8 GPS receivers were used to collect a series of control points located on open areas, free of excessive or significant slope, and at least 5 meters away from any significant terrain break. Most if not all control points were collected at street/road intersections on bare level pavement.

Task 2 was to collect Fundamental Vertical Accuracy (FVA) checkpoints to evaluate the initial quality of the collected point cloud and to ensure that the collected data was satisfactory for further processing to meet FEMA specifications. The FVA points were collected in identical fashion to the Vertical Ground Control Points, but segregated from the point pool to ensure independent quality testing without prior knowledge of FVA locations by the aerial vendors.

Task 3 was to collect Consolidated Vertical Accuracy CVA) checkpoints to allow vertical testing of the bare-earth processed LiDAR data in different classes of land cover, including: Open (pavement, open dirt, short grass), High Grass and Crops, Brush and Low Trees, Forest, Urban. CVA points were collected in similar fashion as Control and FVA points with emphasis on establishing point locations within the predominant land cover classes within each AOI or Functional AOI Group. In order to successfully collect the Forest land cover class, it was necessary to establish a Backsight and Initial Point with the R8 receiver, and then employ a Nikon Total Station to observe a retroreflective prism stationed under tree canopy. This was necessary due to the reduced GPS performance and degradation of signal under tree canopy.

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

Process Step 2

CC ID: 1137895

The R-8 receivers were equipped with cellular modems to receive real-time correction signals from the Keystone Precision Virtual Reference Station (VRS) network encompassing the Region 1 AOIs. Use of the VRS network allowed rapid collection times (~3 minutes/point) at 2.54 cm (1 inch) initial accuracy.

All points collected were below the 8cm specification for testing 24cm, Highest category LiDAR data. To ensure valid in-field collections, an NGS monument with suitable vertical reporting was measured using the same equipment and procedures used for Control, FVA and CVA points on a daily basis. The measurement was compared to the NGS published values to ensure that the GPS collection schema was producing valid data and as a physical proof point of quality of collection. Those monument measurements are summarized in the Accuracy report included in the data delivered to FEMA.

20 FVA points and 15 additional CVA points across the group of AOIs were collected. 20 FVA points are necessary to allow testing to CE95 ? 1 point out of 20 may fail vertical testing and still allow the entire dataset to meet 95% accuracy requirements.In similar fashion, 20 CVA points are necessary to test to CE95 as discussed above. 15 CVA points were collected with the intention at the outset that 5 of the collected FVAs would perform double?duty as Open-class CVA points, to total 20 CVAs per AOI.

The following software packages and utilities were used to control the GPS receiver in the field during data collection, and then ingest and export the collected GPS data for all points: Trimble Survey Controller, Trimble Pathfinder Office.

The following software utilities were used to translate the collected Latitude/Longitude Decimal Degree HAE GPS data for all points into Latitude/Longitude Degrees/Minutes/Seconds for checking the collected monument data against the published NGS Datasheet Lat/Long DMS values and into UTM NAD83 Northings/Eastings: U.S. Army Corps of Engineers CorpsCon, National Geodetic Survey Geoid09 NAVD88.

MSL values were determined using the most recent NGS-approved geoid model to generate geoid separation values for each Lat/Long coordinate pair. In this fashion, Orthometric heights were determined for each Control, FVA and CVA point by subtracting the generated Geoid Separation value from the Ellipsoidal Height (HAE) for publication and use as MSL NAVD88(09).

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

Process Step 3

CC ID: 1137896

Using a Optech Gemini LiDAR system, 56 flight lines of highest density (Nominal Pulse Spacing of 1.0m) were collected over the Ozaukee area. A total of five missions were flown: November 11, 2010, November 15, 2010, 2 on November 16, 2010, November 23, 2010. Seven airborne global positioning system (GPS) base stations were used to support the LiDAR data acquisition: WIM5, SHAN, CHON, FOLA, WEBE, RASN, SIWI. Coordinates are available in the Post-Flight Aerial Acquisition Report.

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

Process Step 4

CC ID: 1137897

Raw airborne GPS and IMU data were extracted from Applanix CARD. The GPS data was differentially processed in PosGPS and integrated with the IMU data in PosPAC. The GPS/IMU data is processed in Applanix to derive a smoothed best estimate of trajectory (SBET).The SBET was used to reduce the LiDAR slant range measurements to derive the Return measurement for each LiDAR pulse for all LiDAR pulses within for each flight line. The coverage was imported into TerraScan and tiled into 1500m x 1500m tiles. An initial accuracy assessment is done using the ground point survey data. The data then is classified to extract a bare earth digital elevation model (DEM). Once all project data was imported and classified, the survey ground control data was imported again and calculated against the LAS Class 2 (Ground) data for an accuracy assessment. As a QC measure, a routine was used to generate accuracy statistical reports by comparison among LiDAR points, ground control, and triangulated irregular networks (TIN). Any systematic bias in the data is removed to meet or exceed the vertical accuracy requirements.

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

Process Step 5

CC ID: 1137898

The calibrated and filtered LiDAR point cloud was hand checked for accuracy. All points were placed in one of the following categories: 1 Unclassified, 2 Ground, 7 Noise, and 12 Overlap Points. Model Key points were then generated from the Ground points and placed in Category 8. Requested elevation values to were then provided to CompassData for their evaluation of the Consolidated Vertical Accuracy (CVA).

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

Process Step 6

CC ID: 1137899

The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 16 N, NAVD88 (orthometric) heights in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes:

1. The data were converted from UTM coordinates to geographic coordinates.

2. Erroneous elevations were removed.

3. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 09.

4. The LAS data were sorted by latitude and the headers were updated.

Process Date/Time: 2016-05-24 00:00:00

Catalog Details

Catalog Item ID: 50191
GUID: gov.noaa.nmfs.inport:50191
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:24+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