This is because he was doing a double activation that day…putting two parks on the air at the same time. Note that the QSO with N7OOS was entered twice, with two different park numbers. However, there are six QSOs shown that were Park-to-Park. Most of these are blank because the other station was not in a park. The eleventh column is SIG_INFO, which is the POTA designator for the other station. The 7th column is MY_SIG_INFO, which is the POTA designator (K-8295) for the park I was activating. The figure below shows a POTA log using ADIFMaster. My understanding is that this works only for the simple case of two activators, each operating from only one park. The POTA system will try to identify Park-to-Park (P2P) radio contacts in the file, by comparing activator logs. For example, the file name K0NR-K-4404-20211017.adi indicates the station callsign (K0NR), operating from park K-4404 on. If you get these fields set correctly in the ADIF file, the SOTA database will log the activation and the S2S contacts correctly.įor simple POTA activations, you just need to get the QSO information correct and the file name indicates the park you were operating from. However, N0TZW and N3ALT were on W0C/PR-031 that day resulting in a pair of S2S contacts. Most of the rows are blank, because the other station was not on a summit. The 9th column is SOTA_REF, which is the SOTA reference of the other station’s summit, if any.

In this case, it was W0C/SP-084 and is the same for all of the QSOs. The 6th column is MY_SOTA_REF, which is the SOTA reference for the summit I was activating. The figure below shows a recent SOTA log, in ADIF format, displayed by ADIFMaster. The SOTA database supports uploading ADIF files, including support for Summit-to-Summit (S2S) contacts. Then, if the SOTA summit is inside a POTA-designated park, we may try to do both simultaneously. Our combination SOTA + POTA activations usually start out as a SOTA activation.

The complete documentation for ADIF can be found here: SOTA Logs

Also, an ADIF file can be imported into other logging programs and Logbook of The World. (Let me know if you do.) The ADIF file format can handle this and is the way to go for such a log file. I am not aware of a logging program that will handle both simultaneously. Lately, I’ve been trying to figure out how to do one log file for both SOTA and POTA. My apologies in advance if I get any of this wrong. Some of this is not well-documented…at least I haven’t found it…so I am sharing what I’ve figured out. I continue to learn about the file formats and various tricks for generating the logs. I previously wrote about some of the tools I use for managing SOTA and POTA logs.

Best ham radio logging software