Hi everyone,
I’m working on a project in PIX4Dmatic that combines drone images (DJI M4E) with images from a Share S20 laser scanner (which has a left and a right camera). Since Share S20 camera support was introduced in one of the recent Matic versions, I’ve been trying to process the scanner images alongside the drone data.
The issue: When importing the right camera images of the Share S20, Matic splits them into two separate camera groups:
-
SHAREUAV_SHARESLAMS20RightCam_SVCA01_3.6_3504x4672– correctly identified as the Share S20 right camera (n=179 images) -
Generic_ShareUAV_R2000_SVCA01_3.6_3504x4672– assigned a generic camera model with completely different intrinsic parameters (n=1,237 images)
The left camera (SHAREUAV_SHARESLAMS20LeftCam_SVCA01_3.6_3504x4672, n=1,416) is imported cleanly as a single group without any splitting.
Camera internals comparison:
Looking at the intrinsic parameters of both models, the differences are substantial:
| Parameter | Generic (R2000) | SHAREUAV (S20 from PIX4D DB) |
|---|---|---|
| Pixel size | 2.4 µm | 7.25 µm |
| Sensor width | 8.41 mm | 25.40 mm |
| Sensor height | 11.21 mm | 33.87 mm |
| Principal point x | 1752 px | 1746 px |
| Polynomial coefficients | 0, 1, 0, 0, 0 | 0, 1, +0.022, −0.023, +0.061 |
| Affine c / f | 1752 / 1752 | 2322 / 2322 |
| Source | user input | PIX4D database |
The Generic model appears completely uncalibrated – zero polynomial distortion coefficients, wrong pixel size, no proper calibration entry. This will likely corrupt the reconstruction for the 1,237 affected images.
Please see the attached screenshots for reference.
My questions:
-
Is this expected behavior, or is this a bug in camera model detection?
-
Should I manually reassign all images to the correct Share S20 right camera model, or would that introduce errors?
-
Has anyone successfully processed Share S20 data in PIX4Dmatic and run into the same issue?
Any help appreciated – thanks in advance.
Manuel



