Here is an unpopular opinion: most bad orthomosaics are not processing failures. They are QC failures. The map finished, somebody glanced at a thumbnail, and the link went to the client before anyone zoomed into the parking lot where the cars smeared or the tree line where the seam wandered.
Orthomosaic QC desktop work fixes that, and it belongs on the machine that processed the job. You check the ortho where the data already lives, you reprocess on your own hardware if something is off, and only then do you ship. That is the SkyView Desktop wedge: process locally, no per-map cloud processing fee, review before anything leaves the box. SkyView is on the September 2026 waitlist. It is not available today. Join at pilotledger.com/#pricing.
QC is a step, not a vibe
If your QC is "it looked fine at full extent," you do not have QC. You have hope. A client will zoom in further than you did, and they will find the seam you didn't.
The reason shops skip it is usually friction. When the ortho lives in a cloud seat, every check means waiting on tiles to stream, and every fix means another upload and another wait. So people stop checking. The fix is not more discipline. The fix is putting the check right next to the processing, on hardware you own, where a second look costs you nothing but a few minutes.
Same processing-first story as process drone maps on your own hardware: reconstruct locally, keep the intermediates local, upload finished deliverables when the handoff actually needs them.
Orthomosaic QC checks you can run on your own desktop
Ask Mav (6 Oct 2026) confirms a practical set of local checks in SkyView Desktop. None of them are magic. All of them are things you should be doing anyway.
- Read the progress log. It reports reconstruction activity, including how the engine handled image matches and scene connections. If a block of images barely connected, the log is where you find out before the client does.
- Check the processing record for control. If you flew with ground control, inspect the processing record to see whether control image observations were actually used during reconstruction. "I imported GCPs" and "the reconstruction used them" are not the same sentence.
- Run the surface fit check. Sample elevations at target locations and do a vertical comparison. It is a sanity check you can do in minutes, and it catches the kind of problem a pretty ortho hides.
- Measure something you know. Use the measurement tools to verify scale and units against a feature with a known size. A curb, a building edge, a painted line. If the number is wrong, nothing else on the map deserves trust yet.
- Toggle the layers. Switch between the point cloud, the orthomosaic, and the mesh to compare how each one represents the same scene. When the ortho looks strange but the point cloud looks solid, you have learned something about where the problem lives.
- Zoom and look, on purpose. Visual inspection is still manual, and it should be. Hunt for seams, blur, holes, and streaks from moving objects or thin overlap. Pick the spots that usually break: vehicles, water, tree edges, roof edges, repeating textures.
- Read the positioning label honestly. SkyView labels a reconstruction as Surveyed, Declared, or Relative to describe the positioning evidence behind it. Use that label in your client notes the way it is meant to be used.
What the labels and checks do not prove
This is where pilots get into trouble, so it is worth being blunt.
- A Surveyed label means coordinate metadata was imported. It is not, by itself, evidence that a control adjustment or an independent accuracy assessment happened.
- SkyView does not turn a Relative or Declared reconstruction into a certified survey, and the labels do not establish metric scale, deformation limits, or legal suitability.
- No QC pass here is an accuracy guarantee. If the job needs a stated accuracy, that comes from your control, your checkpoints, and your professional judgment, not a software badge.
- Resampling or zooming does not create detail the camera never captured. Whatever output GSD you choose when processing a dataset into deliverables, disclose the GSD you actually delivered.
Saying these things out loud to a client is not weakness. It is the reason they call you back.
Why local QC changes the reprocess decision
Here is the opinionated part. When a reprocess costs you an upload and a wait on someone else's queue, you talk yourself out of it. "It's probably fine." When the reprocess runs on your own workstation with no per-map cloud processing fee, the math flips. You fix the gap, rerun, and check again.
That is the real value of orthomosaic QC on the desktop. Not a fancier checklist. A cheaper "no, not yet."
It pairs with the rest of the local workflow. Build terrain products where you already did QC, as in DSM and DTM on your own desktop and contours from your local DSM. When the map passes, share it as browser tiles instead of a giant file, covered in Client Ortho Tiles in the Browser, No 2GB Download and share client orthos.
A five-minute QC habit before every delivery
Steal this and make it boring:
- Skim the progress log for weak image matches or disconnected scene pieces.
- Confirm control was used if you flew control.
- Run one surface fit check and one known-distance measurement.
- Toggle ortho, point cloud, and mesh at your two worst-looking spots.
- Write the positioning label and delivered GSD into your delivery note.
If any line fails, reprocess locally and run the list again. If every line passes, ship it.
Processing first, then the business side
SkyView sells processing: local hardware, no per-map cloud processing fee, September 2026 waitlist. Not available today, and there is no download link here.
Pilot Ledger's quoting, jobs, and pay tools are the short second beat. Once the ortho passes QC, the job moves to invoice in the same system you quoted it in. That matters, but it is not why you QC the map. You QC the map because your name is on it.
Join the waitlist
If you want orthomosaic QC desktop checks next to the processing, on your own hardware, with reprocessing that doesn't cost you a per-map cloud fee, join the SkyView waitlist for September 2026 at pilotledger.com/#pricing. Not available today. Processing first, and QC before anything ships.