Hi Joe, and Gary,

Thanks for the tip Joe! I have been getting that a lot recent;y, which I have attributed to the fact that when logging calls into JTAlert, the call gets looked up in QRZ, and populates a 6 digit grid.

I now try to delete those last two characters, and that seemed to work, but is a bit hit and miss.
Your advice will save me a lot of grief!

And, like Gary, I have just had the same issue with a match for VK5PO from 2012!

73 de Phil GU0SUP

-----Original Message-----
From: "Joe Subich, W4TV" <lists@...>
Sent: Wednesday, 19 October, 2022 14:31
To: DXLab@groups.io
Subject: Re: [DXLab] log vs LotW mismatch


Check the "Ignore subsquare mismatches" box on the LotW tab
in QSL Config.

> what happens when its a new/different Zone as can happen with
> numerous entities?

Subsquare mismatches will not impact zones - zone mismatches will
still overwrite/notify/ignore based on your settings in "Handling
of LotW QSL detail inconsistencies."

73,

    ... Joe, W4TV

On 2022-10-19 8:33 AM, CSM\(r\) Gary Huber - AB9M wrote:
> I am frequently seeing FT8 QSO GRIDSQUARE mismatches, usually in the least significant portion of the the Gridsquare as below;
>
> Date      Time           Call    Band          Mode       Submode       Station Call    Result
>
>    2022-07-23  11:48:00          VK5PO     20M           FT8                             AB9M    log vs LotW mismatch: updated GRIDSQUARE with PF95gn from LoTW; was previously logged as PF95hj
>    2022-03-18  12:01:15          VK5PO     40M           FT8                             AB9M    log vs LotW mismatch: updated GRIDSQUARE with PF95gn from LoTW; was previously logged as PF95hj
>
> I see no issue using the LoTW Gridsquare of a previously logged QSO with a callsign, but what happens when its a new/different Zone as can happen with numerous entities?
>
>
> 73 ES DX,
>
> Gary - AB9M
>