INQ: Conduit is not editable

[avinash-218]

INQ: Conduit is not editable

[AngelVelezSosa]

That's not supported out of the box. You'd have to create some experience around the import progress to map it to a "proper" conduit family for it to work as if it were created natively.

[AngelVelezSosa]

This isn't part of the Revit IFC. The open isn't really currently open-sourced, not because it is secret in any way, but because the priority has been on export and link (we had been waiting on IFC4 Design Transfer View to be official, but that likely won't be happening...)

This isn't really an IFC issue per se but a UX issue. IFC doesn't have a concept of Revit families, so any full native interop needs some sort of hand-holding to get the right data created. There are many partial solutions out there, but I am not one to recommend one or the other. There are definitely people on this board associated with those alternatives that might have pointers.

[avinash-218]

Is there any resource using which I could understand how to do such mapping? not just for conduit but for every other revit native elements??

Since revit-ifc is opensourced, referring me the source code snippets to understand such mapping would be helpful.

[avinash-218]

thanks !!

[avinash-218]

That's not supported out of the box. You'd have to create some experience around the import progress to map it to a "proper" conduit family for it to work as if it were created natively.

Having a plugin in revit would do the work, apart from this, anything you could suggest so that i can have the mapping in place for all revit family items??