Hello Erotokritos,
sorry myself, I got sick and catched covid unfortunately so here very late my responses to your questions:
- Importing uas data in TBC results in the creation of a huge project which stores a copy of original photos, and a second override photo with lower resolution, which, if I am correct, are the thumbnails shown in TBC. This is fine if you want to process the project in TBC. But if I just want to process the baseline trajectory to compute the coordinates of the photos? Is there an option only do that and not create huge projects?
No, as during the import of the images we determine the camera model and also assign to each image the related values. So the current version won't support this processing behavior.
- importing the data seems that TBC supposes the antenna is Phantom 4 RTK and the antenna height method is the Bottom of antenna mount. Is this correct? I thought, correct me if I am wrong, that offset values in the MRK file are from the antenna Phase Center of the drone. So i expect the same for the raw data. Should i change manual to antenna phase center?
No, at the moment the text written for the antenna (Phantom 4 RTK) during the import is a dummy entry name, but we are using a general DJI file for the moment as we do not have more accurate information from DJI about the offset.
Concerning the MRK and OBJ file it is difficult to say something about the MRK. As the MRK is "rewritten" from DJI. If they "corrected" the data offset values based on the phase center or the antenna bottom is unclear.
We can assume very strong, that the Rinex file is based on the antenna center, as this is the file created during the flight.
So I assume we won't find a solution for the MRK here unless we find a clear statement or press release from DJI, which origin the MRK file corrections are using.
Hope this helped Erotokritos.