Simplify bulk modification and backup/restore for advanced users by enabling JSON download/upload of triggers.
Note: in theory users can already do this by reverse-engineering the https://hamalert.org/ajax/trigger_update endpoint, but it’s not documented anywhere and subject to change.
Yes, this! I’ve built a DB of upcoming SES/DXpeditions that I use to create the ‘Wanted Callsigns’ files for JAlert. I’d like to extend that to include adding those same triggers to HamAlert. Frankly, it could work the other way around by using the HamAlert web interface to build a list for JAlert.
73 - Tim - KC1RET
I have created a script in PowerShell to create triggers for all missing DXCCs per band. Maybe this is useful for others so I make it available here:
How to use it:
Put all provided files to a folder, e.g. “c:\temp\hamalert”.
Export an ADIF file to this location.
Login at hamalert.org and open the developer tools from your browser.
Locate the PHP Session cookie for hamalert.org and copy the value into your clipboard.
Open the powershell script with an editor and fill in all needed information, as described in the script.
Run the script once to test, all is working fine without errors.
If that is the case, remove the comment at the end of the script to allow the script, creating the triggers.
Fixed an issue with DXCC list today.
Previously created triggers might not work due to a type issue, since they were passed as string but the system requires integer. This should be fixed now.
An import option for triggers. Ideally, an export option as well.
As a text file, CSV, or similar format. The interface should be documented so that third-party developers (like me) can write supporting tools that simplify the process of entering (and then importing) one or more triggers.
Brief background:
I’ve cobbled together some software that retrieves a PDF listing ongoing DXpeditions, parses it, and writes the call signs into a file, separated by commas. You can then copy the contents of that file and paste them into a trigger. However, this is manual work and could easily be handled via an import feature. If all the other trigger parameters (bands, modes, etc.) could also be included in the file, there would be almost no work involved. Just click “Import” and you’re done. I could modify my software so that the user’s preferred modes, bands, and other parameters are set once and then saved as defaults, so you don’t have to re-enter them for every trigger every time.