Yes, exactly. This is the catch. Revit & others are violating the IFC somehow, they will be exposed.yorik wrote:The problem is, the radius is already written into the IFC file by FreeCAD. But other applications export additional properties so when they read the file back, they can do special things with these properties. Revit does that a lot. But it is not something that is part of the IFC definition, it's each application that chooses to do like they want.
Ya, sure. I'll explore the IFC file of Revit in detail and find those additional properties.yorik wrote:So we need to know which IFC property needs to be there for solibri to see the radius. If you discover that, we can implement it in FreeCAD.
Alright, thanks. I'll go through the references you mentioned.yorik wrote:As for how IFC is implemented in FreeCAD, it is a much too big question to be responded here in a simple way. We basically use IfcOpenShell, and everything happens in src/Mod/Arch/importIFC.py. The insert() function takes care of importing, while the export() function does the export. I suggest you look at that file, and check the ifcopenshell website, there are a couple of python examples there that show how it works.
@Amrit3701, we need to have a look at these.