PIX4Dmatic can process images captured by practically any camera as long as the images contain the necessary EXIF/XMP (metadata) tags.
Note: Multispectral and thermal cameras are not compatible with the PIX4Dmatic software at the moment.
PIX4Dmatic does not impose a limit on the size or resolution of the images that can be imported.
If image geolocation and orientation (yaw, pitch, roll) are not written in the images' metadata, it is possible to import the information with either a .txt or .csv file. To import the image geolocation and orientation with a .csv or .txt file, please see the Image geolocation and orientation import format article.
Important: Image geolocation and orientation values, written on the images' metadata, are not necessary in order to be able to import and process them in PIX4Dmatic from version 1.34.0 and newer.
Information: PIX4Dmatic uses one of the following camera models when images are successfully imported:
- The precalibrated internal camera parameters for images captured with a camera that is in the internal camera model database.
- The EXIF-driven generic camera model for images that are captured with a camera that is not in the camera model database that have the Required (
) and Required for Exif-driven generic camera model (
) tags. See the EXIF and XMP tag information for project creation article for reference. - A generic camera model for images that are captured with a camera that is not in the camera model database that have the Required () and at least one of the following sets of tags:
Exif.Photo.FocalPlaneResolutionUnitandExif.Photo.FocalPlaneXResolutionorExif.Photo.FocalPlaneYResolutionorExif.Photo.FocalLengthandExif.Photo.FocalLengthIn35mmFilm.
See the EXIF and XMP tag information for project creation article for reference.
Every camera model is optimized during the Calibrate step to calculate optimal camera parameters for each project.
Precalibrated camera models
| Manufacturer | Camera | Syntax |
|---|---|---|
| Apple | iPad with PIX4Dcatch | Apple_Pix4Dcatch.iPad8.9_1920x1440 |
| Delair | Delair UX11 | DJI_UX11-3B_12.0_5048x4228 |
| DJI | Mavic Air 2 | FC3170_4.5_4000x3000 |
| Mavic Pro | FC220_4.7_4000x3000 | |
| Mavic 2 Pro | L1D-20c_10.3_5472x3648 | |
| Mavic 3 | L2D-20c_12.3_5280x3956 | |
| Phantom 3 Professional | FC300X_3.6_4000x3000 | |
| Phantom 4 | FC330_3.6_4000x3000 | |
| Phantom 4 Pro | FC6310_8.8_4864x3684 FC6310_8.8_5472x3648 |
|
| Phantom 4 Pro V2 | FC6310S_8.8_4864x3648 FC6310S_8.8_5472x3648 |
|
| Phantom 4 RTK | FC6310R_8.8_5472x3648 | |
| Zenmuse P1 | ZenmuseP1_24.0_8192x5460 ZenmuseP1_35.0_8192x5460 | |
| Zenmuse X4S | FC6510_8.8_5472x3648 | |
| Zenmuse X5S | DJI_FC6520_15.0_5280x3956 | |
| Zenmuse X7 | DJI_FC6540_24.0_6016x4008 | |
| Parrot | ANAFI | Anafi_4.0_4608x3456 Anafi_4.0_5344x4016 |
| ANAFI Ai | ANAFIAi_5.3_4000x3000 ANAFIAi_5.3_8000x6000 |
|
| ANAFI USA | Parrot_AnafiUSA_4.0_4608x3456 | |
| senseFly | Aeria X | senseFlyAeriaX_18.5_6000x4000 |
| S.O.D.A. | S.O.D.A._10.6_5472x3648 | |
| S.O.D.A. 3D | S.O.D.A._10.6_5472x3648 | |
| S.O.D.A. Corridor | S.O.D.A._10.6_5472x3648 | |
| Sony | Alpha 7R IV | ILCE-7RM4_FE24mmF2.8G_24.0_9504x6336 |
| Cyber-shot DSC-RX1RM2 | DSC-RX1RM2_35.0_7952x5304 | |
| Cyber-shot DSC-WX220 | DSC-WX220_4.4_4896x3672 | |
| UMC-R10C | UMC-R10C_E15mmF4.5_15.0_5456x3632 UMC-R10C_E20mmF2.8_20.0_5456x3632 |
|
| Autel | Autel Evo II Pro 6K | XT705_10.6_5472x3648 |
Hi All,
It is now possible to import the image geolocation and orientation using .csv or .txt files. This is especially useful when using PPK workflows that generate text files instead of writing the values directly in the EXIF.
The file needs to include the image name, image coordinates, and the Yaw, Pitch, Roll angles. See the Image geolocation and orientation import format article for more information.
Best,