engine_components
engine_components copied to clipboard
ThatOpen
Custom model tree for the multiple IFC files
Description 📝
Custom model tree – to show both federated Ifc Model structure and individual Ifc model structure Can we also have option to move the model or orient the model origin as well as the orientation of the building?
Suggested solution 💡
No response
Alternative ⛕
No response
Additional context ☝️
No response
Validations ✅
- [X] Read the docs.
- [X] Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.
Hey @ThatMetaverseArchitect I'm going to create a new issue for orientating the building and leave this just to make the entity tree support multiple models. I'm adding this to the roadmap system!
Hey @ThatMetaverseArchitect can you please also resend this model? Thanks!
FIxed! The library now provides features to code your own tree according to your needs, as well as federation tools to make sure your models are aligned.
@agviegas federation works... do you know how we can export the ferderated models as a MERGED IFC?
IFC merging is possible with the core library, but we haven't created any specific component for it yet. But we plan to do it, hopefully in the next milestone, so the template already has a built-in merge function. If you create a feature issue in this repo, I'll make sure to keep you posted once we do it
@agviegas ,
we had a look at the current template. We were not able to find or understand a built-in merge function.
Did you mean that built-in merge as a federation feature from the model tree like the image below?
we understood merge IFCs as one IFC model so that we can export as a merged IFC model from the app.
Once you clarify this, I will create a feature issue in this repo so that we can keep tracking on the updates. Thanks.
Currently there's no built-in merge function to export a new merged IFC, but we can add it as a feature. Feel free to create a new feature issue and I'll take care.