This guide explains how to export the camera parameters from 3DF Zephyr so a tileset can be uploaded into Twinsity.
3DF Zephyr support is in Beta. A project exported with these settings has been through the whole flow and comes out correct. If something does not behave as described here, tell us.
The camera export, and the one tileset setting that decides how well your model performs in Twinsity. The processing steps that come before them are not covered here, so follow 3DF Zephyr's own documentation for those and use the requirements below as the target.
| File type | Format | Notes |
| 3D tileset | Zipped tileset | Cesium 3D Tiles: a tileset.json and the tile files beside it |
| Camera parameters | A folder | Two .txt files, not one. See below |
| Original images | .jpg or .png |
All images used in the reconstruction |
All three are required for a successful upload.
3DF Zephyr gives you two camera files, so you select a folder
3DF Zephyr writes externals.txt and internals.txt, one holding where each image was taken and the other holding the lens values. Twinsity needs both, so the upload wizard asks for the folder that contains them rather than a single file. There is no one file to select.
3DF Zephyr can also write an internals.xml from the same dialog. Leave that option unchecked. If you export it anyway, Twinsity ignores it and reads only the two .txt files.
externals.txt and internals.txt.| Setting | Value |
| Reference images | Distorted |
| Change Reference System | ☑ Checked, set to WGS 84 (geocentric) |
| Export internal and external parameters (TXT) | ☑ Checked |
| Rotation axis | X Y Z |
| Every other export option | ☐ Unchecked |
Reference images is the first option in the dialog. Distorted means the exported lens values describe your original images, which are the ones you upload. Anything else describes images that were corrected on the way out, and Twinsity does not have those.
Change Reference System, set to WGS 84 (geocentric), puts your cameras in the coordinate system Twinsity expects. Without it they come out in the project's own coordinates and will not line up with your model.
Rotation axis is X Y Z by default. Leave it there.
That destination folder is what you hand to the upload wizard.
Use Export LoD Mesh and set the Format to gltf.
The export gives you a tileset.json with the tile files beside it. Zip the whole thing, keeping the folder structure as it is.
Set the maximum texture size to 2048.
3DF Zephyr can write textures up to 32768 x 32768. A model built from those asks for more graphics memory than a browser will give it, and the 3D view stalls as you move around, worse the closer you look. 2048 keeps enough texture detail for inspection work while staying inside what a browser can hold.
If a model you have already uploaded moves sluggishly, re-exporting the tileset at 2048 is the fix. Your images and camera parameters do not need re-exporting with it.
3DF Zephyr lists each image by its file name alone, without the folder it sits in. Two images with the same file name in different folders cannot be told apart, and both are reported as unmatched at the Setup step.
If your capture produces repeated file names, rename them before you process in 3DF Zephyr, so the export and your image folder agree. See Understanding how your images are matched to the model.
At the Setup step, under Camera Metadata, the picker reads Choose cameras folder or drag here. Select the folder holding the two .txt files.
Once the folder and your images are both selected, the wizard reports Camera coordinate system: Georeferenced with EPSG:4978 beneath it. If it reports anything else, Change Reference System was not set to WGS 84 (geocentric) on export. See Troubleshooting a coordinate system mismatch.
tileset.json and the tile files beside it.externals.txt and internals.txt.Once your files are ready, continue with Preparing to upload a project.