Logging and stuff
For logging purposes I just use QRZ.com as it does most of the things I need. I have nothing against the various logging packages, it's just that they are all way over the top for my meagure needs. I don't do high pressure stuff or contesting (yet!) so my needs are simple.
However, I do maintain a local database primed from the data in QRZ. It is there that I store eQSL information and WAB square information. QRZ does have fields for eQSL but I decided to store it locally.
Having all this data to hand made me think of ways to use it. Having reapplied my programming hat I now have a few useful modules. My next aim is to make them into a dashboard sort of display rather than console output as now.
One module displays data from pskreporter via the extremely useful pskreporter MQTT feed (see mqtt.pskreporter.info) and stores this in a database along with distance (direction is planned). A web page displays it so I can see where I am being heard (provided that data gets into pskreporter of course).
Another module takes UDP data from wsjt-x and tells me which of the stations calling CQ have been logged before and have confirmed via QRZ or LoTW. I wrote this for the 2024 '12 days of QRZ' event to save me chasing stations that never acknowledge via QRZ.
And I finally updated the code that copies data from QRZ to the local database so it updates any changed fields. That is particularly important as otherwise confirmation information will be missing from the local database.
I already had code in place to transfer data from wsjt-x to QRZ on either PC and to transfer the data between wsjt-x on the Linux and Windows PCs so each knows what the other had seen.
Of course, much if not all of this could be achieved by using any of the many quite excellent logging packages out there. But I like putting code together and keeping my hand in.