ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2006_NJ_Hunterdon_m547
MD_DataIdentification
| 1 |
|
2006 FEMA New Jersey Flood Mitigation Lidar: Hunterdon County
|
This metadata record describes the lidar topographic elevation mapping of
Hunterdon County, NJ that occurred in July 2006. Products generated include lidar
point clouds in LAS 1.0 collected with a Leica ALS-50 Aerial Lidar Sensor.
|
SV_Identification
| 1 |
|
2006 FEMA New Jersey Flood Mitigation Lidar: Hunterdon County |
|
|
| 2 |
|
None |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 1 |
|
|
|
|
|
resourceProvider |
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
| 1 |
|
Angela R. Worley |
EarthData International |
Project Manager |
aworley@earthdata.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 |
|
|
-75.195215 |
-74.703495 |
40.787876 |
40.339414 |
|
|
| 1 |
|
-75.195215 |
-74.703495 |
40.787876 |
40.339414 |
| 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 |
|
2007-02-26T00:00:00 |
EarthData has developed a unique method for processing lidar data
to identify and remove elevation points falling on vegetation, buildings, and other
non-ground structures. The algorithms for filtering data were utilized within EarthData's
proprietary software and commercially available software written by TerraSolid. This
software suite of tools provides efficient processing for small to large scale projects
and has been incorporated into ISO 9001 compliant production workflows. The following
process was employed: - Using the lidar data provided by EarthData, the technician
performed calibrations of the data. - Using the lidar data provided by EarthData,
the technician performed a visual inspection of the data verify that the flight lines
overlap correctly. The technician also verified that there were no voids, and that
the data covered the project limits. The technician then selected a series of areas
from the data set and inspected them where adjacent flight lines overlapped. These
overlapping areas were merged and a process which utilizes ArcGIS 3D Analyst and EarthData's
proprietary software was run to detect and color code the differences in elevation
values and profiles. The technician reviewed these plots and located the areas that
contained systematic errors or distortions that were introduced by the lidar sensor.
- Identified systematic distortions were removed and the data were re-inspected. Corrections
and adjustments can involve the application of angular deflection or compensation
for curvature of the ground surface that can be introduced by crossing from one type
of land cover to another. - The lidar data for each flightline was trimmed for the
removal of the overlap areas between flightlines. The data was checked against a control
network to ensure that vertical requirements were maintained. Conversion to the client-specified
datum and projections were then completed. The lidar flightline datasets were then
tiled for batch processing and data management. - The initial batch processing removed
95% of points falling on vegetation. The algorithm also removed the points that fell
on the edges of hard features such as buildings, elevated roadways and bridges. -
The technician interactively processed the data using lidar editing tools. During
this final phase, the data was TINed based on desired thematic layers to evaluate
the automated classification previously performed. This allowed the technician to
quickly reclassify points from one layer to another and recreate the TIN surface to
see the effect of edits. Georeferenced images were toggled on and off to aid in identification
of problem areas. The data were also examined with an automated profiling tool to
aid in reclassification. - The final DEM was written to las 1.0. - The point cloud
data delivered in las 1.0
|
| 1 |
|
2010-09-22T00: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 projected
in New Jersey State Plane coordinates, and referenced to NAVD88 using Geoid 03. CSC
performed the following processing steps 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-04-28T00: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.
|
|
