Drone2Tractor
lvl.1
Australia
Offline
|
DJI Natalia Posted at 11-12 01:09
Hi, there. Sorry for the late reply.
Please note that you can not create flight plans that will utilize both (L1 & P1) at the same time.
Thank you for your understanding.
Hello Natalia,
Can we add this as a feature request. The L1 and P1 make a very interesting combo for data collection. To a degree, it does not matter that their field of views are not the same. During the mission setup, you would have the options to indicate which sensor is the primary and which is the secondary for when determining the flight path. i.e. if you select the P1 as the primary, you should get options around doing a photogrammetry style operation where we select the side overlap, and the forwards. At the mission summary, we would get a page that details the L1 data coverage for the area during the flight.
Something similar for if we choose the L1 as the primary. In this situation you would have the same sliders, but if the side overlap of the L1 is too low, a warning could be presented to the end user that the P1 will not have any side overlap.
Both of these also would need to have the position offsets sent to the corresponding payload to ensure that the position of the images/lidar returns are correctly adjusted. Or we would need to have an option in the Terra software to input an offset (whether custom or set known offsets of the dual payload).
In our situation, we now need to do at minimum 2 separate sets of flights to get the data that is required, when if we could fly with both at the same time, we would be able to fly only once.
This particular setup may also be of interest to other operators with the L1, and a thermal flying at the same time, or the L1 with the Z30 for asset inspections that also render a clean 3D model from the LIDAR, potentially enabling us to take real measurements from the images when blended with the L1 data. |
|