-
Notifications
You must be signed in to change notification settings - Fork 18
Description
Several times over the last five years or so we have attempted to compile a list of updates needed in the topobathy domain profile. I'm going to attempt to compile them here.
Classifications
These changes are a composite of what I've gathered from #72, the LWG call earlier this year, and past discussions at various conferences such as ILMF and JALBTCX. Please provide corrections as I'm sure my notes are incomplete.
- Class 40 (unchanged)
- Current definition: Bathymetric point (e.g., seafloor or riverbed; also known as submerged
topography)
- Current definition: Bathymetric point (e.g., seafloor or riverbed; also known as submerged
- Class 41 (clarified)
- Current definition: Water surface (sea/river/lake surface from bathymetric or topographic-bathymetric lidar; distinct from Point Class 9, which is used in topographic-only lidar and only designates “water,” not “water surface”)
- New definition: Water surface of sea, river, lake or other body of water, typically used in refraction. This is distinct from ASPRS Class 9, which is used in topographic-only lidar to designate “water” in general, not “water surface.”
- Class 42 (unchanged)
- Current definition: Derived water surface (synthetic water surface location used in computing
refraction at water surface)
- Current definition: Derived water surface (synthetic water surface location used in computing
- Class 43 (unchanged)
- Current definition: Submerged object, not otherwise specified (e.g., wreck, rock, submerged piling)
- Class 44 (REMOVE - several users have identified that it's redundant with Class 43 and that IHO classifications occur on derived products, not within the lidar)
- Class 45 (revised - in practice most folks have been using this as a submerged -- i.e., refracted -- noise class, rather than using it as an indicator of submerged pulse extinction)
- Current definition: No-bottom-found-at (bathymetric lidar point for which no detectable bottom
return was received) - New definition: Water column noise (submerged noise within the water column not identified as a real submerged object or identified as submerged backscatter -- i.e., noise points from the bathymetric lidar that are submerged and were therefore refracted)
- Current definition: No-bottom-found-at (bathymetric lidar point for which no detectable bottom
- Class 46 (NEW)
- Submerged vegetation (submerged vegetation occurring below the water surface (class 41) and above the bathymetric bottom (class 40), especially seagrass)
ExtraBytes
Most of the ExtraBytes defined in v1 of the LDP are widely unused. The Bathymetry flags ExtraByte is used often, but the rest are largely ignored. Here's a summary:
(pseudo)-reflectance(REMOVE)- It's weirdly named, poorly understood, and -- as far as I know -- unused because there are other standardized way to provide similar attributes.
sigma xyz(REPLACE - the triple-XB data types were removed in a previous revision of LAS 1.4. Replace with the two xy/horizontal and z/vertical ExtraBytessigma xyandsigma z)water column optical depth(???????)figure of merit(unchanged.... apparently it's a CZMIL thing?)Bathymetric flags(rename tobathymetric flagsto be consistently lowercase)refracted range(ADD from standard table)
Admin
The previous version of the LDP should be referenced as Version 1 of the topobathy LDP, while the revised version should be referenced as Version 2 to simplify references in publications and specifications.
LAS files need a method by which the file's contents provide a hint that a LDP was followed during the file's creation. Adding this to the header can't happen without a new version of LAS (e.g., 1.5), but the LDP reference could be added to #82 as a component of the new Classification Lookup VLR, with a lookup table maintained in the wiki.
(Incidentally, this is a good example of why these public GitHub issues threads are so valuable... compiling this information from MANY sources was quite a bit of work.)