Main cluster bearing Sometimes wrong

[nc8x]

in the main cluster many callsigns report bearing of 263/83 which are incorrect . but in the small cluster on the far right if you click on the same callsign it reports the correct headings. double checking those callsigns they do have a locator entered into hamqth . wondering what I got wrong this time .

[G4POP]

This is a question that appears very, very often, so once more with feeling!

When a cluster spot is received it is checked against the country file using the prefix this uses a standard locator approximately in the centre of the country the prefix indicates - This is the reason that you often see many spots from the same country with the same bearing. We do not check every spot against QRZ or HamQTH and we never will because of the load it would put on those servers.

However when you double click on the cluster spot the call sign is added to the Call sign entry field and a lookup is done with either QRZ or HamQTH which most times return an accurate Locator (Grid Square) for the calculation to be done on and this results in the accurate information seen in the display and saved to the log.

Sometimes there is no locator recorded at either QRZ or HamQTH and the bearing shown will again be that taken from the country file and be an approximation of the centre of the country. This Locator however will not be saved to the QSO because clearly it is not accurate.

[nc8x]

I thought the bearing information was taken directly from the cluster . I wasent aware that it was checked against another file. sometimes I use the ve7cc software and it shows the bearing there and I am not aware of it checking against another file.

If the bearing in the main cluster is going to be wrong quite often , can that field be removed from the cluster layout ?

[G4POP]

It's not wrong it's an approximation and close enough to start swinging a beam to peak the signal

No you cannot remove the bearing info from the cluster but you could narrow the window down so that you don't see it if it's a big issue!

[nc8x]

Close ? k1mi is reporting in the main cluster as 263/83 but the true heading is 152/332

263 is west and 152 is nearly south

[G4POP]

How would you propose we obtain the information without using QRZ or HamQTH?

Are you certain that you have entered your own locator correctly in the Log4OM station info tab, that would cause errors

[nc8x]

I am not sure I thought it was in the data returned by a dx cluster . the ve7cc client software reads the bearing from the cluster , and I also think hrd logbook does the same . Where does the log4om get the information for the calls that show the correct bearing ?

[G4POP]

I am not sure I thought it was in the data returned by a dx cluster . the ve7cc client software reads the bearing from the cluster , and I also think hrd logbook does the same . Where does the log4om get the information for the calls that show the correct bearing ?

Are you certain that you have entered your own locator correctly in the Log4OM station info tab, that would cause errors

As I stated earlier the locator on which the bearing is calculated from is taken from the country file which is if you like the DXCC list

[nc8x]

I am pretty sure I have

[G4POP]

As all of the entries that you refer to are in your own country, it's pointing to the same place, the center of your own country, if you check bearings for other countries it will be a more accurate approximation.

Perhaps someone else can explain this better than I am but as an example

I live near London UK and if the cluster sees a G station it will indicate the middle of England which is at about 340 degrees from me, but the G station could be in Dover which is South east of me.

If the spot is for an Italian station it will approximate to about 120 degrees, somewhere near Florence

However when I click each of the spots in the examples above we then have the correct locator to work on and the heading is corrected.

The further away the station is the better the approximation is, the closer like in your situation the greater likely hood of inaccuracies.

The software does not know what country you are going to work until you click a spot!