Configuration File

Export user-defined property sets is the equivalent to exporting schedules as property sets, however, it uses a text file as a configuration file instead. The default template file can be found here: C:\ProgramData\Autodesk\ApplicationPlugins\IFC 20xx.bundle\Contents\20xx and includes detailed instructions and examples.

Everything between <> is replaced:

<Pset Name>: Name of the Pset, don’t use Pset_ as Prefix as this is reserved for standard IFC Psets

I[nstance]/T[ype]: used to specify Instance or Type properties, obsolete in current versions as the selection happens automatically, use either I or T

<element list separated by β€˜,’>: this is the place where either one or more IFC classes for which this Pset will be applied are listed, e.g. IfcWall, IfcSlab, IfcColumn. If the Pset should be applied to all elements, use the next higher entity ( with - IfcBuildingElement building elements like walls, doors, etc. or IfcElement to include also Civil and Distribution elements. This can be checked in the IFC documentation by searching for Entity inheritance.

Note: Starting with Revit 2024.1, it is no longer sufficient to specify the IFC class such as IfcElement or IfcWall to export Type Properties , but rather requires the specification of the type (e.g. IfcElementType or IfcWallType). As there is no type definition for doors and windows in IFC 2x3 schema, IfcDoorStyle and IfcWindowStyle need to be used. When exporting to IFC4, IfcDoorType / ifcWindowType are used.

<Property Name>: property name as displayed in Revit

<Data type>: the supported IFC data types are listed in the template file, the most commonly used are Text, Integer, Real, Length, Volume, Boolean.

There are currently 40 IFC property types that are supported in the Revit IFC export. Not every property type in Revit can be mapped directly to the IFC type, as IFC uses a different way of specifying some of the units. When mapping Revit data type that does not have a direct mapping to the IFC data type, it can be mapped to a primitive type, e.g. Real or Integer. This will export the value unconverted using Revit internal units.

<[opt] Revit parameter name, if different from IFC> is an optional field and can be omitted, if the name of the Revit property should also be used for the IFC property. If the IFC property should have a different name, it can be entered here.

Note: All entries are separated by a <TAB> and the file should be saved in the UTF-8 format.

Example:

Last updated

Β© 2024 Autodesk Inc.