Merge remote-tracking branch 'main_ssh/main-1.5' into website

Author: hobu

.github/workflows/pdf.yml

@@ -19,6 +19,8 @@ jobs:
       run: |
           python3 --version
           sphinx-build --version
+          DEBIAN_FRONTEND=noninteractive apt-get update  -y
+          DEBIAN_FRONTEND=noninteractive apt-get install texlive-fonts-recommended -y
     - name: Lint .rst files
       run: |
         if find . -name '*.rst' | xargs grep -P '\t'; then echo 'Tabs are bad, please use four spaces in .rst files.'; false; fi
@@ -43,4 +45,9 @@ jobs:
         name: Misspelled
         path: build/spelling/output.txt
         if-no-files-found: ignore
+<<<<<<<<< Temporary merge branch 1
+
+
+=========
+>>>>>>>>> Temporary merge branch 2
 

source/01_intro.txt

@@ -12,27 +12,26 @@ produce points with X, Y, and Z coordinates. The purpose of LAS is to provide
 an open format that allows different hardware and software tools to
 exchange point cloud data in a common format.
 
-This document reflects the fourth revision of the LAS format specification
+This document reflects the fifth version of the LAS file specification
 since its initial version 1.0 release.
 
 
 LAS 1.5 Revision History
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Summary of LAS 1.5 revisions (GitHub Issue numbers included when applicable):
+Summary of LAS 1.5 revisions (topic links included when applicable):
 
-* R00 - Approved Version (XXXXXXX).
+* R00 - Approved Version (August 2025). 
 
 
 Comparison of LAS 1.5 to Previous Versions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The additions of LAS 1.5 include:
+The additions of LAS 1.5 include (topic links included when applicable):
 
-* Backward compatibility with LAS 1.1 – LAS 1.4.
-* LAS 1.5 mode which supports:
-
-  * Removed support for PDRFs 0-5.
+  * Backward compatibility with 64-bit LAS 1.4 files.
+  * Header compatibility with LAS 1.1 - 1.4 files.
+  * Removed support for legacy Point Data Record Formats 0-5.
     (`I-128 <https://github.com/ASPRSorg/LAS/issues/128>`_)
   * Added Max/Min GPS Time fields to header block.
     (`I-118 <https://github.com/ASPRSorg/LAS/issues/118>`_)
@@ -44,143 +43,8 @@ The additions of LAS 1.5 include:
     `I-129 <https://github.com/ASPRSorg/LAS/issues/129>`_)
   * Clarify requirement that the Extra Bytes VLR must be unique.
     (`I-150 <https://github.com/ASPRSorg/LAS/issues/150>`_)
-
-LAS 1.4 Revision History
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Summary of LAS 1.4 revisions (GitHub Issue numbers included when applicable):
-
-* R11 - Approved Version (Nov 2011).
-* R12 - Errata (June 2012) - Typographical corrections:
-
-  * Corrected Public Header Size in descriptive paragraph to 375 bytes.
-  * Corrected two instances of Scan Angle Rank from "Unsigned Char" to "Char".
-
-* R13 - Added Domain Profile Section (July 2013).
-* R14 - Multiple updates (March 2019):
-
-  * Aesthetic changes from migration to GitHub.
-  * Multiple capitalization & typo corrections.
-  * Updated ASPRS contact info.
-    (`I-30 <https://github.com/ASPRSorg/LAS/issues/30>`_)
-  * Additional standard classifications 19-22 for PDRFs 6-10:
-    (`I-11 <https://github.com/ASPRSorg/LAS/issues/11>`_,
-    `I-26 <https://github.com/ASPRSorg/LAS/issues/26>`_)
-
-    * Class 19 -- Overhead Structure in PDRFs 6-10.
-    * Class 20 -- Ignored Ground.
-    * Class 21 -- Snow.
-    * Class 22 -- Temporal Exclusion.
-
-  * Added OGC endorsement.
-    (`I-31 <https://github.com/ASPRSorg/LAS/issues/31>`_)
-  * Added minimum PDRF sizes to attribute tables.
-    (`I-47 <https://github.com/ASPRSorg/LAS/issues/47>`_)
-  * Section reorganization:
-    (`I-57 <https://github.com/ASPRSorg/LAS/issues/57>`_)
-
-    * Addition of Table of Contents with section numbers. (c.f. 
-      `I-27 <https://github.com/ASPRSorg/LAS/issues/27>`_,
-      `I-49 <https://github.com/ASPRSorg/LAS/issues/49>`_)
-    * Divided Defined Variable Length Records section into Coordinate
-      Reference System VLRs section (s3) and Other Specification Defined
-      VLRs (s4).
-    * Expanded EVLR discussion in Legacy Compatibility section (s2.1) and moved
-      Legacy Compatibility section to EVLR definition (now s2.7.1).
-    * Swapped order of LAS 1.4 Revision History (now s1.1.1) and
-      LAS 1.4 Additions (now s1.1.2).
-    * Rearranged paragraphs in Extra Bytes VLR description.
-
-  * Deprecated "tuple" and "triple" extra byte data types.
-    (`I-1 <https://github.com/ASPRSorg/LAS/issues/1>`_)
-
-    * Added explanation and example of implicit arrays from descriptor names.
-
-  * Clarified that ExtraByte min/max should be an untransformed value.
-    (`I-4 <https://github.com/ASPRSorg/LAS/issues/4>`_)
-  * Clarified that Legacy Point Counts should be set to zero if using non-legacy
-    PDRFs. (`I-12 <https://github.com/ASPRSorg/LAS/issues/12>`_)
-  * Clarified Full Waveform descriptions and added wiki link.
-    (`I-9 <https://github.com/ASPRSorg/LAS/issues/9>`_)
-  * Renamed X(t), Y(t), and Z(t) from waveform packets to Parametric dx/dy/dz.
-  * PDRF9 now correctly requires Scanner Channel like other PDRFs.
-    (`I-29 <https://github.com/ASPRSorg/LAS/issues/29>`_)
-  * Clarified origin date/time for Adjusted Standard GPS Time.
-    (`I-40 <https://github.com/ASPRSorg/LAS/issues/40>`_)
-  * Clarified null-termination of fixed-length ``char`` arrays, especially VLR
-    Description. (`I-46 <https://github.com/ASPRSorg/LAS/issues/46>`_)
-  * Clarified relationship between FileSourceID and PointSourceID.
-    (`I-59 <https://github.com/ASPRSorg/LAS/issues/59>`_)
-  * Added language to support technologies other than conventional linear-mode
-    lidar scanners. (`I-35 <https://github.com/ASPRSorg/LAS/issues/35>`_)
-
-    * Clarified and renamed Synthetic Return Numbers Global Encoding bit.
-    * Clarified Synthetic point classification flag.
-    * Clarified validity of zero-value PointSourceID.
-    * Unified Return Number and Number of Returns descriptions between
-      legacy and non-legacy PDRFs.
-    * Clarified Scan Direction and Edge of Flight Line Flags for non-rotational systems.
-
-  * Added wiki link for Project ID examples.
-    (`I-38 <https://github.com/ASPRSorg/LAS/issues/38>`_)
-
-* R15 - Errata and typo corrections for R14 (July 2019):
-
-  * Minor editorial punctuation corrections.
-    (`I-78 <https://github.com/ASPRSorg/LAS/issues/78>`_)
-  * Fixed unintended reordering of Min/Max XYZ in R14 LAS header.
-    (`I-79 <https://github.com/ASPRSorg/LAS/issues/79>`_)
-  * Added missing Scanner Channel field in note about PDRF6-10 bit field.
-    (`I-80 <https://github.com/ASPRSorg/LAS/issues/80>`_)
-
-* R16 - DRAFT
-
-  * Clarified uniformity of GPS Time for all returns of a pulse.
-    (`I-81 <https://github.com/ASPRSorg/LAS/issues/81>`_)
-  * Added example usage of Overlap bit.
-    (`I-5 <https://github.com/ASPRSorg/LAS/issues/5>`_)
-  * Reworded mandatory zero Classification for Synthetic PDRF0-5.
-    (`I-86 <https://github.com/ASPRSorg/LAS/issues/86>`_)
-  * Added Byte Offset columns to Header, VLR, EVLR, and PDRF tables.
-    (`I-55 <https://github.com/ASPRSorg/LAS/issues/55>`_)
-  * Clarified how and when certain header fields should be zero-filled.
-    (`I-101 <https://github.com/ASPRSorg/LAS/issues/101>`_)
-  * Added Official LAS Wiki section.
-    (`I-71 <https://github.com/ASPRSorg/LAS/issues/71>`_)
-  * More closely aligned data types with C99 definitions.
-    (`I-115 <https://github.com/ASPRSorg/LAS/issues/115>`_)
-
-For detailed information on changes in revisions R14 and newer, review the
-inline differencing provided on the `GitHub page <https://github.com/ASPRSorg/LAS>`_.
-
-
-Comparison of LAS 1.4 to Previous Versions
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The additions of LAS 1.4 include:
-
-* Backward compatibility with LAS 1.1 – LAS 1.3 when payloads consist of only
-  legacy content.
-* LAS 1.4 mode which supports:
-
-  * Extension of offsets and field sizes to support full 64 bit.
-  * Support for up to 15 returns per outgoing pulse.
-  * Extension of the Point Class field to support 256 classes.
-  * Definition of several new ASPRS standard classes.
-  * Extension of the Scan Angle field to 2 bytes to support finer angle resolution.
-  * Addition of a Sensor Channel bit field to support mobile mapping systems.
-  * Addition of Well Known Text (WKT) definitions for Coordinate Reference
-    Systems.
-  * Addition of an Overlap bit to indicate points in the overlap
-    region while maintaining the class definition.
-  * Addition of an (optional) :ref:`extrabytes_vlr_label` Variable Length Record to describe
-    "extra bytes" stored with each point.
-
-* Other minor changes:
-
-  * Added definitions for "LAS Domain Profile" and "LAS Domain Profile
-    Description".
-  * Added references to :ref:`Official LAS Wiki <laswiki_link>`.
+  * Deprecated Classification Lookup VLR.
+    (`I-82 <https://github.com/ASPRSorg/LAS/issues/82>`_)
 
 
 Conformance
@@ -204,7 +68,7 @@ this standard can be directed to ASPRS:
 * Online at https://github.com/ASPRSorg/LAS
 * By phone at 225-408-4747
 * By email at las@asprs.org or asprs@asprs.org
-* By mail at 8550 United Plaza Blvd, Suite 1001 Baton Rouge, LA 70809
+* By mail at 8550 United Plaza Blvd, Suite 1001, Baton Rouge, LA 70809
 
 OGC
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

source/02.00_definition.txt

@@ -22,7 +22,7 @@ allows, for example, adding projection information to a LAS file without having
 to rewrite the entire file.
 
 
-.. table:: LAS 1.4 Format Definition
+.. table:: LAS 1.5 Format Definition
 
     +--------------------------------------------+
     | :ref:`headerblock_label`                   |
@@ -35,19 +35,18 @@ to rewrite the entire file.
     +--------------------------------------------+
 
 
-A LAS file that contains point record types 4, 5, 9, or 10 could potentially
+A LAS file that contains point record types 9 or 10 could potentially
 contain one block of waveform data packets that is stored as the payload of any
 Extended Variable Length Record (EVLR). Unlike other EVLRs, the Waveform Data
 Packets (if stored internally to the file) have the offset to the storage
 header contained within the Public Header Block ("Start of Waveform Data Packet
 Record").
 
 .. include:: ./02.01_legacy.sub
-.. include:: ./02.02_crs.sub
-.. include:: ./02.03_datatypes.sub
-.. include:: ./02.04_header.sub
-.. include:: ./02.05_vlr.sub
-.. include:: ./02.06_point.sub
-.. include:: ./02.07_evlr.sub
+.. include:: ./02.02_datatypes.sub
+.. include:: ./02.03_header.sub
+.. include:: ./02.04_vlr.sub
+.. include:: ./02.05_point.sub
+.. include:: ./02.06_evlr.sub
 
 

source/02.01_legacy.sub

@@ -1,30 +1,28 @@
 Legacy Compatibility (LAS 1.1 - LAS 1.3)
 ................................................................................
 
-LAS 1.4 moves the file specification from a 32 bit file structure (maximum
-value of :math:`2^{32}-1 \equiv 4,294,967,295 \equiv \mbox{UINT32\_MAX}`) to a
-64 bit file structure (:math:`2^{64} - 1`).
-
-To maintain the ability to place a LAS 1.1 through LAS 1.3 payload (point
-record types 0-5, GeoTIFF coordinate reference system, referred to as "Legacy"
-payloads) in a LAS 1.4 file structure, it is necessary to duplicate some of
-the fields within the LAS 1.4 file structure. These duplicate fields are named
+LAS 1.4 moved the file specification from a 32 bit file structure to a
+64 bit file structure.
+To maintain the ability to place a LAS 1.1 through LAS 1.3 payload
+in a LAS 1.4 or LAS 1.5 file header, optional support for the 32 bit field 
+variants is retained alongside the required 64 bit fields.
+These duplicate 32 bit fields are named
 "Legacy xxx" where "xxx" denotes the meaning of the field.
 
-A LAS 1.4 file writer who wishes to maintain backward compatibility must
+A LAS 1.5 file writer who wishes to maintain backward compatibility must
 maintain both the legacy fields and the equivalent non-legacy fields in
 synchronization. However, this is not possible if the number of points
 exceeds UINT32_MAX, in which case the legacy fields must be set to zero. If a
 file writer is not maintaining backward compatibility, the legacy fields must
 always be set to zero.
 
 If there is a discrepancy between a non-zero legacy field and the equivalent
-LAS 1.4 field, the LAS 1.4 reader should use the legacy value to maintain the
-same behavior as a LAS 1.1 through LAS 1.3 reader. Best practice is to also
+LAS 1.5 field, the LAS reader should use the legacy value to maintain the
+same behavior as prior versions of LAS. Best practice is to also
 throw an informative error so that the file can be repaired.
 
 LAS 1.4 introduced the option to define Variable Length Records (VLRs) as
-Extended Variable Length Records (EVLRs) instead. A LAS 1.4 file writer wishing
+Extended Variable Length Records (EVLRs) instead. A LAS file writer wishing
 to maintain backward compatibility must use only VLRs. See the
 :ref:`evlr_legacy_label` section for more information.
 

source/02.02_crs.sub

@@ -1,3 +1,7 @@
+.. raw:: latex
+
+    \newpage
+
 Data Types
 ................................................................................