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.
Contour lines are still the elevation language many civil teams, site supers, and GIS reviewers expect. An orthomosaic shows what the site looks like. A surface answers height. Contours turn that height field into a deliverable someone can open in CAD or GIS without arguing about what the raster "meant."
If your shop needs drone contours desktop DSM workflows — generate contour lines from a local digital surface model on the workstation you already own, without making a whole-job cloud seat the default path — that is the SkyView Desktop wedge. SkyView Desktop launches October 12, 2026. View plans at pilotledger.com/#pricing.
Contours sit on a surface — start with the right one
Contours are not a freestanding product. They inherit the surface underneath them. A DSM carries roofs, piles, canopy tops, and equipment. A DTM (or ground-classified surface) is bare earth after non-ground classes are out of the way. Contours from the wrong surface invent ridges that are roofs, or erase stockpiles a superintendent still has to move.
That distinction is operational, not academic. Drainage conversation, pad grades, and design handoffs all hang on which surface you contour. SkyView Desktop can generate contours from a local DSM, a DTM, or another elevation surface already in the project — including an imported surface when that is the controlled height field for the job. The DSM/DTM surface lane is covered separately in DSM and DTM on Your Own Desktop. This post's unique root is contours from that local DSM (or related surface), not the surface definition itself.
Why contour work still gets pushed to a cloud meter
The capture is local. The reconstruction can be local. Then the habit returns: upload the whole job because the last subscription treated contour export as a cloud-seat privilege. Plant LTE becomes the critical path. A one-line CRS fix or a cleaner toe means another upload loop. Site privacy — industrial yards, unannounced pads — gets treated as someone else's storage problem while you wait for lines you could have minted on the machine that already holds the dense cloud.
You already paid for a desktop that can hold the elevation product. Using it as a card reader while a vendor meters the contour pass 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 hardware you own, upload finished deliverables when the client handoff actually needs them.
Contours on the 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 contour work, Ask Mav (29 Sep 2026) confirms a practical desktop path:
- Hold a local elevation surface — DSM when visible tops are the question; DTM or ground classes when bare earth matters. Classification, when needed, stays a separate desktop step (point cloud classification).
- Generate contours on that surface — during initial processing (interval and TIN point spacing set in processing options), or later via the Generate surface deliverables tool from a selected point cloud with class and density choices that match the job.
- Edit and crop on-hardware — manual contour edits (including endpoint snap and join where supported), crop to a drawn boundary, and a smoothing pass for presentation. Do not measure from a smoothed line when the quantitative source of truth is the raw surface.
- Export what the client actually opens — 3D DXF with real elevations on vertices for Civil 3D-style handoff, or GPKG for GIS. Keep the working set local until the package is ready to ship.
- Upload finished products when shipping — shareable orthos and hosted views when the client needs them. Ortho web viewing is tiled (Client Ortho Tiles in the Browser, No 2GB Download). Contours remain a surface-derived CAD/GIS deliverable, not a substitute for volumes (cut-and-fill) or a Gaussian splat walkthrough.
The product claim this post leans on is the processing wedge: local hardware, no per-map cloud processing fee, drone contours desktop DSM work without treating a cloud seat as the only place lines can be born.
Interval discipline without invented defaults
Ask Mav is explicit on what not to invent: a pixel size or horizontal cell size does not justify a particular contour interval by itself. Choose the interval from measured vertical accuracy, terrain behavior, and the delivery specification the client (or their engineer) already uses. This article will not publish a default interval, an accuracy percentage, or a one-size "survey grade" claim.
Smoothing is presentation. Measuring belongs on the raw surface. Endpoint snap and join are not supported for closed lines or geographic-degree CRS sets — know the CRS before you promise a cleanup pass you cannot finish.
That discipline is how commercial contour packages survive Friday review. Pretty lines that ignore the surface and the CRS become a redo, not a deliverable.
Field pattern: when the client asks for "the contours"
Commercial pad. Superintendent wants grade lines for a dirt meeting. Contour the surface you labeled — DSM for context, DTM when the conversation is bare earth — and ship DXF/GPKG with CRS notes. Unlabeled "elevations" are how arguments start.
Stockpile and earthwork context. Contours describe shape; volumes answer quantity. Keep both local when you iterate. Contours do not replace a documented base for inventory; volumes do not replace a contour set the civil team asked for by name.
Design handoff. Civil teams want lines in their CRS with clear surface provenance. A local path lets you regenerate after a CRS fix or a reclassified toe 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 contour package ships. Quote the mapping flight, schedule the reflight, invoice when the DXF/GPKG lands. They are not the H1. Lead with CRM on a contours-from-DSM processing post and you are selling the wrong door.
Before the October 12 launch
If you want drone contours desktop DSM deliverables — local surface to contour lines on your hardware, edit and export on-machine, upload what you ship — view SkyView plans for the October 12, 2026 launch at pilotledger.com/#pricing. Processing first. Contours that inherit an honest surface.