# Pix4dmapper Elevation Error

**URL:** <https://community.pix4d.com/t/pix4dmapper-elevation-error/33461>\
**Category:** PIX4Dmapper Questions/Troubleshooting\
**Created:** [May 15, 2025, 5:47am UTC](https://community.pix4d.com/t/pix4dmapper-elevation-error/33461 "2025-05-15T05:47:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![himalay.sharma](https://avatars.discourse-cdn.com/v4/letter/h/f04885/32.png) [@himalay.sharma](https://community.pix4d.com/u/himalay.sharma)\
**Post date:** [May 15, 2025, 5:47am UTC](https://community.pix4d.com/t/pix4dmapper-elevation-error/33461/1 "2025-05-15T05:47:00Z")

</div>

Hi Pix4D Community,  
I am using pix4dmapper version 4.4.12

1. I first processed the drone data in Pix4DMapper for volume calculation.  
Its quality report with raycloud snap.  
 ![database](https://global.discourse-cdn.com/pix4d/original/2X/8/8f5ba62ebce9ec350ac5b8e893bef92968115167.png)

[Maruti PP ERH\_report.pdf](https://community.pix4d.com/uploads/short-url/mPqpVhEhcTIyF9e9W6iojknZMn9.pdf) (1.9 MB)

 ![RayCloud](https://global.discourse-cdn.com/pix4d/original/2X/4/4029b15b7a7f88246a6653494329501f52018cec.jpeg)

1. I knew the mean sea level, so I processed it in (MSL) EGM 84 Geoid in my computer. The elevation obtained in the first processing was the same elevation I got after processing (MSL) EGM 84 Geoid. The elevation did not change.  
Its quality report with Ortho snap.  
[Maruti ERH MSL84\_report.pdf](https://community.pix4d.com/uploads/short-url/oemKkVKb2PZB1wp65u1mp5DcnLO.pdf) (2.0 MB)  

2. I again did the same process in another computer with (MSL) EGM 84 Geoid but still the elevation did not change.

3. I again did the same process in another computer with (MSL) EGM 84 Geoid but still the elevation did not change.

4. I did the same process again on a laptop and the elevation got changed. I did the same process on three computers, but the elevation did not change, but when I did the same process on the laptop, the elevation changed, despite having the same pix4dmapper and the same version. Why did this problem occur?  
Its quality report and ortho snap.  
[MCCPL\_MSL84\_report.pdf](https://community.pix4d.com/uploads/short-url/p33llSjlmEbTgHRjz3MAdgfikGK.pdf) (2.0 MB)

---

<div class="post-metadata">

**Author:** ![Kapil\_Khanal](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/kapil_khanal/32/304_2.png) [@Kapil\_Khanal](https://community.pix4d.com/u/Kapil_Khanal)\
**Post date:** [May 15, 2025, 5:31pm UTC](https://community.pix4d.com/t/pix4dmapper-elevation-error/33461/2 "2025-05-15T17:31:37Z")

</div>

Hello @himalay.sharma, For the last project, you are using different processing option that is why you might be getting the difference. Turn on the Geometrically verified matching option or the best way would be copying the .p4d file to your laptop and double click on it to open a project with same processing option that was used on that old project.

 ![image](https://global.discourse-cdn.com/pix4d/original/2X/8/8c31560bcc24e1d9d3f7f6189ca63f9d58f60afd.png)

 ![image](https://global.discourse-cdn.com/pix4d/original/2X/2/295dee4f663ac517a562654c258520a226a19a5b.png)

---

<div class="post-metadata">

**Author:** ![himalay.sharma](https://avatars.discourse-cdn.com/v4/letter/h/f04885/32.png) [@himalay.sharma](https://community.pix4d.com/u/himalay.sharma)\
**Post date:** [November 5, 2025, 4:33am UTC](https://community.pix4d.com/t/pix4dmapper-elevation-error/33461/3 "2025-11-05T04:33:10Z")

</div>

Hi Kapil Thank you for your input.

I have another situation here

we have 2700 image of mine with GCP collected through TS (WGS 84, 44N) and after processing the data its rms error is 0.138 m which is high and not acceptable. few gcp lift by 0.6m & gcp’s are not setting up on the position.

but earlier we used the same work flow, but gcp collected through DGPS (WGS 84, 44N) only in which our rms error comes less than 10mm.

now I am not able to understand why it happening with work flow using TS and not with DGPS.

What should I do to tackle this situation.

Next step I will take gcp with both TS & DGPS and process the same data set.

---

<div class="post-metadata">

**Author:** ![Kapil\_Khanal](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/kapil_khanal/32/304_2.png) [@Kapil\_Khanal](https://community.pix4d.com/u/Kapil_Khanal)\
**Post date:** [November 7, 2025, 11:31pm UTC](https://community.pix4d.com/t/pix4dmapper-elevation-error/33461/4 "2025-11-07T23:31:25Z")

</div>

Hello @himalay.sharma, The high RMS error is likely the result of poor camera optimization, inaccurate GCPs, improper marking of the GCPs, and incorrect accuracy values for the capture GCPs. So, my suggestion is to first ensure that the project is processed well, the GCPs are clearly visible, and manually mark enough GCPs(8-12).

If you are capturing the same point with TS, you can compare those values to see if the GCPs captured are inaccurate. However, you should be able to get reliable GCPs with TS.

Please attach two quality reports, one using the GCPs from TS and the other using DGPS, so that I can look into it to see if there is any issue related to the processing.
