Agisoft Metashape
Agisoft Metashape => General => Topic started by: Zim240 on February 24, 2018, 12:44:00 AM
-
Good day,
I am importing cameras from external sources using the import camera function.
I am using bingo.dat format.
Below is the file content:
* <____Photo_ID__><___Easting__><__Northing__><__Height_><___Phi__><__Omega_><__Kappa_><____Camera_ID_>
ORIA 07044634.jpg 374281.163 863977.346 1036.290 3.1500 0.1307 -3.0353 S000000
ORIA 07045014.jpg 374476.399 873007.337 1054.190 0.0515 -2.2880 121.6280 S000000
ORIA 07045017.jpg 374302.955 872910.869 1052.826 3.8781 -0.6670 120.1826 S000000
Also the camera information in bingo.dat
file_version: 1
begin gridgroup "Image deformation grids"
enabled: yes
order_index: 0
camera_name: "iXU1000-R (50mm)"
description: "Calibration grid"
begin grid "Image deformation grid 1"
enabled: yes
inverse_scale: 1.000000
columns: 27
rows: 21
description: " "
begin gridpoints
-26.3040 -20.2381 -26.0000 -20.0000
-24.2631 -20.2235 -24.0000 -20.0000
-22.2250 -20.2087 -22.0000 -20.0000
-20.1899 -20.1942 -20.0000 -20.0000
-18.1582 -20.1801 -18.0000 -20.0000
-16.1298 -20.1667 -16.0000 -20.0000
-14.1048 -20.1543 -14.0000 -20.0000
-12.0829 -20.1431 -12.0000 -20.0000
-10.0640 -20.1333 -10.0000 -20.0000
-8.0476 -20.1250 -8.0000 -20.0000
-6.0334 -20.1185 -6.0000 -20.0000
-4.0209 -20.1137 -4.0000 -20.0000
When I am done importing, I import the orientation details into the reference pane also.
For some reason the orientations give large errors on the reference pane. (See screenshot)
Why is this happening?
After I import cameras, I import an mesh and produce an orthomosaic with planer XY projection. With the current state of affairs I see large mismatches on the seamlines as photoscan has changed the exteriors somehow.
Thank you in advance for your help.
-
Hi Andre240,
You don't need to import your camera orientations in order to generate an accurate model. Instead, only use camera LOCATIONS. When running the photo alignment, enable REFERENCE PRESELECTION.
Note that the large orientation errors you've encountered are probably due to a different 'orientation convention' that PhotoScan is using. It has been discussed in the forum in the past.
All the best.
Regards,
SAV