Boundary Nor Respected by Flight Path - Drone Plows Right Through "Boundary"
I set a boundary to avoid colliding with a tree. The path ignored the boundary and the drone went straight through and violated the "boundary". Twice I've had collisions with trees. The boundary just stopped the drone from taking pictures, but let the drone cross the "boundary". Also not taking picture is cause for the customer to demand a reshoot. Here is a screen shot the the Path piercing the "boundary": 
Comments
7 comments
The mapping boundary simply defines where you want to capture data. If you want to define a no go zone, you need to use restriction zones:
https://support.dronelink.com/hc/en-us/articles/4418513904147-Intro-to-Restriction-Zones-to-Create-No-Fly-Zones-Around-Obstacles
The other thing to remember, those maps may not be reflecting current state of the tree. : ) They grow like crazy and who knows when the mapping image was taken.
I did a timelapse shoot for a home that was being built a number of years ago. I set up the locations in the winter and then had to move several of them once the spring arrived because they trees exploded in size!
Tony - that was my first lesson! Ouch!
Jim - Thanks - I'll check it out! Can we combine that with Boundary as an selection option? I hate flying into trees.
Barry - Husqvarna !
Hey Daniel. Just a bit more info. As Jim stated the boundary is just defining what will be captured so don’t look at those for any other purpose. The drone flies the path, not the boundary lines. So the plan you have indicates the path is directly inline with the tree. I’d suggest creating a test map, doesn’t matter where and add a restricted zone or two anywhere on the path. You can adjust the size/ area, horizontal or vertical bypass and some other options. I don’t run maps often but I test a lot of functions just to see how they work. I ran a couple with different zones both vertical and horizontal bypass and it was easy. Flew great. Also suggest importing the KMZ file to Google Earth and run once completed. Still wont be a current map but at least give a much better idea of what may be there at that time before going to the actual site.
Also when flying the mission you can pause at any time so it doesn’t hit that tree or anything else. I’m always ready to pause if I’m flying really low AGL missions or within a closer proximity to trees or buildings. I’ve had to pause some and even cancel a few missions over the past couple of years. Some may have been ok but if too close and risky then I cancel. Better to be safe then sorry.
Good luck.
Upvoting Mike on that. Always be ready on the pause. : ) Ultimately, sometimes plans work so well in the real world. Pause, change offset if needed, resume.
Good advice Mike, I use KMZ as well in mission planning. I also run my Mini 3 Pro up first for height and size of obstacles evaluation before an autonomous mission and have adjusted the mapping plan as a result. (saved me a couple of times!).
Please sign in to leave a comment.