-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update topobathy LDP to v2 #117
Comments
One addition for the admin section: The community seemed to feel that using the GitHub wiki would be a fine place to publish the LDPs, so long as versioned PDFs could be available for download and referenced in standards or publishing documents. |
@nkules Have any followup on this from the topobathy meeting at GeoWeek? |
One change I've received/thought of: Class 45 -- Water Column Default instead of Water Column Noise. This would mirror the existing Default class (2) and more accurately convey its intended use as non-specific, rather than implying it's all noise. i.e., it could be submerged vegetation unless Class 46 is present. |
Evon, there wasn't anything to add from Geoweek. I did bring this up in our topobathy workshop, but there were no questions directly related to this. However I am hoping it encouraged all of those attending to join in this discussion! Thank you for keeping on top of this! |
Updates from JALTBTCX 2022:
Lingering questions from JALTBCTX 2022:
I'll post a link to the LDPv2 draft once I get access to the ASPRS GDrive. |
Here is a link to the draft: https://docs.google.com/document/d/1UZYaIHZQp5ljSdSDLRs6sJnY3DJlWSqRdfWfh3N4DwU/edit On Monday 8/1 I will generate a PDF copy of the draft and forward it to Karen to request feedback from the ASPRS community at large via the weekly newsletter. |
The draft has been updated significantly to incorporate comments from JALBTCX, the LWG meeting, and emails from @parrishOSU and @johnsonn. https://docs.google.com/document/d/1UZYaIHZQp5ljSdSDLRs6sJnY3DJlWSqRdfWfh3N4DwU/edit# I also removed most of the tracked edits, leaving just the ongoing discussion threads. Some resolution of the lingering questions:
|
A few updates were posted to the doc this week in preparation for JALBTCX 2023:
The publication of this LDP is imminent, pending final comments from JALBTCX. |
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.
topography)
refraction at water surface)
return was received)
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)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 xy
andsigma z
)water column optical depth
(???????)figure of merit
(unchanged.... apparently it's a CZMIL thing?)Bathymetric flags
(rename tobathymetric flags
to 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.)
The text was updated successfully, but these errors were encountered: