Context
Hi, All
I am currently using the specklepy converter to process and upload IFC files.
Description
I understand that Speckle processes and stores IFC geometry as-is (converted to Speckle objects via specklepy) without any simplification, and the frontend viewer renders these converted original geometries.
Expected Behavior / Problem
When dealing with large-scale IFC files, this behavior causes Out-Of-Memory (OOM) crashes either on the server side during the specklepy conversion process or on the browser/viewer side during rendering.
Proposed Solution / Question
Are there any plans or features on the roadmap to address this within the Speckle ecosystem or specklepy specifically?
- Option to simplify or decimate geometry/meshes during the IFC import/conversion process.
- Viewer-side optimizations, such as vertex reduction or LOD (Level of Detail) management for visualization.
Any insights or recommended workarounds for managing large IFC assets using specklepy would be greatly appreciated.