Feedback wanted: pre-checking mapping image sets before processing

[yan_imagery]

I’m working on a small tool for checking drone mapping image sets before sending them to processing platforms like Pix4D, WebODM, DroneDeploy, etc.

The checks are basic but practical:

- estimated compression savings
- preserved image dimensions
- RTK GPS quality
- unusually large files
- potentially blurry frames, shutter/drone speed analysis

Sample result:

Sample Drone Dataset Report

www.imageryworkbench.com

I’m mainly looking for workflow feedback:

- Do you pre-check image sets before processing?
- Would compression before upload be useful or concerning?
- Are there other checks that would matter more for mapping jobs?

Thanks.

 

[clackey]

approved by admin

 

[adm_geomatics]

I’m working on a small tool for checking drone mapping image sets before sending them to processing platforms like Pix4D, WebODM, DroneDeploy, etc.

The checks are basic but practical:

- estimated compression savings
- preserved image dimensions
- RTK GPS quality
- unusually large files
- potentially blurry frames, shutter/drone speed analysis

Sample result:

Sample Drone Dataset Report

www.imageryworkbench.com

I’m mainly looking for workflow feedback:

- Do you pre-check image sets before processing?
- Would compression before upload be useful or concerning?
- Are there other checks that would matter more for mapping jobs?

Thanks.

Did I see this on Reddit UAVmapping as well?

 

[jrios]

That sounds useful, especially for mapping jobs where the problems usually show up after processing has already wasted time.

For me, the most valuable pre-checks would be overlap gaps, blurry images, exposure changes, missing sections, weak GPS data, altitude inconsistencies, and whether the flight actually covers the full area the client expects.

I would be careful with compression though. For simple documentation it may be fine, but for mapping or measurement work I’d want to know exactly what is being changed before sending it into processing.