Potential Feature for Discussion- ADIF import for missing DXCCs

[chrisdebian]

Bjoern @YetAnotherHam has been doing some initial work addressing the ability to import ADIF files to augment existing information, and potentially addressing gaps.

Bjoern, please can you:

1. Give a brief summary of the problem you're trying to solve.
2. Give a brief summary of the solution you've been working on, no matter how nascent/ immature.
3. State how you see this fitting into the HamAlert approach.

With this information, @manuelkasper can then see if this approach compliments his existing work, and we can work out next steps. We would then create an issue in the relevant HamAlert repository.

73
Chris

[YetAnotherHam]

I am interested in getting alerts for those DXCCs, which I have not worked, yet.
Since manual setup and maintaining these triggers would take a lot of time and lead to errors,
it would be great to have a feature to import an ADIF file and create triggers for missing DXCCs.
So I wrote a PowerShell script which is doing this job.
The usage of the script is not very user friendly at the moment and using a JSON endpoint which might change during the further development of HamAlert. And it is still a "quick and dirty" solution which can be improved.

It would be great to either:

• make HamAlert capable to import ADIF files or
• have an "official" and documented API endpoint

to create triggers (semi)-automated.