Is there a way to stop LOTW QSL's updating locator (grid square)?

[yo3ipr]

Hi Daniele

Was this included in 1.28.0? It was missed in 1.27.0

Thanks & 73 Tony YO3IPR

[IW3HMH]

Not yet, we made some changes to LOTW Integration and we kept that stopped to avoid having potential regression on the whole part.

It's already fixed on the code, ready for 1.29.
Lotw download will not change the gridsquare if you already have a gridsquare set.

[yo3ipr]

That's great news Danielle, thank you. If you prefer you can add an option in the settings "allow grid square update from LOTW" but with default off

73 de Tony, YO3IPR / G4IPR

[yo3ipr]

Fixed in version 1.29.0 released 1 Aug 2017:

- LOTW download doesn't change the gridsquare if something it's already saved on the QSO

Note also however:

- LOTW QSO download now updates country if different from log.

[IW3HMH]

Yes, gridsquare set by the user has the priority over the default one from LOTW.
But country reported in LOTW has the priority in case errors due to calls in countries with same prefix, unrecognizable by log4om (e.g. Minami Torishima)

73
Daniele IW3HMH

[N6VH]

Could this be made optional? It is very possible that the grid square was obtained from QRZ or hamqth.com. However, the ham could be operating in a different grid square. That is very likely in V/UHF contests. For those chasing grid squares for awards (VUCC), the information in LOTW is what is used for the award.

Another solution would be to have a very obvious note in the LOTW download log that the grid square is different in the log than that in LOTW.

Incidentally, I just checked hamqth.com, and my grid square is incorrect there (only the 5th and 6th characters, however). I tried to change it, but that page could not be accessed at that time.

73,

Jim N6VH