New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BlenderBim - Export ifc from selection - Feature request #4316
Comments
You might know this already. The following is one way to do it... 2024-02-13_10-55-06_blenderBlenderblender.mp4 |
Wow! Thanks! |
Unfortunately I am receiving the following error: Python: Traceback (most recent call last): |
Can you share the file, or a parred-down version of it, if sensitive? |
Btw, i think i was incorrect in thinking you could create a new file... I just tested, and it doesn't seem to work, like i thought it would. Sorry for the misinformation. |
Unfortunately I can't share the file, it's under a very strict NDA. |
the only way I managed to extract the bars I want in a separate ifc was to delete all other elements not in my selection. |
yes, unfortunately, this is a known issue. |
Have you tried using the ExtractElements parch recipe? I think it does what you're asking (although the graphical integration isn't as slick as it could be) |
I tried it pasting the GlobaID of one element into the Query, but I don't know how to paste in multiple GuID's. |
Little update. It actually works, just pasting the Guid's separated by commas. The problem I faced was actually for some elements which give me an error when trying to export. It's something with this ifc file. I will paste the error here:
|
This error looks like file has some invalid ifc - it seems like it doesn't have either IfcApplication or IfcPersonAndOrganization to initialize IfcOwnerHistory. As for the original feature request, it can indeed be done by generating query listing selected guids in Search section and then use it for ExtractElements IfcPatch recipe. I'm not sure if we should add special "extract from selection" button to this recipe UI since then it would make sense copying the entire Search UI there. |
For the moment I coded my own plugin which does this. It's quite basic, stores the guids from selection as a string delimited by commas and pasted it into the IfcPatch recipe. I needed something then. It worked, but as I said that particular ifc had some issues. |
I assume your file was in IFC2X3 and in IFC2X3 OwnerHistory on IfcRoot elements is not optional. See: https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/TC1/HTML/ifckernel/lexical/ifcroot.htm |
It would be nice to have a feature to be able to extract selected objects to an output ifc.
Similar to "ExtractElements" recipe from Ifc Patch but for specific selected objects, not for a full subset of elements.
The text was updated successfully, but these errors were encountered: