Drone mapping used to mean expensive software, but the open-source toolkit has matured to the point where a small team can produce professional orthomosaics, elevation models, and 3D point clouds without a licence fee. The core of that toolkit is OpenDroneMap, a photogrammetry engine that turns overlapping drone photographs into maps, and WebODM, a web interface that makes the same engine approachable. QGIS completes the trio, not as a photogrammetry tool but as the place where the finished maps are analysed, styled, and shared.

OpenDroneMap processes a folder of geotagged drone photographs, matches features between overlapping images, reconstructs the camera positions, and builds an orthomosaic, a digital surface model, a digital terrain model, and a dense point cloud. It runs from the command line or inside a Docker container, which makes it powerful and scriptable but intimidating for a first-time user, since there is no friendly button to press. Its strength is flexibility: you can tune processing options, run it on a server, automate batches of flights, and inspect every intermediate product, which matters when a survey goes wrong and you need to know why.

The cost of that flexibility is hardware and patience. Photogrammetry is computationally heavy, and a large survey can take hours on a modest laptop, with memory usage that surprises users accustomed to photo editing. Start with a small flight, perhaps fifty to a hundred images, to learn the workflow and to gauge your machine, before attempting a thousand-image survey. Ground control points, markers surveyed with accurate GPS, improve absolute accuracy dramatically and are worth the effort for any map that will be measured or shared professionally.

WebODM wraps OpenDroneMap in a web interface where you drag in photographs, choose a preset, press a button, and watch progress in the browser, with the finished maps displayed on an interactive map. It also adds conveniences like task management, measurement tools, and a viewer for point clouds and elevation models, which make it practical for teams that fly regularly but do not want to manage command-line jobs. The software itself is open source, although the developers offer a paid installer and cloud options for users who prefer not to set it up themselves.

The trade-off is that WebODM hides some of the engine's options behind presets, so advanced tuning may still require dropping to the command line. For most agricultural, construction, and survey uses, however, the presets are well chosen, and the time saved on setup outweighs the lost control. A sensible pattern is to learn in WebODM, then move to OpenDroneMap directly when you need batch automation or a custom processing chain, treating the two as one toolkit with two doors rather than as competing products.

Once WebODM or OpenDroneMap produces an orthomosaic and elevation models, QGIS is where the real work begins: measuring areas, drawing field boundaries, computing vegetation indices, overlaying cadastral data, and producing print-ready maps. Neither photogrammetry tool replaces a GIS, and trying to analyse inside them quickly becomes frustrating, so plan the handoff from the start and keep your outputs in standard formats like GeoTIFF and LAZ. QGIS also handles the ground control and accuracy checks that turn a pretty picture into a trustworthy map.

Paid tools still have a place: they may process faster, offer better support, or integrate with a specific drone's workflow, and a team flying daily may value that enough to pay. But for learning, for small projects, and for organisations with more time than budget, the open trio is genuinely capable, and its outputs are compatible with the paid world. Fly a test survey, process it free, measure something you know, and let the accuracy of the result decide whether you need to spend anything at all.