QGIS for drone mapping works best as the GIS hub between photogrammetry and flight-planning tools: import a georeferenced orthomosaic, inspect the coordinate reference system (CRS), create or clean a survey boundary, and export that boundary or mission data in the format your downstream app accepts. QGIS core handles the mapping and data work; current plugins can also generate drone flight plans for supported workflows.
Last updated: September 19, 2026 — checked against QGIS 4.2.2, QGIS 3.44.14 LTR, and current DJI/Litchi/QGIS-plugin workflow documentation.
Quick Answer
To use QGIS for drone mapping, process your overlapping drone photos into a georeferenced orthomosaic when needed, load the GeoTIFF/COG in QGIS, verify the CRS, create or import the survey boundary, then export a clean KML/KMZ/GeoJSON boundary or use a compatible QGIS flight-planning plugin when you need a mission file.
Key Takeaways
- Use GeoTIFF or Cloud Optimized GeoTIFF for drone rasters, and use GeoPackage as the default editable vector format in QGIS[3], [16].
- Treat raw geotagged photos and a finished orthomosaic as different inputs; QGIS can display photo locations, while photogrammetry software creates the map-ready orthomosaic[12].
- Check CRS definitions and build raster overviews before troubleshooting slow or misplaced layers[14], [17].
- DJI Pilot 2, Map Pilot Pro, and Litchi use different import/export workflows, and newer QGIS plugins can generate flight-plan outputs directly for supported apps[7], [18], [19].
At a Glance
| Time Required | Varies by data size and task; importing a finished orthomosaic is quick, while photogrammetry processing can take much longer |
| Difficulty | Beginner to intermediate |
| Tools Needed | QGIS, geotagged drone photos or processed orthomosaic, optional photogrammetry software, and a compatible flight-planning app |
| Cost | QGIS is free and open-source; costs depend on your drone, processing software, storage, and mission app |
QGIS is free, open-source GIS software for creating, editing, analyzing, and exporting spatial data. As of this update, the official download page lists QGIS 4.2.2 “Belém do Pará” as the current release and QGIS 3.44.14 “Solothurn” as the LTR[1].
With QGIS, you can create vector layers such as parcel outlines, work-zone boundaries, waypoints, and survey limits, then compare them with drone rasters in the same project. QuickMapServices can add basemap context, while native XYZ Tiles provide another basemap path[4].
Note: QGIS core does not fly the aircraft. It prepares and analyzes geospatial data. However, current plugins such as FlyPath and GeoFlight Planner can create flight-plan outputs for supported DJI/Litchi-style workflows; the drone app or controller still executes the mission[18], [19].
For the steps before QGIS, see drone mapping and photogrammetry basics, the orthomosaic creation workflow, and the separate guide to drone mapping mission planning tools. This page stays focused on the QGIS handoff: CRS checks, raster/vector work, boundaries, and exports.
Preparing Your Drone Imagery for QGIS
Good preparation reduces avoidable alignment problems. Verify that your source photos contain the expected EXIF GPS metadata before processing, but do not treat camera geotags alone as proof of survey accuracy. Photogrammetry software such as OpenDroneMap can turn overlapping images into georeferenced orthophotos, point clouds, 3D models, and elevation products[12].
Use GeoTIFF for standard georeferenced raster exchange and Cloud Optimized GeoTIFF (COG) when you want tiled/overview-friendly access to large rasters. QGIS 4.2 includes a processing algorithm for creating COGs, and QGIS/GDAL support GeoTIFF workflows directly[3], [13]. Organize files into project-based folders so imagery, vectors, reports, and exported mission files remain traceable.
Remember the basic data split: drone imagery is raster data, while parcels, flight boundaries, GCPs, waylines, and survey limits are usually vector data. You will often analyze both together in one QGIS project.
| Step | Action | Purpose |
|---|---|---|
| Geotag Images | Verify EXIF GPS accuracy | Support proper alignment during processing |
| Create Orthomosaics | Process in ODM, Pix4D, Metashape, or another photogrammetry tool | Create map-ready imagery for analysis |
| Export Formats | Use GeoTIFF/COG for rasters; GeoPackage for vectors | Retain geospatial data and reduce file confusion |
Installing and Setting Up QGIS
The official QGIS download page currently lists QGIS 4.2.2 as the latest release and 3.44.14 LTR as the long-term build. QGIS recommends the LTR when stability is the priority; Windows builds are 64-bit, and official signed/notarized macOS installers are available[1].
System Setup Checklist
QGIS does not publish one simple RAM/CPU number that fits every drone project. Plan around the size of your rasters and whether you are only viewing an orthomosaic or also running photogrammetry in separate software:
- Use a supported 64-bit operating system; QGIS ships 64-bit Windows executables[1].
- Keep enough local storage for source imagery, processed rasters, overviews, exports, and backups.
- Build raster overviews when large orthomosaics pan or zoom slowly[17].
- Separate QGIS requirements from photogrammetry requirements; tools such as OpenDroneMap can require substantially more RAM and storage as image counts grow[20].
- Use a projected CRS appropriate to the work area when measuring distance or area, rather than assuming the project default is suitable[14].
After installation, consider enabling QuickMapServices for basemap access. QGIS also supports native XYZ Tiles, so a plugin is not required for every background-map workflow[4].
Downloading QGIS Software
Visit the official QGIS website and choose the Latest or LTR build for your operating system. Windows users can also use the OSGeo4W network installer. On macOS, QGIS provides official signed and notarized installers; MacPorts is an alternative installation path[1].
Launch QGIS and set your Project CRS. QGIS reprojects layers on the fly by default, so mixed-CRS layers can still line up visually when their coordinate reference systems are defined correctly[14].
Pro Tip: Create one project folder before you import anything. Keep raw photos, processed rasters, vector layers, exports, and reports in separate subfolders so QGIS does not lose file paths later.
Importing Drone Maps Into QGIS
For accurate placement, your imagery must be georeferenced. Drag and drop a GeoTIFF or COG into QGIS, or use Layer → Add Layer → Add Raster Layer…. If your image is not georeferenced, use Georeferencer to place control points and write a referenced raster[2].
- Confirm your raster format before import; GeoTIFF and COG are recommended for drone mapping[3], [13].
- Build overviews, also called pyramids, for smoother zooming on large mosaics.
- Adjust layer symbology, contrast, transparency, and blending for clarity.
- Set the project CRS from a trusted layer if needed; QGIS will reproject other defined layers on the fly[14].
Checking Geotags Before Import
Before you load drone photos or processed imagery, check whether the files contain GPS information. Geotagged images usually include latitude, longitude, and altitude in EXIF metadata. If that data is missing or wrong, your map may appear in the wrong place or fail to align with parcel layers.
For individual photos, QGIS 4.2 includes the native Import geotagged photos processing tool, which creates a point layer from geotagged JPEG or HEIC/HEIF files and carries available altitude, direction, and timestamp metadata into attributes[21]. That is useful for reviewing capture locations; for a continuous mapping surface, process the overlapping image set into an orthomosaic and import the resulting GeoTIFF.
Building Overviews for Large Orthomosaics
Large drone mosaics can feel slow if QGIS must render the full-resolution raster at every zoom level. Building overviews creates lower-resolution display layers inside or beside the raster. This helps QGIS pan and zoom more smoothly while preserving the original detail for close inspection.
Warning: Do not assume a layer is accurate just because it appears in QGIS. Always check CRS, ground control, image processing quality, and boundary source accuracy before using the map for field decisions.
Creating Shape Files for Flight Planning
Terminology note: an ESRI Shapefile is not a single .shp file; it relies on required sidecar files such as .dbf and .shx. QGIS documentation identifies GeoPackage (.gpkg) as the default vector format, so it is the cleaner master format for editable boundaries. Export a separate KML/KMZ or GeoJSON copy only when the next app needs it[16].
| Step | Description |
|---|---|
| Create Vector Layer | Start a new GeoPackage or Shapefile polygon layer for the boundary |
| Digitize | Toggle editing and trace the property or area of interest |
| Attributes | Add fields such as site_id, alt_agl, notes, and mission_type |
| Export for Apps | Right-click layer → Export → Save Features As… → KML/KMZ or GeoJSON for mission planners |
Tip: Use QuickMapServices or XYZ tiles to add basemaps when tracing boundaries[4].
Choosing the Right Vector Format
Use GeoPackage while editing inside QGIS because it keeps layers in one file and avoids the missing-sidecar-file problems common with shapefiles. Use KML or KMZ when you need a lightweight file for Google Earth-style viewing or flight-app import. Use GeoJSON when your downstream tool supports web-friendly vector data.
For most drone workflows, you can follow this simple rule: work in GeoPackage, export a copy in the format your mission app accepts, and keep the original GeoPackage as your master file.
Can QGIS Plan Drone Flights Directly?
Yes, with plugins. QGIS core is a GIS rather than an aircraft-control app, but the current plugin ecosystem can generate mapping flight paths and export files for supported downstream apps. This is the biggest practical difference from older QGIS drone workflows that stopped at drawing a polygon.
| QGIS Option | Best Fit | Current Output / Workflow |
|---|---|---|
| FlyPath | DJI Fly mapping and corridor missions | Generates native DJI WPML KMZ mission files; current plugin listing supports QGIS through 4.x[18] |
| GeoFlight Planner | Photogrammetry, terrain-following, circular, and facade planning | Creates flight lines/photo points and Litchi-compatible CSV-style workflows; current 4.0.2 release supports QGIS 3.44–4.x[19] |
| Flight Planner | Block/corridor photogrammetric planning and coverage evaluation | Creates waypoint, photo-range, projection-center, and flight-line layers; current release supports QGIS 4.x[22] |
Choose a plugin only after confirming the drone model, controller, mission app, and file format you actually use. A mission file that imports successfully still needs field review for altitude, obstacles, return-to-home behavior, camera settings, battery limits, and applicable aviation rules.
Safety: A QGIS boundary or generated route does not validate airspace, legal permissions, obstacle clearance, or site conditions. Review the finished mission in the flight app/controller and follow the rules that apply where you operate.
Visualizing Property Boundaries in QGIS
Import parcel data, such as GeoPackage or Shapefile layers, and style polygons for clear visibility. Accurate boundaries support better flight lines, safer planning, and stronger deconfliction between the mission area and nearby obstacles.
Importing Parcel Data
Create a new polygon layer and digitize the parcel boundary if you do not already have official parcel data. Confirm attributes, then export a copy as KML/KMZ when you need to transfer the boundary to mission-planning apps. Add context with basemaps through the QuickMapServices plugin or XYZ Tiles[4].
- Select the polygon layer type.
- Digitize in Editor mode.
- Confirm feature attributes.
- Export as KML/KMZ or GeoJSON.
- Transfer the file to a mobile device, controller, or cloud workflow for mission planning.
Creating Shape Files
When people say “shape files,” they often mean “a polygon boundary you can reuse.” In QGIS, prefer a GeoPackage while editing. Export to KML/KMZ if your app requires it. Name files descriptively, such as farm_north_boundary.kmz, to avoid confusion later.
Styling Boundaries for Field Use
Clear styling makes field decisions easier. Use a strong outline color, a transparent fill, and simple labels for site names or mission IDs. If your map includes several parcels, group related layers and use consistent naming so the exported boundary does not get mixed up with a reference layer.
Exporting Shape Files for Flight Missions
Export your boundary polygons for the flight app you use. The right export format depends on the app, drone model, controller, and mission type.
- DJI Pilot 2, such as workflows for Mavic 3 Enterprise / M3E, supports importing KML/KMZ for boundaries and waypoint missions through microSD or controller storage[7].
- Map Pilot Pro has workflows for importing KML and exporting KMZ for DJI Fly and DJI Pilot ecosystems[6], [5].
- Litchi Mission Hub can import KML polygons to help with flight planning, and its current workflow also supports DJI Fly KMZ export. Litchi added KML polygon import in December 2025, so the older “coming soon” limitation no longer reflects the current Hub behavior[8], [9].
Export Settings to Check Before Transfer
Before you transfer a file to a controller or app, check the exported layer name, geometry type, and coordinate reference system. KML encodes geographic longitude/latitude using a WGS 84-based coordinate reference system, so export the intended geometry correctly rather than relying on a mislabeled source layer[23]. Also confirm that you exported only the intended boundary layer, not every reference layer in the project.
- Use polygon geometry for area boundaries.
- Use clear file names that include the site and date.
- Open the exported file in QGIS or Google Earth before sending it to the controller.
- Keep a backup of your original GeoPackage project layer.
Integrating KML Files With Flight Planning Apps
Importing KML/KMZ into mission apps lets you snap grid patterns and waylines to your exact boundary. This helps you reduce overshoot, avoid missing edges, and keep flight planning tied to the real area of interest.
KML File Formats
KML and KMZ act as a bridge between GIS and flight apps. They work well for Google Earth-style viewing and easy sharing. Many apps accept KML/KMZ for boundaries, and some also support them for missions, such as waypoints or lines. Check your app’s documentation for supported tags, file-size limits, and coordinate order[7], [5].
- Seamless visualization in Earth and flight apps
- Boundary polygon imports to seed flight grids
- Optional conversion between GeoJSON and KML for compatibility
- Compact KMZ packaging when you need a zipped KML workflow
Importing to Apps
Once you export a KML/KMZ from QGIS, transfer it to your device through USB, microSD, AirDrop, or cloud storage. Then import it in the app:
- DJI Pilot 2: use Route → KMZ/KML Import and choose your file[7].
- Map Pilot Pro: import KML to visualize boundaries; you can also export KMZ that DJI apps can use[6], [5].
- Litchi: KML polygons can be imported to support flight planning, and the Hub can export KMZ for DJI Fly workflows. CSV-based workflows are also used in the Litchi ecosystem[8], [9].
Testing Your File Before Flying
Always test the exported file before you fly. Open it in a viewer, confirm the boundary lands in the correct location, and make sure the shape is complete. A file can import successfully but still contain the wrong boundary, a mislabeled CRS, or extra geometry you did not intend to use.
- Confirm the imported boundary is over the correct site.
- Confirm the mission app interprets the file as the intended geometry or route type.
- Review altitude, speed, overlap/photo settings, turn behavior, and return-to-home settings in the mission app.
- Confirm the route stays clear of known obstacles and matches the actual field conditions.
Utilizing QGIS Tools for Enhanced Mapping
QGIS includes several tools that make drone mapping more useful after you import the imagery. You can style rasters, compare layers, check measurements, clean vector boundaries, and prepare exports for field use.
- Create and edit vector layers in GeoPackage; export to KML/KMZ or GeoJSON for apps.
- Add basemaps through QuickMapServices or native XYZ Tiles[4].
- Use Georeferencer for scanned maps or unreferenced imagery[2].
- Optimize rasters by building overviews and considering COG for large files[13].
- Use on-the-fly reprojection, and set the project CRS appropriately[14].
- Use layer groups to separate raw imagery, processed outputs, reference data, and export-ready mission boundaries.
- Use labels and attribute tables to track site IDs, flight altitude notes, survey dates, and mission comments.
Common QGIS Drone Mapping Problems
If something looks wrong in QGIS, start with the simplest checks. Many drone mapping issues come from missing CRS definitions, non-georeferenced imagery, broken file paths, or rasters that need overviews.
| Problem | Likely Cause | Fix |
|---|---|---|
| Imagery appears in the wrong place | Missing or incorrect CRS/georeferencing | Check layer CRS, geotags, and georeferencing settings |
| QGIS is slow when zooming | Large raster without overviews | Build pyramids/overviews or use a COG workflow |
| Flight app rejects the file | Unsupported format, geometry, or export option | Export a clean polygon as KML/KMZ and test it first |
| Boundary looks incomplete | Unclosed polygon or wrong layer exported | Validate geometry and export only the intended boundary |
Engaging With the Drone Community for Support and Learning
Forums and groups accelerate learning. For mission-planning specifics, such as DJI Pilot 2 KML/KMZ behavior or Litchi Hub export options, vendor knowledge bases and user forums often have practical tips from people using the same drones, apps, and controllers[7], [8], [9].
When you ask for help, include your QGIS version, operating system, drone model, flight app, file format, CRS, and a screenshot of the layer panel. Those details help others diagnose the problem faster.
Frequently Asked Questions
What types of drones are best for aerial mapping?
Choose a mapping drone around the accuracy, area, camera, and positioning requirements of the job. The DJI Mavic 3 Enterprise (M3E) combines a 20 MP 4/3 camera with a mechanical shutter and optional RTK module, while the fixed-wing eBee X is aimed at larger-area mapping. Also check software compatibility, local operating rules, and launch/landing constraints before choosing a platform[10], [11].
Can QGIS process raw drone photos into an orthomosaic?
QGIS can import geotagged JPEG, HEIC, and HEIF photos as point locations, which is useful for checking where images were captured. Creating a full orthomosaic from overlapping drone photos is normally a photogrammetry task handled in software such as OpenDroneMap, Pix4D, or Agisoft Metashape. Import the finished georeferenced raster into QGIS for GIS analysis, styling, measurements, boundary work, and export[21], [12].
Can QGIS plan drone flights directly?
QGIS core is a GIS, not a flight-control app, but current plugins can generate flight-planning outputs. FlyPath can generate DJI WPML KMZ missions for supported workflows; GeoFlight Planner creates mapping plans and Litchi-compatible CSV output; and Flight Planner supports photogrammetric block and corridor planning. Confirm the plugin version, drone, controller, and target app before relying on any exported mission[18], [19], [22].
Can I use QGIS on a Mac?
Yes. QGIS provides official signed and notarized macOS installers for the current release and long-term release. The QGIS download page also lists MacPorts as an alternative installation route[1].
How do I troubleshoot import issues in QGIS?
Check the file format, layer CRS, project CRS, file path, permissions, and QGIS log messages. For unreferenced rasters, use Georeferencer[2]. For very large rasters, build overviews or use a Cloud Optimized GeoTIFF workflow to improve display performance[13], [17].
Are there alternative software options to QGIS for drone mapping?
Yes. Commercial GIS and photogrammetry tools include ArcGIS Pro, Pix4D, and Agisoft Metashape. Open-source OpenDroneMap can process drone images into orthophotos, point clouds, 3D models, and elevation products[12]. QGIS is useful as the GIS workspace where you inspect, edit, style, analyze, and export the resulting geospatial data.
How can I share my QGIS maps with others?
Export map layouts as PDF or PNG, share GeoPackage layers, or publish web maps through QGIS Server or compatible cloud tools. For field work, QGIS also points users to mobile-focused tools such as QField and Mergin Maps[1].
Should I use shapefile or GeoPackage in QGIS?
Use GeoPackage for most editing work in QGIS because it stores vector layers and related data in one SQLite-based file. Use ESRI Shapefile when another tool specifically requires it. For flight apps, export a separate KML, KMZ, GeoJSON, CSV, or other supported copy from your master data rather than making the interchange file your only editable source[16].
Conclusion
For a reliable QGIS drone-mapping workflow, keep processed imagery in GeoTIFF or COG, keep editable vector work in GeoPackage, verify the CRS before export, and create KML, KMZ, GeoJSON, CSV, or mission files only when the downstream tool requires them. If you need route generation inside QGIS, use a current flight-planning plugin that matches your drone and target app.
Before launch, reopen the exported boundary or mission in the controller or flight app and confirm its location, geometry, altitude settings, camera actions, return-to-home behavior, and obstacle context. Treat QGIS as a planning and validation workspace—not as a substitute for current airspace checks, operating rules, or field safety decisions.
References
- QGIS downloads and platform notes. QGIS Downloads — current release, LTR, Windows, macOS, Linux, and installer guidance.
- QGIS Georeferencer user manual. QGIS Documentation — control-point georeferencing and referenced-raster output.
- GDAL GeoTIFF driver. GDAL GeoTIFF Driver — GeoTIFF and raster overview support.
- QuickMapServices plugin. QGIS Plugins — basemap plugin guidance.
- Map Pilot Pro mission export for DJI Fly. Drones Made Easy — KMZ export workflow.
- Map Pilot Pro KML import discussion. Drones Made Easy Community — KML boundary-import troubleshooting and style requirements.
- DJI Pilot 2 mission import/export workflow. Propeller Aero Help — KML/KMZ import workflow for DJI Pilot 2.
- Litchi Hub KML polygon import update. Litchi Forum — December 2025 update adding KML polygon import and DJI Fly KMZ export changes.
- Litchi Hub to DJI Fly workflow. Litchi Forum — current Hub-to-DJI Fly KMZ workflow and compatibility notes.
- DJI Mavic 3 Enterprise. DJI Enterprise — Mavic 3 Enterprise camera and RTK mapping features.
- eBee X fixed-wing mapping platform. EagleNXT — eBee X platform and mapping use cases.
- OpenDroneMap. OpenDroneMap on GitHub — open-source photogrammetry outputs and project source.
- QGIS raster conversion tools. QGIS Documentation — Cloud Optimized GeoTIFF creation in current QGIS.
- QGIS coordinate reference systems. QGIS Documentation — project CRS and on-the-fly transformation.
- QGIS supported data formats. QGIS Documentation — GeoPackage defaults and Shapefile structure.
- QGIS raster overview tools. QGIS Documentation — raster pyramids/overviews for faster display.
- FlyPath plugin. QGIS Plugins — DJI WPML KMZ mission generation and current compatibility.
- GeoFlight Planner plugin. QGIS Plugins — photogrammetry flight planning, terrain-aware tools, and Litchi-compatible CSV output.
- OpenDroneMap installation and hardware guidance. OpenDroneMap Docs — photogrammetry hardware guidance distinct from QGIS desktop requirements.
- QGIS geotagged-photo import. QGIS Documentation — native import of geotagged photos as point features.
- Flight Planner plugin. QGIS Plugins — photogrammetric block/corridor planning and coverage outputs.
- OGC KML 2.3 specification. Open Geospatial Consortium — KML coordinate-system requirements.
