Importing 3 ADI files from a POTA 3-fer

App Help & How-To
1

What is the best way to switch from HAMRS to WRL and import my previous activation data? I am attempting to switch from HAMRS to WRL. My last activation was 7 days ago at US-7270, 39 contacts 3-fer. With HAMRS, I duplicate the 7270 log to create the 0646 and 8316 logs, each show 39 contacts. When I import them to WRL it shows 39 contacts for 7270 and zero contacts for the other 2. When I click on Activities, POTA US-7270 it says last activated 7 days ago by KE5FAR (that is me) but Number of times activated is 0. I understand that WRL handles duplicates and multiple parks differently. Does this only work when WRL is the original logging program?

1 Like
2

@KE5FAR Hey Frederick

Its reading those contacts (for the other two parks) as duplicates because its the same QSO’s (same time, freq, band/mode) since WRL handles the 2fer/3fer/etc differently.

What you can do is just add the other park numbers into your logbook (US-7270_07202025) and make sure you’ve set your logbook activity to POTA.

I’ve manually went in and done this for you.

image
image1575×470 43.4 KB

You should still set your ‘saved location’ for this logbook as well.

So in the future what i would personally do is go into WRL and create a new logbook, set the activity as POTA (this sets the MY_SIG, SIG, etc fields per the pota needs), then do the import into that logbook using one of your park adif’s and then just add the other parks to that logbook.

Let me know if any of this doesn’t make sense or you need another hand.

Thanks & 73
Brad K4AZE

3

Hi Brad,
Thanks for the quick reply. I totally understand what you are saying and gave it a try.

1 Like
4

Yessir no problem at all! Happy to help! Let me know if you need a hand with anything!

Thanks & 73
Brad K4AZE

5

Hi Brad,
So far so good. I deleted the QRZ log and imported the POTA activations successfully, better organized by Park#.
I am having one issue with US-3791 Trail of Tears because it spans across multiple states. I am trying to correct the Location Settings but these changes won’t stick. (all other changes do)

locationSettings.JPG
locationSettings.JPG1194×304 22.4 KB

1 Like
6

@KE5FAR i’ll take a look for you. which of the 3 logbooks (US-3791 TrailofTears, US-3791_07042025, or US-3791_07032025) is the one your trying to update, the first one? ie US-3791 TrailofTears?

Thanks & 73
Brad K4AZE

7

Either or both, same issue. I submitted a bug report because it is only allowing the POTA pinned location, but it is a road with a park number spanning many grids and states. We need to be able to edit the location. Same is true for US-0646, POTA has it pinned in place that is correct for that location but the park boundaries around the Buffalo River spans many grids and states.

1 Like
8

@KE5FAR Got it, yea i got your bug report. We are looking into it and have a meeting tomorrow where we will discuss it further. I’ll reach back out on the bug report tomorrow afternoon after out meeting :wink:

Thanks & 73
Brad K4AZE

9

IMO, I think that in the same way we can edit our QTH location, we should be able to edit a POTA location. It should not be tied to a POTA pin. It is the responsibility of the operator to confirm that they are in the property boundaries.

1 Like
10

@KE5FAR Frederick, Yes we agree. We are ensuring the user can modify the location even if its being pulled from another source.

Thanks & 73
Brad K4AZE