ifc-properties -- Property sets, quantities and units -- the non-geometric payload most
consumers actually want.
references/ifc-spec/ ships the official property set definitions as XML:
317 for IFC2x3 and 420 for IFC4. That is a machine-readable catalogue, so
standard Psets are data here rather than hand-written tables.
Module map
| Module | Role |
|---|---|
pset |
IfcPropertySet and single/enumerated/list/table properties |
quantity |
IfcElementQuantity: length, area, volume, weight, count |
template |
IfcPropertySetTemplate and property templates |
standard |
The official Pset catalogue from the shipped XML definitions |
unit |
Unit assignment, prefixes and conversion-based units |
value |
IfcValue measure types and their interpretation |
query |
Lookup helpers: property by name, pset by element |
nesting |
Bounded, cycle-aware traversal of complex properties and quantities |
error |
Why a property lookup failed |
Status
Implemented: value, pset, quantity (including transactional quantity
edits), unit, template, query and the release-bound exact lookups.
standard is a reserved scaffold; the shipped Pset/Qto catalogue is
ifc-template-catalog. Open work is tracked in GitHub issues.
What this crate will not do
It never computes a shape measurement. An IfcQuantityArea is what the
authoring tool asserted, and it may disagree with the geometry. Callers
that want a check compute the value with a geometry service and pass it to
[compare], which reports agreement rather than inventing it.