This handful of scripts and simple applications grew out of my need for a simple way to convert ADIF formatted log files to comma separated files, suitable for upload to the Summits on the Air (SOTA) database. I make no claims to being a programmer, but I can usually borrow and butcher someone else's code and get the job done.
It all started with a command line run php script, with the ADIF parsing logic borrowed from code written by Ansgar, DG2KBC. Running a command line script was fine for me, but I though it would be nice if it could be even easier. That led me to find Platypus, which is an application wrapper for scripts running on Macs. It was very easy to turn my script into a small drag and drop application. That worked great until the SOTA v2 format was published, which provided support for Summit to Summit (S2S) contacts in the log. I then needed to throw up a prompt to ask how to process the log file - as an activator's or a chaser/S2S log? I found another handy tool called CocoaDialog that provides nice OS styled dialog boxes for scripting languages to handle additional input.
Before ADIF ver. 3.0.4 was released there was no supported way to log SOTA information in logging software. To facilitate processing the SOTA information, I came up with a standardized way of logging that information. Just for your information, I keep my activation logs in a separate file from my chaser/general log file. Partly out of habit, but also because I couldn't come up with a way to reconcile both types of contacts in a single log. If you have a better method, I would love to hear it!
Please let me know if you have any questions or problems.
73 de pat, KI4SVM
All of my apps (except those that support the new SOTA ADIF fields) are expecting the SOTA information in my standardized format for SOTA contacts. All of the SOTA related information should be input into the comments or notes field that is used your logging software. You are free to modify the underlying script if you wish, to adapt it to your own logging practices.
Here are two examples from a chaser log file:
SOTA W4C/US-001 Thanks for the QSO!
SOTA W4G/NG-031
The script will parse the first SOTA reference as the summit you made contact with, and add anything after the first reference to the comments field for the SOTA database.
Activator logs follow the same convention (just reversed). For example:
SOTA W4C/US-002 Thanks for the S2S from W4Z/ZZ-999
SOTA W4C/US-002
The script will parse the first SOTA reference as 'your summit', and if there is a second summit reference, as 'their summit'. Anything after the first reference will be added to the comments field for the SOTA database.
MacLoggerDX ver. 5.49 Beta 14 or higher now supports the two new SOTA fields defined in the ADIF ver. 3.0.4 standards. This makes processing logs much easier and frees up the comments field for actual comments.
To use, drag an .adi file exported from MLDX onto the app's icon. The log file can contain SOTA chaser contacts, activator contacts and also non-SOTA contacts, which will be ignored in processing. A comma separated values formatted file will be generated as needed, for easy upload to the SOTA database. There is no interaction with this app, other than dragging a file onto it. It will silently create your file in the same location and name as the input file, but with a .csv file extension added.
 MLDX->SOTA (Single CSV File Output)
0.95
|
|
Drag and drop app for processing log files from MacLoggerDX ver. 5.49 Beta 14 or higher for upload to the Summits on the Air database. This app will only work when the new SOTA database fields are used in logging your information. Modified to only output a single comma separated file, which can be uploaded as both an activator's log as well as a chaser's log as needed. Changelog
|
|
 2015-01-15 00:00:00  MacIntosh  502.79 KB  1,419 |
Download |
This app is for older versions of MacLoggerDX which do not support the two new SOTA fields. This app requires the comments field to use My Standardized Format for SOTA Data for your SOTA contacts.
To use, drag an .adi file exported from MLDX onto the app's icon. If you are processing a chaser file, it may contain SOTA contacts, but must not contain activator contacts. If you are processing an activator file, if must not contain any chaser contacts. Either file may contain non-SOTA contacts. Contacts without SOTA information in the comments field will be ignored during processing.
The app will ask you whether it is a chaser or an activator file. A comma separated values formatted file will be generated as needed, for easy upload to the SOTA database. It will silently create your file in the same location and name as the input file, but with a .csv file extension added. An activator's file which contains Summit to Summit contacts can also be upload as a chaser file for S2S credit.
| MacLoggerDX to SOTA
0.94
|
|
Drag and drop app for processing log files from MacLoggerDX for upload to the Summits on the Air database. This app requires your comments field to use my standard format for logging your SOTA contacts. If you process an activation log and it contains Summit to Summit contacts, you can also upload the output file as a chaser log to get credit for your S2Ss. Changelog
|
|
| 2015-01-15 00:00:00 MacIntosh 785.7 KB 1,359 |
Download |
This app is for processing log files from Aether for upload to the SOTA database. This app requires one line of your notes field to use My Standardized Format for SOTA Data for your SOTA contacts.
To use, drag an .adi file exported from Aether onto the app's icon. If you are processing a chaser file, it may contain SOTA contacts, but must not contain activator contacts. If you are processing an activator file, if must not contain any chaser contacts. Either file may contain non-SOTA contacts. Contacts without SOTA information in the comments field will be ignored during processing.
The app will prompt you whether it is a chaser or an activator file and ask for the callsign you were using when the contacts were made. A comma separated values formatted file will be generated as needed, for easy upload to the SOTA database. It will silently create your file in the same location and name as the input file, but with a .csv file extension added. An activator's file which contains Summit to Summit contacts can also be upload as a chaser file for S2S credit.
| Aether->SOTA
0.94
|
|
Drag and drop app for processing log files from Aether log for upload to the Summits on the Air database. This app requires that one line of your notes field to use my standard format for logging your SOTA contacts. If you process an activation log and it contains Summit to Summit contacts, you can also upload the output file as a chaser log to get credit for your S2Ss. Changelog
|
|
| 2015-01-15 00:00:00 MacIntosh 783.87 KB 1,446 |
Download |
This app is for processing log files from RUMlog for upload to the SOTA database. This app requires your notes field to use My Standardized Format for SOTA Data for your SOTA contacts.
To use, drag an .adif file exported from RUMlog onto the app's icon. If you are processing a chaser file, it may contain SOTA contacts, but must not contain activator contacts. If you are processing an activator file, if must not contain any chaser contacts. Either file may contain non-SOTA contacts. Contacts without SOTA information in the comments field will be ignored during processing.
The app will prompt you whether it is a chaser or an activator file. A comma separated values formatted file will be generated as needed, for easy upload to the SOTA database. It will silently create your file in the same location and name as the input file, but with a .csv file extension added. An activator's file which contains Summit to Summit contacts can also be upload as a chaser file for S2S credit.
| RUMlog->SOTA
0.94
|
|
Drag and drop app for processing log files from RUMlog for upload to the Summits on the Air database. This app requires your note field to use my standard format for logging your SOTA contacts. If you process an activation log and it contains Summit to Summit contacts, you can also upload the output file as a chaser log to get credit for your S2Ss. Changelog
|
|
| 2015-01-15 00:00:00 MacIntosh 784.52 KB 1,481 |
Download |
Here are two PHP scripts which may be helpful in developing your own solution for processing ADIF files containing SOTA contacts. These will not work out of the box for you, but should be easy to adapt to your logging application's quirks. One script is the basis for my app for processing log data which contains the new ADIF defined SOTA fields and the other is for logs utilizing my standard data format for SOTA contacts.
| Sample PHP script using ADIF SOTA fields
0.94
|
|
Simple PHP script, suitable for adaptation to your logging needs and setup. This script is expecting the SOTA contact information to be entered into the SOTA database fields as defined in the ADIF v.3.04 specifications. Changelog
|
|
| 2015-01-15 00:00:00 2.58 KB 1,435 |
Download |
| Sample PHP script using my standard data format
0.94
|
|
Simple PHP script, suitable for adaptation to your logging needs and setup. This script is expecting the SOTA contact information to be entered using my standard data format. Changelog
|
|
| 2015-01-15 00:00:00 2.72 KB 1,321 |
Download |