I’m working on a pipeline that uses ODM’s split-merge feature for large photo sets. Point cloud and DSM merge correctly, but the textured meshes remain separate — split-merge produces one mesh per submodel, and there’s no way to merge a new area’s mesh into an existing base model either.
This seems related to the split-merge mesh limitation discussed here: Feature request: Return meshes from split merge · Issue #199 · OpenDroneMap/NodeODM · GitHub and Offer a single textured mesh as output in split-merge processes
Has there been any progress on textured mesh merging (from split-merge specifically, or more generally from separate runs), or is a manual/external tool (e.g. MeshLab) still the recommended approach? Thanks!