IFC processing error log

We have extended the time of processing up to one hour. But medium size files (~30 mb) don’t succeed in parcing. Small note reports about error.
Colleagues, I have two simple questions about ifc:

  1. Main: do you plan to increase the speed of processing? 10 min+ is a little bit discouraging.
  2. Is the log with error available for download somewhere in interface?

If you need any help in testing the import option or need any logs please feel free to contact with me. IFC files processing for us is one of the main functions.


Hi @PavelNedviga - thanks for putting the effort and time into this. It probably has to do with the parser we’re using, namely web-ifc.

Beyond sending us the model, can you let us know if it loads up fine in the demo app from ifc.js peeps here: IFC.js?

If yes, we’ll need to look into it closer on our end. It means the problem is in getting all the elements’ metadata (this is something the demo app doesn’t do upfront, as we do, but only does on selection).

If not, do report this to the ifc.js community, as they’re always up for finding and fixing edge cases!

a rant ffs ifc files are pain in the proverbial place to deal with. it seems that the exception is when they work as expected :/


I guess I have same problem. All ifc models I try to load gives an error message except the model containing only space objects. But it seems that spaces cannot be displayed (maybe transparency settings?). Appears text saying “No displayable objects found in object e71c1ca…”

Whole model loads up perfectly in the demo app from ifc.js (except spaces)

I’m new with Speckle so it’s possible that i’m doing something wrong :slight_smile:


1 Like

Heya @ElsaK, would you mind sending us that file to test against it? I’ll ping you via a direct message on the forum with contact details!

PS: we’d be happy to sign an NDA if needed.


Good news everyone! Once this PR is merged we’ll have much better IFC file imports - like seriously better (think ±30x faster imports, property set support, etc.)

@ElsaK, your file works wonderfully with the new parser. Once we push the update I’ll ping you (and @PavelNedviga) to try it out again on our testing server!


The update is live. But, as always SIGH things work wonderfully on my computer but not on our kube cluster - there are files that locally go through fast but fail in production.

Cautiously, do give it a try. In the meantime, I’ll have steal @iainsproat and @gjedlicska (i hope they don’t hate me too much already) to debug remotely and see what deal is. I hope it’s a simple matter of resource allocation for the converter node, but you never know.

1 Like