Skip to content
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

Editorial updates for LAS 1.5 #131

Open
1 of 12 tasks
esilvia opened this issue May 11, 2023 · 1 comment
Open
1 of 12 tasks

Editorial updates for LAS 1.5 #131

esilvia opened this issue May 11, 2023 · 1 comment
Assignees
Milestone

Comments

@esilvia
Copy link
Member

esilvia commented May 11, 2023

What is the issue about?

No response

Issue description

Editorial changes not to forget before the final release:

  • LAS 1.4 as the latest version is explicitly referenced multiple times throughout the specification, especially in the header block and introductory sections.
  • Ensure that LAS 1.5 is the new reference point.
  • Collapse LAS 1.4 revision summary
  • Convert Intensity normalization to formatted math equation
  • Prettify tables
  • Standardize around numbers as numerals (esp. Return Number section)
  • Cross-link all references to Global Encoding (esp. Return Number) using RST semi-automated substitution links
  • "Code" formatting isn't working as expected.
  • Add ISO link for calculating epoch? WKT for LAS 1.5 #144 (comment)
  • Update ASPRS logo: https://github.com/ASPRSorg/LAS/blob/master/source/_static/asprslogo45.png
  • Scrub lingering references to geotiff
  • Remove references to PDRF 4 and 5 in WDP VLR
@esilvia esilvia added this to the v1.5 milestone May 11, 2023
esilvia added a commit that referenced this issue May 11, 2023
Began work on LAS 1.5 introductory sections. (#131)
esilvia added a commit that referenced this issue Jul 6, 2023
Began work on LAS 1.5 introductory sections. (#131)
Added Min/Max GPS Time to header block. (#118)
@esilvia
Copy link
Member Author

esilvia commented Mar 11, 2025

@hobu You mentioned being able to replicate the Sphinx styling in the RTD builds. I've been playing around with it off and on for a few days and I still can't figure it out. The issue is primarily with the table formatting -- I don't care so much about it matching LAS 1.4 so much as I care about the tables being as readable as possible, and the borders & shading in particular stand out to me as glitchy. Any chance you can take a crack at it?

Edit: Here's a PDF from a recent LAS 1.5 build to show you what I mean. Pay particular attention to Table 3 (header block), Table 7 (PDRF 6 definition), and Table 8 (bit field encoding) as noteworthy examples using different styling techniques.

LAS.pdf

@esilvia esilvia self-assigned this Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant