I´m interested in Litchis Height above Ground feature. I´m flying an ANAFI Thermal, using it to look for Fawn (Baby Roe) in meadows, before they get mown.
Since the really crappy resolution of ANAFI´s Thermal Camera, it is vital to maintain height over ground. Terrain Changes here permanently, so even if you fly at 30m above Starting Point, you may be 10m or 50m above Ground. Too high, and you miss something because of low resolution, too low, and you miss something because of narrow field of view.
To get Height above ground in FF6, the only way is to work with Google Earth and get Terrain Height of each and every Flight Point, and calculate "height" manually.... Very easy to make a mistake. So beeing able to use Litchi instead would be of grat benefit. Also because of the Ability to program with the Ergonomics of a PC Mouse....
Reaaly looking forward to this !
Unfortunately it will not be possible to report automatically "above ground" altitudes in the ".json" files which are used by Flight Plan because the ".csv" file which is generated by Litchi hub and which is used by our small program for building the Flight Plan mission does not contain these data. This Excel file only contains a column with raw altitudes and an other column specifyng how this altitude has to be interpreted by the app. This column defines an "Altitude mode" that can be 0 (raw altitude is used) or 1 (altitude above ground elevation is used).
However, our little app can help to edit Flight Plan waypoints to set them at "above ground altitudes" as calculated by Litchi. I have built a short "above ground" mission over an uneven terrain which is my usual playground :
Mission Hub - Litchi. All waypoints are set at 40m "above ground".
As usual in the hub altitude at each waypoint is defined as the desired altitude above ground elevation (here 40m) and between brackets, the absolute altitude the drone has to reach to comply with these fixed 40m above ground (for waypoint 5 above the beach, this altitude will be roughly 5 m. In fact, I think that it rather should be 0m because altitude above sea level at waypoint 1 will be roughly 80m, i.e. ground elevation = 40m at this waypoint). The Litchi mission displayed in Google Earth :
If, with our little app, I transcript this .csv mission in .json mission for Flight Plan, I obtain this in FF6 :
All altitudes are set at 40m and not above ground level but the advantage is that all other settings of my Litchi mission are faithfully reported here (heading, gimbal pitch, speed ...) and specially the position of waypoints which is absolutely identical to the hub one.
Thus, if I trust "above ground" altitudes defined by the Litchi hub, I have just to edit all Flight Plan waypoints for altitude in order to get my complete Anafi mission. This is what I have done below in reporting the bracketted rounded values displayed in the hub :
This edition can be done in the app or directly by editing the .json file with a text editor in your PC.
Hope this helps. I'm going to test this this afternoon by compairing the same missions flawn with my Mavic and by Anafi. Crossing fingers