NCEI (formerly NGDC)
EMMA logo
Back to Collection NOAA/NESDIS/NGDC/MGG/Lidar
View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2008 USGS South New Jersey County Project Lidar: Portion of Salem County

browse graphicThis kmz file shows the extent of coverage for the 2008 USGS Salem County, NJ lidar data set.
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
Cite this dataset when used as a source.
Online Access
  • Online access is not available for this resource
Distribution Formats
  • LAZ
Distributor DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Dataset Point of Contact Roger Barlow
USGS Geospatial Liason for DC, DE, MD, NJ, and Chesapeake Bay
U.S. Geological Survey
Documentation links not available.
  • publication: 2010-08-01
Data Presentation Form: Digital image
Dataset Progress Status Complete
Data Update Frequency: Unknown
Supplemental Information:
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,500Hz (73.5 KHz), collecting four returns per pulse. The scan rate was be set at 42Hz. 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 ( 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. Data delivered from vendor as LiDAR point data in LAS 1.1; ASPRS classification scheme: Class 1 - Unclassified; Class 2 - Bare Earth Ground; Class 9 - Water; Class 12 - Overlap.
Purpose: 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.
Use Limitations
  • These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • DOI/USGS > United States Geological Survey, U.S. Department of the Interior
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Time Period: Unknown to Unknown
Spatial Reference System: urn:ogc:def:crs:EPSG::4269 Ellipsoid in Meters
Spatial Bounding Box Coordinates:
N: 39.692673
S: 39.354456
E: -75.391667
W: -75.561039
Spatial Coverage Map:
Theme keywords
  • Bathymetry/Topography
  • Light Detection and Ranging
  • LiDAR
Place keywords
  • US
  • New Jersey
  • Salem County
Use Constraints No constraint information available
Fees Fee information not available.
Lineage information for: dataset
  • Dewberry - Geospatial Services Group
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
Processing Steps
  • 2008-07-15T00:00:00 - 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-01T00:00:00 - 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.
  • 2010-07-01T00:00:00 - The NOAA Coastal Services Center (CSC) received files in LAS format. The files contained LiDAR intensity and elevation measurements. CSC 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.
  • 2011-05-03T00:00:00 - The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg ( The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.
Last Modified: 2013-06-05
For questions about the information on this page, please email: