The Attribute speckle_type in IFC Models

Sicheng_Zhu · 3 November 2022 15:12

I have uploaded some IFC files and receive the data via API. But the attribute speckle_type is not displayed the same as the value in Speckle Server.

In Speckle Server there are IfcWall, IfcWindow. But in API there is only Base Type.

Could you please fix it, that we can also get the speckle_type in order to orgnize the data better.

dimitrie · 3 November 2022 16:58

Hi @Sicheng_Zhu, unfortunately that’s how stuff works in Speckle land. Longer explanation on why this is happening:

when we convert the ifc file, we do set the type to be IfcWall, etc.
in .NET, when receiving the data, Speckle looks for a type called IfcWall, and finds none
that’s because we haven’t implemented the ifc object model as strongly typed classes.

It is a legitimate request, and proably the easiest way to fix this is in the conversion of the ifc file, where we could store the type under another property that wouldn’t get overridden at deserialisation.

I’ve logged the issue and we should be able to pick it up one in the next weeks.

github.com/specklesystems/speckle-server

IFC: Store type in another property besides `speckle_type`

opened 04:57PM - 03 Nov 22 UTC

didimitrie

bug [ file import service ]

**Problem:** We store the IFC type in `speckle_type`. This prop gets rewritt…en on deserialisation in .NET to `Base` (as it should) because we don't have any IFC classes in our .NET OM. **Solution**: When parsing the IFC file, store the type twice: in speckle_type (doesn't hurt), but also in another property (say, `ifc_type`) so that it's available down the line in .NET. Related forum discussion: https://speckle.community/t/the-attribute-speckle-type-in-ifc-models/4004

Sicheng_Zhu · 4 November 2022 08:34

Hi Dimitrie. Thank you very much for the answer and logging the issue! I am looking forward to using the updated IFC version for further implementation!