Reading the quality report
After the upload finishes, MapperTool runs an automatic data check on the image EXIF — no processing time is spent yet, so a bad dataset costs you nothing but the upload. The report flags issues to fix before you start the job.
Four things are checked:
- GPS coverage — do the images carry position data, and does it cover the mapped area sensibly?
- Overlap — do neighbouring images share enough of the scene for photogrammetry to match them?
- Flight altitude — was the altitude consistent across the flight?
- Camera consistency — do all images come from the same camera setup?
Treat the report as a gate: anything it flags is worth fixing before you start, because processing runs on the render nodes and a weak dataset produces a weak result. Sometimes the fix is removing a stray file; sometimes it means re-flying part of the area — the recommendations in image requirements and flight basics help you avoid the flags in the first place.
When the report looks clean, you are ready to choose your outputs and start processing.
This guide is being written. The essentials above are accurate today; the detailed walkthrough lands here soon.