SOTA Import: References messed up

[DK9JC]

Problem: ADIF import messes up <MY_SOTA_REF:9> [Summit where I am on] with <SOTA_REF:9> [Summit the other guy is on]

I imported my latest SOTA log (ADIF from VK port-a-log) into 2.8.0.0 have now the following problems:

2020-07-05_12h28_39.png (34.35 KiB) Viewed 2559 times

2020-07-05_12h28_48.png (43.38 KiB) Viewed 2559 times

2020-07-05_12h29_00.png (47.2 KiB) Viewed 2559 times

It happens both with "Apply quality check corrections" on and off.

<MY_SOTA_REF:9>DM/RP-179 works okay on all entries.
My 2 worked "summit-to-summits" are also OK:
<SOTA_REF:9>SP/BZ-041

But somehow some entries have the <MY_SOTA_REF:9>DM/RP-179 in <SOTA_REF:9> after the import.
I wonder is there is some matching logic involved.

ADIF log seems to be OK:

www.vk3zpf.com
<ADIF_VER:5>3.0.4
<PROGRAMID:22>VK3ZPF - VK port-a-log
<PROGRAMVERSION:11>Gisborne_02
<EOH>
<QSO_DATE:8>20200704 <TIME_ON:6>153758 <TIME_OFF:6>153758<CALL:6>[CALL]
<FREQ:5>7.137 <BAND:3>40M <MODE:3>SSB
<COMMENT:15>QTH = DM/RP-179
<RST_SENT:2>53 <RST_RCVD:2>31
<APP_EQF_TRACK:6>FT-891 <OPERATOR:7>DK9JC/P
<MY_RIG:6>FT-891
<MY_ANTENNA:11>EFHW FT-140
<STATION_CALLSIGN:7>DK9JC/P
<MY_SOTA_REF:9>DM/RP-179
<QSLMSG:56>SOTA DM/RP-179 JN39tv
<EOR>

[DK9JC]

Another problem:

I now tried to delete those entries by hand but it will not let me do this:

After I click on "SOTA@DM/RP-179" and the the red "-" Remove selected reference it deletes in the white box but the upper one with the state stays. After saving and reload the "SOTA@DM/RP-179" is still there.

[G4POP]

Thank you for sending me your Port-a-log ADIF file and I can see why on import the other station is being allocated your SOTA ref.

You may have noticed during import that Log4OM scans for award references automatically.

Untitled.jpg (88.44 KiB) Viewed 2542 times

It does this by scanning the comments field and notes field in addition to the normal field references like DXCC, County, State etc.

Because you have entered YOUR SOTA Ref in the Port-a-log comments field Log4OM is assuming that this is the other stations reference and adding it to the SOTA_REF field.

We do this because many programs and users store award refs like IOTA, SOTA and WWFF etc in that field because not many other programs specifically provide dedicated support for these awards.

Removing that information from Port-a-log, if that is possible, will avoid this happening in the future.

However the fact that you cant delete the entry is a puzzle which I will check and get back to you about.

[G4POP]

Having removed YOUR SOTA refs from the comments field of your Port-a-log ADIF and importing it into an empty database the results are correct

Chaser.jpg (139.41 KiB) Viewed 2540 times

ASctivate.jpg (146.34 KiB) Viewed 2540 times

Capture.JPG (143.41 KiB) Viewed 2540 times

[DK9JC]

Thank you for sending me your Port-a-log ADIF file and I can see why on import the other station is being allocated your SOTA ref.

I thank you once agn for you fast and good support.

I wonder is there is some matching logic involved.

You may have noticed during import that Log4OM scans for award references automatically.

That was exactly what I assumed after I saw this strange behaviour.

Removing that information from Port-a-log, if that is possible, will avoid this happening in the future.

As often - if you know why something happens you can work with it. I have set VK port-a-log so, that the comments are left blank and I do not use my activator reference anywhere als as in <MY_SOTA_REF:9>.

Screenshot_20200705-192347.png (70.4 KiB) Viewed 2535 times

Having removed YOUR SOTA refs from the comments field of your Port-a-log ADIF and importing it into an empty database the results are correct

I did the same now and I can confirm that the automatic award logic is the reason.

[G4POP]

Another satisfied customer