The ability to import kml files from external sources seems to be difficult to utilize in a reliable way. It was difficult to get it to import a file. For me, I first had to create a mission on the explorer app and save it before any uploaded file was even visible.
The good news is the ability to for example export a Litchi mission and import as a kml, at least then have the waypoints to work with. Having good success with this now having found a few tricks including disable curves in the Litchi mission. The bad news is there is some cleanup to do if duplicate waypoints get brought over as part of the kml, plus, have lost pois, as well as waypoint actions and issues with altitudes.
Have also seen where autel throws an error if trying to rename an imported mission from litchi if using kml vs. vml (you can import both, one throws an error on rename). For example, from litchi you can export as a klm and as a vlm (besides as csv etc). The klm can be imported into to autel, renamed, etc without an error from the explorer app. However if you import the vlm, it will load the waypoints, you can edit the waypoints, however if you try to rename the mission the explorer app will throw an error.
The issue continues to be you can import the waypoints, even alt, however takes time to add or fix pois, then go to waypoints and set poi if applicable, adjust altitudes, cruising speed, and adding waypoint actions. However the biggest issue is if after taking the time to do the above on the app (desktop would help speed things up), you save, and make a local copy, however you cant export/save that mission to another device/app. Those missions and time to set them up now have an affinity to the device they are on, if something happens to that device, sol.
