# Camera Calibration failed and flight lines linking abnormally.

**URL:** <https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841>\
**Category:** PIX4D International\
**Created:** [July 21, 2025, 11:57am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841 "2025-07-21T11:57:21Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 21, 2025, 11:57am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/1 "2025-07-21T11:57:21Z")

</div>

Hello,  
With the attachment below, can anyone suggest why does it show so many green lines and when we run the initial processing we found that most of the images are not calibrated only 10% of the images are calibrated .

 ![Screenshot 2025-07-21 171546](https://global.discourse-cdn.com/pix4d/original/2X/9/9c64a6f1ad5fee9cd1e4ab1d229339fc1ea59e10.jpeg)

Can anyone help , Thank You

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [July 21, 2025, 5:44pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/2 "2025-07-21T17:44:54Z")

</div>

This is likely because the time stamps on the images are incorrect or do not correspond to when the images were actually captured.

Can you describe your project to us in more detail? What camera are using, how was the data acquired, etc.

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 22, 2025, 5:47am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/3 "2025-07-22T05:47:20Z")

</div>

Project Overview  
This project involved collecting aerial data for forest area with the goal of creating 3D models and mapping terrain.

Drone and Camera Details  
We used a Trinity F90+ equipped with a camera model Sony RX1RM2\_35.0\_7952x5304

Flight and Data Acquisition Method  
Flight missions were planned using QBase3D with flight parameters set to 80% front overlap and 75% side overlap at an altitude of 210-230 meters AGL.

Data Retrieval and Processing  
The data was stored on an onboard SD card and transferred to a computer for processing.  
We conducted a total of four UAV flights, designated as Fly\_0114, Fly\_0115, Fly\_0116, and Fly\_0527. Notably, Fly\_0114 and Fly\_0527 were flown almost simultaneously using two separate Trinity F90+ drones, with only a 20-minute gap between their takeoff times. Fly\_0114 was launched first, followed by Fly\_0527, and both drones were airborne concurrently for approximately 25 minutes.

The remaining two flights, Fly\_0115 and Fly\_0116, were conducted independently after the completion of the first two.

For image geotagging, we used Post-Processed Kinematic (PPK) correction in QBase 3D, referencing our base station (iBase) for high-accuracy positioning. The image data was then processed using Pix4Dmapper. However, as you’ve seen, the output did not meet expectations, resulting in the issues shown earlier.

Attached below are the screenshots of the kml flight lines and some screenshots from pix4dmapper.

 ![Screenshot 2025-07-22 111004](https://global.discourse-cdn.com/pix4d/original/2X/e/e43ae64927fff608da94140729be3705fbe3525e.jpeg)

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 22, 2025, 5:48am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/4 "2025-07-22T05:48:08Z")

</div>

![Screenshot 2025-07-18 172530](https://global.discourse-cdn.com/pix4d/original/2X/c/c6be92f2fca50be7efbee21a2ab2ebc7aae679ed.png)

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 22, 2025, 5:48am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/5 "2025-07-22T05:48:52Z")

</div>

![Screenshot 2025-07-18 165959](https://global.discourse-cdn.com/pix4d/original/2X/f/fb472f072fc00c0d799f2d73b3d42d7db6aa7878.jpeg)

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [July 22, 2025, 3:18pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/6 "2025-07-22T15:18:33Z")

</div>

I’m guessing there was an issue with the time stamps during the PPK process. Despite this, it should still be possible to process the dataset. Can you attach the PDF quality report to the posting? We can take a look to see what else could be going on.

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 23, 2025, 5:16am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/7 "2025-07-23T05:16:42Z")

</div>

I have attached the quality report below,  
[Umtasor full\_report.pdf](https://community.pix4d.com/uploads/short-url/l0xTtyR2zoyic7qAMgwRX3CjIqk.pdf) (2.9 MB)

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [July 23, 2025, 1:56pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/8 "2025-07-23T13:56:19Z")

</div>

I see you processed using the rapid template. Have you tried using 1/4 image scale under step 1?

I also suggest using the Alternative calibration method. This might be more appropriate for your project.

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 25, 2025, 4:18am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/9 "2025-07-25T04:18:08Z")

</div>

We tried processing as you suggested its improving but still so many uncalibrated images. Can you suggest something for help.

Attached quality report below,  
[Quality\_report.pdf](https://community.pix4d.com/uploads/short-url/qwRRrpRm5ySahc7ipv5t74FPRjd.pdf) (2.9 MB)

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [July 25, 2025, 3:43pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/10 "2025-07-25T15:43:04Z")

</div>

How did it perform using 1/4 image scale?

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 28, 2025, 5:24am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/11 "2025-07-28T05:24:28Z")

</div>

Same error,  
[Quality\_report.pdf](https://community.pix4d.com/uploads/short-url/qwRRrpRm5ySahc7ipv5t74FPRjd.pdf) (2.9 MB)

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [July 28, 2025, 3:38pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/12 "2025-07-28T15:38:21Z")

</div>

These look like the exact same reports.

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 29, 2025, 8:52am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/13 "2025-07-29T08:52:54Z")

</div>

Sorry my bad, attached below is the right one  
[Umtasor1\_4\_report.pdf](https://community.pix4d.com/uploads/short-url/t6oucg24FkH4i5uATAEk5zhirhQ.pdf) (2.6 MB)

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [July 29, 2025, 4:36pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/14 "2025-07-29T16:36:46Z")

</div>

It looks like the 1/2 scale performed slightly better. But the results are still not great. It looks like you flew the project on a flat plane. However, it also appears that the terrain rises and falls. From what I can tell, your overlap might be too low in the areas where the terrain rises. This will cause the cameras to not calibrate. Ultimately, you might need to fly this at a higher elevation to ensure proper overlap throughout the project.

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [July 31, 2025, 4:59am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/15 "2025-07-31T04:59:04Z")

</div>

Okay ,  
Given that we have existing UAV data and are unable to conduct a return field survey, could you suggest any techniques or methodologies to maximize the utility and reliability of the available dataset?

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [July 31, 2025, 6:43pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/16 "2025-07-31T18:43:44Z")

</div>

Hi Victor,

Can you try splitting the project up into subsections? You might be able to get some of the areas to calibrate if they are separate. If successful, then you can merge them back in a later step.

---

<div class="post-metadata">

**Author:** ![pix4d25nesac](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@pix4d25nesac](https://community.pix4d.com/u/pix4d25nesac)\
**Post date:** [August 12, 2025, 8:54am UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/17 "2025-08-12T08:54:57Z")

</div>

We have tried that also but the errors are the same .

---

<div class="post-metadata">

**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\
**Post date:** [August 12, 2025, 3:22pm UTC](https://community.pix4d.com/t/camera-calibration-failed-and-flight-lines-linking-abnormally/33841/18 "2025-08-12T15:22:39Z")

</div>

I am sorry but ultimately the overlap is likely too low to get good results.
