Poor ortho output with DJI Matrice 4e

PIX4Dmatic PIX4Dmatic Questions/Troubleshooting
1

I’ve been using Matic to process large corridor-like projects (10k photos) and was previously using a mavic 3e with a subscription to an rtk service.

Since updating to the Matrice 4e, running all the same settings on both the flight plans and Matic, I’m left with poor edge sharpness, and distortions in the orthos I’m generating.

Does anyone know of things to try, or settings to change to attempt to get this working?

I’ve tried a dozen things to try and get this to process correctly, including earlier versions (but only as far back as when the Matrice 4e became supported). It does seem to be struggling with vertical objects, but still see distortions in lower-altitude objects.

I get much better results using another processing software, so I’m convinced there is either a setting or incompatibility I’m running into.

Thanks in advance.

image
image1064×574 71.1 KB

image
image1421×836 125 KB

2

Hi @OttawaDrones,
Could you share the quality report for this project? I’d like to see how it was processed.
What software did you use to compare the results?
Thank you in advance
Regards

3

Hi @Alvaro_Santiago , thanks for the quick reply.

Please find attached the quality report.

I used WebODM to process a smaller subset of the data, roughly 480 photos, which I’ve also attempted with Matic with the same results.

A few things I’ve tried:

  • earlier versions
  • various processing change options
  • different coordinate systems
  • with/without gcps
  • reviewed image exif data to confirm geotagging looked ok

Screenshot from WebODM using default settings and no control:

image
image1688×1128 254 KB

Paul Ottawa 417 - June 1 2025-quality_report_2025-06-02_05-59-46.pdf (591.8 KB)

1 Like
4

Hi @OttawaDrones

Thanks for sharing the information. I reviewed the processing steps and the dense point cloud isn’t generated, so the DSM and orthomosaic use the automatic tie point as input.
Try reprocessing the project by going to Calibration > Dense Point Cloud > DSM (with dense point cloud as input) > Orthomosaic. This additional step will increase the project’s processing time, but I’m confident the result will be as expected.

I look forward to hearing from you. Wishing you a great day in the meantime.
Best regards

5

Hey @Alvaro_Santiago ,

Thanks again for the quick reply.

I believe you’re right – I’m not sure why I didn’t select dense point cloud, and if this is the problem, I’ll need to make sure I’m more careful with my process steps.

I’ll report back after processing.

6

Hi @OttawaDrones,
Have you had the chance to try to generate the DSM and Orthomosaic using the dense point cloud as input?
Regards

7

Hi @Alvaro_Santiago
Sorry for the delay – yes, much better results with the dense point cloud. Thanks for your quick help.

1 Like