Potential Bug with Metashape's Gaussian Export Script and Nerfstudio's expectations

[Jordan-Pierce]

Describe the bug Hi, I could be wrong about this, and hope if anyone knows the answer I can quickly close this bug report.

I'm using Metashape's script to export data from a photogrammetry scene to be used in place of COLMAP for Nerfstudio's new Gaussian Splatting. COLMAP is hard to install...

Their script exports both a copy of the original images (useful for the cameras.xml file), and the images.bin file to be used in Nerfstudio's COLMAP data parser. However, they write the original name of the image (cam.label) to the images.bin file, whereas the Nerfstudio's Metashape data processor creates images of different scales with the convention of "frame_0000N.jpg", and a transform.json using the same naming convention.

My question is, would this not create an issue? Or is there some code in Nerfstudio that is agnostic to this difference in naming convention and simply deals with this situation? If it is an issue, I'm happy to create a PR for the Metashape script, but wanted to confirm before doing so. Thanks.

Additional context Using Metashape 2.0.1, but the current version of the script (2.0.3) is the same.