Epic 147E: bounded COPC to 3D Tiles exporter - #104
Merged
Merged
Conversation
Add CopcNodeReader to spatialrust-io: opens a COPC file once, loads only hierarchy metadata, and yields one PointCloud per octree node in deterministic (level, x, y, z) order. spatialrust-interchange gains export_copc_tileset behind tiles3d-copc, which mirrors the COPC octree into tileset.json plus one pnts tile per node with a per-tile RTC_CENTER, bounded by max_level, without materializing the whole cloud. Add the tiles3d_copc_export example and facade-level E2E tests.
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.
Summary
Extends the Epic 147 3D Tiles work with a bounded COPC → 3D Tiles exporter. A COPC file's octree hierarchy is walked one node at a time and written as
tileset.json+ one.pntstile per node — the whole cloud is never materialized.Deliverables
spatialrust-ioCopcNodeReader(147E): opens a COPC file once, loads only hierarchy metadata, exposes nodes in deterministic(level, x, y, z)order, and reads onePointCloudper node on demand.spatialrust-interchangeexport_copc_tileset(featuretiles3d-copc): mirrors the COPC octree into atileset.json, writes onepntstile per node with a per-tileRTC_CENTER, bounds the hierarchy withmax_level, and returns a byte/point/tile receipt.interchange-tiles3d-copc,tiles3d_copc_exportexample, and facade E2E test.Contract
tiles3d-copcis the only interchange feature that pullsspatialrust-io/spatialrust-core; the basetiles3dcodec remains dependency-free.Verification
cargo test -p spatialrust-interchange --features tiles3d-copc— 22 testscargo test -p spatialrust --features "interchange-tiles3d-copc io-pcd io-copc" --test tiles3d_smoke-D warningsclean;cargo fmt --all --checkcleangrid.copc.laz→ 9 tiles / 200,000 points in ~2.4 MB pnts, no full-cloud materialization