Skip to content

Was the removal of GLOMAP's post-processing intentional? #4253

@VladyslavZavadskyi

Description

@VladyslavZavadskyi

Is your feature request related to a problem? Please describe.
Yes. Since GLOMAP is global, it puts everything into one map. This may hurt performance of some downstream applications (such as Gaussian Splatting), since those disconnected maps do not share reference frame and are forced into one coordinate system. I can tell GLOMAP team recognized this as an issue, because they've added post-processing step which prunes weakly-connected components. Removing it is a major downgrade.

Describe the solution you'd like
Either add it to COLMAP or point me in the direction of how it can be done with existing tools.

Describe alternatives you've considered
I thought maybe it was removed because analogous solution exists as a part of the COLMAP toolbox, but alas, I wasn't able to find anything like it. I also have a home-made python networkx solution which I implemented before I found it existed in GLOMAP (or before GLOMAP team added it, whichever came first), but being in python - it's slower. It's pretty trivial to add into your codebase, but I don't want the pain of maintaining a fork. I could do a pull-request if you don't mind.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions