buildingSMART / buildingSMART/IFC4.x-development

Why does IfcRigidOperation support IfcPlaneAngleMeasure

Open
#710 4 comments 0 reactions 0 assignees View on GitHub
allocated allocated-core ifc-update-out
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

The usecase of IfcRigidOperation is to do a simple **translation** from A to B, most commonly when you truncate large coordinates.

Yet FirstCoordinate and SecondCoordinate allow IfcPlaneAngleMeasure... but why? Lat longs (i.e. angle measures) are very small numbers anyway which seem as though you'd never need to transform them, and the usage of another unit type complicates matters (default unit of angle measures ... radians / degrees?) and mixing of unit types between object placements which are IfcLengthMeasure + IfcPlaneAngleMeasure = ?

I'm a little surprised and confused on how to implement this. It looks as though it'll just create a lot of confusion for users.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.