Importing of SOTA chasing ADIF QSOs should be recognized as SOTA chasing QSOs

Feature Requests
1

When importing an ADIF file with QSOs from chasing SOTA, the WRL fields theirActivities, theirParks, and theirParkData should be populated to reflect the SOTA reference of the activator that I chased.

WRL should recognize ADIF QSO records that are SOTA chasing QSOs and import them accordingly.

And a little mountain symbol should show in the Tags column of the logbook QSO listing.

If (1) the ADIF record contains their SOTA_REF data,

or (2) if the record contains SIG (=SOTA) and “SIG_REF” with a SOTA reference,

or (3) if the record contains all three fields (SOTA_REF, SIG (=SOTA) and SIG_REF),

then the WRL import should properly populate the gheirActivities, theirParks, and theirParkData fields in WRL.

I created a test ADIF with the three QSOs to test the three cases (1,2,3) as listed above, and imported it into a log book "SOTA Chaser WRL test ADIF import’. You can see the raw ADIF data as WRL smartly retains it in the contactString field.

WRL didn’t recognize any of the SOTA chasing QSOs in the ADIF as being SOTA chasing QSOs

(I wonder if the same issue exists with POTA_REF, etc. hmmm.)

The template for the logbook shouldn’t matter. I have a WRL master station log book for all the activtity from my home, and sometimes I’m just ragchewing, sometimes I’m hunting/chasing SOTA or POTA.

If I’m hunting/chasing on FT8, it’s by far faster and easier for me to take the ADIF from wsjtx, add their pota and sota references, and upload to WRL into my master station log book.

Thanks! and 73,

Tony.

3 Likes
2

@KA3ZPH Hey Tony Good Morning,

So there are a couple of things going on here. There is an issue with those icons not showing (and the ‘Their Summit’ field not getting added properly) if you import an adif into a logbook that has been setup with the SOTA activity (i’ve got the team looking into this).

However with that said, those Icons only show up if the logbook has the pota or sota (or iota, wwff, etc) activity added.

The second issue is that in the adif that you imported, its not setup correctly. There is no “MY_SIG”, “MY_SIG_INFO” or “MY_SOTA_REF” fields added there is only the 'SIG", “SIG_INFO” , and “SOTA_REF” fields added which are used when a Summit 2 Summit has taken place.

Here is a screen recording explaining this a bit more in detail:

Like I said i’ve created a ticket for this and have the team looking into this.

Thanks & 73
Brad K4AZE

2 Likes
3

Hi Brad, thank you so much for the fast reply! You guys are the best.

Appreciate you all looking at why the “their summit” fields aren’t getting populated. I think that will address my enhancement request.

Two thoughts:

  1. Regarding the first issue you mentioned, I have a WRL log book for all the QSOs at my home station. From my home I do different activities, so I switch the template back and forth based on what I’m doing. Often it’s just the WRL Default template. So the whole logbook is not setup as a SOTA or POTA activity; just some of the QSOs are me chasing/hunting activators.
  2. Regarding the second issue you mentioned, I’m at home, in my house, chasing SOTA and hunting POTA. So there are no MY_SIG, MY_SOTA_REF, MY_SIG_INFO fields. I’m not in a park and I’m not on a summit.

You might ask why I need to import ADIFs with hunting/chasing SOTA and POTA, why don’t I just use WRL to log the QSOs and skip the import? It’s because I’m running WSJTX (FT8, etc.) and WSJTX provides me the ADIF file. It’s fastest and easiest for me to add their SOTA ref to the WSJTX ADIF and import it to WRL.

Thanks and 73,

Tony

1 Like
4

@KA3ZPH So those icons are currently only going to show in an activator template and not in a hunter template. Your use case is pretty much the same as I operate. I just hunt, and because of that I use the 'WRL POTA/SOTA/IOTA/WWFF Hunter Template I created which has all the fields I need to be able to add whatever i’m hunting.

For WSJTX you can simply just use the WRL Integrations app + WRL Web App and stream your WSTJX contacts straight into your WRL logbook or use the Desktop app (which has built in cat control and UDP streaming) like I use to stream my FT8/FT4, etc contacts into my logbook.

Additionally, since you have a QRZ subscription you can also do what I do and have QRZ auto export enabled so whenever you log a contact it automatically gets exported to QRZ. I also have the LOTW integration setup in my QRZ logbook so I can send my contacts there as well easily.

With the QRZ and LOTW integration, if they are both setup in your WRL account you can also use the QSO manager to re-check for confirmations and pull in any QRZ and LOTW confirmations you have too.

Now with that all said we do plan to change things up a bit in the future and have those icons (tree icon for pota, mountain icon for sota, etc) so regardless of if its a pota/sota activation as long as there is data in the ‘Their Park’, ‘Their Summit’, etc fields.

I hope this helps.

I’ll update you once the team has had a chance to look at the import issue, but it sounds like since you were just hunting and not activating then everything is working as expected where the icons showing up are concerned.

1 Like