Skip to content

LAS 1.5 public comment thread #162

Closed
Task
Closed
LAS 1.5 public comment thread#162
Task
Labels
meta
Milestone
v1.5

Description

@esilvia
esilvia
opened on Apr 24, 2025

The LAS Working Group (LWG) seeks public comment for the initial draft of the brand-new LAS 1.5 specification. The latest iteration of the draft is available here:

LAS_1.5R20_draft_for_public_comment_v1.pdf

Comment Period

Per ASPRS bylaws, the public comment period will last at least 30 days, beginning approximately April 30th, 2025.

Comments will be due by May 31st, 2025 and incorporated into the specification by the LWG. The final version will be submitted to the ASPRS Board of Directors for final approval and publication.

How to Comment

Any member of the public is welcome to contribute changes, corrections, or comments during the public comment period.

When commenting, please provide enough context for us to identify the section being commented on by providing section numbers, page number, a commented PDF, and/or screenshots.

You can submit comments using any of three methods:

  1. Users with a GitHub account may contribute comments directly on this Issue thread.
  2. ASPRS members may contribute comments on this Discussion page: https://community.asprs.org/wg-las/discussion/las-15-initial-draft-ready-for-public-comment
  3. Anyone can email the LWG directly at las@asprs.org

Thank you for your interest in the LAS specification!

Activity

  1. esilvia
    added the
    Task
    issue type on Apr 24, 2025

  2. esilvia commented on Apr 24, 2025

    @esilvia
    esilvia
    on Apr 24, 2025
    MemberAuthor

    My own comments:

    • code or mono-spaced fonts aren't formatted correctly. @hobu already took a crack at fixing that in one of his forks, so I'll be looking at that shortly, now that this is ready to go.
    • It seems to me that sections 2.2 and 3.0 are probably redundant. It used to be that 3.0 was all about the VLRs specifically, while 2.2 parsed out the nuances between Geotiff and WKT, but since 1.5 doesn't include Geotiff they both include basically the same information. My hunch is that 2.2 can be merged into 3.0.
    • The VLR §2.5 and EVLR §2.7 sections should probably cross-reference to the CRS (§3) and spec-defined (§4) VLR sections, as well as the registry on the wiki.
  3. esilvia
    added this to the v1.5 milestone on Apr 24, 2025
  4. esilvia
    added a commit that references this issue on May 15, 2025

    Remove all draft notation and prep for publication (#162)

    bd76ca3

  5. esilvia commented on May 16, 2025

    @esilvia
    esilvia
    on May 16, 2025
    MemberAuthor

    The documentation on page 12 says:

    if the file utilizes a point record format not supporting GPS Time

    But with the deprecation of PRF 1-5, now all supported formats contain a Time.
    Should that part of the sentence be removed?

    I concur with this suggestion.

  6. esilvia commented on May 16, 2025

    @esilvia
    esilvia
    on May 16, 2025
    MemberAuthor

    Private comments contributed via email on May 7, 2025:

    • Page 10 – Point Data Record Length section – I would suggest using a valid PDRF as an example, not a deprecated one.
    • Page 12 – The sentence at the very top of the page (‘If there are no EVLRs, this value must be zero.’) is a duplication of the last sentence in the Number of Extended Variable Length Records section at the bottom of Page 11.
    • Page 29 – Extra Bytes section, second paragraph – I would suggest using a valid PDRF as an example, not a deprecated one.
  7. esilvia
    added
    meta
    on May 27, 2025

  8. esilvia commented on Jun 9, 2025

    @esilvia
    esilvia
    on Jun 9, 2025
    MemberAuthor

    @ASPRSorg/lwg

    The public comment period for the LAS 1.5 draft has ended. Our next LWG meeting will be next Thursday, June 19th to discuss the proposed changes.

    I'll do my best to attempt to address the above comments prior to that meeting, based on the time available.

  9. esilvia
    added a commit that references this issue on Jul 17, 2025

    Replicating PR#164 on LAS 1.5 branch.

    8c422d1

  10. esilvia commented on Jul 17, 2025

    @esilvia
    esilvia
    on Jul 17, 2025
    MemberAuthor

    Discussion from today's LWG meeting:

    • Agreed that section 2.2 is mostly redundant. Summarize essential parts in the Global Encoding description, then move the rest to section 3.0.
    • All other edits suggested in this thread have been incorporated (thanks everyone!)
  11. esilvia
    added 2 commits that reference this issue on Jul 17, 2025

    Replace reference to PDRF 1 with PDRF 6 (#162)

    05b03dd

    Fix repeated words (typo, #162)

    2c2ad0f

  12. esilvia commented on Aug 21, 2025

    @esilvia
    esilvia
    on Aug 21, 2025
    MemberAuthor

    Today's LWG meeting on Aug 21, 2025, completed the edits of the CRS sections as outlined in PR #165 and available in this PDF:

    LAS_1.5_with_consolidated_crs.pdf

    I'll leave that PR up for review until Monday, and merge it for final board approval after that.

  13. esilvia commented on Aug 28, 2025

    @esilvia
    esilvia
    on Aug 28, 2025
    MemberAuthor

    LAS 1.5 has been officially approved and published!
    https://publicdocuments.asprs.org/las-v15-r00-2025
    Great work everybody!

  14. esilvia
    closed this as completedon Aug 28, 2025

  15. jstoker74 commented on Aug 28, 2025

    @jstoker74
    jstoker74
    on Aug 28, 2025 via email
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    meta

    Type

    Task

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions