-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Return meshes from split merge #1594
Comments
@pierotofy -- the links you reference in the NodeODM issue, would that be something similar to how multispectral datasets are handled with symlinks or something as simple as what we see in |
Symlinks are not available on Windows (you need to use hardlinks, which only work for files, not directories). Using links is the proper way to implement this imo. Naive copies are both slow and explode disk space. Starting from Line 149 in bf824d3
|
Per https://community.opendronemap.org/t/offer-a-single-textured-mesh-as-output-in-split-merge-processes/14608 , long term, returning a mesh from split merge would be beneficial. In the interim, returning the meshes that are produced may be an acceptable alternative.
Sibling issue here:
OpenDroneMap/NodeODM#199
The text was updated successfully, but these errors were encountered: