Data availability

OpenLiDARViewer is local-first: it processes the scans a user opens in their own browser, and it neither ships nor requires a proprietary dataset to run. This document records where the data referenced by the project comes from and how it can be obtained.

Bundled test fixtures

Small fixtures live under tests/ and are used only by the automated test suite. Their provenance and licensing are recorded in THIRD_PARTY_NOTICES.md (section "Test fixtures"). Most are synthetic, generated by the scripts under scripts/ (for example scripts/make-fixtures.py) with fixed seeds, so they are reproducible and carry no third-party redistribution constraints. Any fixture derived from an external source is listed in THIRD_PARTY_NOTICES.md with its origin and license.

External / streamed open data

The viewer can stream public open-data point clouds (for example COPC and EPT sources) that the user chooses. These datasets are hosted by their respective providers and are not redistributed by this repository. A catalog of known public sources, with links, is maintained in docs/public-lidar-catalog.md, and provider attributions are listed in public/credits.html and docs/credits.md. Availability, licensing, and terms of each dataset are governed by its provider; consult the provider before reuse.

Reproducing analysis outputs

The committed benchmark and calibration outputs under benchmarks/out/ are regenerated deterministically from fixed-seed inputs by npm run repro (see docs/benchmarks.md). No external data download is required to reproduce them.

Summary

• No proprietary dataset is required to build, test, or run OpenLiDARViewer.
• Bundled fixtures are synthetic or explicitly licensed (see THIRD_PARTY_NOTICES.md).
• External point clouds are user-supplied or streamed from third-party open-data hosts; this repository redistributes none of them.