Troels Olsen

If I remember correctly, you can not. But I'd argue that; Ifc does have a attribute for the number, it's just called name. As an example, a door: Name = short ID = Mark = door number. Name in IFC, always = short ID. In the case of the project, IfcProject Root.Name could/should easily originaly have been ment to refer to a short project number for the client, not the consultant. So what I often do in my specifications, is requesting a value for the project number/ID. The consultant can leave out their...

Hi Matthew. We often run into the same problem with our MEP consultants on healthcare projects. They handle it same way by splitting the export - but if possible it's prefferable to recieve the files as 'one system per file', not 'one floor per file', for downstream purposes.

Hi Antonio. I´d recommend that you set as a goal, to add the IfcExportAs and IfcExportType shared parameters to all families in your library and over time fill them all out with appropiate entities and enumerated types. Obviously starting with the ones you use the most. This will give you better control over the export ,raise the quality of your files considerably and in the long run save you time. Actually I think you will find, that IFC is more comprehensive for MEP, than the revit categories.

We don't make types for railings. Are you sure? Supported IFC entities indicate that IfcRailingType is supported.

Hi David, The first problem i usually have, is that I forget a blind "tab" in the empty fields, where the RVT parameter match my desired IFC one ie: Propertyset: MySet I IfcBuilding MyParameter1 Text (Tab) MyParameter2 Text (Tab) That might be it?

We need to be able to apply IfcSystems to all IFC2X3 elements to aggregate freely, not only IfcDistributionElements that are (needs to be..) connected. To my knowledge this is not currently possible and is a real limitation. For IFC4, we will naturally need IfcBuildingSystem and IfcDistributionSystem too.

Just ran into this. I have a wall, with sweeps embedded. The wall contains info on export, but the sweeps exports to IfcBuildingElementProxy, does not contain any info or any relations to the wall! So I have no real control over this element. I'd expect that the sweeps embedded inside the construction, be a part of the wall, not export as individual elements (even without any relations, information etc). A reveal embedded into the wall, does cut and is related to the wall. Another sweep is applied...

Try adding a yes/no parameter called "LoadBearing" on type level, for those two categories, and turn it of where needed. I use the shared parameter from here https://sourceforge.net/projects/ifcexporter/files/Misc/ File: IFC Shared Parameters File 3-10-15.txt