Expand description
Currency and dimensional agreement for cost arithmetic.
§Why this exists
IfcMonetaryUnit states a currency as a plain string ("EUR", "GBP").
Nothing in the schema stops a file carrying cost values in two currencies,
and nothing marks which one a given IfcCostValue is in – the currency
lives on the project’s UnitsInContext, not on the value.
So summing two cost values is only meaningful when the file states exactly one monetary unit. When it states several, this crate reports the ambiguity instead of adding numbers that are not comparable. A silent sum across EUR and GBP is a wrong total that looks right, which is the worst failure mode a cost tool has.
§Slots, verified against IFC4 EXPRESS
IfcMonetaryUnit 0 Currency (IfcLabel, not an enum in IFC4)
IfcProject 8 UnitsInContext -> IfcUnitAssignment
IfcUnitAssignment 0 Units SET of unit entitiesEnums§
- Currency
Error - Why a monetary total could not be trusted.
Functions§
- monetary_
units - Every
IfcMonetaryUnitin the file, in file order. - project_
currency - The single currency this file’s costs are expressed in.