I would like to share my experience and ask about an issue with my workflow following the update to the new Litchi Mission Hub.
Previously, in the classic version (V1), my workflow was fast and streamlined: clients provided pre-established, very long, and exact flight paths in KML format; I simply imported the KML file, and the platform automatically generated the entire mission along with all its waypoints. From there, I only had to fine-tune the flight parameters (altitude, speed, curves), finishing the setup in just a few minutes.
However, in the new Litchi Mission Hub, this process has become very tedious. When importing a KML file, the system only loads it as a visual Map Overlay, forcing me to manually trace and click every single waypoint along the client’s path. This doubles my workload and introduces potential inaccuracies on strict routes. The platform now essentially expects CSV files to load waypoints directly, but I have not found any tool or converter to automatically transform a KML file into Litchi’s required CSV structure.
Is there any setting, feature, or method in the new Litchi Mission Hub to automatically generate waypoints directly from a KML file as before, or any practical solution to avoid redrawing everything manually?