ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2007_OR_Silver_Falls_m105
MD_DataIdentification
| 1 |
|
2007 Oregon Parks and Recreation Department Silver Falls State Park Lidar
|
The dataset represents the Lidar elevations for Silver Falls State Park in
Marion County, Oregon. The LiDAR data was collected during March 2007. This was a
leaf-off condition. The lidar data are multiple return and bare earth classified.
An Optech 3100 LiDAR system was mounted in a fixed-wing aircraft and flown 900 meters
above ground level (AGL). A pulse repetition frequency (PRF) of 71 kHz with at least
100% overlap (minimum 50% side-lap) was used. Greater than 8 points per square meter
and near nadir scan angles were used to increase penetration of vegetation to ground
surfaces. Ground level GPS and aircraft IMU were collected during the flight. In some
areas of heavy vegetation or forest cover, there may be relatively few ground points
in the LiDAR data. Elevation values for open water surfaces are not valid elevation
values because few LiDAR points are returned from water surfaces. Watershed Sciences,
Inc. collected the LiDAR and created this data set for Oregon Parks and Recreation.
|
SV_Identification
| 1 |
|
2007 Oregon Parks and Recreation Department Silver Falls State Park Lidar |
|
|
| 1 |
|
Lidar Final Report |
|
|
| 2 |
|
None |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 1 |
|
|
|
|
|
resourceProvider |
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
| 1 |
|
|
|
Citation URL |
|
|
ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/silver_falls/LiDAR_Report_Silver_Falls.pdf |
| 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 |
|
Ian Madin |
Oregon Department of Geology and Mineral Industries (DOGAMI) |
|
ian.madin@dogami.state.or.us |
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 |
|
|
Oregon Parks and Recreation Department |
|
|
originator |
|
| 1 |
|
Pamela Grothe |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
|
processor |
|
| 1 |
|
ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/silver_falls/LiDAR_Report_Silver_Falls.pdf |
Lidar Final Report |
|
information |
| 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 |
|
|
-122.693363 |
-122.578226 |
44.916888 |
44.819233 |
|
|
| 1 |
|
-122.693363 |
-122.578226 |
44.916888 |
44.819233 |
| 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 |
|
Lidar Final Report |
|
crossReference |
| 1 |
|
2007-01-01T00:00:00 |
Acquisition. The LiDAR data was collected during March 2007. This
was a leaf-off condition. An Optech 3100 LiDAR system was mounted in a fixed-wing
aircraft and flown 900 meters above ground level (AGL). A pulse repetition frequency
(PRF) of 71 kHz with at least 100% overlap (minimum 50% side-lap) was used. Greater
than 8 points per square meter and near nadir scan angles were used to increase penetration
of vegetation to ground surfaces. Ground level GPS and aircraft IMU were collected
during the flight.
|
| 1 |
|
2007-01-01T00:00:00 |
Processing. 1. Flight lines and data were reviewed to ensure complete
coverage of the study area and positional accuracy of the laser points. 2. Laser point
return coordinates were computed using the REALM survey suite and PosPac based on
independent data from the LiDAR system, IMU, and aircraft. 3. The raw LiDAR file was
assembled into flight lines per return with each point having an associated x, y,
and z coordinate. 4. Visual inspection of swath to swath laser point consistencies
within the study area were used to perform manual refinements of system alignment.
5. Custom algorithms were designed to evaluate points between adjacent flight lines.
Automated system alignment was computed based upon randomly selected swath to swath
accuracy measurements that consider elevation, slope, and intensities. Specifically,
refinement in the combination of system pitch, roll and yaw offset parameters optimize
internal consistency. 6. Noise (e.g., pits and birds) was filtered using REALM software
tools based on known elevation ranges and included the removal of any cycle slips.
7. Using TerraScan and Microstation, ground classifications utilized custom settings
appropriate to the study area. 8. The corrected and filtered return points were compared
to the RTK ground survey points collected to verify the vertical and horizontal accuracies.
9. Points were broken into processing bins and output areas and output as laser points,
TINed and GRIDed surfaces. Bare earth DEMs meet PSLC specifications.
|
| 1 |
|
2008-11-15T00:00:00 |
The NOAA Coastal Services Center (CSC) received the files in las format.
The files contained Lidar elevation and intensity measurements. The data was in Lambert
Conformal Conic projection and NAVD88 Geoid 03 vertical datum. CSC performed the following
processing to the data to make it available within Digital Coast: 1. The data were
converted from Lambert Conformal Conic coordinates to geographic coordinates. 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 |
|
2009-07-21T00: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.
|
|
