Open Moult opened 4 years ago
so the IfcSite GUID in the shared parameters file is actually obsolete - we now have IfcSite GUID, IfcBuilding GUID and IfcProject GUID as built-in parameters (in addition to a few extra: Application Name, Application Version, and Organization). ... but they don't show up as properties, only in schedules, filters, tags, and ODBC export. I see no reason why they shouldn't also show up in project information, though, so have filed a task to amend this. This isn't an open source issue, so it would have to wait for a future release of Revit.
so the IfcSite GUID in the shared parameters file is actually obsolete - we now have IfcSite GUID, IfcBuilding GUID and IfcProject GUID as built-in parameters (in addition to a few extra: Application Name, Application Version, and Organization). ... but they don't show up as properties, only in schedules, filters, tags, and ODBC export. I see no reason why they shouldn't also show up in project information, though, so have filed a task to amend this. This isn't an open source issue, so it would have to wait for a future release of Revit.
Thank you, Angel. While your at it, would it be possible consider adding more of the IFC exporter parameters, from "File Header" and "Project Address, either nominated as shared parameters or built in to project information? It's hard to explain the workflow, where users need to fill them out in the exporter and write back to PI, or the parameters as Author, can only be used in the exporter, not as parameters elsewhere.
In general, we are rethinking parameters as a whole. I think the overall goal would be to have 0 IFC shared parameters (at least, bSI-defined ones; there may be custom ones), so I want to hold off adding a few more parameters here and there until we have a full story around this. It is on the roadmap.
so the IfcSite GUID in the shared parameters file is actually obsolete - we now have IfcSite GUID, IfcBuilding GUID and IfcProject GUID as built-in parameters (in addition to a few extra: Application Name, Application Version, and Organization). ... but they don't show up as properties, only in schedules, filters, tags, and ODBC export. I see no reason why they shouldn't also show up in project information, though, so have filed a task to amend this. This isn't an open source issue, so it would have to wait for a future release of Revit.
The builtin parameters show in Revit UI after running an IFC export with the store globalid after export option enabled.
And they are read-write now, I believe. But they aren't there "by default".
What is the recommend workaround until this is fixed in Revit? I can:
1) Ask people to export first, and then edit the parameters, or 2) Ask people to create the parameters manually to their project with the same name as the builtin ones 3) Distribute a forked version of the shared params file with the additions and let them select from there (same as option 2, but with a bit more guidance I guess)
I would think option 1.
no using the shared parameters, can I get the GlobalId of the IfcProject, or IfcSite or IfcBuilding?
In this file: https://github.com/Autodesk/revit-ifc/blob/master/Install/Program%20Files%20to%20Install/IFC%20Shared%20Parameters-RevitIFCBuiltIn_ALL.txt
If I want to manually specify the
GlobalId
of theIfcProject
, orIfcSite
orIfcBuilding
, the only applicable parameter I see isIfcSiteGUID
.However, I have tested an import and see that you can override them with these parameters in the
Project Information
dialog:Can the discrepancy by resolved, and the additional parameters added for
IfcBuilding
andIfcProject
?