Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2023: 2010 U.S. Department of Agriculture- Natural Resources Conservation Service (USDA-NRCS) Topographic Lidar: Eastern Connecticut,

Item Identification

Title: 2010 U.S. Department of Agriculture- Natural Resources Conservation Service (USDA-NRCS) Topographic Lidar: Eastern Connecticut
Short Name: ct2010_usda_east_m2598_metadata
Status: Completed
Publication Date: 2013-11

Earth Eye collected LiDAR data for approximately 4,589 square kilometers that partially cover the Connecticut counties of Hartford, Tolland, Windham, Middlesex and New London. The nominal pulse spacing for this project

was no greater than 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 1-Unclassified, 2-Ground, 7-Noise, 9-Water. Dewberry produced 3D breaklines

and combined these with the final LiDAR data to produce seamless hydro flattened DEMs for the 4,840 tiles (1000 m x 1000 m) that cover the project area.


The purpose of this LiDAR data was to produce high accuracy 3D elevation products, including tiled LiDAR in LAS 1.2 format, 3D breaklines, and 1 m cell size hydro flattened Digital Elevation Models (DEMs). This data was produced

for the U.S. Corp of Engineers and USDA-NRCS Connecticut for use in projects dealing with conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling.



Supplemental Information:

A complete description of this dataset is available in the Final Project Report submitted to the both the U.S. Corp of Engineers and USDA-NRCS Connecticut. A copy of this report can be found here:

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


Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
None Bare earth
None Light Detection and Ranging

Physical Location

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

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: As Needed
Data Presentation Form: las
Entity Attribute Overview:

LiDAR points in LAZ format (ASPRS Class 1,2,7,9)

Entity Attribute Detail Citation:


Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of USDA-NRCS, USACE, Earth Eye, Dewberry, NOAA, the Office for Coastal Management or its partners.

Support Roles

Data Steward

CC ID: 671471
Date Effective From: 2013-11
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: 671473
Date Effective From: 2013-11
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: 671474
Date Effective From: 2013-11
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: 671472
Date Effective From: 2013-11
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: 1134906
W° Bound: -72.645174
E° Bound: -71.787609
N° Bound: 42.034505
S° Bound: 41.296986

Extent Group 1 / Time Frame 1

CC ID: 1134905
Time Frame Type: Range
Start: 2010-11-03
End: 2010-12-11

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.

Distribution Information

Distribution 1

CC ID: 740577
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: 740578
Download URL:
File Name: Bulk Download

Simple download of data files.



CC ID: 740580
URL Type:
Online Resource


CC ID: 740581
URL Type:
Online Resource


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

This graphic shows the lidar coverage for Hartford, Tolland, Windham, Middlesex and New London Counties, Connecticut.

Activity Log

Activity Log 1

CC ID: 671495
Activity Date/Time: 2016-05-23

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 671494
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: 718202
Activity Date/Time: 2018-02-08

Partial upload of Positional Accuracy fields only.

Activity Log 4

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

Partial upload to move data access links to Distribution Info.

Data Quality

Horizontal Positional Accuracy:

Lidar source compiled to meet 1 meter horizontal accuracy.; Quantitative Value: 1.0 meters, Test that produced the value:

Dewberry does not perform independent horizontal accuracy testing on the LiDAR. LiDAR vendors perform calibrations on the LiDAR sensor and compare data to adjoining flight lines to ensure LiDAR meets the 1 meter horizontal

accuracy standard at the 95% confidence level. Please see the final project report delivered to the US Corp of Engineers for more details. Units in meters.

Vertical Positional Accuracy:

The vertical accuracy of the LiDAR was tested by Dewberry with 62 independent survey checkpoints comprised of the following land cover classes: open terrain (22), grass/weeds/crops (20) and forest (20).

Checkpoints in open terrain were used to compute the Fundamental Vertical Accuracy (FVA). Project specifications required a FVA of 0.185 m based on a RMSEz (0.0925 m) x 1.9600. All checkpoints were used to compute the

Consolidated Vertical Accuracy (CVA).

; Quantitative Value: 0.09 meters, Test that produced the value:

Based on the vertical accuracy testing conducted by Dewberry, using NSSDA and FEMA methodology, vertical accuracy at the 95% confidence level (called Accuracyz) is computed by the formula RMSEz x 1.9600. The dataset for the

Connecticut LiDAR project satisfies the criteria: Lidar dataset tested 0.09 m vertical accuracy at 95% confidence level in open terrain, based on RMSEz (0.0925 m) x 1.9600.

Based on the vertical accuracy testing conducted by Dewberry, using NDEP and ASPRS methodology, consolidated vertical accuracy at the 95% confidence level is computed using the 95th percentile method. The dataset for the

Connecticut LiDAR project tested 0.17 m vertical accuracy at 95% confidence level in all land cover categories combined.

Completeness Report:

A visual qualitative assessment was performed to ensure data completeness and bare earth data cleanliness. No void or missing data, the bare earth surface is of good quality and data passes vertical accuracy specifications.

Conceptual Consistency:

Data covers the tile scheme provided for the project area.


Process Steps

Process Step 1

CC ID: 1134901

Data for the U.S. Corp of Engineers High Resolution LiDAR Data Acquisition & Processing for Portions of Connecticut project was acquired by Earth Eye, LLC.

The project area included approximately 1,741 contiguous square miles for portions of Connecticut including a buffer of 200 meters. LiDAR sensor data were collected with an Leica ALS60 sn146 LIDAR System. No imagery was

requested or delivered. The data was delivered in the UTM coordinate system, meters, zone 18, horizontal datum NAD83, vertical datum NGVD88, Geoid 09. Deliverables for the project included a raw (unclassified) calibrated LiDAR

point cloud, survey control, and a final control report.

The calibration process considered all errors inherent with the equipment including errors in GPS, IMU, and sensor specific parameters. Adjustments were made to achieve a flight line to flight line data match (relative

calibration) and subsequently adjusted to control for absolute accuracy. Process steps to achieve this are as follows:

Rigorous LiDAR calibration: all sources of error such as the sensor's ranging and torsion parameters, atmospheric variables, GPS conditions, and IMU offsets were analyzed and removed to the highest level possible. This method

addresses all errors, both vertical and horizontal in nature. Ranging, atmospheric variables, and GPS conditions affect the vertical position of the surface, whereas IMU offsets and torsion parameters affect the data horizontally.

The horizontal accuracy is proven through repeatability: when the position of features remains constant no matter what direction the plane was flying and no matter where the feature is positioned within the swath, relative

horizontal accuracy is achieved. Absolute horizontal accuracy is achieved through the use of differential GPS with base lines shorter than 25 miles. The base station is set at a temporary monument that is 'tied-in' to the CORS

network. The same position is used for every lift, ensuring that any errors in its position will affect all data equally and can therefore be removed equally. Vertical accuracy is achieved through the adjustment to ground control

survey points within the finished product. Although the base station has absolute vertical accuracy, adjustments to sensor parameters introduces vertical error that must be normalized in the final (mean) adjustment. The minimum

expected horizontal accuracy was tested during the boresight process to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA) for a Horizontal accuracy of 1 meter RMSE or better and a Vertical Accuracy of RMSE(z)

= 9.25 cm.

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

Process Step 2

CC ID: 1134902

Earth Eye delivered LiDAR swaths to Dewberry that were calibrated and projected to project specifications. Dewberry processed the data using GeoCue and TerraScan software. The initial step is the setup of the GeoCue project,

which is done by importing a project defined tile boundary index encompassing the entire project area. The acquired 3D laser point clouds, in LAS binary format, were imported into the GeoCue project and tiled according to the

project tile grid. Once tiled, the laser points were classified using a proprietary routine in TerraScan. This routine removes any obvious outliers from the dataset following which the ground layer is extracted from the point

cloud. The ground extraction process encompassed in this routine takes place by building an iterative surface model.

This surface model is generated using three main parameters: building size, iteration angle and iteration distance. The initial model is based on low points being selected by a "roaming window" with the assumption is that these

are the ground points. The size of this roaming window is determined by the building size parameter. The low points are triangulated and the remaining points are evaluated and subsequently added to the model if they meet the

iteration angle and distance constraints. This process is repeated until no additional points are added within iterations. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain

angle allowed within the classification model.

Dewberry utilizes a variety of software suites for data processing. After the initial ground classification, each tile was imported into Terrascan and a surface model was created to examine the ground classification. Dewberry

analysts visually reviewed the ground surface model and corrected errors in the ground classification such as vegetation, buildings, and bridges that were present following the initial processing. Dewberry analysts employ 3D

visualization techniques to view the point cloud at multiple angles and in profile to ensure that non-ground points are removed from the ground classification. After the ground classification corrections were completed, the

dataset was processed through a water classification routine that utilizes breaklines compiled by Dewberry to automatically classify hydro features. The water classification routine selects ground points within the breakline

polygons and re-classifies them as class 9, water.

The data was classified as follows:

Class 1 = Unclassified. This class includes vegetation, buildings, noise etc.

Class 2 = Ground

Class 7= Noise

Class 9 = Water

The LAS header information was verified to contain the following:

Class (Integer)

GPS Week Time (0.0001 seconds)

Easting (0.01 foot)

Northing (0.01 foot)

Elevation (0.01 foot)

Echo Number (Integer 1 to 4)

Echo (Integer 1 to 4)

Intensity (8 bit integer)

Flight Line (Integer)

Scan Angle (Integer degree)

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

Process Step 3

CC ID: 1134903

The NOAA Office for Coastal Management (OCM) received topographic files in LAS V1.2 format. The files contained lidar elevation measurements, intensity values, scan angle values, return information, flightline information,

and adjusted standard GPS time. The data were received in UTM Zone 18N, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were meters. OCM performed the

following processing for data storage and Digital Coast provisioning purposes:

1. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09.

2. The topographic las files were converted from a Projected Coordinate System (UTM Zone 18N) to a Geographic Coordinate System (NAD83).

3. The topographic las files' horizontal units were converted from meters to decimal degrees.

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

Catalog Details

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