# Enquiry about the meaning of ZED360 Calibration result

**URL:** <https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727>\
**Category:** C++\
**Tags:** sdk, unity\
**Created:** [February 2, 2026, 6:22am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727 "2026-02-02T06:22:21Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![waystogetthere](https://community.stereolabs.com/user_avatar/community.stereolabs.com/waystogetthere/32/5710_2.png) [@waystogetthere](https://community.stereolabs.com/u/waystogetthere)\
**Post date:** [February 2, 2026, 6:22am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/1 "2026-02-02T06:22:21Z")

</div>

**Dear ZED Team,**

Recently, I have been working with the **Fusion API** , specifically the **Livelink (Fusion) project**, using **three ZED 2i cameras connected to the same local computer**.

As part of the workflow, the Fusion API requires the **multi-camera calibration JSON file generated by ZED360** as input. I am particularly interested in understanding the **`pose` field** in this configuration file, which consists of **16 numerical values**.

**My questions are as follows:**

1. Could you please clarify what these **16 values in the `pose` field represent**?

2. If some of these values correspond to **camera position (translation)**, are the units expressed in **meters** (e.g., 1.39 m, 0.88 m, etc.)?

3. I recall seeing a statement suggesting that **the first camera connected to the computer is set as the world origin (x = 0, y = 0, z = 0)**.  
However, after inspecting the code and printing the camera translations at runtime, I noticed that **Camera 0 does not have a (0, 0, 0) translation**.

I have attached:

- The **calibration JSON file** generated by ZED360

- A **code snippet showing the printed camera translations** , which appears to be related to the values in the calibration file

The motivation behind these questions is that, before proceeding to analyze **fused skeleton joint data** , I would like to have a clear understanding of the **coordinate system and spatial reference frame** used by the Fusion API.

**Thank you very much for your time and support.**

Best regards,

waystogetthere

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [February 2, 2026, 11:20am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/2 "2026-02-02T11:20:13Z")

</div>

Hi @waystogetthere  
You can find all the relevant information to use the Fusion module on the ZED SDK API documentation:

> **[Fusion Module | API Reference | Stereolabs](https://www.stereolabs.com/docs/api/group __Fusion__ group.html)**

Please do not hesitate to report any missing information or parts that are not clear.

---

<div class="post-metadata">

**Author:** ![waystogetthere](https://community.stereolabs.com/user_avatar/community.stereolabs.com/waystogetthere/32/5710_2.png) [@waystogetthere](https://community.stereolabs.com/u/waystogetthere)\
**Post date:** [February 3, 2026, 8:38am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/3 "2026-02-03T08:38:33Z")

</div>

Hi, thanks for your feedback. I would like to clarify the interpretation of the camera pose returned at runtime when using Fusion.

1. Interpretation of the runtime camera translation  
When printing the camera pose returned by `cfg.pose.getTranslation()` in Fusion, I obtain a translation such as  
`(x = 0, y = 1.3984, z = 0).`  
Could you please confirm whether this means that the camera origin is located 1.3984 meters directly **above** (the coordinate system is set to `LEFT_HANDED_Y_UP`) the Fusion world origin, i.e. the Fusion world origin lies directly below the camera along the Y axis?
2. Difference between calibration JSON and runtime pose (Y sign only)  
I noticed that the Y component of the translation has the opposite sign compared to the value stored in the ZED360 calibration JSON file, while the X and Z components remain unchanged.  
In my code, the Fusion runtime is explicitly initialized with `LEFT_HANDED_Y_UP`, whereas the ZED360 calibration result appears to use a default Y-down coordinate convention.  
Could you please confirm whether this difference in the Y sign is expected and caused by the coordinate system conversion applied when loading the calibration file (i.e. Y-down in calibration vs Y-up in runtime)?  
Thank you for your clarification.

---

<div class="post-metadata">

**Author:** ![BenjaminV](https://community.stereolabs.com/user_avatar/community.stereolabs.com/benjaminv/32/3863_2.png) [@BenjaminV](https://community.stereolabs.com/u/BenjaminV)\
**Post date:** [February 3, 2026, 10:24am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/4 "2026-02-03T10:24:15Z")

</div>

As you said, the pose available in the calibration file generated by ZED 360 is in `COORDINATE_SYSTEM::IMAGE` (with Y down).

The first camera to be loaded is defined as the world origin; its position will be (0, -H ,0) with H being its height.

---

<div class="post-metadata">

**Author:** ![waystogetthere](https://community.stereolabs.com/user_avatar/community.stereolabs.com/waystogetthere/32/5710_2.png) [@waystogetthere](https://community.stereolabs.com/u/waystogetthere)\
**Post date:** [February 3, 2026, 3:49pm UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/5 "2026-02-03T15:49:57Z")

</div>

Thanks! This is really helpful!

---

<div class="post-metadata">

**Author:** ![waystogetthere](https://community.stereolabs.com/user_avatar/community.stereolabs.com/waystogetthere/32/5710_2.png) [@waystogetthere](https://community.stereolabs.com/u/waystogetthere)\
**Post date:** [February 4, 2026, 6:49am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/6 "2026-02-04T06:49:41Z")

</div>

Thanks, that clarifies the coordinate system.

Following this, I noticed that in the calibration JSON from ZED360, the pose of the first loaded camera is essentially a pure translation, placing the camera origin at (0,−H,0) in IMAGE coordinates. **However, the estimated height H does not match the physically measured camera height (I measured H′ in the real world).**

Given this, would it be valid to **define a simple linear correction** (rigid translation) to adjust the first camera pose, so that the mapped point can be (0,−H′,0) instead of (0, H, 0)? Since there is a calibration error for the first loaded camera, if the relative position between the reference camera and other cameras, we can then apply the same correction consistently to all other camera poses in the calibration file.

From a geometric point of view, this would correct the world-frame vertical offset while preserving all inter-camera relative poses.

---

<div class="post-metadata">

**Author:** ![waystogetthere](https://community.stereolabs.com/user_avatar/community.stereolabs.com/waystogetthere/32/5710_2.png) [@waystogetthere](https://community.stereolabs.com/u/waystogetthere)\
**Post date:** [February 4, 2026, 6:53am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/7 "2026-02-04T06:53:18Z")

</div>

For example, the calibration result shows that the first loaded camera has a position (0 1.38 0) in the fusion world, where the origin point in fusion world is 1.38m right below the first loaded camera.

The pose matrix is:

T1 =

```auto

1 0 0 0

0 1 0 -1.38

0 0 1 0

0 0 0 1

```

However, the true height is 1.50m, so the true spatial mapping matrix is:

T1\_{true} =

```auto
1 0 0 0

0 1 0 -1.50

0 0 1 0

0 0 0 1

```

Note that we can find a matrix C such that T1\_{true} = CT1

Then we should apply the C to both T2 and T3

---

<div class="post-metadata">

**Author:** ![SL-PY](https://community.stereolabs.com/user_avatar/community.stereolabs.com/sl-py/32/3_2.png) [@SL-PY](https://community.stereolabs.com/u/SL-PY)\
**Post date:** [February 5, 2026, 8:25am UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/8 "2026-02-05T08:25:14Z")

</div>

hi,  
As the system is rigid between the cameras, If you want to ‘move’ one, you should apply the same transformation to each camera of the system (Apply only translations, as the rotation is given by the camera IMU).  
The height of the first camera (H) is computed by ZED360 only if your anckles are being seen during the calibration process, otherwise it remains at 0. The wrong measurement you get may came from a poor detection of this.

---

<div class="post-metadata">

**Author:** ![waystogetthere](https://community.stereolabs.com/user_avatar/community.stereolabs.com/waystogetthere/32/5710_2.png) [@waystogetthere](https://community.stereolabs.com/u/waystogetthere)\
**Post date:** [February 5, 2026, 3:35pm UTC](https://community.stereolabs.com/t/enquiry-about-the-meaning-of-zed360-calibration-result/10727/9 "2026-02-05T15:35:01Z")

</div>

Thanks for the clarification — that makes sense.  
I’ll re-run ZED360 calibration ensuring the ankles are clearly visible throughout the process (to avoid an incorrect H estimate).  
In the meantime, since the camera rig is rigid, I’ll apply the same global translation offset (Δy = H′ − H) to **all** camera poses in the calibration JSON (translation only, no rotation changes), so the inter-camera geometry remains unchanged.
