Reduce processing overhead for large amount of imagery data
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- cli, performance
Research direction
Start by tracing the command-line image-processing and upload flow to find where geotags are read and whether prior processing is recorded. Review the linked forum discussion for the context around missing status tracking. Done means previously uploaded or processed images are identified and skipped without losing correct processing for new imagery.
Written by the indexing model from the issue text.
Description
Although processing images (reading geotags) are fast, for large amount of data it's still slow. We should avoid processing the same images that has been uploaded or processed. See https://forum.mapillary.com/t/mapillary-tools-0-8-no-status-kept/6197/16
- Dominant language
- Python
- Stars
- 315
- Forks
- 145
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 2
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.
More from mapillary/mapillary_tools
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
mapillary/mapillary_tools#827 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
mapillary/mapillary_tools#819 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mapillary/mapillary_tools#783 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
mapillary/mapillary_tools#748 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
mapillary/mapillary_tools#747 · 9 comments ·
All issues in mapillary/mapillary_tools
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100