-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MapConversion or RigidOperation, when no transformation/translation are required? #19
Comments
If you have to convert the coordinates When you say map meters, you probably mean projected coordinates from a curved surface to a circular plane i.e. map, right? In that case no conversion is required and Curious, if this is the understanding of the rest of the group. 😄 |
Sorry but I have been out of action for a while. I agree with Sergej that it is option 1. The data is already in map metres (that is, Eastings and Northings) and so IfcMapConversion should not be used. |
Another question - edge cases (a) Data already in map coordinates and map metres
when it is only a zero translation? Or can IfcRigidOperation be left out? (b) IfcMapConversion and IfcMapConversion when it is just a unit operation. That is, scales all one, zero rotation and translation This is extremely important because one has to be aware that the data will be inaccurate if the length covered is too large. EDIT: Markdown syntax. |
+1 for option 1. |
Option1 it is. Thanks all |
There is the need to agree on the best pair of IFC entities to be used for the following scenario:
Option 1
Use IfcRigidOperation with its attributes
FirstCoordinate
,SecondCoordinate
,Height
set to0
.Example
Option 2
Use IfcMapConversion with its attributes
Eastings
,Northings
,OrthogonalHeight
set to0
, and itsScale
set to1
Example
@LeeGregory12d @pjanck @SergejMuhic what would be the best option in this scenario?
The text was updated successfully, but these errors were encountered: