Supported Cameras & File Formats For 360° Tour Import
Each supported camera produces its own proprietary file format. AVAG automatically converts these into a standard format during processing, meaning you don’t need to do any conversion yourself. Just select your camera from the device dropdown when creating a new dataset and upload the file in the format your camera produces.
Standard format (Mosaic X and compatible devices)
Section titled “Standard format (Mosaic X and compatible devices)”If your camera outputs a standard CSV or TXT file with the following columns, it will be recognized automatically:
ImageFileName GPSTime X Y Z Roll Pitch Heading
Example:
images-avag/office-1-scan-003.jpg 1431344936.0 -748316.08 -1053449.76 207.12 -1.08 -0.35 262.60
This format may also work for other cameras that output a standardized CSV or TXT file with the same column structure.
Camera-specific formats
Section titled “Camera-specific formats”| Camera | File format | File name / extension |
|---|---|---|
| Mosaic X | Standard CSV/TXT | .csv or .txt |
| FARO FOCUS_SCENE | Proprietary iQscene format | Must be named exactly positions.txt |
| FARO BLINK_SCENE | Same as FARO FOCUS_SCENE | Must be named exactly positions.txt |
| FARO BLINK – HQ SCENE | Same as FARO FOCUS_SCENE | Must be named exactly positions.txt |
| FARO ORBIS 1.0 – Connect | gs-vision JSON | .gs-vision |
| FARO ORBIS 1.0 – SCENE | Same as FARO FOCUS_SCENE | Must be named exactly positions.txt |
| FARO ORBIS Premium – Connect | gs-vision JSON | .gs-vision |
| FARO ORBIS Premium – SCENE | Same as FARO FOCUS_SCENE | Must be named exactly positions.txt |
| GeoSLAM – Connect | gs-vision JSON | .gs-vision |
| GeoSLAM – SCENE | Same as FARO FOCUS_SCENE | Must be named exactly positions.txt |
| Flir Ladybug 5+ (RiPROCESS) | Proprietary RiPROCESS CSV | .csv |
| CHC RS10 | OrbitPos TXT format | .txt |
Important notes
Section titled “Important notes”FARO SCENE devices – for FARO FOCUS_SCENE, FARO BLINK_SCENE, FARO BLINK HQ SCENE, FARO ORBIS 1.0 SCENE, FARO ORBIS Premium SCENE, and GeoSLAM SCENE, your metadata file must be named exactly
positions.txt. Any other filename will cause the import to fall back to the standard CSV format, which may produce incorrect results if your file doesn’t already contain the standard columns.
gs-vision devices – FARO ORBIS Connect, FARO ORBIS Premium Connect, and GeoSLAM Connect all use the gs-vision JSON format (.gs-vision). Make sure your export from the device software produces a .gs-vision file before uploading.