Launch update — September 29, 2026: SkyView Desktop launches October 12, 2026. Approximately 50 pilots will field-test it in a private beta before launch. Pre-launch Desktop access requires beta approval and an assigned SkyView license. Ask about beta access or view SkyView plans.
Cut-and-fill numbers are how earthwork jobs get paid, scheduled, and argued about. The map that supports those numbers is usually a dense surface — a point cloud, a DSM, sometimes a bare-earth DTM after ground classification — and that surface is heavy. The quiet industry habit is to push the whole job into a cloud processor so someone else’s meter can return a volume table.
That habit is what this post is about. If you want cut fill drone volumes computed from data that stays on your workstation — process locally, keep the intermediate surfaces on your hardware, upload finished deliverables when you choose — that is the SkyView Desktop wedge. SkyView Desktop launches October 12, 2026. View plans at pilotledger.com/#pricing.
What cut-and-fill actually asks for
A cut-and-fill report is not a pretty ortho. It is a comparison between surfaces: design vs existing, week N vs week N+1, pad before vs pad after. Stockpile inventory is the same family of math with a different base rule — pile surface against a toe plane or pad.
What the calculation needs, in practice:
- A current surface you trust in the project coordinate system (dense cloud, DSM, or DTM).
- A reference — design surface, prior flight, or agreed base.
- Clean ground logic when vegetation or equipment would inflate or hide dirt.
- Documented base rules so next week’s number means the same thing as this week’s.
None of that requires shipping every intermediate file to a vendor cloud by default. It requires a local processing path that can build and hold those surfaces on the machine you already own.
The pain: uploading the whole job to meter a volume
Commercial volume work often fails on logistics, not on trigonometry:
Bandwidth. A dense cloud or full imagery set is not a PDF. Plant cellular, hotel Wi-Fi, and remote yards punish the upload more than your CPU. Waiting overnight for a cloud queue so you can re-run one base rule is a second flight day without the flying.
Iteration cost. Volume deliverables iterate. The toe was wrong. The design CRS did not match. The superintendent wants last week vs this week, not design vs existing. Per-map or per-credit cloud meters punish those cleanup loops. Local hardware processing with subscription framing — no per-map cloud processing fee — keeps the loop on your desk.
Site privacy. Quarries, industrial plants, and unannounced pads produce high-resolution models of someone else’s property. Keeping heavy intermediates on your machine means the raw job does not need a vendor cloud “just because that is how the software is sold.” Finished deliverables can still be uploaded and shared when the client handoff requires it.
Same processing-first story as process drone maps on your own hardware: reconstruct locally, keep control of the intermediate data, and only move what you mean to hand over.
Surfaces on your desktop: the honest SkyView path
SkyView is Pilot Ledger’s desktop processing lane. Front door: process on your hardware. No per-map cloud processing fee. Raw imagery does not have to leave the machine for processing to start. Finished deliverables can be uploaded and shared when you choose.
For cut-and-fill work, that matters because the volume math sits on top of the surfaces you keep local:
- Reconstruct locally — build the point cloud and elevation products on your workstation.
- Classify when ground matters — bare-earth volumes need a ground class that does not treat canopy as dirt. SkyView Desktop supports local point cloud classification as a separate desktop step after reconstruction (manual classification, Quick classification buttons and custom classes; automatic classification is deferred for the beta). That classification post is the classing root; this post’s root is volumes without uploading the whole job.
- Hold the surfaces on-machine — DSM, classified ground, and comparison surfaces stay available for cut-and-fill and stockpile workflows you run locally or export into the CAD/earthwork tools your client already uses.
- Upload the finished layer — when the client needs a shareable ortho or hosted view, send the finished product, not every intermediate gigabyte. Ortho web viewing is tiled for clients (Client Ortho Tiles in the Browser, No 2GB Download). Gaussian splats remain a desktop GPU step after reconstruction — a visual product, not a substitute for a controlled surface when the deliverable is cubic yards.
The product claim this post leans on is the processing wedge — not a laundry list of volume-panel labels. Local hardware. No per-map cloud processing fee. Surfaces and classified ground available on the desktop so you can compute cut fill drone volumes without making a whole-job cloud upload the default path. Keep the job on your machine; compute volumes from local surfaces; upload what you ship.
Field pattern: earthwork and stockpile without the upload tax
A practical commercial pattern looks like this:
Earthwork progress. Fly on a cadence. Process the surface locally. Compare against design or last week with the same CRS and the same base rules. Hand the superintendent a cut/fill trend they can argue from — not a one-off snapshot with undocumented toes.
Stockpile inventory. Name the piles. Fix the base (pad, toe plane, or prior surface). Classify or clean so loaders and berms do not become “inventory.” Re-run when the yard asks for a second cut. Local iteration beats re-uploading the whole cloud for every tweak.
Export and handoff. Many civil and quarry clients still want the volume table or surface in their tools. A local path lets you finish cleaning on your hardware, then export the surface or report they asked for — without metering every intermediate reprocess on a cloud processor.
That is the difference between “we process maps” and “we can answer quantity questions without treating bandwidth as a deliverable.”
SkyView Desktop launch
Process on your own hardware, then use PilotLedger to manage the job and deliver finished work.
Pilot Ledger quoting, jobs, and pay are a short second beat — why pilots stay after the surface is done. Quote the earthwork flight, schedule the cadence, invoice when the volume table ships. They are not the H1. Lead with CRM on a cut-and-fill processing post and you are selling the wrong door.
Bottom line
Cut fill drone volumes live on surfaces. When those surfaces — point clouds, DSMs, classified ground — stay on your desktop after local processing, you can iterate volume work without uploading the whole job to a cloud meter as the default step.
SkyView Desktop is the desktop processing workflow launching October 12, 2026 aimed at that processing-first workflow: reconstruct on your hardware, classify ground when the volume needs bare earth, keep intermediates local, upload finished deliverables when the client handoff requires them. No per-map cloud processing fee.
View launch plans at https://pilotledger.com/#pricing. Process first. Keep the surfaces. Compute the cut and fill without treating the whole job as an upload tax.