Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
IFC Objects lost in translation #1000
I've uploaded an IFC4 file on my local BIMserver v1.5.147, but a few IfcWallStandardCases seem to be missing from it. They are not displayed in the viewer nor the object tree (I tried the BIMsurfer included in BIMvie.ws and BIMsurfer 3). Another viewer (BIMvision), on which I tried to view my model, displayed everything well.
The method GetDataObjectFromGuid, executed from Console, does return the objects and the same information as in the IFC file.
When I re-download the IFC file, the objects are still present, and the file displays fine in BIMvision, but trying to checking it in BIMserver returns errors.
I thank you for your consideration.
Is there anything in the BIMserver log file during upload? Are there perhaps issues with generating the geometry?
Please post both the relevant part of the BIMserver log as well as the geometry generation report linked to the Revision as Extended Data.
If you can share the IFC file that would be even more useful, we can try to reproduce it (or a similar file with the same problem).
Here's the file :
Here are the lines from the BIMserver log :
And here is the geometry generation report :
So far, what I get here with roughly the same version:
I am using the exact same version of IOS.
So what's interesting to know is on what OS you are (I have tested this on Window 10 so far).
Curiouser and curiouser.
My server also runs on Windows 10, and the walls are displayed just fine on a server running on a Debian9 VM. Both were installed automatically from the .war by tomcat9.
As for the GUIDs : 2N8Cd2RGP5i9wSaakjj2zY is the most consequent wall.
Ok I have a clue now. IOS has a few different settings. With both layersets and quantities enabled I can now reproduce your situation, with some walls (including 2N8Cd2RGP5i9wSaakjj2zY) missing.
There have been bugs in BIMserver where it does not correctly report and/or apply these settings, which makes it a bit harder to identify what's going on. This should be fixed in the next release.
I'll talk to the developer of IfcOpenShell and share the the model with him and report back in this issue.