Class TIfcDerivedUnitElement
Unit
Declaration
type TIfcDerivedUnitElement = class(TIfcPersistent)
Description
A derived unit element is one of the unit quantities which makes up a derived unit.
Spec: https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcDerivedUnitElement.htm
Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 4468).
Hierarchy
- TObject
- TPersistent
- TComponent
- TIfcPersistent
- TIfcDerivedUnitElement
Overview
Methods
| Protected | function WantsGlobalId: Boolean; virtual; |
| Protected | class function IfcClassName: String; virtual; |
Properties
| Published | property GlobalId: String read FGlobalId write FGlobalId; |
| Published | property Unit: TIfcNamedUnit read FUnit write FUnit; |
| Published | property Exponent: Integer read FExponent write FExponent; |
Description
Methods
| Protected | function WantsGlobalId: Boolean; virtual; |
|
This item is declared in ancestor TIfcPersistent.
If Strictly following the spec, this should be only defined for TIfcRoot, because only IfcRoot has GlobalId. In reality, we need GlobalId at TIfcPersistent to load some files, and we sometimes need | |
| Protected | class function IfcClassName: String; virtual; |
|
This item is declared in ancestor TIfcPersistent. Name for the IFC standard, used in IFC files. By default, this is just ClassName with prefix 'T' removed. | |
Properties
| Published | property GlobalId: String read FGlobalId write FGlobalId; |
|
This item is declared in ancestor TIfcPersistent. Globally unique identifier for the object instance. Note: Not declared as TGUID, because TGUID cannot be published, but also we don't really need it: for our purposes, this identifier is just an arbitrary string. Note: IFC 4.3 specification puts this only at IfcRoot, not at every IFC class. But testcase https://github.com/buildingsmart-community/Community-Sample-Test-Files/blob/main/IFC%204.0.2.1%20(IFC%204)/ISO%20Spec%20archive/wall-with-opening-and-window.json (from IFC 4.0) shows this can be present at any IFC class, in particular TIfcGeometricRepresentationContext. In fact, TIfcGeometricRepresentationContext needs to have IFC JSON documentation says this, which seems to (unfortunately it is not unambiguous enough...) allow this at any IFC class: "Whereas the | |
| Published | property Unit: TIfcNamedUnit read FUnit write FUnit; |
|
The fixed quantity which is used as the mathematical factor. Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 4474). | |
| Published | property Exponent: Integer read FExponent write FExponent; |
|
The power that is applied to the unit attribute. Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 4477). | |
Generated by PasDoc 0.17.0.snapshot.