Reconcile two ADI logs.
Inspect each pair. Choose what survives.
- 1. Load logs
- 2. Review pairs
- 3. Export copy
Choose two exports, or try the synthetic sample to see a real review.
Resolve header conflicts
Choose the header value for the new copy. Both source headers remain in the manifest.
Same contact, different records?
A desktop log and a portable export can overlap. This bench shows the evidence before you combine a pair.
- Match the contact
- Callsign, band, mode, submode and UTC time identify possible pairs.
- Inspect the differences
- Choose A or B for each conflicting field. One-sided fields are preserved.
- Account for every record
- Only a merge reduces the count. Unreviewed pairs keep both contacts.
New to ADI files? Read the review workflow.
Load two logs to begin.
0input contacts
0merged pairs
0output contacts
Unreviewed pairs keep both contacts. The manifest records source mappings and discarded conflict values.
Before this returns to your logger
A candidate is not a duplicate verdict. Repeated contacts and different operating locations can produce similar records. Review STATION_CALLSIGN and MY_* fields before merging. What to inspect.
Import into a separate test log first. Check the output count, retained fields and station details. Save both downloads with your original exports. Use the import checklist.
Matching rules and processing limits
Cross-file contacts must have the same callsign, band, mode and submode within the selected window (0, 30, 60 or 120 seconds). No within-file deduplication, mode translation or frequency-to-band inference. Missing matching fields stay unmatched and retained.
Maximum 2,000 candidate pairs, 256 fields per source record and 1 MiB per field. Split busy logs by date if a limit is reached. Incompatible USERDEF headers are rejected. This checks structure, not every field value or award requirement. Read the matching rules.