ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2007_OR_Panther_Creek_Leaf_On_m81
MD_DataIdentification
| 1 |
|
2007 Bureau of Land Management (BLM) Lidar: Panther Creek Watershed, Yamhill
County
|
The dataset represents LiDAR elevations acquired during a leaf-off and a leaf-on
vegetative condition for the Upper Panther Creek Watershed in the Yamhill County study
area in Oregon. The date of collection for the leaf off data is 20071208. The date
of collection for the leaf on data is 20070903. The area of interest covers ~5577
acres (~8.71 sq miles). The LiDAR survey utilized a Leica ALS50 Phase II laser mounted
in a Cessna Caravan 208B set to acquire > or = 105,000 pulses per second (i.e. 105
kHz pulse rate). The scan angle was +/- 14 degrees from nadir. These settings are
designed to yield an average native density (number of pulses emitted by the laser
system) of > or = 8 points per square meter over terrestrial surfaces. LiDAR intensity
values were also collected. 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 the Bureau of Land Management.
|
SV_Identification
| 1 |
|
2007 Bureau of Land Management (BLM) Lidar: Panther Creek Watershed, Yamhill County |
|
|
| 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/Yamhill_BLM_LiDAR_Report.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 |
|
|
DOI/BLM > Bureau of Land Management, U.S. Department of the Interior |
|
|
originator |
|
| 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 |
|
Pamela Grothe |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
|
processor |
|
| 2 |
|
|
Watershed Sciences, Inc. |
|
watershedsciences.com |
processor |
|
| 1 |
|
ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/Yamhill_BLM_LiDAR_Report.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 |
|
|
-123.402927 |
-123.318967 |
45.319222 |
45.273033 |
|
|
| 1 |
|
-123.402927 |
-123.318967 |
45.319222 |
45.273033 |
| 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 on December 8, and September
3, 2007. A Leica ALS50 Phase II LiDAR system was mounted in a fixed-wing aircraft.
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 ALS Post Processing software suite and
IPAS Pro software 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 ALS postprocessing software, 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 exported as laser
points, TINed and GRIDed surfaces.
|
| 1 |
|
2008-07-17T00: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 UTM
Projection, Zone 10N and NAVD88 Geoid 03 vertical datum. CSC performed the following
processing to the data to make it available within the LDART Retrieval Tool (LDART):
1. The data were converted from UTM 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.
|
|
