Search Help Show/Hide Menu
Summary
Item Identification
Keywords
Physical Location
Data Set Info
Support Roles
Extents
Spatial Info
Access Info
Distribution Info
URLs
Activity Log
Data Quality
Lineage
Catalog Details

Summary

Browse Graphic

Short Citation
OCM Partners, 2024: 2012 FEMA Topographic Lidar: Hudson-Hoosic and Deerfield Watersheds, Massachusetts, https://www.fisheries.noaa.gov/inport/item/49774.
Full Citation Examples

Abstract

The Light Detection and Ranging (LiDAR) dataset is a survey of the Hudson-Hoosic and Deerfield project area. The entire survey area for Massachusetts is approximately 690 square miles. The LiDAR point cloud was flown at a nominal post spacing of 2.0 meters for unobscured areas. The LiDAR data and derivative products produced are in compliance with the U.S. Geological Survey National Geospatial Program LiDAR Guidelines and Base Specifications, Version 13-ILMF 2010. The flight lines were acquired by Northrop Grumman, Advanced GEOINT Solutions Operating Unit. Derivative products from the aerial acquisition include: high accuracy multiple return LiDAR data, both raw and separated into several classes, along with hydro flattening breaklines, bare earth DEM tiles, control points, and FGDC compliant XML metadata.

Distribution Information

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

  • LAS/LAZ - LASer

    Simple download of data files.

Access Constraints:

None

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.

Controlled Theme Keywords

elevation

Child Items

No Child Items for this record.

Contact Information

Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202

Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202

Extents

Geographic Area 1

-73.38316° W, -72.554743° E, 42.750152° N, 42.398132° S

Time Frame 1
2012-03-20
Time Frame 2
2012-03-30
Time Frame 3
2012-03-21
Time Frame 4
2012-03-27
Time Frame 5
2012-04-02
Time Frame 6
2012-04-03
Time Frame 7
2012-04-06
Time Frame 8
2012-04-07
Time Frame 9
2012-04-13
Time Frame 10
2012-04-14
Time Frame 11
2012-04-17
Time Frame 12
2012-04-18
Time Frame 13
2012-04-19
Time Frame 14
2012-04-20
Time Frame 15
2012-04-29
Time Frame 16
2012-04-30

Item Identification

Title: 2012 FEMA Topographic Lidar: Hudson-Hoosic and Deerfield Watersheds, Massachusetts
Short Name: ma2012_fema_deerfield_m2556_metadata
Status: Completed
Publication Date: 2013-10
Abstract:

The Light Detection and Ranging (LiDAR) dataset is a survey of the Hudson-Hoosic and Deerfield project area. The entire survey area for Massachusetts is approximately 690 square miles. The LiDAR point cloud was flown at a nominal post spacing of 2.0 meters for unobscured areas. The LiDAR data and derivative products produced are in compliance with the U.S. Geological Survey National Geospatial Program LiDAR Guidelines and Base Specifications, Version 13-ILMF 2010. The flight lines were acquired by Northrop Grumman, Advanced GEOINT Solutions Operating Unit. Derivative products from the aerial acquisition include: high accuracy multiple return LiDAR data, both raw and separated into several classes, along with hydro flattening breaklines, bare earth DEM tiles, control points, and FGDC compliant XML metadata.

Purpose:

The purpose of this project was to produce a high resolution LiDAR data set of approximately 2,895 square miles over the Hudson-Hoosic and Deerfield

Watersheds in New York.

Notes:

10418

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
None LAZ
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,10,14)

Entity Attribute Detail Citation:

none

Distribution Liability:

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

Data Set Credit: Please credit FEMA and Northrop Grumman for all products derived from this data.

Support Roles

Data Steward

CC ID: 676468
Date Effective From: 2013-10
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: 676470
Date Effective From: 2013-10
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: 676471
Date Effective From: 2013-10
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: 676469
Date Effective From: 2013-10
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: 1134554
W° Bound: -73.38316
E° Bound: -72.554743
N° Bound: 42.750152
S° Bound: 42.398132

Extent Group 1 / Time Frame 1

CC ID: 1134538
Time Frame Type: Discrete
Start: 2012-03-20

Extent Group 1 / Time Frame 2

CC ID: 1134541
Time Frame Type: Discrete
Start: 2012-03-30

Extent Group 1 / Time Frame 3

CC ID: 1134539
Time Frame Type: Discrete
Start: 2012-03-21

Extent Group 1 / Time Frame 4

CC ID: 1134540
Time Frame Type: Discrete
Start: 2012-03-27

Extent Group 1 / Time Frame 5

CC ID: 1134542
Time Frame Type: Discrete
Start: 2012-04-02

Extent Group 1 / Time Frame 6

CC ID: 1134543
Time Frame Type: Discrete
Start: 2012-04-03

Extent Group 1 / Time Frame 7

CC ID: 1134544
Time Frame Type: Discrete
Start: 2012-04-06

Extent Group 1 / Time Frame 8

CC ID: 1134545
Time Frame Type: Discrete
Start: 2012-04-07

Extent Group 1 / Time Frame 9

CC ID: 1134546
Time Frame Type: Discrete
Start: 2012-04-13

Extent Group 1 / Time Frame 10

CC ID: 1134547
Time Frame Type: Discrete
Start: 2012-04-14

Extent Group 1 / Time Frame 11

CC ID: 1134548
Time Frame Type: Discrete
Start: 2012-04-17

Extent Group 1 / Time Frame 12

CC ID: 1134549
Time Frame Type: Discrete
Start: 2012-04-18

Extent Group 1 / Time Frame 13

CC ID: 1134550
Time Frame Type: Discrete
Start: 2012-04-19

Extent Group 1 / Time Frame 14

CC ID: 1134551
Time Frame Type: Discrete
Start: 2012-04-20

Extent Group 1 / Time Frame 15

CC ID: 1134552
Time Frame Type: Discrete
Start: 2012-04-29

Extent Group 1 / Time Frame 16

CC ID: 1134553
Time Frame Type: Discrete
Start: 2012-04-30

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/#/lidar/search/where:ID=2556

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

Distribution Information

Distribution 1

CC ID: 741269
Start Date: 2021-08-16
End Date: Present
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2556
Distributor: NOAA Office for Coastal Management (NOAA/OCM) (2013-10 - Present)
File Name: Customized Download
Description:

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

File Type (Deprecated): Zip
Compression: Zip

Distribution 2

CC ID: 741270
Start Date: 2021-08-16
End Date: Present
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2556/index.html
Distributor: NOAA Office for Coastal Management (NOAA/OCM) (2013-10 - Present)
File Name: Bulk Download
Description:

Simple download of data files.

File Type (Deprecated): LAZ
Distribution Format: LAS/LAZ - LASer
Compression: Zip

URLs

URL 1

CC ID: 741274
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2556/supplemental/ma2012_fema_deerfield_footprint.KMZ
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz
Description:

This graphic shows the lidar coverage for Berkshire and Franklin Counties, Massachusetts.

Activity Log

Activity Log 1

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

Date that the source FGDC record was last modified.

Activity Log 2

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

Partial upload of Positional Accuracy fields only.

Activity Log 4

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

Partial upload to move data access links to Distribution Info.

Data Quality

Horizontal Positional Accuracy:

There is not a systematic method of testing when testing horizontal accuracy in LiDAR. However this is tested during calibration of the sensor and is rechecked during the comparing of parallel and perpendicular flight lines. Additionally the horizontal accuracy is checked by collecting building corners during the survey. Lines are then digitized representing the building outline and the differences are measure from each individual survey point to the corner of the building outline. Stats are calculated to ensure horizontal tolerances are met. These measurements resulted in an RMSEr

of .21 meters and equals a RMSE accuracy of .36 meter horizontal accuracy at the 95 % confidence level. Accuracy defined by NSSDA at the 95 % confidence level would be multiplier by 1.7308 times the RMSE.

Quantitative Value: 0.36 meters, Test that produced the value: Value represent horizontal accuracy assessment at the 95% confidence interval. Units in meters.

Vertical Positional Accuracy:

The accuracy assessment was performed using the NSSDA standard method to compute the root mean square error (RMSE) based on a comparison of ground

control points (GCP) and DEM derived from the LiDAR dataset. Testing was performed prior to gridding of the filtered LiDAR data points and

construction of the 32-bit ESRI float grid format bare earth tiles. The RMSEz figure was used to compute the vertical National Standard for Spatial

Data Accuracy (NSSDA). A spatial proximity analysis was used to select edited LiDAR data points contiguous to the relevant GCPs. A search radius

decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size. Cumulative error results from the

errors inherent in the various sources of horizontal measurement. These sources include the airborne GPS, GCPs and the uncertainty of the accuracy

of the LiDAR data points. This accuracy is achieved prior to the subsampling that occurs through integration with the inertial measurement unit (IMU)

positions that are recorded. It is unclear at this time whether the initial accuracy is maintained. The horizontal accuracy of the GCPs is estimated

to be in the range of approximately .03 to .04 meters. Finally, sample size was considered. The specification for the National Standard for Spatial

Data Accuracy is a minimum of 20 points to conduct a statistically significant accuracy evaluation which provides a reasonable approximation of a

normal distribution. The intent of the NSSDA is to reflect the geographic area of interest and the distribution of error in the data set (Federal

Geographic Data Committee, 1998, Geospatial National Standard for Spatial Data Accuracy, Federal Geographic Data Committee Secretariat, Reston,

Virginia, p.3-4). Additional steps were taken to ensure the vertical accuracy of the LiDAR data including: Step 1: Precision Bore sighting (Check

Edge-matching) Step 2: Compare the LiDAR data to the Field Survey (The vertical accuracy requirements meet or exceed the required RMSEz of 12.5cm

and the vertical accuracy of 24.5cm at the 95% confidence level). Data collected under this task order exceeds the required National Standards for

Spatial Database Accuracy (NSSDA) accuracy standards. SVA accuracies at the 95th Percentile collected and tested, as target accuracies results as

follows: Tall Weeds Crops =0.22 meters, Fully Forested = 0.40 meters. Consolidated Vertical Accuracies (CVA) at the 95th Percentile =0.25 meters.

Final accuracy statement for this task order is as follows; FVA Tested 0.15 meters vertical accuracy at the 95% confidence level.

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

Value represents the Fundamental Vertical Accuracy (FVA) assessment at the 95% confidence interval. This represents the FVA checkpoints compared

against the derived DEM at the 95% confidence interval. Units in meters.

Completeness Report:

Ground Truth data was collected of the three major land cover classes representing 10% of the predominate vegetation dispersed within the area of

interest. 30 points were collected in each of the three predominate vegetation classes bare earth, tall weeds crops, and fully forested, points

collected in the trees vegetation class were collected with a Total Station. Pair of points was surveyed using the local NGS CORS network once completed

the total station is used to collect the forested vegetation class. A total station was used to collect all the shots collected in the forested vegetation

class, due to the limited GPS signal when working in and around tree canopy.

Conceptual Consistency:

The GPS survey was tied into the local NYSNet Realtime Network located in NEW York, and Vermont, and the KEYNet Realtime Network located in the

Northeast covering Massachusetts. These networks are networks of continuously operating GPS reference stations that allows for Realtime Kinematic

(RTK) capabilities within a realtime network (RTN). This allows for corrections to be applied to the points as they are being collected, eliminating

the need for an adjustment. As a quality control measure several check-in points consisting of NSRS published horizontal and vertical control points

were used as checks within the real-time networks used. The survey crew checked into these published points daily to validate the consistency of the

network. The NSRS published points also confirm that the project will meet the 5cm local network accuracy at the 95% confidence level. Data analysis

was accomplished by comparing ground truth checkpoints with LiDAR points from the derived DEM and reported three ways 1. FVA 2. SVA 3. CVA. Additionally

the FVA points were assessed against the TIN derived from the LAS LiDAR point cloud controlled and calibrated swath data to ensure they met the

required accuracy of 12.5cm RMSEz and 24.5cm at the 95% confidence interval.

Lineage

Process Steps

Process Step 1

CC ID: 1134531
Description:

The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey, laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collected by receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 40 km radius from the flight survey area.

Process Date/Time: 2012-04-30 00:00:00

Process Step 2

CC ID: 1134532
Description:

The ABGPS, IMU, and raw scans are integrated using proprietary software developed by Optech and delivered with the Optech System. The resultant file is in a LAS binary file format. The LAS version 1.2 file format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return number, intensity value, xyz, etc.). The resultant points are produced in the NAD83/2007 UTM 18 North Coordinate System, with units in Meters and referenced to the NAVD88 datum. The LiDAR mass points were processed in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as defined by the LAS 1.2 specification. The datasets were divided into a 1500 meter by 1500 meter tiling scheme. The tiles are contiguous, do not overlap, and are suitable for seamless topographic data mosaics that include no "no data" areas. The names of the tiles include numeric column and row designations and all files utilize the LAS file extension.

Process Date/Time: 2012-06-05 00:00:00

Process Step 3

CC ID: 1134533
Description:

The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters are applied as appropriate for the production of bare earth digital elevation models (DEMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces.

Process Date/Time: 2012-06-19 00:00:00

Process Step 4

CC ID: 1134534
Description:

Filtered and edited data are subjected to rigorous QA/QC, according to the Northrop Grumman, Advanced GEOINT Solutions Operating Unit Quality Control Plan and Procedures. A series of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is established by Northrop Grumman, Advanced GEOINT Solutions Operating Unit and GPS-derived ground control points (GCPs) in various areas of dominant and prescribed land cover. These points are coded according to land cover, surface material, and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment, as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error, and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA), according to Federal Geographic Data Committee (FGDC) specifications.

Process Date/Time: 2012-08-27 00:00:00

Process Step 5

CC ID: 1134535
Description:

The Bare Earth DEM was extracted from the raw LIDAR products and attributed with the bare earth elevation for each cell of the DEM. Bare Earth DEMs do not include buildings, vegetation, bridges or overpass structures in the bare earth model. Where abutments were clearly delineated, this transition occurred at the junction of the bridge and abutment. Where this junction was not clear, the extractor used their best estimate to delineate the separation of ground from elevated bridge surface. In the case of bridges over water bodies, if the abutment was not visible, the junction was biased to the prevailing stream bank so as not to impede the flow of water in a hydrographic model. Bare earth surface includes the top of water bodies not underwater terrain, if visible.

Process Date/Time: 2012-09-10 00:00:00

Process Step 6

CC ID: 1134536
Description:

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, and GPS week 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-10-01 00:00:00

Catalog Details

Catalog Item ID: 49774
GUID: gov.noaa.nmfs.inport:49774
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: 2023-10-17 16:12+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