# GNSS Fusion Covariance, Missing gnss\_ref\_pose TF, and CMake Policy Warnings When Building ROS 2 Humble

**URL:** <https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733>\
**Category:** Software\
**Tags:** docker, jetson, ros2\
**Created:** [December 17, 2024, 6:34pm UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733 "2024-12-17T18:34:26Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![whypushhh](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/w/b5e925/32.png) [@whypushhh](https://community.stereolabs.com/u/whypushhh)\
**Post date:** [December 17, 2024, 6:34pm UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/1 "2024-12-17T18:34:26Z")

</div>

Hello,

I’m running the ZED ROS2 Wrapper (master branch) inside a Docker environment on a Jetson platform (L4T R35.4.1) with ZED SDK 4.2.2 and ROS 2 Humble, using a ZED X camera. When I enable GNSS by launching the wrapper as follows:

ros2 launch zed\_wrapper zed\_camera.launch.py camera\_model:=zedx enable\_gnss:=true gnss\_antenna\_offset:=[0.0,0.25,-0.6]

I have a GNSS source publishing on the `/smc_2000/fix` topic,

 ![image](https://community.stereolabs.com/uploads/default/original/2X/9/9227dcc778ca3ed9c532390dc4fcb02d4330d23f.png)

and the covariance values there are properly populated. However, the `pose/origin_fix` topic produced by the ZED Wrapper always shows a covariance array filled with -1 when GNSS is enabled.

 ![스크린샷 2024-12-06 170140](https://community.stereolabs.com/uploads/default/original/2X/4/47d742129434362e01848d33578a1778f561a153.png)

Additionally, when launching `zed_display`, the aerial map in RViz2 indicates that the `gnss_ref_pose` TF is missing

Because the Humble Docker image provided by `dustynv` is based on Ubuntu 20.04, I couldn’t install ROS Humble packages via apt and had to build from source. If you have any advice on that, please let me know. Also, despite using CMake version 3.22.1, I kept getting CMP0146 and CMP0148 warnings during the build. I ended up completing the build by adding `--cmake-args -Wno-dev`. I’m wondering if this could cause any issues.

Also, I ran the docker container with the `-v /etc/localtime:/etc/localtime:ro` and `-v /etc/timezone:/etc/timezone:ro` options on the host PC. Even though the header timestamps appear to be very similar when compared, I still occasionally encounter timestamp-related errors.

Thank you for your assistance!

---

<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:** [December 18, 2024, 11:09am UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/2 "2024-12-18T11:09:06Z")

</div>

Hi @whypushhh  
Welcome to the [StereoLabs](https://www.stereolabs.com/) community.

Unfortunately, covariance is not yet available for GNSS fixed position.

---

<div class="post-metadata">

**Author:** ![whypushhh](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/w/b5e925/32.png) [@whypushhh](https://community.stereolabs.com/u/whypushhh)\
**Post date:** [December 19, 2024, 2:22am UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/3 "2024-12-19T02:22:08Z")

</div>

Hi, @Myzhar thank you for your previous response, but unfortunately, I couldn’t fully understand it because I encountered an error related to covariance.

Let me explain my current setup and situation:

1. **Environment** :

- I am **not using Docker**.
- Host configuration:
  - ROS 2 Foxy
  - `zed-ros2-wrapper -b humble-4.1.4`
  - ZED SDK 4.1.4

1. **GPS Topic** : When I check the `/fix` topic using `ros2 topic echo`, the covariance data appears to be normal, as shown below:  

2. **GNSS Fusion** : I perform GNSS fusion by running the following command:  
ros2 launch zed\_wrapper zed\_camera.launch.py camera\_model:=zedx enable\_gnss:=true

- I modified `config/common.yaml` to set `gnss_enable: true`, but this did not take effect, so I forcibly set it via the terminal.

1. **Results** :

- The `/zed/zed_node/pose/origin_fix` topic shows the following:  

- The `/zed/zed_node/pose/fused_fix` topic shows the following:  

Although the latitude, longitude, and altitude appear to be correct, the covariance in `/origin_fix` is filled with `-1`.  
5. **Code Review** : I reviewed the `zed_camera_component.cpp` code at line 8170:

 ![스크린샷 2024-12-19 111416](https://community.stereolabs.com/uploads/default/original/2X/c/cbcb2ddc11680711792fe2d5d97ca0662e29e542.png)

- It seems that if the covariance type is `COVARIANCE_TYPE_UNKNOWN`, it is filled with `-1`. However, in my case, the type is `2`, which is not `unknown`.

1. **Logs and Timestamp Issue** : I am also seeing logs indicating “covariance is small, and the timestamp is mismatched.” These logs repeat very quickly:  
 ![스크린샷 2024-12-19 110412](https://community.stereolabs.com/uploads/default/original/2X/4/44d36c8519a88c932ead286eabdfcdf2d6a1930f.png)  
 ![스크린샷 2024-12-19 105658](https://community.stereolabs.com/uploads/default/original/2X/1/107cb487ddf50853ac374a32f492819d9226f894.png)

* * *

### Questions:

1. Why is the covariance in `/origin_fix` filled with `-1` when the covariance type is `2` (not `COVARIANCE_TYPE_UNKNOWN`)?
2. Could there be a configuration or process I missed in enabling proper GNSS fusion?
3. Regarding the timestamp issue:

- What might cause the timestamp mismatch?
- Is there a recommended approach to synchronize timestamps for ZED and GNSS fusion?

I would greatly appreciate your advice and suggestions to resolve these issues. Thank you!

---

<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:** [December 30, 2024, 3:06pm UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/4 "2024-12-30T15:06:45Z")

</div>

Hi @whypushhh  
are you providing GNSS information with fixed values for the covariance?  
What GNSS driver are you using to generate the GPS FIX messages?

---

<div class="post-metadata">

**Author:** ![whypushhh](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/w/b5e925/32.png) [@whypushhh](https://community.stereolabs.com/u/whypushhh)\
**Post date:** [January 7, 2025, 11:33pm UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/5 "2025-01-07T23:33:57Z")

</div>

Hi @Myzhar  
I’m using a Ublox GPS module along with a ROS package to publish GPS Fix messages on a custom topic. In my setup, the GPS covariance is not fixed—it updates continuously. However, I noticed that the covariance values shown in the ZED Wrapper’s `origin_fix` differ from what I’m actually publishing. Because of this discrepancy, it seems that the GPS fusion calibration never completes and keeps restarting.

I’ve attached my Ublox GPS configuration file and launch file below for reference. Could you please advise on why the covariance in the `origin_fix` might not match the one I’m sending and how to ensure the GPS fusion calibration finishes properly?

 ![image](https://community.stereolabs.com/uploads/default/original/2X/9/92b1986fa43092f9cfcac67730027852601d2e20.png)  
 ![image](https://community.stereolabs.com/uploads/default/original/2X/3/355acc722fc886def5bea41895ae9e2929ca5539.png)

Thank you in advance for your help!

---

<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:** [January 8, 2025, 8:57am UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/6 "2025-01-08T08:57:16Z")

</div>

> [@whypushhh](#):
>
> Could you please advise on why the covariance in the `origin_fix` might not match the one I’m sending and how to ensure the GPS fusion calibration finishes properly?

What are the expected values?  
What values do you get?

---

<div class="post-metadata">

**Author:** ![whypushhh](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/w/b5e925/32.png) [@whypushhh](https://community.stereolabs.com/u/whypushhh)\
**Post date:** [January 12, 2025, 11:37pm UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/7 "2025-01-12T23:37:26Z")

</div>

@Myzhar  
As I mentioned earlier, the GPS fix values I am publishing have a covariance of 12.9, 12.9, and 27.6, with a covariance type of 2.

 ![스크린샷 2024-12-19 105512](https://community.stereolabs.com/uploads/default/original/2X/f/f8ae4c0d103af258a7fb04f77ed0e05f445a6620.png)  
However, the covariance values of `pose/origin_fix` are filled with -1, and the covariance type is set to 0.  
 ![스크린샷 2024-12-19 105611](https://community.stereolabs.com/uploads/default/original/2X/f/f71bf18f108e7a687a474afd82dd6a31b136ea9d.png)  
I believe the covariance values should be similar to or the same as the ones I am publishing.

---

<div class="post-metadata">

**Author:** ![radisc](https://community.stereolabs.com/user_avatar/community.stereolabs.com/radisc/32/3453_2.png) [@radisc](https://community.stereolabs.com/u/radisc)\
**Post date:** [February 11, 2025, 7:54am UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/8 "2025-02-11T07:54:07Z")

</div>

I’m having the same exact problem, i’m using the nmea\_navsat\_driver package.

---

<div class="post-metadata">

**Author:** ![whypushhh](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/w/b5e925/32.png) [@whypushhh](https://community.stereolabs.com/u/whypushhh)\
**Post date:** [May 16, 2025, 1:09am UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/9 "2025-05-16T01:09:07Z")

</div>

It says that if you can trust your GPS covariance, you can ignore the covariance warning. Also, the origin\_fix topic has its covariance fixed to -1.

In my case, I kept thinking calibration wasn’t working because there was no log message confirming that it was successful. I added a custom log to the code to print a message when calibration was complete. After moving the system a bit, the log finally showed “calibration OK”, so it seems like the issue is resolved now.

I hope this helps someone else too!

---

<div class="post-metadata">

**Author:** ![Aadesh\_Varude](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/ac8455/32.png) [@Aadesh\_Varude](https://community.stereolabs.com/u/Aadesh_Varude)\
**Post date:** [August 5, 2025, 3:56pm UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/10 "2025-08-05T15:56:14Z")

</div>

Hello ,Thank you for this post it helped me solve my issue.Just out of curiosity how did you figure out if the calibration was complete.My terminal still shows me calibration in progress where as when i visualize the results in rviz the odometry look pretty accurate.

> component\_container\_isolated-2] [2025-08-05 15:34:11 UTC][ZED][WARNING] The covariance you are attempting to ingest for [GeoTracking] has a covariance value close to zero (less than 1 millimeter). It will be clamped for stability purposes.  
> [component\_container\_isolated-2] [INFO] [1754408051.996505833] [zed.zed\_node]: GNSS fusion status: CALIBRATION\_IN\_PROGRESS  
> [component\_container\_isolated-2] [INFO] [1754408051.996591655] [zed.zed\_node]: GNSS reference localization initialized  
> [component\_container\_isolated-2] [INFO] [1754408051.996613383] [zed.zed\_node]: Static transform UTM to MAP [utm → map]  
> [component\_container\_isolated-2] [INFO] [1754408051.996627079] [zed.zed\_node]: \* Translation: {2921425.180,-3968466.141,0.000}  
> [component\_container\_isolated-2] [INFO] [1754408051.996646054] [zed.zed\_node]: \* Rotation: {-0.000,-0.000,44.894}  
> [component\_container\_isolated-2] [ERROR] [1754408051.996809795] [zed.zed\_node]: Ingest error occurred when ingesting GNSSData: GNSS DATA COVARIANCE MUST VARY

Question:

1. Did you make the change in the zed ros2 wrapper source code to log if the calibration was successful or did add it to your files by subscribing to a certain topic.

---

<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:** [August 28, 2025, 8:37am UTC](https://community.stereolabs.com/t/gnss-fusion-covariance-missing-gnss-ref-pose-tf-and-cmake-policy-warnings-when-building-ros-2-humble/7733/11 "2025-08-28T08:37:55Z")

</div>

You can subscribe to the **`~/pose/filtered/status`** or the **`~/geo_pose/status`** topic to obtain this live information → [zed-ros2-interfaces/msg/GnssFusionStatus.msg at master · stereolabs/zed-ros2-interfaces · GitHub](https://github.com/stereolabs/zed-ros2-interfaces/blob/master/msg/GnssFusionStatus.msg)

The information is also available in the [diagnostic report.](https://www.stereolabs.com/docs/ros2/zed-node#node-diagnostic)
