50110
2008 USGS South New Jersey County Project Lidar: Portion of Salem County
usgs2008_salem_m543_metadata
Data Set
Published / External
49401
Lidar - partner (no harvest)
Project
Completed
2010-08
The South New Jersey County Lidar Project is to provide LiDAR data for the New Jersey Department of Environmental Protection (NJ-DEP)
for Cape May, Cumberland, and part of Salem Counties in New Jersey. These datasets will be the initial acquisition to support
the United States Geological Survey (USGS) and the New Jersey Department of Environmental Protection (NJ-DEP). This LiDAR data set was
collected in April 2008 for the bay side of Salem County and covers 76 square miles. The data are classified as follows:
Class 1 - Unclassified/Extracted Features
Class 2 - Bare Earth, Ground
Class 9 - Water
Class 12 - Overlap
The South New Jersey County Lidar project is to provide LiDAR data for New Jersey Department of Environmental Protection (NJ-DEP).
This project acquired and produced high accuracy bare-earth processed LiDAR data in LAS format and 2.0-meter Digital Elevation
Models (DEMs) in ArcGrid format for approximately 874 square miles covering the 3 New Jersey counties of Cape May, Cumberland, and part
of Salem that is south and west of the Coastal Area Facility Review Act (CAFRA) line.
10754
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/543/supplemental/2008_USGS_South_NJ_Lidar_Salem_County.kmz
The following were the data acquisition parameters:
Technical Acquisition Parameters:
Utilizing Leica ALS50 II laser systems which can collect data at laser pulse rates up to 150 KHz, Photo Science flew the project
area at 5,000 feet AGL and utilized a 29 degree full-angle field of view. Flights were accomplished nominally at 115 knots
(ground speed) with a pulse rate of 73,500 Hz (73.5 KHz), collecting four returns per pulse. The scan rate was be set at 42 Hz.
These settings resulted in a swath of 2,586 feet with maximum along track and cross track spacing of 4.62 feet (1.41 meters).
Environmental Acquisition Conditions:
Leaf-Off, snow free, non-flood conditions, low tide.
Low tide: Acquisition was performed within a window of +/- 3 hours from mean low tide for the project area (flight windows that
occur twice a day, that are approximately six hours in length but could be longer depending on the lunar cycle). Low tide is defined
as when the height of tide is different from Mean Lower Low water by fifty percent (50%) of the tide range or less as predicted by the
National Oceanic and Atmospheric Administration (NOAA), National Oceanic Service (NOS) Center for Operational Oceanographic Product
and Services (http://www.co-ops.nos.noaa.gov/). All flight lines affected by tide stage were coordinated with predicted tides at
existing gauges at Cape May, Ship John Shoal, and Reedy Point.
Nominal Pulse density:
Average point density is 1.58 points per sq meter
Average point spacing is 0.8 meters, or 8 decimeters
Calibration procedures:
Photo Science has created a significant boresight facility at the Frankfort, KY airport where the Lidar platforms are stationed
when not in service. Boresighting at this facility takes place with our Lidar sensors at numerous times throughout the year.
Additionally, a mini-calibration site was established at the Millville Municipal Airport at the project site. Additional calibration
flights were conducted over this site to ensure accurate determination of the calibration parameters throughout the times of acquisition.
GPS:
Acquisition for this project was broken into three sub areas with base stations from the NGS database selected near the center of each
acquisition area to serve as control for all lifts. Ground based GPS receivers were occupied at these stations during all aerial collection.
The published NGS positions of these base stations and raw GPS observation data were used in the kinematic GPS post-processing of all
lifts to provide positioning for the point clouds produced for this project.
Maximum and mean differential baseline lengths:
Nominal Maximum base line distance = 20 Miles
Mean base line distance = 11 Miles
Geoid Model Used:
Geoid 03 was used for all elevation conversions to orthometric heights.
Reference System:
Horizontal: New Jersey State Plane Coordinate System, 1983 North American Datum, feet
Elevation in North American Vertical Datum of 1988 (NAVD88), meters
Theme
ISO 19115 Topic Category
elevation
Theme
Light Detection and Ranging
Office for Coastal Management
Charleston
SC
Data Set
Unknown
LAS
Attributes included: x, y, z to two significant digits; intensity and class as integers. Also includes echo return, time stamp, etc.
LiDAR point data in LAS 1.1; ASPRS classification scheme: Class 1 - Unclassified/Extracted Features; Class 2 - Bare Earth Ground;
Class 9 - water; Class 12 - overlap.
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or
its partners.
Acknowledgment of the U.S. Geological Survey would be appreciated for products derived from these data.
Data Steward
2010-08
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Distributor
2010-08
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Metadata Contact
2010-08
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Point of Contact
2010-08
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Ground Condition
-75.561039
-75.391667
39.692673
39.354456
Discrete
2008-04
Yes
Unclassified
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer;
None
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.
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=543
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/543/index.html
Bulk Download
Simple download of data files.
https://coast.noaa.gov
Online Resource
https://coast.noaa.gov/dataviewer
Online Resource
2016-05-23
Date that the source FGDC record was last modified.
2017-11-14
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.
2018-02-08
Partial upload of Positional Accuracy fields only.
2018-03-13
Partial upload to move data access links to Distribution Info.
The following aspects of the LiDAR data was verified during the course of the project processing:
-Data accuracy and errors
-Anomaly checks through full-feature hillshades and 3-D modeling
-Post automated classification Bare-earth verification
-Final quality control of deliverable products ensuring integrity, graphical quality
Compiled to meet 1 m horizontal accuracy
Independent accuracy testing was performed by Dewberry using 60 high accuracy quality control checkpoints distributed around Salem,
Cumberland, and Cape May County on near level open bare terrain, urban terrain and near level vegetated terrain. Dewberry uses testing
procedures consistent with those specified in the National Standard for Spatial Data Accuracy (NSSDA). Target equivalent to
2 ft contours: 0.363 m
FVA - Fundamental Vertical Accuracy in open terrain (RMSEz x 1.9600): 0.13 m;
CVA - Consolidated Vertical Accuracy (95th Percentile) all categories: 0.16 m;
SVA - Supplemental Vertical Accuracy (95th Percentile) in mixed vegetation: 0.18 m;
SVA - Supplemental Vertical Accuracy (95th Percentile) in urban: 0.12 m;
13 points are included inside the Salem dataset, the consolidated accuracy (95th Percentile all categories) for these points is 0.12 m.
; Quantitative Value: 0.13 meters, Test that produced the value:
National Standard for Spatial Data Accuracy.
Using NSSDA standards, this LiDAR dataset was tested 0.13 m fundamental vertical accuracy at 95% confidence level in open terrain
using RMSEz x 1.9600, compared to 0.363 m for 2 ft equivalent contour.
Data completeness and integrity was verified.
All LAS formatted LiDAR data are validated to ensure that data on delivery media is in correct physical format and is readable and correctly
georeferenced and projected. Note that LiDAR intensity is not calibrated or normalized.
LiDAR
Range
2008-04-08
2008-04-17
LiDAR points were used to produce the deliverables. | Source Geospatial Form: digital data | Type of Source Media: hard drive
1
Leica software was used in the post processing of the airborne GPS and inertial data that is critical to the positioning of the sensor
during all flights. This software suite includes Applanix's PosPac and Waypoint's GrafNav solutions. PosPac provides the smoothed best
estimate of trajectory (SBET) that is necessary for Leica's post processor to develop the point cloud from the LiDAR missions. The point
cloud is the mathematical three dimensional collection of all returns from all laser pulses as determined from the aerial mission.
At this point this data is ready for analysis, classification, and filtering to generate a bare earth surface model in which the above
ground features are removed from the data set.
The point cloud was manipulated within the Leica software; GeoCue, TerraScan, and TerraModeler software was used for the automated data
classification, manual cleanup, and bare earth generation from this data. Project specific macros were used to classify the ground and
to remove the side overlap between parallel flight lines. All data was manually reviewed and any remaining artifacts removed using
functionality provided by TerraScan and TerraModeler.
The project was tiled adhering to the State of New Jersey 5000'x 5000' tile schema and each tile was saved in LAS format 1.1 including
GPS time.
Note: The Julian date and year written in the LAS header is actually the file creation date and has no connection to the acquisition date.
However the GPS time (second of the week) is registered for each point in the LAS file and the week of acquisition can be deduced from
the file name which include the GPS week (1474 = week starting 04/06/2008; 1475 = week starting 04/13/2008). When an area includes data
from flightlines acquired over two different GPS weeks, separate files for the data captured in each of the weeks are delivered.
For example tile B18D14 has data from both weeks; therefore there are two separate files: B18D14_1474.LAS & B18D14_1475.LAS.
2008-07-15T00:00:00
2
A Terrascan macro was used to classify the Lidar points inside rivers and lakes from class 2 to class 9. This classification was
visually inspected by comparing the bare earth class against the hydro breaklines. Then the elevations were converted from feet to
meters to meet the final delivery specifications.
2008-07-01T00:00:00
3
The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements.
OCM performed the following processing on the data to make it available within Digital Coast:
1. The data were converted from New Jersey State Plane coordinates to geographic coordinates.
2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03.
3. The LAS header fields were sorted by latitude and updated.
2010-07-01T00:00:00
gov.noaa.nmfs.inport:50110
Anne Ball
2017-11-15T15:24:20
SysAdmin InPortAdmin
2022-08-09T17:11:39
2022-03-16
OCM Partners
OCMP
1002
Public
No
2022-03-16
1 Year
2023-03-16