I know this is an older thread, but I’ve been exploring this workflow from the Rhino side and thought I’d share one approach that may still be useful for others finding this discussion.
I’ve been using Heron in Grasshopper to establish the geographic reference in Rhino, and then exporting the georeferenced model as KMZ for upload to Cesium ion.My current workflow is roughly:
This allows the model to be positioned geographically before it is brought into Cesium, rather than positioning it manually afterwards. One thing to note is that the height may still need to be adjusted manually in Cesium ion, depending on the elevation reference and the source data. In my workflow, I use the geographic reference primarily to establish the horizontal position, and then check and adjust the vertical placement in Cesium ion as necessary.The image below shows an example of the same model in Rhino and after being placed in its real-world 3D context in Cesium ion.
I’ve shared more about this Rhino → Cesium workflow here:
Rhino Models in Cesium
Cesium ion is also currently testing direct Rhino (.3dm) support through Early Access, so it will be useful to see how georeferencing and placement are handled in that workflow compared with the KMZ approach.