Section 47 of 102
46. Geometric Transformations
Stable section ID: S05-CON-007-SECTION-47 · 49 content blocks
Geometric Transformations define the mapping of positions, directions, orientations, and geometry between coordinate systems.
BDL shall support:
translation;
rotation;
rigid-body transformation;
coordinate-system conversion;
explicitly controlled reflection;
unit conversion;
approved scaling for nonphysical representations.
A transformation shall define:
Transformation ID;
source coordinate system;
target coordinate system;
translation vector;
rotation representation;
scale where permitted;
handedness change;
accuracy;
source;
status;
evidence.
Example:
transformation Node_To_Building {
from: @Node_N01.local_coordinates;
to: @Building_CS;
translation: [3600 mm, 3200 mm, 2400 mm];
rotation: euler_xyz(0 deg, 0 deg, 90 deg);
scale: 1.0;
}
Rigid physical Components shall normally use scale 1.0. Scaling physical geometry to make incompatible Components fit shall be prohibited.
Transformation chains shall be composed deterministically:
- transform(
- @Interface_Point,
- through: [
- @Interface_To_Cartridge,
- @Cartridge_To_Node,
- @Node_To_Building,
- @Building_To_Site
]
);
BDL tools shall detect:
missing transformations;
circular transformation dependencies;
inconsistent units;
handedness conflicts;
noninvertible transformations;
excessive accumulated uncertainty.
Reflections and mirroring shall be explicit because they may change Interface orientation, handedness, utility routing, structural behavior, and assembly sequence.
Measured As-Built transformations shall remain separate from nominal design transformations, with both linked through configuration status and evidence.