I received the following feedback from my most recent WWFF email log submission for my KFF uploader from PoLo 2024 October:
also just a suggestion for your next submission i’ve noticed that in your park section (my_sig_info) you did your WWFF park but under your P2P section (sig_info) you did their POTA park would it be possible if you just do your park as your POTA park not your WWFF park? just because i run everyone’s log submissions through a software that verifies and converts POTA references to WWFF references and by having your park as WWFF and their park as POTA it spams me with errors so next time if you get any P2P POTA parks have your park be POTA park so that way my software can swap everything over with very minimal errors
Unfortunately it sounds like there’s A Special Tool to try to handle KFF uploading straight POTA logs, but the PoLo choices in ADIF fields are chewing something up. Most of the p2p I had in my logs are selected from the spots screen. The auto-prompting for POTA p2p “US-” versus WWFF p2p “KFF-” means I don’t think I had repeatedly used the wrong program’s p2p field. I did not get specific feedback about which log(s) had the problem fields, but can look into that more if needed.
If your KFF rep is N3KAE/Al, the “Special Tool” referred to is mParks Converter. It converts a WWFF log to POTA or vice versa.
If you create and submit a POTA log, it needs to be pure POTA and a WWFF log needs to be pure WWFF. PoLo creates both but for Park2Parks, you need to enter the correct reference for both programs to get a valid log for each.
So for a contact with a POTA park you need to ask the OP or find the WWFF equivalent and enter both on the QSO into PoLo to get both logs as valid.
If you just leave it as POTA and never mind about WWFF references, then mParks will convert it. But not all WWFF are kind enough to run POTA logs thru mParks for you.
As Sebastian says, the current release of PoLo will create pure WWFF and pure POTA logs for you. I use the output (2 separate logs) without issue. But your P2P contacts will be subject to you making the match and entering the counterparty reference on each QSO in question.
Unfortunately sounds like the momentum only supports WWFF as an aside to POTA. I’d like to credit my WWFF p2p properly and expect that I have at least a couple of QSOs with a single-program activator on the WWFF side. The advice I got back from KFF was to send in just-as-POTA logs (of course as single-reference activations, per the WWFF rules). Alas.
I re-exported a KFF-configured log in PoLo November 2024 and still see: <MY_SIG:4>WWFF <MY_SIG_INFO:8>KFF-4238 <SIG:4>POTA <SIG_INFO:7>US-7770 <POTA_REF:7>US-7770 <EOR> in one of the p2p QSOs. I haven’t submitted this yet since I usually do monthly batches to cut down on emails.
So in the log. you have it set as KFF to activate but you are only ever recording the POTA numbers for P2P?
i.e. you enter their park here?
with no corresponding KFF number here?
Because I can make this happen under these circumstance.
But you need to record the KFF P2P number for a KFF activation. If the other OP does not know it, then you need to find it out late and enter it in the KFF P2P record.
PoLo has no ability to match the equivalent KFF for POTA number. But you are correct in that, in these circumstances, the POTA SIG and SIG_INFO should be omitted.
In which case, you will risk not getting your P2P. In WWFF, at least one OP must have the P2P reference. if both omit it then none is awarded. If one only records it, then both OPs are awarded the P2P.
This is most likely a POTA-only p2p. I’d have to run through some cases to generate a sample log using: POTA autofilled spot, WWFF autofilled spot, manual POTA p2p, and manual WWFF p2p to see what the different generation cases are.
Yes, that is the unfortunate problem to handle WWFF p2p. A potential enhancement for PoLo would be to do the mParks style conversion and autofill the other program’s park when it’s unambiguous. Of course, there are plenty of non-matching POTAs and one-to-many ambiguous conversions between the databases.
autofilled spots do not populate both program numbers.
at least not until such time as further development on spot merging takes place and then it will also be subject to OPs who spot both programs and many do not
But surely it will only work where the activator spots both programs?
Maybe if a spotter does it too. But if a KFF activator only sets up for a KFF park and spots to GMA - it will only be seen as one spot and therefore no merging is possible. ??
thanks
the point for the OP here is that firstly, it is not realistic to ever expect spots to contain merged data. It may be a convenience provided by PoLo in the future but secondly, it should not be relied upon for recording the varied data of 2 park programs.
If you want to confirm P2P contacts correctly, you will always need to check that both park numbers are recorded against the QSO.
