This has been requested by several people, and it’s something we’re working on.
It will be a button in the Operation Data screen, where you currently can export ADIF files and such, that would directly export the log QSOs to QRZ.com using their XML Logbook APIs.
How about an option to export to LoTW
That is much harder, because it requires running the TQSL app inside the phone.
But this might end up being a feature of a future cloud sync service.
Would I be correct in saying that this feature will only work for those with a paid QRZ XML account?
73 Ed.
Yes, there’s no way to do it without an XML-level subscription.
We do produce a “Generic ADIF” export for operations, which is ideal for importing on QRZ manually.
I don’t know if it’s a limitation of additional log books created within QRZ.com, but I can’t seem to export /P operations created in PoLo to QRZ via ADIF.
Use case: create new logbook for SOTA activations in another country, e.g. EA8/KI2D/P. When you save that new logbook in QRZ it will show the operator as EA8/KI2D, and any PoLo logs you export as EA8/KI2D/P will throw an error on QRZ import due to owner callsign mismatch.
I’m not trying to hijack the thread, just adding some weight behind the need for a direct export-to-QRZ feature. More than happy to help with testing etc.
Mark,
Have you tried using PoLo with the station_callsign and operator callsign set differently so the logs will import?
Alan
I just checked with a callsign like you suggested, and the ADIF file generated by PoLo has the right callsign.
Maybe QRZ has problems importing it because you had a “/P” in the log? Maybe it’s a bug on their side, but only when you have both EA8/ and /P?
And if you’re already identifying as EA8/KI2D, doesn’t this imply “portable” by itself? Do you need to include both that and “/P”?
Thanks for the response, @VK1AO and @KI2D. On my last export from this morning’s SOTA outing I used station callsign EA8/G5MUP and operator callsign EA8/G5MUP/P, and that imported into QRZ.com without issue. But I’m not sure if that’s going to cause problems later on because a lot of SOTA operators always log /P - think it’s mandatory in some regions - and I don’t know how strict QRZ.com is when it comes to lining up confirmations.
Not necessarily, because people have holiday homes where their shack isn’t portable, and they may have a certain level of pedantry forced upon them by local legislation. OFCOM (in Great Britain) dropped the need for /P and also for secondary regional identifier (I can be GD5MUP or G5MUP when I’m at home in Isle of Man) but I understand France is still quite strict on that sort of thing, and when I operate in France as F/G5MUP then I must use /P when portable.