Large point-cloud assets need an inspectable catalog around them: which file revision is being used, where it came from and which processing step produced a derivative. A metadata application can answer those questions without pretending to decode or spatially index the asset.
Executed synthetic walkthrough: this article includes actual light-mode OriginChainDB screenshots, the downloaded query CSV and a validated local application adapter. External industry systems were not connected.
Conceptual illustration of the synthetic application workflow. Light PNG · Dark PNG. This is not a product screenshot.
The sourced development
On 3 September, OGC announced publication of the LAZ 1.4 Community Standard, which defines lossless compression for LAS 1.4 point-cloud data. This article uses that standards development as context for a metadata and provenance proposal. It does not claim that OriginChainDB implements LAZ decoding, native point-cloud storage or a spatial-index feature.
Read the primary source. OGC published the standards announcement on 3 September 2026.
The operational question
A team can have several similarly named asset files with different acquisition dates or processing histories. Searching filenames alone does not establish which revision produced a deliverable. The prototype question is: can a reviewer trace a derivative back to its recorded source asset and processing receipt?
A tested OriginChainDB application pattern
Keep large binary files in an appropriate external asset store. Use asset IDs, content digests, storage references and processing receipts as application records. Relationships connect derivative IDs to source IDs. The fixture uses symbolic digest labels only; they are explicitly not hashes of real files.
-
Create asset and derivation tables in a fresh demonstration schema. The fixture keeps file bytes external and uses symbolic digest labels, synthetic asset IDs and processing receipt IDs.
-
Inspect the stored assets. Query derivations with separate LEFT JOINs for their source and derivative endpoints so a missing reference remains visible.
-
Export the successful report and run route-export.py. It checks the endpoint evidence and emits resolved or missing-reference states without opening an external file.
-
Use those states to show a provenance review queue. Access to the actual external artifact, hash verification and geospatial validation remain separate production steps.
Run the local application rule
The following executable fixture uses synthetic records and no network connection. It verifies the stated application rule without substituting a local result for a live database demonstration.
Download example.py · Expected local output
python example.py
assets={"A1","A2","A3"}
links=[("A3","A1"),("A3","A2"),("A3","A9")]
result={"resolved":[list(e) for e in links if e[0] in assets and e[1] in assets],"missing_sources":[b for a,b in links if b not in assets]}
assert result["resolved"] == [["A3","A1"],["A3","A2"]]
assert result["missing_sources"] == ["A9"]The live console report and actual export resolve A3’s links to A1 and A2, and retain the proposed A3-to-A9 link as missing_source. The CSV adapter checked those endpoint states. This is a tested metadata-reference handoff, not LAZ decoding, spatial indexing or geospatial validation.
The recorded integration walkthrough
The three stills below were extracted from actual native console recordings after private fields were blurred before encoding. They show the synthetic stored inputs, the successful operation and its returned result. Query timing visible in the console is one observation and is not a performance benchmark.
Three synthetic asset records preserve revisions and symbolic digest labels. Open the image to inspect the full-size console view.
Two LEFT JOINs check derivative and source endpoints without opening external files. Open the image to inspect the full-size console view.
The actual result resolves two links and retains A9 as a missing source. Open the image to inspect the full-size console view.
Reproduce the SQL-to-application handoff
Setup and report SQL · Actual downloaded CSV · CSV adapter · Executed adapter result · Verification receipt.
Use a new demonstration namespace for a repeat run; do not reset an existing one. Run the setup statements separately, inspect the input rows, then run the report below. Export the complete successful result and pass that file to the adapter.
SELECT d.link_id AS link_id, d.derivative_id AS derivative_id, d.source_id AS source_id, d.receipt_id AS receipt_id, a.asset_id AS resolved_derivative, s.asset_id AS resolved_source, CASE WHEN a.asset_id IS NULL THEN 'missing_derivative' WHEN s.asset_id IS NULL THEN 'missing_source' ELSE 'resolved' END AS reference_state FROM academy_news_20261015_laz.derivations d LEFT JOIN academy_news_20261015_laz.assets a ON d.derivative_id = a.asset_id LEFT JOIN academy_news_20261015_laz.assets s ON d.source_id = s.asset_id ORDER BY link_id;python route-export.py export.csvThe adapter reads a local CSV, checks the application rule and emits records. It makes no network call and sends no external action. The synthetic contract CSV supplied beside the adapter is a separate offline test; it is not the live export.
Limits and evaluation
Metadata can be wrong or stale even when its identifiers are internally consistent. Verify actual digests against authorized file bytes, document coordinate reference information where relevant, and retain processing-tool versions. A provenance path does not prove measurement accuracy or fitness for an engineering decision.
The practical next step
The demonstrated database contribution is a connected record of asset references and processing evidence. It makes the missing source visible before a reviewer trusts a derivative. Next, add authorized external-file hash checks and processing-tool versions, while keeping file decoding and fitness-for-use evaluation outside this metadata claim.
Claims and remaining evidence · Local execution receipt · OriginChainDB documentation. No partnership, native industry adapter, certification, customer outcome or production deployment is claimed.
