Glossary
Orthomosaic
A single large aerial image built from hundreds of overlapping drone photos, geometrically corrected so every part of it sits at the right place and the right scale. It is the image a drone map is measured on.
Definition
An orthomosaic is the flat, measurable image that comes out of a mapping flight. The drone does not take one picture of the field; it flies a grid and takes hundreds of overlapping photos, and photogrammetry software then works out where the camera was for each one, builds a model of the ground surface, removes the perspective from every individual photo, and blends them all into one continuous georeferenced raster. The important word is ortho, meaning the result behaves as though every pixel were photographed from straight overhead. In a single raw photo only the centre is truly looking down. Everything toward the edges is viewed at an angle, so scale changes across the frame and anything with height leans outward away from the middle. That is why you cannot reliably measure a distance on an ordinary aerial snapshot: two features the same size will occupy different numbers of pixels depending on where they fall in the frame. Orthorectification removes that, using the camera geometry and an elevation model to reproject each pixel to where it would appear from directly above. Because the finished image is georeferenced, every pixel carries a real coordinate, which is what makes it measurable — a distance, an area, or a boundary traced on an orthomosaic corresponds to the distance, area, or boundary on the ground, and the image can be laid over other data in the same coordinate system. Two properties are worth separating in your head. Resolution is how finely the ground is sampled, which is set by the camera and the height flown and expressed as ground sample distance. Accuracy is whether the image sits in the correct place, which is set by positioning and control. A very fine orthomosaic can still be shifted, tilted, or sitting at the wrong elevation, so a supplier quoting only centimetres per pixel has described the detail and said nothing about the position.
In an Alberta Context
On an Alberta farm the orthomosaic is the deliverable most field mapping work actually rests on, because it is the layer you can put a number to. Drowned-out acres are traced and measured off it rather than estimated by eye from a truck window, which is the difference between an insurance or program conversation with a figure in it and one without. Hail and frost assessment uses it the same way, to establish the extent and pattern of damage across a quarter instead of the appearance of it from the approach road. It is also how a usable field boundary gets drawn when no boundary exists yet, traced to the farmed edge rather than the title line, and how wet holes, bush margins, and a yard site get excluded from an acre count. Flights repeated across a season stack up, so the same quarter at three dates shows whether a patch is growing, holding, or recovering, which no single visit answers. Multispectral work sits on the same foundation: an NDVI map is a multi-band orthomosaic with an index calculated from it, which is why the geometry has to be right before the vigour numbers mean anything. It is worth knowing what the orthomosaic is not. A mapping flight also produces elevation products, a surface model and a point cloud, and those are what drainage and tile planning are designed against, because that work depends on the height of the ground rather than on image detail. Alberta parkland also produces predictable artifacts. Powerlines, fence posts, and lone poles tend to smear or break, because a ground surface model does not describe thin objects standing above it. Shelterbelts and bush lean at the edges of the flown area where overlap thins out, cattle and vehicles that moved during the flight can ghost or appear twice, and a flight long enough for the sun to move or the cloud to change can leave visible seams between flight lines. None of that is a processing failure, and none of it affects a measurement in open crop.
Why It Matters
Because it is the difference between a picture of a field and a measurement of one. A drone photograph tells you a corner looks poor. An orthomosaic tells you the poor area is a specific number of acres, sitting in a specific place, with a boundary you can hand to an agronomist, an adjuster, or a prescription. Everything downstream of a mapping flight inherits its geometry: acre counts, zone areas, the boundary a prescription is built inside, the coverage record compared against it afterward. If the base image is shifted or wrongly scaled, every one of those numbers is wrong in the same direction and nothing later in the chain will reveal it, because the map will look entirely convincing. That is the practical reason to ask two separate questions of any supplier rather than one. What is the resolution, and what is the positional accuracy. The first is set by the camera and the height flown; the second by RTK positioning and, where the work has to line up with a benchmark or a contractor’s grade control, by surveyed ground control points. Fine resolution creates confidence that a map has not necessarily earned, and a crisp image invites the assumption that everything about it is precise, including where it sits. The last reason is comparison over time. Orthomosaics from different dates only mean something beside each other if they are in the same place, so consistent accuracy is what turns a folder of images into a record. Get that right and three flights across a season answer questions a single visit cannot. Get it wrong and you have three attractive pictures that cannot be laid on top of one another.
Frequently Asked Questions
+What is an orthomosaic?
It is one large aerial image assembled from hundreds of overlapping drone photos and geometrically corrected so that every pixel sits at the right place and the right scale. Photogrammetry software determines where the camera was for each photo, builds a model of the ground surface, removes the perspective from each image, and blends them into a single georeferenced raster you can measure directly.
+How is an orthomosaic different from a normal aerial photo?
In a single photo only the centre is genuinely looking straight down. Toward the edges the ground is viewed at an angle, so the scale changes across the frame and anything with height leans outward from the middle, which means two features of the same size cover different numbers of pixels depending on where they land. An orthomosaic removes that, so it behaves as though every pixel were photographed from directly overhead, and it carries real coordinates rather than being just a picture.
+Can I measure acres on an orthomosaic?
Yes, and that is most of the point of having one. Because the image is georeferenced and at consistent scale, a boundary traced on it corresponds to the boundary on the ground, so areas and distances measured from it are real figures. That is how drowned-out acres, hail-damaged extent, and farmed field boundaries get quantified rather than estimated.
+Does a finer orthomosaic mean a more accurate one?
No, and the two are commonly confused. Resolution is how finely the ground is sampled, set by the camera and the height flown and expressed as ground sample distance. Accuracy is whether the image sits in the correct position and at the correct elevation, set by RTK positioning and surveyed ground control points where the job demands them. A very fine image can still be shifted or tilted, so ask about both separately.
+Why do powerlines look smeared or broken in a drone map?
Because orthorectification reprojects pixels using a model of the ground surface, and a ground surface model does not describe thin objects standing above it. Powerlines, fence posts, and lone poles therefore get stretched, broken, or blurred. It is a normal and expected characteristic of the product rather than a processing failure, and it does not affect measurements taken in open crop.
+How much photo overlap does an orthomosaic need?
A lot, which is why a mapping flight looks so repetitive. The software has to see the same ground in several images from different positions to work out where the camera was and how high the ground is, so mapping missions are flown with high forward and side overlap — commonly quoted in the region of seventy to eighty percent for agricultural work. Where overlap thins out, typically around the edge of the flown area, geometry gets weaker and tall features lean, which is why the flight area is normally set a little wider than the ground of interest.
+Is an orthomosaic the same as an elevation model?
No. They are separate products from the same flight. The orthomosaic is the flat, measurable image; the elevation products are a surface model and a point cloud describing the height of the ground. Drainage and tile planning are designed against the elevation data, because that work depends on ground height rather than image detail, so a job needing elevation accuracy is not served by a finer image.
+Can I compare orthomosaics from different dates?
That is one of the strongest uses, provided the accuracy is consistent, because two images only mean something beside each other if they are genuinely in the same place. The same quarter flown at three points in a season shows whether a patch is spreading, holding, or recovering, which a single visit cannot tell you. If positional accuracy varies between flights, the differences you see may be registration error rather than a change in the crop.
+Is an NDVI map an orthomosaic?
It is built on one. Multispectral imagery is processed into a multi-band orthomosaic, and the vigour index is then calculated from the relevant bands. That is why the geometry has to be right before the index values are worth acting on: an NDVI layer that is shifted or wrongly scaled places real crop variation in the wrong part of the field, and any prescription built from it inherits that error.