Mavic 3 waypoint missions

Does anyone here own a Mavic 3? I am writing a utility to convert a DJI Mavic 3 waypoint mission into a Litchi mission. I need some example Mavic 3 kmz files for testing purposes.

If you have a Mavic 3 and would like to provide some sample data, please let me know.


I have an “alpha” version of the “Mavic 3 Waypoint to Litchi” converter ready for testing. Because it is based on seeing only one Mavic 3 KMZ file, there are undoubtedly cases where it will fail. If it does fail, please contact me. I need to examine more Mavic 3 KMZ files to ensure that this converter will work reliably.

Will M3Enterprise files work for you? How about going from Litchi to M3?

I would think they are the same. Yes, I would like to see some examples. I also have a “Litchi To M3” converter mostly written. However, I need to see more sample kmz files first.

I just bought a Mavic 3 and I want to experience with waypoints. I had first a Mavic 2 zoom and used Litchi verry often. So I am interested in what you are doing.
So far I can see now the waypoints in te Mavic 3 don’t use online elevation . Is that correct?
When I have more experience with the Mavic 3 I will send you exemples of missions.

Yes, that is correct. However, neither does the Litchi app. On-line elevation is only used in Litchi’s Mission Hub if the “Above Ground” option is checked when planning missions.


I converted a Litchi flight (CSV) to the Fly app (KMZ), see both screenshots.
You say On-line elevation is only used in Litchi’s Mission Hub if the “Above Ground” option is checked when planning missions.

In Litchi’s screenshot, you see that terrain elevation is taken into account and the converted version in the Fly app does not. Therefore, isn’t it tricky to use this conversion in the Fly app?

You are correct. This highlights an unfortunate difference between exporting a Litchi mission as a CSV file and flying a Litchi mission using the Litchi app.

In your case, you set the height of all waypoints at 40 meters above ground. When flying this mission using the Litchi app, the drone will fly to the heights shown in parenthesis at each waypoint. WP1=40, WP2=48, WP3=53.9, FP4=47.9. However, when exporting this same mission as a CSV file, the above-ground heights are written to the file. WP1=40, WP2=40, WP3=40, etc. If this CSV file is converted to an M3 mission, it uses the values in the CSV file which are all 40 meters.

This is an unfortunate result of only storing the above-ground heights in the CSV file. I wish we were given a choice. There is a work-around. Depending on the number of waypoints, this may be time-consuming.

In Litchi’s Mission Hub, create your mission as you have already done with the “Above Ground” option checked. Then, at each waypoint, enter the height shown in parenthesis and uncheck the “Above Ground” option. Do this for every waypoint. This way, the above-ground heights will be written to the CSV file and those same above-ground heights can be converted to an M3 mission.

thanks for the reply. This works but unfortunately is very cumbersome in combination with all the other conversion steps.

Yes. I wish there was a better way to extract the “above home-point” heights but they aren’t written to the CSV file. Sorry.

I am getting the error “File size too large” for KMZ files over 4kb. Any suggestions?

Otherwise, it seems to be working nicely.

I have increased the limit to 5KB. Try now.

Need 6… That’s the largest one I promise.

That’s much larger than any mission I’ve seen. I’m curious what is making it so large. I’ve increased it to 6KB.

Must be all those unsupported actions?

1 Like

That could be. Actions add a lot of code to the wpml data.

1 Like

Thank you for such a quick response. That seems to have worked out.

Thanks again!

I have modified my “Litchi to Mavic 3 Waypoints” converter to make a Google Elevation API call when converting a mission with the “Above Ground” option checked. This enables me to adjust Litchi’s “Above Ground” heights to “Above Take-off” heights in the Mavic 3 mission. Please give it a try.


Hallo Wes Barris,
Herewith the results of my test with the new version.
I looked at two flights, look at the attachements

Two observations:
1.There are differences in heights between Litchi AG and the DJI Fly app after conversion, see list below

Conversion GE APL Litchi AG Difference
Waypoint Height
1 15,00 15 0
2 8,9 7,7 1,2
3 7,1 7,5 -0,4
4 13,9 11,1 2,8
5 13,3 10,2 3,1
6 6,2 5,2 1
7 8,9 6,1 2,8
8 10,1 10,1 0
9 20,6 18,6 2
10 12,7 12,7 0
![image 476x357](upload://cDiS09WMqSiHqSFrtF6R1xZHKc1.png)
Waypoint Height
1 40 40 0
2 57,1 48 9,1
3 59,3 53,8 5,5
4 59,5 47,9 11,6
5 39,7 39,7 0
![image 476x216](upload://6V3NGQWCfIh2xjGzPQlQJfBcFrQ.png)

What is the cause?

  1. In the flight with 10 waypoints (Bjorn) the converted flight is not coorrect, wpt 8,9 and 10

kind regards,
Hans heijnen

That is weird. Looking at the WPML code, I do not see what would be causing that. Would you do two things:

  1. Please try converting your Litchi mission using this temporary development version of the converter and then load the resulting KMZ file to your flying device and see if it changes anything.
  1. Please create a similar mission using DJI Fly (the exact coordinates do not have to be the same) and then send both the DJI KMZ file and your Litchi CSV file to me. I would like to compare my conversion with your DJI file to see the differences.