POTA Log File Cleaner
(for Windows)
POTA Log File Cleaner utility will take an ADI file from ACLog, HAMRS, WSJT-X or any other logging software, check for common errors, remove unnecessary fields and data, and produce a POTA specific ADI file to upload to the Parks on the Air website.
For "x-fer" activations it is also useful to create multiple ADI files by simply changing the park reference and clicking the "Force overwrite" checkbox to produce an ADI file for each park.
USAGE
1. Download the .zip file. Windows (or anti-virus program) will likely block the download with a warning because the file is not "signed." But you can bypass the warning to complete the download.
2. Extract the POTA ADI File Cleaner.exe file to your desktop
3. Right click the file and select "Run as administrator" from the popup menu.4.
Checks for the following common errors typically found in ADI files:
Error checking for Park number (including park number in a SIG_INFO field)
1. Is there a dash, not more than 1 dash, can’t be first, can’t be last
2. Does the prefix before the dash only contain letters and numbers
3. Does the suffix after the dash only contain digits
4. If the park number in the MY_SIG_INFO field does not match the park reference on the form a mismatch error will get thrown.
Error checking for callsigns (this includes station call sign, operator call sign, and call signs in the CALL field)
1. Compound call sign errors
2. Call sign does not contain any space or punctuation; only contains letters or digits
3. Call sign contains at least 1 digit
4. Call sign must at least be 1x1 call
5. If there is a STATION_CALLSIGN in the ADI file and it does not match the Station call sign in the form, a mismatch error will be thrown.
Error checking for Date:
1. Must be number and formatted correctly
2. Date of any QSO cannot be greater than current date
Error checking for Time_On:
1. Must be number and formatted correctly
Error Checking state/province:
1. If the park designation is US (K) or Canada (VE) then a drop box will be active and force selection of state/province
2. The MY_STATE field will only contain 2 characters if US or Canadian park.
3. If US/Canadian location does not match the MY_STATE field, a mismatch error appears.
Error checking for Band
1. Check the band matches any allowable amateur radio bands from 160M – 1MM; anything else throws an error
Error checking for Mode
1. Check the mode matches a mode listed in the ADIF spec, and also any mode listed in N3FJP’s mode list, and include C4FM because HAMRS logs it as a MODE rather than a sub-mode.
Error check for minimum fields in each record.
1. Verify each QSO record has at minimum CALL, BAND, MODE, DATE, TIME_ON, and STATION_CALLSIGN. OPTIONAL fields that may be included are OPERATOR, MY_STATE, and SIG_INFO.
NOTES:
I know that if there is an operator field then a STATION_CALLSIGN is not necessary. However, a station call sign is required on the form, so if a STATION_CALLSIGN is NOT in the ADI file it will be added automatically using the call sign from the form.
The station call sign must be identical for each QSO in a single ADI file. Operator call signs can vary, and do not have to match the station call sign, or other operator call signs because multiple operators can operate under a club or special event call sign.
If the US State or Canadian province is enabled and selected, and there is no MY_STATE field, then the MY_STATE field will be automatically written to the output. I know this is not always required, but this simplifies things.
If the park is not a US state or Canadian province and the ADI field contains a MY_STATE field, that field and data will be preserved in the output.
It is possible with some logging software (HAMRS) that the OPERATOR field can have entries, and also empty strings (blank). I don't check for this, and not sure how the POTA backend handles this either. If this is a big issue, I can add it.
If you find any errors or problems, please email WA7WJR@HOTMAIL.COM