PilotLedger emblem PilotLedger
← Back to Blog
PL

Desktop Photogrammetry Without a Per-Map Processing Fee

Commercial mapping work does not end when the aircraft is on the ground. The client paid for a map. Turning a card of imagery into that map is photogrammetry. For many operators, that step still runs on someone else's servers, and the processing is metered.

SkyView is the desktop photogrammetry application on Pilot Ledger. It is built to process on the machine you own, with no per-map cloud processing fee. It is on the waitlist. It is scheduled for September 2026. It is not available to customers today.

The fee is the argument

Cloud photogrammetry is a clear offer. You upload the images. Their infrastructure does the work. You receive an orthomosaic. The first job is straightforward. The fifth job in the same month is when the meter becomes part of how you bid.

Most of those platforms meter cloud processing per map, per project, or per credit. A second pass on the same site often draws on the same meter. You either carry a processing line item that was never in the original quote, or you absorb it.

I fly mapping work out of Springdale, Arkansas, for Drones Inbound. I have been a commercial drone pilot for eight years. I am not writing this as a complaint about the quality of cloud processors. They are serious tools. I am writing it because I want desktop photogrammetry that does not add a per-map processing fee to a job I already flew.

This is not a feature comparison. I am not claiming SkyView beats any cloud processor on features. It does not, not yet, and I will not write that. Process on your desk. Do not pay a per-map processing fee to turn the card into a map.

How a cloud processor meters the work

DroneDeploy is a useful public example of metered cloud processing. I will not quote a dollar plan price. I will cite what their own pages say.

On DroneDeploy's pricing page, individual plans list an images-per-map upload cap. The Individual Flight & Analysis plan allows up to 3,000 images per map. The Ag Lite plan allows up to 1,000. The Advanced plan lists a 10,000-image upload per map. Those caps are marked subject to the Fair Usage Policy.

That policy is the meter. Each account tier has a limitation on cloud data processing, measured in yearly gigapixels of imagery uploaded. Gigapixels are calculated from image resolution. Mapping frequency, map size, and camera resolution all change how quickly an account uses that allowance. The published yearly allowances are:

If usage exceeds the limit, the policy says DroneDeploy notifies the account owner and discusses a contract adjustment. In cases of significant overuse, it reserves the right to restrict or block product use.

That is cloud processing with a published ceiling. It is not unlimited processing because a subscription is paid. The work is metered. If that model fits how you run a program, it is a real product. If you already own a workstation and you do not want a per-map, per-project, or per-credit processing charge on every site, the meter is the issue this post is about.

I already wrote about processing drone maps on your own hardware and about processing locally instead of paying Pix4D cloud fees. Those posts cover the machine and last week's competitor. This one is the fee.

Desktop photogrammetry, no per-map processing fee

SkyView is a desktop application. The photogrammetry runs on your CPU and GPU. You process the site on the computer in the shop. There is no per-map cloud processing fee for that work.

Outputs include:

Raw imagery stays local unless you export it. That is the rule. When a layer is ready, you send the selected finished layer from Import/Export. The upload is that deliverable, not the raw card and not the entire project. Files at or under 100 MB go in one step. Larger files split and chunk. The upload can run in the background while you start the next site.

The argument is not that local work is invisible. The argument is that turning the card into a map does not generate a new processing charge each time you fly.

Local processing has a cost. It is yours.

Desktop photogrammetry uses your processor, your graphics card, your disk, and your time. A weak workstation will be slow. A large dataset will take the afternoon. That is honest, and I will not write around it.

Minimum specification:

A machine at the floor may not finish a large block before lunch. You are trading a metered processing invoice for time on hardware you already own.

What you do not add is a new processing fee every time a contractor who already paid you asks for another site. You do not hit an images-per-map cloud cap because the processing never left the shop. You do not reprocess into another draw on a yearly gigapixel allowance because the client wanted a second pass.

Your maps. Your machine. No per-map processing fee.

What is live, and what is on the waitlist

Quoting, jobs, and pay are live on Pilot Ledger today. You can bid the acreage, keep the job, and collect. That is the shop around the map, and it is a short second beat here. Processing is the waitlist product.

SkyView will be included with paid Pilot Ledger plans when it ships. The public page still shows a waitlist, because the desktop application is not shipping today. September 2026.

Join the waitlist on the pricing cards.

The fee should not decide whether you process

Most mapping software talks about GSD and tie points. Those matter. I care about them on the flight. After the flight, the business question is whether processing this site costs another metered charge.

I built a desktop photogrammetry application because I want the heavy work on my machine, and I do not want a per-map processing fee on a job I already flew. Cloud processors will remain serious tools for operators who want their servers to do that work. This post is for the operator who does not want the fee attached to each map.

Process on the desk. Watch for September. Join the waitlist at pilotledger.com/#pricing.