Export 3D Tiles 1.1 and 3TZ
Create a validated, locally written 3D Tiles hierarchy with direct GLB content, stable BIM feature identity and optional projected placement.
- Applies to
- Current Prism release · Navisworks Manage 2025–2027
- Availability
- Ultra and eligible Pilot access
- For
- Geospatial, web-streaming and large-model platform teams
- Last reviewed
Start with the Web Balanced profile
| Profile | Target GLB | Leaf triangles | Features | Use |
|---|---|---|---|---|
| Lightweight | 2 MiB | 50,000 | 2,000 | Constrained delivery and lower-powered clients. |
| Web Balanced | 4 MiB | 100,000 | 5,000 | Default balance for ordinary web streaming. |
| High Fidelity | 8 MiB | 250,000 | 10,000 | Higher detail where bandwidth/device budgets allow it. |
The simplified screen defaults to .3tz, Web Balanced, local coordinates, lines on, points off, validation on, warnings allowed, full-detail leaves and public-delivery metadata redaction.
Container, geometry and compatibility
- Choose .3tz for one atomic portable archive or an unpacked directory when the hosting pipeline expects individual tiles and tileset.json.
- Profiles control byte, triangle, feature, hierarchy-depth, parent-detail and position-tolerance targets. Editing a controlled value changes the profile to Custom.
- Optional meshopt compression and GPU instancing reduce transfer/runtime cost when the viewer supports them.
- Compatibility mode disables optional performance extensions and expands eligible repeated geometry while retaining required BIM metadata extensions.
- Lines are on and points off by default; include only the primitives the target viewer and use case need.
Choose local or projected placement
| Mode | Use | Required checks |
|---|---|---|
| Local | A local viewer or a later placement pipeline supplies geographic context. | Metres, source origin and true-relative alignment. The result is explicitly not globe-positioned. |
| Projected | The tileset must be placed on the globe from a known project CRS. | Horizontal EPSG, optional vertical CRS, origin, height reference, true north and control-point verification. |
BIM identity and metadata
- Every emitted feature carries stable identity for picking; source names, categories, hierarchy and provenance are available according to the selected redaction policy.
- Named profiles redact source model and hierarchy path by default for public delivery while preserving stable picking and selected non-sensitive fields.
- Add properties through an exact property-set/property allowlist. Wildcards expand deterministically and the combined list is bounded; warnings identify dropped or colliding fields.
- Optional JSON/CSV companions carry the scoped property table and join on the same stable feature ID.
- Fast extraction identity and best-effort data limits still apply; the Tiles writer does not present Fast identity as equivalent to Standard.
Validate and publish outside Prism
Run target validation
Require valid tileset structure, GLB/accessor/feature invariants, references and archive integrity.
Test the target clients
Open representative output in the exact Cesium, ArcGIS or other standards-aware versions you support.
Check position and detail
Verify control points, tile refinement, parent/leaf detail, selection identity and metadata.
Publish with your platform
Prism writes local files only; it does not upload, host or include an embedded web viewer.
Retain the validation record
Retain the 3TZ-internal audit or side reports with CRS, profile, redaction and validation evidence.