ifc-element-type
Element, resource, and process type definitions: the IfcTypeObject catalogue.
| Status | Implemented |
| Latest release | 0.4.2 (2026-10-28) |
| Registries | crates.io ifc-element-type |
| Via the facade | openbim-ifc feature element-type |
| API documentation | rustdoc · docs.rs |
| Source | crates/ifc-element-type/ |
Overview
Element, resource, and process type definitions.
An IFC model separates what a thing is from where it sits. The type definition carries the shared description: a pump type names the pump model, and every pump placed from it inherits that.
This crate owns the 132 concrete IfcTypeObject subtypes. They sit in one crate because they are one uniform shape with one shared WHERE rule, not because they are one domain: the list spans HVAC, structure, furniture, resources and processes. Splitting them across domain crates would copy the same rule and the same slot table into a dozen places.
The catalogue in table is generated from the schema by scripts/gen-element-types.py; create_type is the writer. It takes no model and writes the catalogue's IFC4X3 layout; create_type_in and create_type_with_owner_history write the model's declared release, which IFC2X3 needs for its required OwnerHistory (#202).
Depends on
Changes
Latest release, 0.4.2 (2026-10-28):
Changed
- Copyright holder in NOTICE and licence texts is rheonda.
Full history: crates/ifc-element-type/CHANGELOG.md