Pota my_state adif [ANSWERED]

App Help & How-To
1

POTA ADIF export keeps my home state as TN rather than the state of the park I am activating. Makes a difference when submitting to LotW.

2 Likes
2

@KQ4TV Hey Bruce!

Thanks for the heads up, i’ll have the team push a fix for this as soon as possible.

I’ll reach back out here once we’ve pushed that update.

Thanks & 73
Brad K4AZE

1 Like
3

@KQ4TV Hey Bruce,

We double checked this and its exporting as expected. When creating the logbook you just need to set the pota activity and enter the park then select the park from the dropdown. Then after you’ve logged your contacts and you export the pota logbook (ie Export US-1234 ADIF and NOT the Export ADIF button). it will have the correct state based on the park reference.

Let me know if you have any questions or issues.

Thanks & 73
Brad K4AZE

4

Okay, thanks. I guess I assumed that since there was a POTA adif and a non-POTA adif that one was for submission to the POTA organization and the other was for submitting to LotW and were different formats.

73,
Bruce KQ4TV

5

@KQ4TV Yes thats correct. The POTA ADIF is for submitting to POTA as they require a certain format and certain fields to be added (ie MY_SIG, MY_SIG_INFO, SIG, SIG_INFO, etc).

What I do, and would probably be the easiest for you as well. Is to use the QRZ export integration so every time you log a qso in WRL it auto exports to QRZ and then from within QRZ you can just export those QSO’s to LOTW.

Here is a quick screen recording: WRL + QRZ Auto Export + QRZ ->LOTW | Loom

Let me know if you have any questions or concerns.

Thanks & 73
Brad K4AZE

6

I watched your screen recording and either I am misunderstanding something or I think you may be.
I have not tried exporting from QRZ to LotW yet but I did have QRZ export an adi file to me. When I look at the file, all records still have <my_state:2>TN when it should have <my_state:2>OR for contacts I made from POTA entities in Oregon or <my_state:2>AR for contacts I made from POTA entities in Arkansas.

I import adi files from WSJT-X to WRL. I have not yet been able to get WRL to pickup contacts from WSJT-X using the WRL CAT Control app.

So far I have been getting the adi files for each POTA activation from WRL and editing the <my_state:2> entry to match the appropriate state. If I do not do that LotW rejects the import because it seems to recognize that I could not make a contact from a park in Oregon and still have my state be Tennessee.

Am I still missing something somewhere?

Thanks, 73
Bruce

7

@KQ4TV It sounds like something isn’t getting setup correctly before you’re importing your qso’s.

Here is another screen recording showing everything starting with creating the logbook, setting the pota activity and park reference, logging a couple of contacts, then exporting in both the pota format and a standard adif format. Both show the my_state as what the park reference is.

Which leads me to believe something is happening before importing or the data in the wsjtx import is incorrect itself.

Thanks & 73
Brad K4AZE

8

@KQ4TV Ok i think i figured out the issue. I went and looked at the adif’s your imported from WSJTX. Those ADIF’s don’t have the ‘my_state’ field, only a ‘my_gridsquare’ however in all the adi’fs i looked at that you’ve imported the gridsquare is set to your qth gridsquare (even for the Oregon activations). So since the imported ADIF doesn’t have a my_state and only has the ‘my_gridsquare’ we are pulling the state based off the gridsquare in the ADIF data.

Here is a quick screen recording outlining this and showing how you can fix that data:

I’ll send you instructions on setting up WSJTX and the cat control app so you can just stream your contacts from wsjtx into your wrl logbook.

Thanks & 73
Brad K4AZE

9

Not sure if the comment went through,

Thank you, Brad! :folded_hands:
What you show is exactly the way I do it. Never set the advanced part on import info for location. Have confirmed and edited location in WRL as some parks, like Olympic NP are huge and cover several grids. I have edited the grid and gps info and saved that in the logbook for that POTA activation.
It does seem like the sci import process may be doing something but I would think that confirming and saving the logbook settings would fix any error introduced by the WSJT-X import.
Also, not seeing the automatic export from WRL to QRZ but maybe I am not being patient enough.

Thanks for your patience in dealing with this. It would seem that something I am doing is causing this. I will need to grab my POTA laptop and see if I can figure something from that.

I would appreciate a tutorial on the WRL CAT Control app and getting it linked with WSJT-X.

Surprised to see that you are in Cookeville. I was TTU class of 1979.

73

1 Like
10

@KQ4TV I’ve been here for about 15 years but from Oak Ridge originally.

Check this video and reply, i figured out what the issue is Pota my_state adif - #8 by K4AZE and then i dm’d you info on setting up WSJTX → WRL

1 Like
11

Thank you @K4AZE !! Much appreciated!