Log4OM

The grid square that comes up on VP8SGI is showing them off the coast of Africa (II99TK).

When I enter them from the cluster, the grid square shows up as KD85JQ in the beam heading and information area then after about 1 second the info boxes changes to green and the grid changes to II99TK. Of course the beam headings are incorrect as well.

Their true grid square is HD15PT.

Is there a way to correct their grid square location?

Thanks,
Ken VA3KA

I noticed the same thing. But two days ago (Thursday) the beam heading was correct and map location was at least close. I just made sure the country, club log and scl file where up to date. I checked the country.xml and clublog.xml file and the lat long were correct. Nothing found in the scl file which would throw its location off. HamQTH (which I am using for lookup) does not show a grid position, but when you look up the call on the HAMQTH website and click on the map, it shows the correct location. Wonder if QRZ users are having this issue? Stumped.

Doug - W7DRM

Ken,
It seems the lat and lon in Cublog is incorrect, try unchecking the Clublog lookup in Options/Settings 1 and entering the call again and you will see what I mean.
Just double click on the QSO in the recent QSO window to edit the grid square

Thanks Terry. That fixed it. What file does the clublog exceptions live?

Doug - W7DRM

When Log4OM paints the path to another callsign and prints locator and maps, the very first information is collected from internal sources, referring to the country center as first proxy.
After 2 seconds Log4OM starts external source search. When informations are collected from external services (QRZ/QRZCQ/HAMQTH) the locator goes green (if received) and the information is updated accordingly.
In that case, user has set something weird on his account.