LoTW Upload Station Profiles

[aa5sh]

Since adding the County to the Station Profile I have experienced tQSL errors due to county not matching my location in tQSL. So I added logic to allow the user to select the station profile. Since the station profile name isn't stored in the contact, I linked on the fields taht seemed to matter to tQSL.

[foldynl]

Yes, you are right. It seems that TQSL has the ability to define fields for QTH (see URL). Unfortunately, I am from a DXCC that does not have these fields, so TQSL does not show me anything like that, and therefore I cannot test it. However, the question is whether, in this case, it makes sense to keep the Callsign and Grid there, when having just the profile might be sufficient. What do you think?

[aa5sh]

It would make sense just to pull it from the Station Profile. Only downside is if operators don’t have good names for their Station Profile to know. I have started to put my callsign because my son - who is a ham - has been on a couple POTA activations with me and it was easier just to use my laptop. 

…

On Dec 16, 2024, at 4:38 AM, Ladislav ***@***.***> wrote: Yes, you are right. It seems that TQSL has the ability to define fields for QTH (see URL <https://lotw.arrl.org/lotw-help/stnloc/?lang=en>). Unfortunately, I am from a DXCC that does not have these fields, so TQSL does not show me anything like that, and therefore I cannot test it. However, the question is whether, in this case, it makes sense to keep the Callsign and Grid there, when having just the profile might be sufficient. What do you think? — Reply to this email directly, view it on GitHub <#551 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXVES3NUBVTNNPERZND2F2UTFAVCNFSM6AAAAABTUEH3POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBVGIYTOOJQGA>. You are receiving this because you authored the thread.

[foldynl]

I'm not sure about this change for a few reasons:

1. It might be confusing for users because your change introduces profiles as combos. This means a user could select callsign AAA, but the profile might have callsign BBB.
2. If we remove callsign and grid and introduce only profiles, the operator has no control over what gets selected. For example, I might have an older combination in the log that doesn’t have a profile, but I still need to select it.
3. The profile shouldn't be mandatory because in some countries, you don't need to use County when using LoTW.

I understand the issue you're trying to fix, but I'm not sure how to make it both user-friendly and simple

[aa5sh]

I understand. I've been getting around it by just making sure to update often before I switch to a different location. Would it maybe make for sense to use a user qso filter there? Maybe even replace the grid option. I know it isn't a huge use case but I could see where it may be important for not only counties but possible POTA etc.

[foldynl]

Do you know what must match for TQSL to accept it? County, POTA, or anything else?

[aa5sh]

The only info I can find was here: https://lotw.arrl.org/lotw-help/developer-submit-qsos/?lang=en And it looks like: MY_DXCC MY_STATE MY_CNTY MY_CQ_ZONE MY_ITU_ZONE MY_GRIDSQUARE MY_VUCC_GRIDS

…

On Jan 26, 2025, at 3:25 AM, Ladislav ***@***.***> wrote: Do you know what must match for TQSL to accept it? County, POTA, or anything else? — Reply to this email directly, view it on GitHub <#551 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXW7KLHAQCGADAG2NCL2MSSYTAVCNFSM6AAAAABTUEH3POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJUGI4TEOJVGA>. You are receiving this because you authored the thread.