IFC dictionary classes don't have relatedIfcEntity

[Moult]

:)

[atomczak]

why would they have @Moult? They are THE IfcEntities already :)

[Moult]

It simply means that when writing code that integrates with the bSDD API the programmer needs to write an edge case conditional for the IFC dictionary which is different to all the other dictionaries. I guess that's OK if that's the intention.

[atomczak]

Please share a bit more about the use case. I know that Bonsai uses the RelatedIfcEntities to filter the classes. But if you have an IFC object it is already classified, so why would you search for more IFC entities related to it?

[Moult]

It's not about searching for IFC classes (which as you rightly say is superfluous), it's about searching for properties related to that IFC class.

[atomczak]

That's not really the intended use. Classes have properties specified explicitly, and they can be related to more than one IFC class. I suggest to only recommend IFC properties once you know the IFC entity of such object.

For example, a Sauna from CCI is related to IfcSpace, but it only has one property specified: HandicapAccessible. Providing all 212 properties of IfcSpace is possible but it does not mean that Sauna is an IfcSpace. For example, a Crown from CCI can be an IfcWall or an IfcRoof.