Not sure if this is a bug, user-error, or a feature I have failed to use correctly. But Polo .adi exports used to offer two types, the standard and the generic. Both had the gridsquare of the park. I never found a need to use the generic .adi. I imported the standard .adi into my desktop logging software (Log4OM in my case) just fine and it captured everything, sig, siginfo, gridsquare, etc. The standard seems to now lack the park gridsquare, but include the sig and siginfo fields. The full seems to include the gridsquare, but lack the sig and siginfo fields. I liked having all of the fields, as I run reports against sig and siginfo for sending QSL cards.
Please tell me this is user error on my part and/or a work-around available so I can have a single .adi file that has everything.
Keep up the excellent work. Best POTA logger I’ve ever used and a happy contributer.
We did implement some changes so that the “activity-specific exports” (what you call “standard”) has only the minimum set of fields required for that activity, and that only the “Full ADIF” (it used to be called “generic”) is the one that includes all the information, including names and notes for each QSO, etc, etc.
What you describe seems to be a consequence of these changes, and it would seem to be a bug. The POTA (I’m guessing you’re talking about POTA here, right?) export should include your location grid.
And the full export should also include SIGINFO fileds. If it doesn’t, it’s a bug. If you email me the logs you generated I can take a look and try to figure out what’s going on.
However, due to how ADIF manages these references, if you have an operation with multiple activities, or a POTA activation with multiple parks, the Full ADIF will only include one of these references in the SIGINFO fields. It should also include POTA_REF fields that allow for comma-separated list of references, but not all logging apps support these yet.
Hi Sebastián, yes, Pota only. I emailed you the two exports from my last activation. I used your email on QRZ.com. Please let me know if there’s a better way to get these to you.
I looked at the files and while you’re right that the new POTA export does not include grids, the Full ADIF seems to have all the fields as I was expecting.
Are you sure you didn’t try to import the POTA one when you thought you were doing the full?
The rows on 2025-03-01 K9YP at US-10448 - Full.adi all have GRIDSQUARE, MY_GRIDSQUARE, SIGINFO, SIGINFO_REF, MY_SIGINFO, MY_SIGINFO_REF, POTA_REF and MY_POTA_REF fields.
Hi Sebastián, Tried importing both into Log4OM. In the past I only ever needed the normal, non-generic.adi, but this last export lacked the MY_GRIDSQUARE tag. I then deleted them and imported the full.adi. And that import included the MY_GRIDSQUARE, but did not import the MY_SIG and MY_SIG_INFO.
I just created a fresh test database and imported the full.adi and it now has all! So, obviously my bad here! I swear to the old gods, and the new, that I went through that same process at least twice with the same results of incomplete information. Perhaps My Log4OM db need maintenance. In any event, the full.adi clearly shows those tags. So again, my bad, sir. I do greatly you looking at this and I deeply apologize for wasting your time.