When exporting a bundle.out registration, no *.rcinfo companion file is exported from RC. These rcinfo are exported for meshes export and multiple other RC exports, and are useful to retrieve export parameters, like the global-shift applied when exporting the bundler with Shifted Project Output setting, EPSG CRS etc. Not sure if other registration export formats do export this companion rcinfo file, but it would be great to add it to at leasst bundle.out export!
Hi,
I suppose this is because the bundle.out is only the registration export. There is no model where the rcinfo file is used for the imported it back into RealityCapture.
Also, there is no option to set shifted project output, as this settings is only for mesh/point cloud export.
Thanks for the feedback.
Actually if the component is indeed georeferenced, there is the option to export the registration (colmap, bundle.out or anything) as Shifted Project Output or Project Output. However, due to floating point precision errors on import in most libs and softwares handling these registration formats, Shifted Project output is preferred, although requiring the shift matrix to map coordinates from shifted CRS to real georeferenced one.
It would be useful still to have a way to get on registration exports the matrix-transform which would bring back dataset exported as shifted-project-output to real world coordinates. There is currently no way in RC (GUI or CLi) to get the matrix-transform between component scene coordinate system and georeferenced project coordinate system CRS, or shifted-project-output for registration export to standard-project-output. The only way is to parse this matrix in the rcinfo on mesh exports. Exporting the exact same info for registration exports would be very valuable.
Thanks again for your time,
OK, you’re right. I had to miss it somehow. I am sorry for that.
The mentioned feature request was created in between.
1 Like
Thanks for adding the feature request to the list!