Manage large areas missions
Hi all,
I am planning to try out a large area mapping mission with my Mavic 2 Pro.
What is the best approach for multi battery flights?
Let's say I had a 1 hour mission, what shoud I do?
Is Dronelink able to restart with the second battery from the point where the first part of the flight ends?
Splitting it in 3 different smaller missions would be tricky.
Comments
5 comments
Dronelink automatically handles battery swaps, just plan it as one mission (assuming you have a modern mobile device).
Great! Then I'll try soon a long single mission. Thank you and congrats for this excellent app!
Hi all,
My question is also about managing large areas.
I'm planning a flight for ~700 acres (280 ha) - for orthophoto mapping.
I originally created a single plan - with only one component - map (+ approach). It looked too big, so I decided to split it into several smaller missions.
I created smaller maps/components within the large plan, as I thought I could fly each map/component separately.
It didn't look like I could do so.
And I didn't find an option to export each component into an individual plan.
I could add the components into a repository - but it wasn't useful, because when I import a component into a new plan - it moves from its original coordinates to where I point with a mouse.
In the end i found a workaround:
I had a large plan "LARGEPLAN" with 10 map components. I copied "LARGEPAN" 10 times, and in each copy I removed 9 maps/components, leavening only 1 for the drone to fly. I think it's the best way so far.
Is there a better approach to what I'm trying to achieve?
The main reason for creating a large plan in the first place is to see how the smaller maps/plans overlap and how large/small the sub-plans will have to be.
On a similar note,
1) is there any way to import KML boundaries of an area as simple lines/polygons, instead of automatically converting them to paths/maps for flight?
2) Is it possible to import a KML file after a plan has been created?
I can only import KML from the dashboard, which then creates l a new plan. But I didn't find an option to import KML into already existing plans.
This would be very helpful for mapping.
Many thanks!
I don't think there is a better way to do this right now. KML is one shot right now (cannot import into an existing plan), but there is no technical reason we couldn't implement that. We don't support polygon overlays from KML right now in the planner.
Thank you for the clarification.
Please sign in to leave a comment.