Skip to content
DJI Mavic 2 Pro Mapping Mission
Introduction
Figure 1. Image taken from DJI Mavic 2 Pro mapping mission
In this lab, my team and I wanted to use the DJI Mavic 2 Pro in a mapping mission. Our first objective was to discover, identify, and implement different methods for grid-based mapping missions. Our second objective was to understand the fundamentals of Metadata and apply that understanding by applying it to our mission. In addition, we wanted to compare the DJI Mavic 2 Pro mapping capabilities against the Skydio 2+. To ensure results were accurate, we mapped the same area as we did the Skydio.
Team members
Table 12
Column 1
Column 2
Column 3
Column 4
Isabella Avedician
Joe Kahi
Jacob Sieber
Venkata Devapatla
There are no rows in this table
*We were given permission to work as a group due to mapping the same area*
What we were flying and why
My team and I wanted to fly the DJI Mavic 2 Pro in the same mapping mission we did as the Skydio 2+. We wanted to test and identify different methods for grid-based mappings and to implement Metadata into our mission planning.
Metadata
General
Location:
William H. Daniel Turfgrass Research and Diagnostic Center
1340 Cherry Ln, West Lafayette, IN 47907
Date: 09/23/2025
Vehicle: Mavic 2 Pro – ID: B serial ID - 1581F1633J27001H1380
Sensor: Gimbal - -90 degrees (nadir)
Battery: 4 lithium polymer smart batteries
Approval # (LAANC/COA/Waiver): Yes
Flight Information
Flight Number: 1
Takeoff Time: 1530
Landing Time: 1539
Altitude (m): 200ft AGL
Sensor Angle: -90 degrees
Overlap: 80%
Sidelap: 80%
Ground Control - no
System used (ie PPK, RTK, Aeropoints) - no
Coordinate System: GPS
Weather
Cloud Cover: METAR says clear but site is cloudy 1500 ft AGL
Wind Direction: 190
Wind Speed: 8-16 knots gustijg
Temp: 26C
Crew
PIC: Venkata Devapatla
VO: Joe Kahi, Jacob Sieber
Data recorder – Isabella Avedician
Site Conditions, Hazards, METAR, LAANC
Figure 2. Site Conditions
The METAR, figure 4, said relatively clear skies. However, upon arrival at site, my team and I saw clouds heading away from us. We looked at the cloud ceiling, and they were well above 1200 ft AGL. Our maximum altitude was 200 ft AGL, which would put us well under the 500 ft AGL requirements.
Figure 3. Hazards at site location
The main hazard at this site was the towers and parked cars nearby. We were not flying near the towers or the parking lot but set out parameters well away from them to ensure no collision or incident occurred.
Figure 4. METAR
The METAR for this mission is as follows:
Table 13
KLAF
Purdue University Airport (Class D Airspace)
231854Z
23rd of September 2025; 1454 EST
19008G16KT
Wind: 190 degrees, Speed: 8 knots, Gust: 16 knots
10SM
Visibility: 10 statute miles
There are no rows in this table
Figure 5. LAANC Authorization
At this site location, we were required to get LAANC to operate and complete our mission. This is due to us being in Class D airspace near KLAF, Purdue University Airport.
Mission Planning and Set-Up
Figure 6. Venkata Devapatla setting up DJI Mavic 2 Pro
Our plan for this mission was to perform a parallel “lawn mower” grid at 60-meter altitude, with 80% lateral and frontal overlap, and with the gimbal angle 90 degrees (straight down). Before setting up we designated roles. The Pilot in Command was Venkata Devapatla, Joe Kahi and Jacob Sieber as Visual Observers, and Isabella Avedician as Data Collector. Before leaving dispatch at Purdue University Airport, we examined the drone to make sure it was airworthy and ready to be used. Upon arrival and set-up, we performed another visual inspection. Then we began to set the UAS up. We used the Drone Deploy app to download the map for this mission. After set-up was finished, the site and hazards were identified and roles were assigned, we were ready to begin our flight.
Figure 7. Parameters for mapping
Using the DJI Go 4 app to connect to the drone. We used the map capture plan, with a maximum altitude of 200 ft AGL. We had enhanced 3D turned on. The drone estimated the entire flight to be a total time of 8 minutes and 50 seconds, go over 3 acres, take 158 images, and use only 1 battery.
Issues Encountered and Resolution
Figure 8. Error message encountered
When setting up the DJI Mavic.2 Pro we had an issue once the drone was connected to Venkata Devapatla’s phone. There was a system warning, figure 8, that revealed IMU altitude error. We fixed this issue by powering off and on the drone and recalibrating it. After doing this, the issue was resolved.
Data Collection
The data collected was the 158 images on the DJI Mavic 2 Pro. We plan to use this data later in the semester.
Table 14
Time to Drive and Set-Up
7 minutes to and from KLAF to Site, set-up took 30 minutes due to issues
Time to Fly Mission
8 minutes 50 seconds
Number of images taken
158 images
Size of each image
Seen in OneDrive Folder
Size of the entire dataset
Seen in OneDrive Folder
There are no rows in this table
Summary
In summary, we successfully completed our two main objectives: to discover, identify, and implement different methods for grid-based mapping missions and to understand the fundamentals of Metadata and apply that understanding by applying it to our mission. We also looked to compare the mapping capabilities of the Mavic 2 Pro to the Skydio 2+ over the same grid. We noticed that the battery died faster in the Mavic 2 Pro then it did in the Skydio 2+. This could’ve been due to the issues we had with the IMU calibration. In general, the Skydio 2+ is easier to fly and provides better quality images than the Mavic 2 Pro. This is due to the Skydio 2+ having 6 navigational cameras and we noticed that obstacle avoidance in the Skydio 2+ is better. If it came down to picking between the two drones, the Skydio 2+ seems to be the better fit for mapping missions because of its 6 navigational cameras, obstacle avoidance, and it's incredible autonomous flight capabilities.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.