Photo Metadata Coverage
Compare caller-supplied requirements and observations for photo metadata coverage.
Description
Photo-metadata coverage checks whether named metadata fields are recorded.
Photo-metadata coverage checks whether named metadata fields are recorded. Field presence is distinct from truthful provenance.1
Compare caller-supplied requirements and observations for photo metadata coverage.
When to use Photo Metadata Coverage
Use this tool to compare caller-supplied requirements and observations for photo metadata coverage.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Photo Metadata Coverage and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter requiredMetadataFields, presentMetadataFields using the field table and calculation rules, then run the tool.
- Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| requiredMetadataFields | Required metadata fields | list of string | Required |
| presentMetadataFields | Present metadata fields | list of string | Required |
Supply required field names and observed field names. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.
coverage%=100×matchedUnique/requiredUnique Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| coveragePercent | Coverage (%) | number; minimum: 0; maximum: 100 |
| matched | Matched items | list of string |
| missing | Missing items | list of string |
| unexpected | Unexpected items | list of string |
{
"input": {
"requiredMetadataFields": [
"creator",
"capture date",
"rights holder",
"license"
],
"presentMetadataFields": [
"creator",
"capture date",
"rights holder"
]
},
"output": {
"coveragePercent": 75,
"matched": [
"creator",
"capture date",
"rights holder"
],
"missing": [
"license"
],
"unexpected": []
}
}Limitations and assumptions
No image or EXIF data is read and no metadata values, edits or source identity are authenticated.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Video Provenance Check: Compare caller-supplied expected and observed records for video provenance check. For a complementary task, use C2PA Provenance Audit: Audit required C2PA provenance assertions.
References
-
Photo Metadata Coverage — tool.io
Similar or alternative tools
- Video Provenance Check
Compare caller-supplied expected and observed records for video provenance check.
- C2PA Provenance Audit
Audit required C2PA provenance assertions.