Currently, as colmap export rotation is different to the las or ply export (by 90 around x) it’s necessary to add +90 rotation on X. Which is fine, but this rotation added in the export carry’s over to different export types. So if I then go to export colmap again, it also has 90 on x.
it’s really useful that the rotation is remembered , but can you make it so that it’s only remembered on each export type?
So for example, if desired you could set colmap to export with -90 x always, and then 0 on all other exports. Or whatever you want to do.
Hi, no changes were made in RS 2.1 to the Colmap export transform. There should be no need to add an additional rotation. At least we were not able to reproduce the issue. If you can provide more info, exact repro steps, we’ll look into it.
I performed a quick test from RS to Postshot, comparing Colmap vs. Ply with Int/Ext params csv, and the transform was the same.
However, I can confirm that the rotation is remembered across multiple exports and agree it might not be ideal. Transform is also remembered when importing Colmap scenes. We’ll look into that.
This is more about the rotation setting being carried between export types. But as you asked, if you export using colmap format with zero for all transforms, then export the pointcloud (sparse or dense) with zero, the colmap points3d.txt has a 90 degree rotation around x compared to the sparse ply.
Whilst this isn’t necessarily an issue, it really is a bit suboptimal that the rotation setting added to the sparse cloud export carries over back to all other exports. It’s really easy to forget to set it back to zero. But both problems could be resolved if the rotation and other transforms are only retained on same export types ..