ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2005-2007_NE_Topobathy_m116
MD_DataIdentification
| 1 |
|
2005 - 2007 US Army Corps of Engineers (USACE) Topo/Bathy Lidar: Maine,
Massachusetts, and Rhode Island
|
MASSACHUSETTS AND RHODE ISLAND: The U.S. Army Corps of Engineers collects
(by themselves and contractors) and maintains LiDAR data including orthophotos in
coastal areas of the United States and its territories. The Corps acquires this data
in the course of performing its mission of Flood Control, Navigation, Environmental
Engineering, and support for the Army and others. Topographic LIDAR datasets were
collected using a SHOALS-1000T at 500m altitude, spot density of 2m x 1 m and sampling
rate 10kHz. Bathymetric data were collected using a SHOALS-1000T hydrographic laser
flying at 400m altitude, spot spacing 5m x 5m and 1kHz sampling rate. MA and RI Data
Date of Collection: Topo 20051111-20051202 Bathy: 20070527-20070601 MAINE: The U.S.
Army Corps of Engineers collects (by themselves and contractors)and maintains LiDAR
data including orthophotos in coastal areas of the United States and its territories.
Topographic LIDAR datasets were collected using a SHOALS-1000T at 500m altitude, spot
density of 2m x 1m and sampling rate of 10 kHz. Topo data were also collected with
a Leica ALS-50 sensor at 1600m altitude spot spacing of 1m x 1m spot spacing, and
133 kHz sampling rate. Bathymetric data were collected using a SHOALS-1000T hydrographic
laser flying at 400m altitude, spot spacing 5m x 5m and 1kHz sampling rate. ME Data
Date of Collection: Topo 20051019-20070806 Bathy: 20070606-20070611 This data is not
a bare earth dataset.
|
SV_Identification
| 1 |
|
2005 - 2007 US Army Corps of Engineers (USACE) Topo/Bathy Lidar: Maine, Massachusetts,
and Rhode Island
|
|
|
| 4 |
|
None |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 1 |
|
|
|
|
|
resourceProvider |
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
| 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 |
|
|
Fugro Pelagos, Inc. |
Hydrographic Lidar Technical Manager |
|
processor |
|
| 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 |
JALBTCX (originator) |
|
US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center
of eXpertise (JALBTCX)
|
Data Production Manager |
JALBTCX@usace.army.mil |
originator |
|
| 1 |
JALBTCX (pointOfContact) |
|
US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center
of eXpertise (JALBTCX)
|
Data Production Manager |
JALBTCX@usace.army.mil |
pointOfContact |
|
| 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 |
|
|
-71.944389 |
-69.714932 |
43.808611 |
41.133922 |
2005-11-11 |
2007-08-06 |
| 1 |
|
-71.944389 |
-69.714932 |
43.808611 |
41.133922 |
| 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 |
|
2008-04-29T00:00:00 |
FOR MASSACHUSETTS AND RHODE ISLAND DATA Acquisition LIDAR data were
acquired using a SHOALS-1000T. Sensor orientation was measured using a POS AV 410.
Prior to survey PDOP was checked and missions planned to avoid PDOP greater than 3.0.
During survey the plane was always within 30km of a GPS ground control point, to provide
a good quality position solution. Final positions were determined using a post-processed
inertially aided Kinematic GPS (KGPS) solution. GPS ground control data were acquired
at 1Hz. Data received by the airborne system were continually monitored for data quality
during acquisition operations. Display windows showed coverage and information about
the system status. In addition, center waveforms at 5Hz were shown. All of this information
allowed the airborne operator to assess the quality of data being collected. Data
were processed in the field to verify coverage and data quality. Processing SHOALS-1000T
data were processed using the SHOALS Ground Control System (GCS). The GCS includes
links to Applanix POSPac software for GPS and inertial processing, and IVS Fledermaus
software for data visualization, 3D editing and tie-line analysis. All data were processed
in NAD83 horizontal and vertical datum. Data were later converted to the NAVD88 vertical
datum using the GEOID03 model. Fugro in-house utilities were used to split the data
in to pre-defined boxes, each covering approximately 5km of shoreline. ASCII files
include Longitude, Latitude, UTM Zone, Easting (UTM), Northing, Elevation, Elevation
(NAD83), Date, Time, Intensity (Topo). FOR MAINE DATA Acquisition Lidar data were
acquired using a SHOALS-1000T. Sensor orientation was measured using a POS AV 410,
while images were acquired at 1Hz using a Duncantech DT4000 digital camera. Prior
to survey PDOP was checked and missions planned to avoid PDOP greater than 3.0. During
survey the plane was always within 30km of a GPS ground control point, to provide
a good quality position solution. Final positions were determined using a post-processed
inertially aided Kinematic GPS (KGPS) solution. GPS ground control data were acquired
at 1Hz. Topographic Data were also acquired using a Leica ALS-50 operated by Fugro
EarthData. Processing SHOALS data were processed using the SHOALS Ground Control System
(GCS). The GCS includes links to Applanix POSPac software for GPS and inertial processing,
and IVS Fledermaus software for data visualization, 3D editing and tie-line analysis.
ALS-50 data were processed the TerraSolid Terrascan software. Applanix POSPac software
was used for GPS and inertial processing. All data were processed in NAD83 horizontal
and vertical datum. Data were later converted to the NAVD88 vertical datum using the
GEOID03 model. Fugro in-house utilities were used to split the data in to pre-defined
boxes, each covering approximately 5km of shoreline. ASCII files include Longitude,
Latitude, UTM Zone, Easting (UTM), Northing, Elevation, Elevation (NAD83), Date, Time,
Intensity (Topo).
|
| 1 |
|
2009-04-20T00:00:00 |
The NOAA Coastal Services Center (CSC) received topo and hydro files
in ASCII format. The files contained Lidar elevation and intensity measurements. Both
the topo and hydro points were classed as 'never classified.' The data were provided
in Geographic coordinates and ellipsoid and orthometric heights. CSC performed the
following processing to the ellipsoid height data to make it available within the
Digital Coast: 1. LASEdit was used to convert the ASCII formatted files to las format.
2. Both the topo and the hydro points were classified as 'never classified.' Hydro
points were changed to class 11, 'water' and topo points were changed to 'unclassified.'
3. The LAS data were sorted by latitude and the headers were updated. 4. The data
were filtered to eliminate elevation outliers.
|
| 1 |
|
2011-03-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.
|
|
