I have a simple IFC model generated using IfcOpenShell. When visualizing in my web client, all the floor slabs import at the ground level. When I load the same model in Blender using the Bonsai extension, the slabs are in the desired locations. Any ideas or suggestions as to what may be causing the discrepancy? OpenIFCViewer also shows the slabs at the ground level.
Generally how I am loading using OBC.IfcLoader:
// Simple loader setup
const fragmentIfcLoader = components.get(OBC.IfcLoader);
await fragmentIfcLoader.setup();
fragmentIfcLoader.settings.webIfc.COORDINATE_TO_ORIGIN = true;
// Load buffer from an IFC file
const buffer = new Uint8Array(arrayBuffer);
await fragmentIfcLoader.load(buffer);
test_ifc.txt (need to change extension back to IFC - required for GitHub upload)
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] 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.
[X] Check that this is a concrete bug. For Q&A join our Community.
alfarok
commented
2 weeks ago
Describe the bug 📝
I have a simple IFC model generated using IfcOpenShell. When visualizing in my web client, all the floor slabs import at the ground level. When I load the same model in Blender using the Bonsai extension, the slabs are in the desired locations. Any ideas or suggestions as to what may be causing the discrepancy? OpenIFCViewer also shows the slabs at the ground level.
Generally how I am loading using
OBC.IfcLoader:test_ifc.txt (need to change extension back to IFC - required for GitHub upload)
Reproduction ▶️
No response
Steps to reproduce 🔢
See attached IFC
System Info 💻
Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅