Hi Benni,
Here an example for a SOTA adif
<QSO_DATE:8>20220619 <TIME_ON:6>090222 <TIME_OFF:6>090222 <CALL:8>SV4SWQ/P
<FREQ:6>14.278 <BAND:3>20M <MODE:3>SSB <QTH:9>Sv/Mc-028 <COMMENT:42>QTH = JN67pj, OE/SB-420, 47.3818, 13.2727. <OPERATOR:6>OE5JFE <STATION_CALLSIGN:8>OE5JFE/P
<RST_SENT:2>59 <RST_RCVD:2>59 <SOTA_REF:9>SV/MC-028 <MY_SOTA_REF:9>OE/SB-420 <EOR>
Those are the SOTA specific ones. Everything else is “standard” QSO stuff
<SOTA_REF:9>SV/MC-028
<MY_SOTA_REF:9>OE/SB-420
You don’t need to seperate that.
As activator or chaser uploads ADIF to the SOTA database the system will figure that out depending on the used SOTA_REF and MY_SOTA_REF.
If there is a
MY_SOTA_REF = Activation
If there is
SOTA_REF = Chase
if both = Summit 2 Summit
For csv it is not that trivial I guess as there are separate upload functions. So make a option on “starting” the app if one activates or chases. Because it can only be the one or other.
Btw. if you include the SOTA spots via the SOTA API to have spots available like in VK-Port-A-Log and transfer the info to the entry fields I am sure you will have a lot of new users.
Swagger UI
73 Joe