What happens to images when they are 'unmatched' but not rejected?

[spwoodcock]

Good example of a project:

https://drone.hotosm.org/projects/settlement-profiling-drone-mapping-phase-1-a-collaboration-by-sdi-kenya-hot-esa-hub-and-kenya-flying-labs-260320260657

Here we have multiple 'unmatched' images, but they aren't explicitly rejected images, so are still present in the DB records, and presumably in the S3 staging area too. Two questions:

1. Ideally the user would have a way to manually match the 'unmatched' photos. I.e. it's just outside of task 1, so 'Assign to xxx' where the user selects a task area and we place it within the imagery for that task.
2. If the imagery is truly unmatched and not belonging in any task area, i.e. it's a wasted photo. We should have a way to delete / reject it.

Currently, what we have is:

• The 'unmatched' image records are in the db, so they displayed on the map in yellow.
• Presumably the imagery still exists in the S3 staging area user-uploads.
• But for now, there is no way to do anything with this unmatched imagery - it just shows on the map and is a bit useless.
• During the classification, we could view these images in a separate section for photos with 'Issues'. Once the classification is done, and the user goes to the Verify Imagery dialog, we can no longer see the section of photos with 'Issues'.

[linear]

TECH-1112

[spwoodcock]

Also, is the matched imagery in user-uploads cleaned up after it's matched and copied to the task dir?
It doesn't really look so to me.