# Insufficient orthomosaic accuracy

**URL:** <https://community.pix4d.com/t/insufficient-orthomosaic-accuracy/26410>\
**Category:** PIX4Dmatic\
**Created:** [May 11, 2023, 7:01am UTC](https://community.pix4d.com/t/insufficient-orthomosaic-accuracy/26410 "2023-05-11T07:01:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![matys.skoracki](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@matys.skoracki](https://community.pix4d.com/u/matys.skoracki)\
**Post date:** [May 11, 2023, 7:01am UTC](https://community.pix4d.com/t/insufficient-orthomosaic-accuracy/26410/1 "2023-05-11T07:01:33Z")

</div>

Hi,

I have a problem with exporting orthomosaics to a jpg file. The flight of drone and calculations are made with an accuracy of 0,9 cm/px but orthomosaic export only allows JPG file with accuracy of 7,1 cm/px. Exporting to tiff the file size is too large, so it is necessary to export the jpg file

What is the solution to achieve accuracy of orthomosaic also 0.9cm/px?

---

<div class="post-metadata">

**Author:** ![matys.skoracki](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@matys.skoracki](https://community.pix4d.com/u/matys.skoracki)\
**Post date:** [May 11, 2023, 7:40am UTC](https://community.pix4d.com/t/insufficient-orthomosaic-accuracy/26410/2 "2023-05-11T07:40:18Z")

</div>

Uploading: plik.pdf…

---

<div class="post-metadata">

**Author:** ![Chris\_Putnam](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/chris_putnam/32/4946_2.png) [@Chris\_Putnam](https://community.pix4d.com/u/Chris_Putnam)\
**Post date:** [May 11, 2023, 5:23pm UTC](https://community.pix4d.com/t/insufficient-orthomosaic-accuracy/26410/3 "2023-05-11T17:23:55Z")

</div>

Converting to a .jpg format compresses the file and averages pixels to do so. That’s why the file size is smaller. What is the use case for the ortho? Why is the Geotiff to large (upload constraints, software constraints, etc)? I have used Global Mapper to tile the image into smaller images vs one larger ortho.

---

<div class="post-metadata">

**Author:** ![matys.skoracki](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@matys.skoracki](https://community.pix4d.com/u/matys.skoracki)\
**Post date:** [May 15, 2023, 9:00am UTC](https://community.pix4d.com/t/insufficient-orthomosaic-accuracy/26410/4 "2023-05-15T09:00:28Z")

</div>

The idea is to obtain orthomosaics with an accuracy of 0.9 px / cm in jpg format, and the program does not generate such accuracy.

With the number of photos around 400, this problem does not occur, it only starts with more photos, as in the attached screenshot.

 ![screen](https://global.discourse-cdn.com/pix4d/original/2X/c/c9fe4e29f8600e07ff50c33911a61a8738bcf8ed.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:** [June 1, 2023, 7:57pm UTC](https://community.pix4d.com/t/insufficient-orthomosaic-accuracy/26410/5 "2023-06-01T19:57:43Z")

</div>

Hi matys,  
Have you considered using the tile option for the .tiff file? This way no single file will be that large. This might be the best option.  
 ![image](https://global.discourse-cdn.com/pix4d/original/2X/b/bea39950cff9f64d2c57ec0ffb475301e7b9748d.png)