How to keep drone path inside boundary box when creating grid map?
I'm adding a map component and manually inserting the four corners of the boundary box to a specific rectangular property. But the flight path that is auto generated spills outside the border of the boundary box. Is there a way to keep the created path inside the boundary box (like DroneDeploy does)?
Comments
4 comments
What's the difference, what for?
The difference: as it appears to be now, the boundary box isn't actually a boundary, and so the drone flies outside the boundary box in grid map mode. What I was wondering (and will request since it appears this functionality doesn't exist) is for the boundary box to actually be a boundary to keep the drone inside the boundary flying a grid inside the boundary box.
What for: to keep the drone from flying outside the boundary box.
The boundary is the boundary for image capture (not flight right now). Most users care more about where the data is captured than where the drone is flying, but I understand the desire.
I know this is somewhat of a feature request, but its quite important to fit with the legislation in my country. Frequently you want to define the area to be mapped as an entire property. Or an area that goes up to a property boundary.
Legally we are not allowed to fly over a property without permission from the owners, so even though the loops are a fleeting breach it can either restrict what can be mapped, or alter the flight plan to be less optimal to allow the overlap loops to take place.
The best solution for my purposes would be to slow the drone as it approaches the end of each run, taking a photo on the end point while still. Then fly to another stop waypoint at the start of the next run, take a photo, and go. The downsides of this are that it would extend flight time required for mapping, and mean that the photos at the end of each run were taken with additional overlap.
Please sign in to leave a comment.