Skip to content

fix: validate shared georeference for multi-scan collections - #150

Merged
snkmcb merged 2 commits into
mainfrom
fix/multiscan-georeference-validation
Sep 12, 2026
Merged

snkmcb merged 2 commits into
mainfrom
fix/multiscan-georeference-validation

Conversation

@snkmcb

@snkmcb snkmcb commented Sep 12, 2026

Copy link
Copy Markdown
Member

Summary

  • enforce a shared GeoReference across all scans in a PointCloudCollection
  • reject scans with mismatched CRS, WKT/PROJ, units, axes, or local origin
  • add regression coverage for a mismatched EPSG code

Validation

  • usdPointCloudCore_tests build
  • usdPointCloudCore_unit
  • editor diagnostics for touched files

@snkmcb
snkmcb merged commit 0e4aa3b into main Sep 12, 2026
4 checks passed
@snkmcb
snkmcb deleted the fix/multiscan-georeference-validation branch September 12, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant