Repository navigation
Conversation
… projected EPSG code
mahach666
force-pushed
the
feature/issue-21-edgewise-scale
branch
from
November 17, 2026 15:02
c88b0e4 to
a5f96ab
Compare
mahach666
force-pushed
the
feature/issue-22-las-exporter
branch
from
November 17, 2026 15:02
d93b040 to
4e9bf94
Compare
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #22
Based on #72 (the branch
feature/issue-21-edgewise-scale); merge the earlier pull requests first.What changed
PclLasOptions: version (1.2/1.4),point format (2 for 1.2; 6/7/8 for 1.4, where 7 adds RGB and 8 adds a zero near infrared), a configurable scale
(default 1 mm) and offset (default the minimum of the data), and an optional GeoTIFF coordinate system record
transcribed from an
EPSG:NNNNsource coordinate system. Mismatched version/format pairs are rejected.Record layout follows the standard (return 1 of 1, full-byte classification, zero GPS time/source/scan angle).
NotSupportedExceptioninstead of overflowing.Files changed
src/PclIO/Export/PclLasOptions.cs: newLasVersionenum andPclLasOptionsrecord (validated init).src/PclIO/Export/PclLasExporter.cs: versioned headers (227/375 bytes), per-format records, VLR writing, new overloads.tests/PclIO.Tests/ExportTests.cs: header/version/format/scale/offset/count/CRS assertions, a full 1.4 round trip thatdecodes the written records, format 6/8 specifics, mismatch and validation tests, overflow-guard test.
tests/PclIO.Tests/OptionsAndPathTests.cs: defaults and validation of the new options.README.md,docs/getting-started.md,docs/public-api.md,CHANGELOG.md: the new behaviour.Tests
dotnet build— 0 warnings, 0 errors.dotnet test— 686 passed, 0 failed, 10 skipped (the tests that need private scan files) on .NET 8 and .NET 10.Limits
PclFile-level round trip yet: reading the output back throughPclFile.Openneeds the LAS reader of issue Format: LAS (*.las) #25.The round trip here parses and decodes the written bytes field by field instead.
EPSG:<1..65535>form as a projected GeoTIFF reference; anything else(geographic codes included) is skipped without a record, which is documented. Non-
EPSGnames never produce a record.