array(2) { ["text"]=> string(41) "! This script is crucial for my workflow." ["context"]=> string(78) "Any help would be greatly appreciated! This script is crucial for my workflow." } array(2) { ["text"]=> string(134) "[first standard property](https://community.osarch.org/discussion/1738/standardizing-bbim-property-sets/p1 "first standard property")!" ["context"]=> string(168) "I'm thinking this would be a good [first standard property](https://community.osarch.org/discussion/1738/standardizing-bbim-property-sets/p1 "first standard property")!" } array(2) { ["text"]=> string(1) "!" ["context"]=> string(1) "!" } array(2) { ["text"]=> string(1) "!" ["context"]=> string(7) "Thanks!" } Objects Disappear from Assemblies When Setting Storey

OSArch Community

Objects Disappear from Assemblies When Setting Storey

  1. P

    Hey everyone,

    I have a script that uses 'Linked Duplicates' to duplicate assemblies (IfcElementAssembly) and distribute houses in a development. This script relies on the assemblies working correctly.

    I need to assign objects within these assemblies to their respective storeys (IfcBuildingStorey), but when I do that, the objects are removed from the assemblies, breaking my 'Linked Duplicates' script.

    Is there a way to assign objects to storeys without them being removed from assemblies, so my 'Linked Duplicates' script continues to work?

    Is this removal of the relationship when setting the storey intentional (to follow good practices or the IFCSchema), or is it a bug in the addon?

    Any help would be greatly appreciated! This script is crucial for my workflow.

  1. W

    I could be wrong, but duplicating the IfcElementAssembly does not automatically duplicate its component elements (I remember trying this a long time ago and it didn't work). Maybe IfcElementAssemblyType is the correct way.

  1. P

    Correct, ctrl+d does not duplicate the components, crtl + shift + d makes a linked duplicate that duplicates components. See https://github.com/IfcOpenShell/IfcOpenShell/pull/3328. I believe Ifcassemblytype can't have geometry, just psets. My problem is just I can't change the spatial container of the elements inside the assembly

  1. T

    My problem is just I can't change the spatial container of the elements inside the assembly

    I don't think you can do this currently...

    I actually think you can't do this via the IFC schema either unfortunately.

  1. T
  1. T

    I wonder if it's worth coming up with an approach to do 'linked groups'. IfcGroups allow for a more flexible mechanism to logically group elements without enforcing a containment hierarchy. I think freecad does this. It's not officially supported by IFC, but this 'problem' has come up again and again and again. Ping @yorik

  1. B

    @theoryshaw What actually link the "linked aggregates" are IfcGroups, most of the logic is already there. So, it seems possible, but I would have to check before confirming. Could you please create an issue as a feature request?

  1. B
  1. T
  1. P

    @bruno_perdigao said:

    @theoryshaw What actually link the "linked aggregates" are IfcGroups, most of the logic is already there. So, it seems possible, but I would have to check before confirming. Could you please create an issue as a feature request?

    @bruno_perdigao, @theoryshaw: should I create the issue? I'm newbie, but if needed I will try.

    @bruno_perdigao said:

    For now, maybe it’s worth using spatial reference as discussed here: https://community.osarch.org/discussion/comment/24421/#Comment_24421

    I've read the discussion, I will try the references, but for that I think I will need to dismantle my assembly and assign the objects to subspaces. The duplication method will be similar to the linked duplicates: ctrl-shift-D?

    Thanks!

  1. T

    should I create the issue? I'm newbie, but if needed I will try.

    go for it, always go for it. :)

  1. P
  1. T

Login or Register to reply.