Select to view content in your preferred language

Better orientation data support needed for drone workflow

54
0
yesterday
Status: Open
ÁkosHalmai
Frequent Contributor

At the beginning of the "New Reality Mapping Workspace", you have to select the scenario, which can be Aerial or Drone. On the drone side, better support needed for orientation data:

1. If you add an image, perspective center is listed, no orientation data is displayed. The user is unable to decide, whether there is no orientation data in the image or just not loaded. Here three extra columns, like yaw, pitch, and roll would be beneficial.

2. At the "Import GPS file" it is possible to load orientation. However, the only accepted format is OPK, which is rarely used in the drone world: Yaw, Pitch, Roll is much more supported, and users are not prepared to do calculations on the local tangential plane. A switch between OKP and YPR would be nice. And if the user loads orientation data, at the Adjust, the Use orientation from metadata should be selected automatically

3. There is an assumption that the location info is loaded from EXIF, but most of the drone manufacturers support XMP metadata, with better and bigger resolution of location, location accuracy and orientation readings.

Best regards,

Ákos Halmai