Drone survey job size calculator.
Enter the size of your site and how much detail you want. You get back how many photographs to expect, a rough flight time, how long processing usually takes and the files that come back. It only ever works out the size of the job.
This calculator needs JavaScript. The table below gives typical job sizes without it.
Priced per job by photo count. You see the exact price before you pay.
An estimate for planning, worked out on flat ground with a common 20 megapixel camera. The assumptions are listed below the examples.
How many photographs a job usually takes.
The same numbers the calculator gives, for sites people ask about most. Flying lower gives finer detail and many more photographs.
| Job | About 3 cm per pixel (110 m) | About 2 cm per pixel (80 m) | About 1 cm per pixel (40 m) |
|---|---|---|---|
| 1 hectare | about 25 | about 30 | about 100 |
| 5 hectares | about 70 | about 120 | about 400 |
| 20 hectares | about 250 | about 400 | about 1,500 |
| 50 hectares | about 550 | about 950 | about 3,700 quoted by hand |
| 1 km road, 40 m wide | about 90 | about 190 | about 500 |
| 5 km road, 40 m wide | about 450 | about 950 | about 2,500 |
Flights above 3,000 photographs are quoted by hand before anything runs.
Where each figure comes from.
Some figures come from Helios's own guidance and measurements. Others are plain assumptions, and they are marked so you can tell the difference.
- Overlap. 80 percent along the flight line and 70 percent between lines, from the Helios capture guidance. Below about 70 percent the model starts to distort.
- Ground detail. The height you fly at sets how much ground one pixel covers. At 100 m it is about 3 cm per pixel, the same guidance. The calculator reproduces that from the camera geometry.
- Camera. A common 20 megapixel drone camera with a 1-inch sensor, photos taken landscape with the long side across the flight line. A different camera changes the count.
- Site shape. A site is treated as a square of the area you enter, flown edge to edge. A long thin site needs more photographs than a square of the same area, so use the corridor option for roads and lines.
- Upload size. About 6.5 MB for each image, from the live Helios figure of roughly 650 MB for 100 photographs from a 20 megapixel drone.
- Flight time. estimate One photograph every 2 seconds, a top speed of 10 metres a second, 10 seconds for each turn and about 25 minutes of flying per battery. These are assumptions, not measurements. Take-off, landing and getting to the site are not counted.
- Processing time. estimate The only measured figures are a median turnaround of about 2.6 hours across Eyona's own runs, and one large run that spent 252 minutes in the photogrammetry stage alone. The bands in between are soft, not a promise. Progress is shown live, stage by stage.
- Files. All in standard formats. Four can be measured on: the point cloud, the mesh, the orthomosaic and the elevation model. The camera poses, the run log, the Gaussian splat and its report (on smaller flights) are not measurement layers, and a splat is never measurable.
About the calculator.
Does the calculator show a price?
No. It works out the size of the job: photos, flight time, processing time and files. Helios is priced per job by photo count, and you see the exact price before you pay.
How much overlap do I need for a good model?
Helios asks for about 80 percent overlap along the flight line and 70 percent between lines, and the calculator uses exactly that. For flat ground such as a stockpile top or a roof surface, push it to 85 and 75 percent. Below about 70 percent the model starts to distort.
My drone is not a 20 megapixel, 1-inch camera. Is the number wrong?
It is a planning number, not a promise. A camera that sees less ground in each photo (a smaller sensor behind the same lens, or a longer lens) needs more photos for the same site. One that sees more needs fewer. Let your own flight app have the last word and use this to sanity-check it.
Can I fly higher to take fewer photos?
Yes, and the count drops quickly, but each pixel then covers more ground, so fine detail is lost. Check the height limit where you fly: many places cap drones at 120 m.
What happens above 3,000 photos?
The Helios app prices flights of up to 3,000 photographs on screen. Above that, a custom quote is prepared before anything runs.
What about hilly sites?
The calculator assumes flat ground at one flying height. Relief changes how much ground each photo sees, so a steep site needs more photos than the figure shown. Treat the result as a floor for a hill.
Related.
Which one measures, which one looks real, and how you get both from one upload.
Use caseDrone site surveyThe site rebuilt in 3D from your photographs, without the desktop software.
Use caseStockpile volume measurementVolumes taken on the point cloud and the surface model, kept as a dated record.
Ready to process a flight?
Priced per job by photo count. You see the exact price before you pay. An account is free and needs no card.
Create an account Email us[email protected] · Eyona Software Development (Pty) Ltd, Cape Town · Helios runs at portal.helios3d.co.za