This scenario was created based on a feedback from our users in the construction industry.


Sometimes, construction projects can have their own, local coordinate system. Often, these coordinate systems are connected to real coordinate system through some simple geometric transformations.


The goal of this scenario was to make sure that we can transform data from some standard coordinate system to a local coordinate system for some manipulations, such as scaling (Scaler), rotation (Rotator), and offset (Offsetter):



See attached template workspace - Scenario 9. Offset Rotate Scale.fmwt

A second workspace of the scenario should bring the point cloud back so that the point cloud after all the transformations matches the original point cloud:



See attached template workspace - Scenario 9. Scale Rotate Offset.fmwt

Inspecting the input and output of both workspaces in Data inspector shows that

• the first workspace correctly scaled, rotated, and moved point cloud to the local coordinate system (on the right side), and
• the second workspace moved, rotated, and scaled the modified point cloud back to its original position, so that the source and the final point clouds match each other (on the left side):

Note, that if you inspect their extents, you don't necessarily get the same numbers - if the extents of the modified point cloud are smaller than the extents of the source point cloud, FME will not update them. This does not affect the actual data. Calculating true extents can be quite expensive (performance-wise), however it might be inconvenient in some cases having them out of sync with the actual data spread - for example, for visualization purposes. In future releases of FME we may add an option that will enforce calculating the real data extents.