We all know that the flight altitude of our P4 is related to altitude of the takeoff point.
This means that if you start to fly from the base of an hill (always 0 altitude) and if you want to fly across that hill (for example altitude 100), if you set a cruising altitude of 50 you're going to crash halfway up the hill. You could set a flight altitude of 120 but, in a survey, this would mean having some photos (the ones taken at the beginning of flight) 120 meters away from the ground and some photos (the ones taken over the final part of the hill) at 20 meters above the ground... so bad...
The ideal solution would be to plan a flight that is maintained at a fixed distance from the ground, regardless of whether the terrain rises or falls... I searched a lot on the net until I found this video...
I did some tests and the concept works well.
Now the problem is how to link this concept to, for example, Mission Planner in order to manually adjust the altitudes of waypoints in a grid survey... or maybe to directly write a Litchi survey mission...
This means that if you start to fly from the base of an hill (always 0 altitude) and if you want to fly across that hill (for example altitude 100), if you set a cruising altitude of 50 you're going to crash halfway up the hill. You could set a flight altitude of 120 but, in a survey, this would mean having some photos (the ones taken at the beginning of flight) 120 meters away from the ground and some photos (the ones taken over the final part of the hill) at 20 meters above the ground... so bad...
The ideal solution would be to plan a flight that is maintained at a fixed distance from the ground, regardless of whether the terrain rises or falls... I searched a lot on the net until I found this video...
I did some tests and the concept works well.
Now the problem is how to link this concept to, for example, Mission Planner in order to manually adjust the altitudes of waypoints in a grid survey... or maybe to directly write a Litchi survey mission...