Warning - error importing Georeferenced data (Point Clouds, DEMs, ...) as Point Clouds, STMs or 3SMs in OpenRoads Designer

When is this going to be fixed? Are there any versions of ORD that do NOT have this bug?

I can't answer for first question, all ORD versions are impacted.
If you need to apply these type of workflows, then please log a Service Request to help manage priorities.
The workaround is to strip GCS from source data (or work from a non-georeferenced file).
Best

Thanks for bringing this to light! I thought this was just an issue affecting the South African coordinate systems. I'm sort of relieved knowing everyone is in the same boat

After years of telling my colleagues it's best practice to work with coordinate systems if you're working with coordinated data, I'm now telling them the opposite.

We import LAS/LAZ files.  Are the geo-referenced point cloud elevations correct at import (when the pod file is created) and the error occurs when the geo-referenced point cloud is used to create a Terrain?  

Sorry for late response.

The issue arises at referencement (LAS/LAZ attachement and POD creation). POD Elevations are incorrect.
TM from POD will also be incorrect (and STM will be 2 times lower)  STM in red and TM from POD is blue.

So Best practice is to work from non georeferenced DGN or strip GCS from incoming data