Skip to main content

Static OI scenes → 3D Tiles 1.1

A small, independently runnable Python converter and local CesiumJS/Three.js interoperability demo for issue #18. It consumes the geometry already bundled in a portable OI scene. It does not tessellate CAD, perform physics, or build a general-purpose streaming hierarchy.

Reproduce

Python 3.11+ is sufficient for conversion and contract tests. The separate viewer/validator package uses Node 22.18+ and a committed npm lockfile. Root application dependencies and provider credentials are unnecessary.

From the repository root:

python tools/geospatial/export_scene.py benchmarks/field-lab/fixtures/field-lab.oi.json tools/geospatial/public/export --longitude=-73.977 --latitude=40.684 --height=30 --heading=0 --license-note="Existing conceptual FIELD-LAB fixture; redistribution permission unresolved"
python -m unittest discover -s tools/geospatial -p test_export.py -v
cd tools/geospatial
npm ci --ignore-scripts
npx playwright install chromium
npm run validate
npm run test:browser
npm run serve

Open http://127.0.0.1:4194/ for CesiumJS or http://127.0.0.1:4194/?viewer=three for the independent 3D Tiles renderer. The server is local; nothing is published or deployed. Both runtimes load the same local tileset without Cesium ion, imagery, login, or tokens. Dependencies and browsers need network access during installation only.

--ignore-scripts avoids unused native SQLite build hooks pulled in by the validator's archive tooling. This adapter validates directory-based JSON/GLB, not SQLite tile archives. The pinned sharp override supplies platform packages instead of the old validator dependency's legacy installation hook. Runtime dependencies retain their own licenses.

Coordinate contract

  • Input is astra.scene v1, meters, right-handed Y-up. OI rotations use Three.js Euler XYZ in degrees.
  • At heading zero, OI +X is east, +Y is up, and -Z is north. The caller explicitly supplies WGS84 longitude, latitude, ellipsoidal height, and heading. Heading rotates clockwise from true north, in [0, 360).
  • GLB positions remain Y-up. A 3D Tiles runtime applies the standard Y-up→Z-up rotation C, mapping (x,y,z) to (x,-z,y). Child transforms are C × OI_pose × inverse(C). The root is WGS84 ENU→ECEF with heading. Tile bounds are Z-up; all serialized matrices are column-major. The empty root uses a conservative extent-sized geometric error to request refinement; exact leaf geometry has zero geometric error.
  • Stored mesh vertices are already normalized and stored instance positions already locate those normalized origins. Do not add originOffset again. The offset is retained as source provenance.
  • The Three.js viewer recenters the ECEF scene into the original local meter frame for numerical precision. It loads the identical geographic tileset.
  • Geographic anchors are illustrative. The converter does not fetch terrain, infer ground height, geocode a lab, or establish surveyed accuracy.

Data and metadata mapping

Input Output
Indexed part geometry and linear RGB Shared-asset GLBs with unlit, double-sided materials
Visible instance placement/rotation One leaf tile per instance; same asset content reused
Asset ID/name and source digest glTF EXT_mesh_features + EXT_structural_metadata property table
Instance ID/name, asset ID, source kind/digest 3D Tiles tile metadata; inherited when geometry is picked
Project identity/revision, cloud binding, source normalization offset, part IDs Allowlisted provenance.json sidecar
Input file byte digest and checkout revision Export report and provenance; revision is null outside Git
Hidden geometry, animation, hierarchy grouping, BOM/compiler findings, source documents, room decoration Explicitly excluded; no claim of lossless IR transfer

There is no static feature ID per animated component: all primitives of a shared asset refer to its single asset feature. Part identities are preserved in node extras and the sidecar. Instance identity belongs to the leaf tile and remains distinct when two instances share one GLB. Arbitrary provider settings, raw IR, source documents and credentials are not copied; this allowlist is stricter than the full OI portable export. It cannot detect secrets pasted into an allowed name.

Validation and evidence

The converter writes tileset.json, content-addressed GLBs, provenance.json and export-report.json with source/output hashes, Python version, payload size and conversion timing. Existing unrelated files in the output directory are not deleted; the report and validators enumerate only current referenced content. Use a fresh output directory for a distributable package.

npm run validate records complete diagnostics from 3d-tiles-validator 0.6.1 and gltf-validator 2.0.0-dev.3.10. The latter reports metadata extensions as unsupported informational messages; the 3D Tiles validator additionally checks those extensions. Zero core errors alone is not proof that every extension or engineering property is valid.

npm run test:browser starts and closes its own Vite server, verifies placement against independent Cesium WGS84/ENU and Three.js Euler implementations within 1 cm, loads both runtimes, and clicks pipette geometry to check exact identity. It saves screenshots, browser/runtime versions, load timing, and memory metrics under evidence/. External browser requests are blocked in this test.

The workflow runs Python checks on Linux/Windows and viewer/conformance checks at two demonstration anchors on Linux. Screenshots, validator diagnostics, checksums, geometry, and timing are uploaded as CI artifacts. Load/capture timing on a software-rendered browser is not interactive FPS or physical performance.

The upstream FIELD-LAB merge has passing benchmark, scene, and runtime workflows at e88f5ce5f8eeb4eda6a49757d5325699cd815cea. Adapter CI is separate and must be checked at the published PR head.

Openness and limits

The new source/documents in this tools/geospatial directory are MIT licensed. That license does not relicense the repository, imported FIELD-LAB or cleanroom assets, dependencies, or generated models. --license-note records the user's evidence or unresolved status; it does not grant permission or certify rights. Confirm original asset permissions before redistributing a grant demonstration.

For a fully MIT-licensed interchange fixture, use fixtures/open-equipment.oi.json: two instances of a newly authored asymmetric workbench envelope, including a 90-degree rotation and shared geometry. Its conceptual boxes do not reuse the existing lab/CAD assets. Substitute that input in the converter command and set --license-note="MIT; tools/geospatial/LICENSE". The browser smoke test specifically targets the 21-instance FIELD-LAB fixture; the minimal fixture can be inspected manually and checked with the validators.

This first version exports the static base layout, not frame zero of the authored animation. No animation, scientific validity, perception, provider generation, cold-chain solver, live operation, or physical validation is implied. The small FIELD-LAB fixture is not a scalability benchmark. A state/replay overlay and resolved asset licensing remain follow-on work; issue #18 should stay open until its remaining evidence gates are addressed.

Metadata

Release files for open-industries 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for open-industries 0.1.0
File Size Uploaded Provenance Actions
open_industries-0.1.0.tar.gz 26.4 kB With provenance Details for open_industries-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for open-industries 0.1.0
File Interpreter ABI Platform Actions
open_industries-0.1.0-py3-none-any.whl Python 3 none any Details for open_industries-0.1.0-py3-none-any.whl

Total release size: 39.6 kB

Release files / open_industries-0.1.0.tar.gz

Download URL open_industries-0.1.0.tar.gz
Size 26.4 kB
Tags Source
SHA-256 checksum
How to use checksums
919a09306298ac85e3a3db6ba69c20bfa582b81e1931ec9011a7a08cb3cd4aed
BLAKE2b-256 checksum
How to use checksums
00486cbe5e890ae63cb26ffe8bd7baf39da088af965235fcfaf431edef851f14
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / open_industries-0.1.0-py3-none-any.whl

Download URL open_industries-0.1.0-py3-none-any.whl
Size 13.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7ae4cb273c203dd7e2205a067ba8d0e425c1e64555fcfa7152b1ae3520564e8a
BLAKE2b-256 checksum
How to use checksums
47c169767b7b4c13de7432fecf07317af69a7003b99073be4bf08de49dc33f11
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Security for open-industries 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for open_industries-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page