Struct ProcessingResult 

pub struct ProcessingResult {
    pub meshes: Vec<MeshData>,
    pub instances: Vec<InstanceRecord>,
    pub mesh_coordinate_space: MeshCoordinateSpace,
    pub frame: MeshFrame,
    pub site_transform: Option<Vec<f64>>,
    pub building_transform: Option<Vec<f64>>,
    pub metadata: ModelMetadata,
    pub stats: ProcessingStats,
}

Result of processing an IFC file.

Fields

meshes: Vec<MeshData>

instances: Vec<InstanceRecord>

#1623 Phase 2 don’t-bake output: per-occurrence instance records emitted when StreamingOptions.enable_instancing is set. Each non-template occurrence of a repeated single-solid IfcRepresentationMap skipped its full materialize; the template MeshData stays in meshes (keyed by InstanceRecord.template_express_id) and each occurrence here places it by a template-relative transform. Always empty when instancing is off, so exporters/determinism see the flat output.

mesh_coordinate_space: MeshCoordinateSpace

The frame the mesh vertices are expressed in, as its wire tag.

Always frame.coordinate_space(): the constructor below is the only writer of either field, and issue_4706_symbolic_shares_the_mesh_frame asserts they agree on a live parse.

frame: MeshFrame

The frame itself: the tag above PLUS the translation that was subtracted and the site rotation that was removed.

A second consumer of the same bytes that has to land in the same frame reads it here rather than re-deriving the three-tier selection from site_transform and the metadata’s origin shift. The server’s symbolic stream is that consumer (#4706): it hands this to extract_symbolic_data_with_provenance_in_frame.

site_transform: Option<Vec<f64>>

IfcSite ObjectPlacement as column-major 4x4 matrix (in meters).

building_transform: Option<Vec<f64>>

IfcBuilding ObjectPlacement as column-major 4x4 matrix (in meters).

metadata: ModelMetadata

stats: ProcessingStats