OpenDroneMap / OpenDroneMap/ODM
Reports for Split/Merge Submodels
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 1.3k
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 4
Description
Can we get Reports for Split/Merge Submodels
Thanks for the add of report view directly in WebODM!
I would think this would be relitatively easy add.
Just run the report after the submodel finishes
Also a second ask would be final Report for Merge
not sure if this would be hard... I am assuming the report subroutine can run on any data set
Thanks for all you do for us!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing WebODM report view and the processing paths where split or merge submodels finish. Determine how reports are currently generated for a dataset, then define what completion means for submodel reports and the final merge report; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100