Excel · dataset · 2026
Topobathymetric Lidar - Clear Lake Tributaries - 2024
Listed in California Open Data
The California Department of Fish and Wildlife contracted NV5 Geospatial, Inc.
Description
(NV5) to conduct airborne lidar surveys to map the topographic and bathymetric (underwater) terrain in sections of six tributaries to Clear Lake that are known or expected to contain Clear Lake Hitch (Lavinia exilicauda chi) spawning habitat, referred to as the area of interest (AOI). The lidar AOI covers approximately 5,942 acres across roughly 54 stream miles.
NV5 acquired the lidar data from April 6th–April 8th 2024, when weather and water conditions were most favorable. Lidar data were acquired using near-infrared wavelength (ʎ=1064 nm) and bathymetric green wavelength (ʎ=532 nm) sensors mounted on a Riegl VQ-880-GII laser platform in a Cessna Grand Caravan aircraft. A PhaseOne iXM-RS150F medium-format digital camera was used to acquire 3-band (red, green, blue) orthoimagery simultaneously with the lidar data.
Read the rest (4 more)
From these data, NV5 produced a classified lidar point cloud and a lidar-derived digital elevation model (DEM). NV5 evaluated the classified, average lidar point densities in the successfully mapped portions of the AOI and found density values of 3.06 points/ft^2 (32.97 points/m^2) for first returns, 1.14 points/ft^2 (12.27 points/m^2) for ground and bathymetric bottom returns, and 1.03 points/ft^2 (11.09 points/m^2) for only bathymetric bottom returns.
Where environmental factors (e.g., water turbidity, depth) or physical obstructions (e.g., bridges, vegetation) limited the lidar’s penetration to the ground surface, referred to as void areas, NV5 interpolated the terrain by using the nearest available lidar point data from the area surrounding each void. In some cases, the resulting interpolated surfaces may contain artifacts that misrepresent the elevation of the underlaying topography or bathymetry within the void extent.
Any use of elevation data within void-interpolated areas should be treated with caution. The lidar elevation data are in U.S. survey feet. The spatial resolution (cell size) of the lidar-derived DEM is 1.5 ft.
The spatial resolution of the orthoimagery is 0.5 ft. This data and metadata were submitted by California Department of Fish and Wildlife (CDFW) Staff though the Data Management Plan (DMP) framework with the id: DMP000723. For more information, please visit wildlife.ca.gov/Data/Sci-Data.
Links
Get the data
Where it is published
- California Open Data dataset page data.ca.gov/dataset/topobathymetric-lidar-clear-lake-tributaries-2024 ↗
landing page · from data ca gov
Documentation and papers
- Publisher page wildlife.ca.gov/Conservation/Watersheds/Instream-Flow ↗
documentation · from data ca gov
Catalogue records · 1
- CKAN API data.ca.gov/api/3/action/package_show?id=41acb481-9fa9-40c2-bb70-c13f50ef3… ↗
metadata API · from data ca gov
Topics
- Stated by source
- Natural Resources
Provenance · 1 source records, 10 field assertions
| Source | Key | Last seen | Raw |
|---|---|---|---|
| California Open Data | 41acb481-9fa9-40c2-bb70-c13f50ef3f8e | 12 d ago | JSON v1 |
| Field | Assertion | Extractor | Evidence |
|---|---|---|---|
| access_level | source · data ca gov | connector:data_ca_gov@1.0.0 | |
| concepts[field].local:field:earth-environmental | mapping · data ca gov | connector:data_ca_gov@1.0.0 | |
| concepts[modality].local:modality:remote-sensing | mapping · data ca gov | vocabulary-mapper@1.0.0 | keywords['remote sensing'] |
| concepts[topic].ckan_group:data_ca_gov:natural-resources | source · data ca gov | connector:data_ca_gov@1.0.0 | |
| created_date | source · data ca gov | connector:data_ca_gov@1.0.0 | |
| description | source · data ca gov | connector:data_ca_gov@1.0.0 | /notes |
| license_text | source · data ca gov | connector:data_ca_gov@1.0.0 | |
| publication_date | source · data ca gov | connector:data_ca_gov@1.0.0 | |
| title | source · data ca gov | connector:data_ca_gov@1.0.0 | /title |
| updated_date | source · data ca gov | connector:data_ca_gov@1.0.0 |