Mapping to IFC Non-Spatial Elements

The IfcElement entity and classes derived from it make up most of the physical objects in an Ifc model, and are usually directly or indirectly spatially contained within an instance of an IfcSpatialStructure derived entity.

Note:
That IFC 4 added many new IFC Element types, and the examples here may use both schemas.

Most mappings in a mapping configuration will therefore be element mappings, and there may be:

• Multiple mappings from the same E3D Element type(s) to different IFC Elements (controlled by the E3D rule)

• Multiple mappings to an IFC Element from different E3D elements

• Mappings with an empty E3D Rule field, where the E3D element type(s) are enough to choose

• Mappings with an empty E3D Elements field, where the E3D rule determines the IFC Element

• Mappings with an empty IFC Element field which means Include E3D Elements of the specified types and matching any rule in the owning element – this includes geometry, and any relevant property sets

• Mappings may have a special value in the IFC Element field, Exclude which means that the E3D element, and any geometry and properties and any children it has are completely excluded from the exported IFC file

  Note:
  Remember that, as always, order is significant First match wins