Identify a file by its fingerprint
find_by_fingerprintRead-onlyIdempotent
Identify the scene a file matches by sending its MD5, OSHASH, or PHASH fingerprints to all configured catalogues. Send all hashes together to resolve matches in one request.
Instructions
Ask every configured catalogue which scene a file corresponds to, from the hashes held for it. Pass every hash of one file together: one request settles what three would ask separately. MD5 and OSHASH match the same file; PHASH matches images that resemble each other, which is no evidence that two files are the same.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sources | No | Narrow to named catalogues. Every configured catalogue is asked by default. | |
| fingerprints | Yes | Every fingerprint held for one file. A file carries one hash per algorithm, so a longer list is an inventory rather than a question. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asked | Yes | ||
| notes | Yes | ||
| matches | Yes | ||
| per_source | Yes | ||
| match_count | Yes | Matches returned: one per scene per fingerprint it carries. | |
| unattributed | Yes | Scenes a catalogue answered with while returning none of the fingerprints asked for. Which hash reached them is unknown, which is kept apart from a catalogue that found nothing. | |
| scenes_matched | Yes | Distinct scenes behind those matches. |