# Rhinoceros to cesium

**URL:** <https://community.cesium.com/t/rhinoceros-to-cesium/13089>\
**Category:** Cesium ion\
**Created:** [April 10, 2021, 9:03pm UTC](https://community.cesium.com/t/rhinoceros-to-cesium/13089 "2021-04-10T21:03:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndreasK](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/andreask/32/4637_2.png) [@AndreasK](https://community.cesium.com/u/AndreasK)\
**Post date:** [April 10, 2021, 9:03pm UTC](https://community.cesium.com/t/rhinoceros-to-cesium/13089/1 "2021-04-10T21:03:22Z")

</div>

Hello world,

I am only a beginner, so please forgive me if this question is trivial.  
I have a question about adding a cad model as an asset to Cesium Ion.

If I have a georeferenced 3D-model in Rhinoceros3D, in a known coordinate system (EPSG:25832, UTM 32).

I want to import that 3D model into cesium as an asset, and to get the geolocation right.

How can I get the placement of the 3D model correct in cesium?  
Does anyone know which format is best to use when exporting from Rhino?

Looking forward to learn from someone that knows better than me.

Best regards,  
Andreas K

---

<div class="post-metadata">

**Author:** ![sam.vargas](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/sam.vargas/32/4968_2.png) [@sam.vargas](https://community.cesium.com/u/sam.vargas)\
**Post date:** [May 28, 2021, 7:23pm UTC](https://community.cesium.com/t/rhinoceros-to-cesium/13089/2 "2021-05-28T19:23:41Z")

</div>

Hi,

Cesium Ion is geo-referencing aware and should support this automatically. If the detection fails or your source is not georeferenced [you can manually adjust the location of the asset in Cesium ion](https://cesium.com/docs/tutorials/locate-data/).

---

<div class="post-metadata">

**Author:** ![KensukeNakata](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kensukenakata/32/34470_2.png) [@KensukeNakata](https://community.cesium.com/u/KensukeNakata)\
**Post date:** [September 7, 2026, 3:11am UTC](https://community.cesium.com/t/rhinoceros-to-cesium/13089/3 "2026-09-07T03:11:37Z")

</div>

Hi @AndreasK

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:

**Rhino → Heron / GIS → WGS84 (EPSG:4326) → KMZ → Cesium ion**

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.

 ![2026-09-03_15h28_46](https://global.discourse-cdn.com/cesium/original/3X/5/c/5cca34520bc342d0b2005cea1901a875745ca73d.jpeg)

I’ve shared more about this Rhino → Cesium workflow here:  
Rhino Models in Cesium

> [@Rhino Models in Cesium](https://community.cesium.com/t/rhino-models-in-cesium/47023):
>
> Hi everyone, I’ve been exploring how 3D models created in Rhino can be connected with GIS and brought into a broader geospatial context through Cesium. In this workflow, I use Heron, a Grasshopper plugin for working with GIS data in Rhino, to establish the geographic reference in WGS84 (EPSG:4326). The georeferenced Rhino model is then exported as a KMZ file and uploaded to Cesium ion, where it can be visualised and shared within its real-world geographic context. Wh…

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.
