forked from PDAL/PDAL
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
writers.copc: fix legacy point/return counts
According to the LAS 1.4 r15 spec (§2.4) > Legacy Number of Point Records > This field contains the total number of point records within the file > if the file is maintaining legacy compatibility, the number of points > is no greater than UINT32_MAX, and the Point Data Record Format is > less than 6. Otherwise, it must be set to zero. > Legacy Number of Points by Return > These fields contain an array of the total point records per return if > the file is maintaining legacy compatibility, the number of points is > no greater than UINT32_MAX, and the Point Data Record Format is less > than 6. Otherwise, each member of the array must be set to zero. All COPC files are LAS1.4 & PDRF>=6, so alway set the legacy point count and return count fields to zero to match the spec. PDAL#2235 * extend the LasTester class to access LasReader internal headers * add the COPC tests to the issue2235 LAS test case
- Loading branch information
Showing
4 changed files
with
51 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters