ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2006_NJ_Middlesex_m549
MD_DataIdentification
| 1 |
|
2006 FEMA New Jersey Flood Mitigation Lidar: Middlesex County
|
LIDAR data is remotely sensed high-resolution elevation data collected by
an airborne collection platform. By positioning laser range finding with the use of
1 second GPS with 100hz inertial measurement unit corrections Terrapoint's LIDAR instruments
are able to make highly detailed geospatial elevation products of the ground, man-made
structures and vegetation. The LiDAR flightlines for this project were planned for
a 50% acquisition overlap. The nominal resolution of this project without overlap
is 1.37m spacing, but effectively is 2.74m with overlap factored. Four returns were
recorded for each pulse in addition to an intensity value. GPS Week Time, Flightline
number and scan angle attributes were provided for each LiDAR point. Data is provided
as random points, in LAS v1.0 format, classified according to ASPRS Class Code 1=
Undefined, 2=Ground.
|
SV_Identification
| 1 |
|
2006 FEMA New Jersey Flood Mitigation Lidar: Middlesex County |
|
|
| 2 |
|
None |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 1 |
|
|
|
|
|
resourceProvider |
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
| 2 |
|
Claude Vickers |
Terrapoint USA |
Production Manager |
claude.vickers@terrapoint.com |
processor |
|
| 1 |
|
|
DHS/FEMA > Federal Emergency Management Agency, U.S. Department of Homeland Security |
|
|
originator |
|
| 1 |
NOAA CSC (originator) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
originator |
|
| 1 |
NOAA CSC (publisher) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
publisher |
|
| 1 |
NOAA CSC(distributor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
distributor |
|
| 1 |
NOAA CSC (processor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
processor |
|
| 1 |
EPSG Registry |
|
European Petroleum Survey Group |
|
|
publisher |
http://www.epsg-registry.org/ |
| 1 |
|
|
Federal Emergency Management Agency, Region II |
|
|
pointOfContact |
|
| 1 |
Mike Sutherland(author) |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
author |
|
| 1 |
Mike Sutherland |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
distributor |
|
| 1 |
|
Pamela Grothe |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
|
processor |
|
| 1 |
|
http://www.epsg-registry.org/ |
European Petroleum Survey Group Geodetic Parameter Registry |
Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured
dataset of Coordinate Reference Systems and Coordinate Transformations.
|
search |
| 1 |
|
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
NAD83 |
Link to Geographic Markup Language (GML) description of reference system. |
information |
| 1 |
|
Ellipsoid in Meters |
| 1 |
|
urn:ogc:def:crs:EPSG::4269 |
|
Bounding Box |
Temporal Extent |
| 1 |
|
|
-74.632358 |
-74.201558 |
40.610366 |
40.249866 |
2006-10-08 |
2006-10-11 |
| 1 |
|
-74.632358 |
-74.201558 |
40.610366 |
40.249866 |
| 1 |
Lidar Use Limitation |
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.
|
| 1 |
Ellipsoid |
Ellipsoid in Meters |
|
| 1 |
NAD83 |
urn:ogc:def:crs:EPSG::4269 |
North American Datum 1983 |
| 1 |
|
2006-10-01T00:00:00 |
-General Overview: The Airborne LiDAR survey was conducted using an
OPTECH 3100EA flying at a nominal height of 1550 meters AGL with a total angular coverage
of 40 degrees. Flight line spacing was nominally 564 meters, providing overlap of
50% on adjacent flight lines. All of the lines were flown in a north/south direction
for the project. -Aircraft A Piper Navajo, registration C-GPJT, was used for the survey.
This aircraft has a flight range of approximately 4.5 hours and was flown at an average
altitude of 1550 meters AGL (Above Ground Level), thereby encountering flying altitudes
of approximately 1550 meters above Mean Sea Level (MSL). The aircraft was staged from
the Linden, NJ Airport, and ferried daily to the project site for flight operations.
-GPS Receivers A combination of Sokkia GSR 2600 and NovAtel DL-4+ dual frequency GPS
receivers were used to support the airborne operations of this survey and to establish
the GPS control network. -Number of Flights and Flight Lines A total of 4 missions
were flown for this project with flight times ranging approximately 16.25 hours under
good meteorological and GPS conditions. 55 flight lines were flown over the project
area to provide complete coverage. Lines were flown at 564 meter spacing to achieve
50% lateral overlap.
|
| 1 |
|
2006-11-01T00:00:00 |
-Airborne GPS Kinematic Airborne GPS kinematic data was processed
on-site using GrafNav kinematic On-The-Fly (OTF) software. Flights were flown with
a minimum of 6 satellites in view (13 degrees above the horizon) and with a PDOP of
better than 4.5. Distances from base station to aircraft were kept to a maximum of
35 km, to ensure a strong OTF (On-The-Fly) solution. For all flights, the GPS data
can be classified as excellent, with GPS residuals of 5 cm average but no larger than
8 cm being recorded. -Calculation of 3D laser points (raw data) The post-processing
software o derive X,Y,Z values from roll, pitch, yaw and range is Optech's Realm.
-Classification and Editing The data was processed using the software TerraScan, and
following the methodology described herein. The initial step is the setup of the TerraScan
project, which is done by importing client provided tile boundary index encompassing
the entire project areas. The 3D laser point clouds, in binary format, were imported
into the TerraScan project and divided in 425 tiles, as per the contract specifications.
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 an iteration. A critical parameter is the maximum
terrain angle constraint, which determines the maximum terrain angle allowed within
the classification model. The data is then manually quality controlled with the use
of hillshading, cross-sections and profiles. Any points found to be of class vegetation,
building or error during the quality control process, are removed from the ground
model and placed on the appropriate layer. An integrity check is also performed simultaneously
to verify that ground features such as rock cuts, elevated roads and crests are present.
Once data has been cleaned and complete, it is then reviewed by a supervisor via manual
inspection and through the use of a hillshade mosaic of the entire project area. -Projection
Transformation The data was processed in the native UTM zone in meters and then transformed
to the New Jersey State Plane final projection system and US survey feet using an
in-house transformation software which utilizes Corpscon DLL.
|
| 1 |
|
2010-09-25T00:00:00 |
The NOAA Coastal Services Center (CSC) received the files in las format.
The files contained Lidar elevation and intensity measurements. The data were in projected
in New Jersey State Plane (NAD83) coordinates, and referenced to the orthometric datum
NAVD88 using Geoid 03. CSC performed the following processing to the data to make
it available within the Digital Coast: 1. The data were converted from New Jersey
State Plane (NAD83) coordinates to geographic coordinates (NAD83). 2. The data were
converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid
03. 3. The LAS data were sorted by latitude and the headers were updated.
|
| 1 |
|
2011-05-13T00: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 http://www.csc.noaa.gov/digitalcoast/.
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 (http://www.laszip.org/). 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.
|
|
