The Role of TRACK and POINTS2D in OpenMVS

[Ioksiong]

Hi! I obtained a COLMAP-like format from another project, where cameras.txt is missing the POINTS2D attribute, and points3D.txt is missing the TRACK attribute. I intend to use this data as input for OpenMVS to extract the mesh. However, I noticed that the InterfaceCOLMAP.cpp code explicitly requires the POINTS2D and TRACK attributes. I would like to know if there is any method to generate POINTS2D and TRACK based on the known 3D points and camera poses, or if OpenMVS can run successfully without using the POINTS2D and TRACK attributes.

[cdcseacave]

If you want to use DensifyPointCloud to estimate a dense point cloud starting from images with camera poses, it is possible to ignore the tracks, though those are helpful in accurately selecting the neighbor views during densification.

[Ioksiong]

If you want to use DensifyPointCloud to estimate a dense point cloud starting from images with camera poses, it is possible to ignore the tracks, though those are helpful in accurately selecting the neighbor views during densification.

Thank you for your reply! So do I need to modify InterfaceCOLMAP.cpp and then recompile OpenMVS now? I'm not sure if the missing track will cause the subsequent ReconstructMesh and RefineMesh commands to fail.

[cdcseacave]

I repeat: DensifyPointCloud will run only with images and camera poses