Solibri can't import all IfcSpaces

agroni

Is it a random exclusion by Solibri for those spaces, or is there something specific that makes them the same…height? Name? ID?
With which BIM Authoring tool did you export it?

marchi

I think the same as @Nando …it is probably an ifc4 issue, where it is possible for some elements to go missing on import - not only spaces.

Xavier

Good afernoon @Nando , @agroni and @marchi ,

Thanks a lot for yous answers.

That’s right, the little IFC that I uploaded in the first post is a small part of a hospital project, in which the IFC format is 4.

We are part of the team of project managers, and we only receive models in IFC 4 format. So if in solibri there is a bug in the import process of IFC 4 files, we will have to find another way to be able to do project management with IFC models. …

Kind regards,
Xavier Coll
EiPM

Matti

@nando said in Solibri can't import all IfcSpaces:

smells like IFC4 issues (from experience). Have you tried getting the file in IFC2x3?

This file is invalid IFC4. The file uses IFCINDEXEDPOLYGONALFACEWITHVOIDS with void lists as (0), (0, 0), or (0, 0, 0).
IFC file generated by GRAPHISOFT ARCHICAD 23.0.0 SPA FULL Windows version (IFC add-on version: 3003 SPA FULL).
The last parameter in IFCINDEXEDPOLYGONALFACEWITHVOIDS is InnerCoordIndices
InnerCoordIndices is: Two-dimensional list, where the first dimension represents each inner loop (from 1 to N) and the second dimension the indices to three or more points that define the vertices of each inner loop. See: https://standards.buildingsmart.org/IFC/RELEASE/IFC4/ADD2_TC1/HTML/schema/ifcgeometricmodelresource/lexical/ifcindexedpolygonalfacewithvoids.htm

#893 = IFCINDEXEDPOLYGONALFACEWITHVOIDS((10, 37, 38, 33, 32, 39, 40, 41, 42, 43, 44, 15, 14, 11), (0));

#574 = IFCINDEXEDPOLYGONALFACEWITHVOIDS((44, 7, 6, 43, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56), (0, 0));

Should be reported to Graphisoft. They might already have a fix in update.

A correct InnerCoordIndices with a single four corner void should look like:

#893 = IFCINDEXEDPOLYGONALFACEWITHVOIDS((10, 37, 38, 33, 32, 39, 40, 41, 42, 43, 44, 15, 14, 11), ((11, 22, 33, 44));

marchi

@Matti-Kannala how does then the other software represent the correct geometry if the IFC is invalid?

Xavier

It’s a good question @marchi …

Matti

We could also allow invalid IFC and in some cases we have done so.
By allowing invalid IFC, the IFC quality will not improve.

In this case the invalid IFC is not imported. I’m adding this to our database, but not promising anything. This is so clearly invalid.

InnerCoordIndices must be

A list containing lists of positive indices: ((11, 22, 33, 44))
The list size must be at least one (at least one void)
The index list must contain at least three indices (a void presenting a triangle)

marchi

@Matti-Kannala if there is an option to import invalid IFC, isn´t there a possibility to implement a warning sign before we import and load a model? Like “Not everything has been loaded”?

Because now we solely catch these issues by visually checking them and the probability that an incomplete/imperfect model is then used is pretty high.

JSN

@marchi said in Solibri can't import all IfcSpaces:

@Matti-Kannala if there is an option to import invalid IFC, isn´t there a possibility to implement a warning sign before we import and load a model? Like “Not everything has been loaded”?

+1

That would definitely be a helpful information.

agroni

@marchi
I Agree… Warnings are most of the time helpful