PilotLedger emblem PilotLedger
← Back to Blog
PL

Drone Panoramas for Site Documentation

I have lost count of the times a client asked, weeks after a flight, "What did the north side of the site look like before the crew poured that slab?" A good map answers part of that question. A panorama often answers the rest. Drone panoramas for site documentation give owners, builders and inspectors a way to stand back in a moment that has already passed and look around.

This post covers what a drone panorama actually is, what it is good for on a job site, where it falls short, and how to make your 360 views a dated record that holds up later instead of a pretty picture that nobody can place in time.

What is a drone panorama?

A drone panorama is a set of overlapping photos taken from one position in the air, joined into a single wide or fully spherical image. Panoramic photographs are generally viewed as a 360-degree circle or a full spherical view, and they are normally created by stitching together photos taken while rotating about a single central position (Wikipedia, VR photography, checked 19 Nov 2026). Desktop stitching tools such as PTGui join overlapping photos automatically and support projections including equirectangular for spherical panoramas (checked 19 Nov 2026).

The key detail is that one center point. A 360 view shows what the camera could see from a single spot in the sky. Turn it, zoom it, and you are always looking out from that same place.

Panorama vs. orthomosaic: two different records

This is where people mix things up. An orthomosaic is also stitched from many photos, but it is built from images taken across the whole site and corrected so the result has a uniform scale, as if you were looking straight down at every point at once. A panorama is not corrected that way. Objects near the drone look larger, objects near the horizon get compressed, and distances change across the frame.

So my rule is simple: a panorama is a visual record, not a measured map. If someone needs a measurement, they need the map. If they need to understand what the site looked like and what was around it, the panorama is often the faster answer.

What drone panoramas are good for on a site

When I think about the panoramas that turned out to matter later, they usually fell into a few buckets:

Where panoramas fall short

Being honest about the limits makes your deliverable more useful, not less. A drone panorama:

Say this to clients up front. Nobody should be pulling a property-line or quantity decision from a 360 view.

How to make panoramas a dated site record

The difference between a nice panorama and a useful one is mostly discipline. Here is the workflow I would build around every visit:

  1. Pick repeatable stations. Choose one to three capture points per site and reuse them every visit, at the same approximate height. Consistency is what makes before-and-after comparisons work.
  2. Capture at a consistent time of day when you can. Long shadows and harsh backlight change how a site reads from visit to visit.
  3. Record the basics. Date, time, station name and altitude belong with every panorama. A 360 view with no date is just a photo.
  4. Pair it with the map. Fly the mapping mission and the panorama on the same visit, so the client gets a measured top-down view plus the context around it.
  5. Name files so they sort. Something like site, station and date in one predictable order saves hours when someone asks for "the March view from the east gate."
  6. Deliver it in one place. Panoramas emailed one at a time get lost. Keep them with the rest of the visit.

Delivering panoramas with the rest of the visit

Delivery is where most of the value is won or lost. A client who has to dig through an inbox for the right file will stop looking. Packaging the visit together, with the map, key photos and notes, is the same idea behind professional client mission reports, and it keeps every visit easy to find later.

That is also where SkyView fits. SkyView Desktop turns RGB drone photos into orthomosaics on your own Windows computer with no per-map processing fee, then delivers results to clients through Pilot Ledger. Its construction monitoring keeps dated site visits, compares progress over time, and lets you review panoramas, photos and video paths from the map. In other words, you capture and stitch your panoramas with your own drone or tools, and the map becomes the place where each visit and its views live together. If you want more on the map side of that delivery, see how to share client orthos.

And because the same account handles your quotes, jobs and getting paid, a recurring progress-documentation client does not mean a new spreadsheet every month.

The short version

Use drone panoramas for site documentation when the question is "what did it look like, and what was around it?" Use an orthomosaic when the question is "where, how big, or how much?" Date everything, shoot from the same stations, and deliver the views alongside the map so nobody has to hunt for them.

If you want your maps, panoramas and client delivery in one workflow, see Pilot Ledger and SkyView plans.