You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Case: use lowercase (always? or when part of the table?)
The docs state that the name is case insensitive so IMO no need to have a rule for that. But there should be a rule to ensure that the (case insensitive) name of a conversion-based unit appears in the table. Example:
US SURVEY FOOT is valid, foot_US is not.
Value: when using a name from this table make sure the value conforms to the table.
Agree, with some tolerance to account for both entering the value exactly as shown in the table versus calculating or deriving it from unit libraries. For example someone might use the pint library to derive the conversion factors.
IfcConversionBasedUnit has a string label for its name, but the docs have a recommended table of units. I would propose the following two rules:
https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcConversionBasedUnit.htm
The text was updated successfully, but these errors were encountered: