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.
I have lost count of how many times a client asked for "the elevations" and got handed an orthomosaic.
Pretty picture. Wrong product. What they meant was a surface they could cut profiles from, design against, or argue quantities on. That surface is usually a DSM (digital surface model — tops of everything the camera saw) or a DTM (digital terrain model — bare earth after you stop treating canopy and roofs as ground). If you want that work to stay on your workstation — DSM DTM desktop-first, no whole-job upload just to mint a GeoTIFF — that is the SkyView Desktop wedge. SkyView Desktop launches October 12, 2026. View plans at pilotledger.com/#pricing.
DSM vs DTM in one honest sentence
A DSM is the elevation of what the reconstruction can see: roofs, piles, trees, equipment, pavement. A DTM is the elevation of the terrain once non-ground classes are out of the way. Swap them casually and you invent dirt that is not there, or erase piles that are.
That distinction is not academic. Earthwork, drainage conversation, pad design, and contour deliverables all hang on which surface you meant. An ortho answers "what does it look like from above." A DSM/DTM answers "what is the height field we are actually using."
Why pilots still ship elevation work to a cloud meter
The capture is local. The reconstruction can be local. Then the habit kicks in: push the whole job to a cloud processor because that is how the last subscription was sold. Bandwidth on a quarry LTE link becomes the critical path. A one-line CRS fix or a reclassified toe means another upload loop. Site privacy — unannounced pads, industrial yards — gets treated as someone else's storage problem.
You already paid for a desktop that can hold a dense cloud. Using it as a camera-card reader while a vendor meters the elevation product is the wrong default for commercial mapping.
Same processing-first story as process drone maps on your own hardware: reconstruct locally, keep intermediates on the machine you own, upload finished deliverables when the client handoff actually needs them.
Surfaces on your desktop: the 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 elevation work, the honest path looks like this:
- Reconstruct locally — build the dense cloud and elevation products on your workstation.
- Know which surface you need — DSM for visible tops; DTM when the question is bare earth.
- Classify before bare earth — a DTM that still includes canopy is just a DSM with a lie in the label. SkyView Desktop supports local point cloud classification as a separate desktop step (manual classification, Quick classification buttons and custom classes; automatic classification is deferred for the beta). That post owns the classing root; this post's root is DSM DTM desktop surfaces after reconstruction.
- Hold the elevation products on-machine — keep DSM/DTM available for contours, profiles, design handoff, or cut-and-fill without making a whole-job cloud upload the default.
- Ship the finished layer — when the client needs a shareable ortho or hosted view, send the finished product. Ortho web viewing is tiled (Client Ortho Tiles in the Browser, No 2GB Download). Gaussian splats remain a desktop GPU visual — useful for walkthroughs, not a substitute for a controlled elevation surface when the deliverable is heights.
The product claim this post leans on is the processing wedge: local hardware, no per-map cloud processing fee, elevation surfaces available on the desktop so DSM DTM desktop work does not require metering every intermediate on a vendor cloud.
Field pattern: pads, piles, and the right surface name
Commercial pad. Superintendent asks for "grades." You deliver a DSM for context and a DTM (or ground-classified surface) for dirt conversation — labeled as such. Mixing them in one unlabeled GeoTIFF is how Friday arguments start.
Stockpile yard. Pile tops live in the DSM family. Inventory still needs a documented base (pad, toe, prior surface). Elevation products and volumes are cousins; the volume post covers the meter-without-upload angle — here the point is keeping the height field local while you clean and re-export.
Design handoff. Civil teams want a surface in *their* CRS with a clear DSM/DTM label. A local path lets you finish cleaning on your hardware, then export what they asked for — without treating bandwidth as a deliverable.
I have handed over enough unlabeled "elevation" files to know the conversation that follows. Name the surface. Document the CRS. Say whether vegetation was classified out. That habit matters more than any logo on the processing box.
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 mapping flight, schedule the reflight, invoice when the elevation package ships. They are not the H1. Lead with CRM on a DSM/DTM processing post and you are selling the wrong door.
Before the October 12 launch
If you want DSM DTM desktop elevation products from local reconstruction — keep the height field on your hardware, classify when bare earth matters, upload what you ship — view SkyView plans for the October 12, 2026 launch at pilotledger.com/#pricing. Processing first. Surfaces with honest labels.