Skip to content

IFCALIGNMENT child elements not included in getSpatialStructure() result #743

@vovka236

Description

@vovka236

Describe the bug 📝

Environment

  • @thatopen/components version: 3.3.2
  • @thatopen/components-front version: 3.3.3
  • @thatopen/fragments version: 3.3.6
  • Browser: Chrome / Edge
  • Model: IFC4x3 bridge model

When loading an IFC4x3 model containing IFCALIGNMENT with nested
IFCALIGNMENTHORIZONTAL / IFCALIGNMENTVERTICAL / IFCREFERENT elements, these child elements
are absent from the object returned by model.getSpatialStructure().
The elements exist in the model and are visible in BIMvision desktop 3.1.2
IFC structure tree, but do not appear in the getSpatialStructure() traversal.

Notably, calling model.getItemsOfCategories(SPATIAL_CATEGORIES) does return
these entities, confirming they are present in the model and recognized as
spatial categories - they are simply missing from the getSpatialStructure() tree.

Image

Reproduction ▶️

No response

Steps to reproduce 🔢

Viadotto Acerno.zip

  1. Load an IFC4x3 model containing IFCALIGNMENT with nested IFCALIGNMENTHORIZONTAL / IFCALIGNMENTVERTICAL
  2. Call: const spatialStructure = await model.getSpatialStructure();
  3. Traverse the returned tree
  4. IFCALIGNMENTHORIZONTAL / IFCALIGNMENTVERTICAL and IFCREFERENT are not present

System Info 💻

System:
    OS: Windows 11 10.0.26200
    CPU: (24) x64 AMD Ryzen 9 7900X3D 12-Core Processor
    Memory: 10.77 GB / 31.12 GB
  Binaries:
    Node: 24.12.0 - C:\Program Files\nodejs\node.EXE
    npm: 11.12.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 148.0.7778.97
    Edge: Chromium (143.0.3650.75)
    Firefox: 145.0.2 - C:\Program Files\Mozilla Firefox\firefox.exe
    Internet Explorer: 11.0.26100.8115

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
  • Check that this is a concrete bug. For Q&A join our Community.
  • The provided reproduction is a minimal reproducible example of the bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions