ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:wa2001_pslc_clallam_m2482
MD_DataIdentification
| 1 |
|
2001-2002 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Clallam
County, Washington
|
TerraPoint surveyed and created this data for the Puget Sound LiDAR Consortium
under contract with Clallam County. The data covers an area of approximately 524 square
miles that extends from the northeastern corner of the county to an area past Joyce.
It also cover an area in the vicinity of Forks to La Push.
|
SV_Identification
| 1 |
|
2001-2002 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Clallam County, Washington |
|
|
| 1 |
|
None |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 1 |
|
none |
|
|
| 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 |
|
Diana Martinez |
Puget Sound Regional Council |
Senior GIS Analyst |
dmartinez@psrc.org |
pointOfContact |
|
| 1 |
EPSG Registry |
|
European Petroleum Survey Group |
|
|
publisher |
http://www.epsg-registry.org/ |
| 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 |
Mike Sutherland (processor) |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
processor |
|
| 1 |
|
|
Puget Sound LiDAR Consortium |
|
|
originator |
|
| 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 |
|
|
-124.674942 |
-122.875000 |
48.192477 |
47.875679 |
2001-01-01 |
2002-01-01 |
| 1 |
|
-124.674942 |
-122.875000 |
48.192477 |
47.875679 |
| 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 |
|
|
Acquisition. Lidar data were collected in leaf-off conditions (approximately
1 November - 1 April) from a fixed-wing aircraft flying at a nominal height of 1,000
meters above ground surface. Aircraft position was monitored by differential GPS,
using a ground station tied into the local geodetic framework. Aircraft orientation
was monitored by an inertial measurement unit. Scan angle and distance to target were
measured with a scanning laser rangefinder. Scanning was via a rotating 12-facet pyramidal
mirror; the laser was pulsed at 30+ KHz, and for most missions the laser was defocussed
to illuminate a 0.9m-diameter spot on the ground. The rangefinder recorded up to 4
returns per pulse. Flying height and airspeed were chosen to result in an average
pulse spacing of about 1.5 meters in the along-swath and across-swath directions.
The data had 30% overlap from flightline to flightline.
|
| 1 |
|
|
Processing. GPS, IMU, and rangefinder data were processed to obtain
XYZ coordinates of surveyed points. For data acquired after January 2003 (NW Snohomish,
Mt Rainier, Darrington, and central Pierce projects), survey data from areas of swath
overlap were analysed to obtain best-fit in-situ calibration parameters that minimize
misfit between overlapping swaths. This reduces vertical inconsistency between overlappoing
swaths by about one-half. Heights were translated from ellipsoidal to orthometric
(NAVD88) datums via GEOID99
|
| 1 |
|
|
ASCII file generation All Point returns with all their attributes
were directly exported into ASCII files. These were first divided into USGS quarter
quads (3.25 minute by 3.25 minute) and then in 25 tiles per quarter quad.
|
| 1 |
|
2013-04-01T00:00:00 |
The NOAA Coastal Services Center (CSC) received topographic files
in ASCII .TXT format. The files contained lidar elevation measurements. The data were
received in Washington State Plane North Zone 4601, NAD83 coordinates and were vertically
referenced to NAVD88 using the Geoid99 model. The vertical units of the data were
feet. CSC performed the following processing for data storage and Digital Coast provisioning
purposes: 1. The ASCII .TXT files were converted to LAS version 1.2 using LAStools'
txt2las tool. 2. The "Total Number of Returns" value was not included in the ASCII
data. An artificial value of 4 total returns was given to each pulse. 3. The data
was filtered for erroneous elevations. 4. The topographic las files were converted
from orthometric (NAVD88) heights to ellipsoidal heights using Geoid99. 5. The topographic
las files were converted from a Projected Coordinate System (WA SP North) to a Geographic
Coordinate system (GCS). 6. The topographic las files' vertical units were converted
from feet to meters. 7. The topographic las files' horizontal units were converted
from feet to decimal degrees. 8. The data were converted to LAZ format.
|
| 1 |
|
2013-05-17T00: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.
|
|
