When I create a new log I have my call as the station call and leave the operator blank. Somehow when I export the file it has my call in both columns.
It’s quite legitimate to have STATION _CALLSIGN and OPERATOR fields
and both set to your callsign.
PoLo allows you to add and change other OPERATORs whilst the STATION remains as is. But having both set to the same is not against the ADIF specification.
Is this causing you an issue?
Alan
Whilst OPERATOR is optional, it is quite legitimate to have both fields set for an operation where they are both the same
And if you don’t like it just remove it from the adif file using a tool like ADIFMaster or a simple text editor with search-replace function.
Every log book programm should be able to handle it as this field is there since the very first version ADIF V1.0 of the adif file definition.
Yes because if I upload it to pota my profile has it right but if I look at the park it shows double the qso’s
There’s something else at play here. I have my callsign in both places in my logs and I never get duplicate QSOs. I haven’t heard of anyone else getting that either.
Did you have to delete your logs and do them again?
Alan
Can you show us an example of a log which caused dupes?
To be honest - just re-checking my workflow. I just leave it as this when I am operating alone
There’s no need to add an operator if you are one in the same.
Alan
I did just as you have it shown the problem is when I export the file it automatically fills the separate operator column
Something is strange. I just re-exported my last log and the OPERATOR column is empty
I found a bug that can sometimes cause that blank operator column.
I can’t remember the details, but a few months ago we got someone complaining that the missing OPERATOR column was causing problems somewhere.
That’s the problem with ADIF… it’s a “standard” that’s is very strict on some areas, but it leaves each app to decide which fields it supports and requires.
@AA4AT can you share which park is showing double QSO counts? POTA should be smart enough to not credit those twice, and if it is, we can reach out to their team to figure this out.
The park was US-10398 the date was 12/22/24. my wife and I did a activation together. I uploaded mine fine however even though I changed the station call to hers in the app and left the operator blank when when I sent her the file it put my call in her Operator column. It credited me twice as many qso’s on the park page. My call is AA4AT hers is K1LY. I know as far as the credit is concerned it’s their glitch however I should be able to export a file leaving the operator blank.
Ah, that explains the double count.
Your wife’s log did include you as the operator. The bug is not that it was included on your log, but that it was included on hers.
I believe the current logic is that if the operation has a station call different from the default from the settings, it will consider the default from the settings to be the operator.
I’ll see if I can make this more robust and explicit.
In the meantime, you can enter your wife’s call as both station an operator for the operation.
Also, for “double operator” operations like this, you can enter “AA4AT,K1LY” as the station call and PoLo will produce the two separate logs for you.
2 Likes
I lied to you, Dan.
Multi-activator support was not included in the December release, only January, which is not yet public.
The good news is that is IS included in the January release, coming very soon.