First off, i really appreciate your development of this great tool. Keep it up!
Based on the flight planning of Qgroundcontrol, it would be nice not only to split up the polygonized measurement area with "makeAP", but also to include the arrivals and departures per flight. Taking these into account when calculating flight time dependent tasks with respect to a given "maxFlightTime" argument, would improve the battery usage. Currently, flights that take place "far" away from the take-off point use the battery too much and those that are close to the take-off point use too little battery capacity.
First off, i really appreciate your development of this great tool. Keep it up! Based on the flight planning of Qgroundcontrol, it would be nice not only to split up the polygonized measurement area with "makeAP", but also to include the arrivals and departures per flight. Taking these into account when calculating flight time dependent tasks with respect to a given "maxFlightTime" argument, would improve the battery usage. Currently, flights that take place "far" away from the take-off point use the battery too much and those that are close to the take-off point use too little battery capacity.
Kind regards