Generally, how do users determine elevation to fly for mapping missions? Using Litchi for example the height above ground is set in the app prior to starting mission, and app controls flight without user input.
Plan your mission and load the kml in to GE. Then do an elevation profile on the route. This will get you close but always take those numbers with a grain of salt and add plenty extra altitude. Add the extra not simply due to the elevation errors, but also due to barometer variations in the AC.
I do not trust Litchi or Google earth for altitude. I do fly many Litchi missions.
Walk the route first and observe(if possible). Fly the route manually at a safe altitude, and then decide what parameters to set in Litchi, always have a good safe margin.
You should of course be flying VLOS, so keep finger on the cancel mission switch. Flying beyond VLOS is asking for trouble.
Walk the route first and observe(if possible). Fly the route manually at a safe altitude, and then decide what parameters to set in Litchi, always have a good safe margin.
You should of course be flying VLOS, so keep finger on the cancel mission switch. Flying beyond VLOS is asking for trouble.
If you by mapping mean waypoint mission, please ignore the rest of this post. If not, try DroneDeploy which is built specifically for this. The new 3d capture feature currently in beta is excellent.
Similar threads
