Callsign locator

[HB9VQQ]

Perfect, tnx Doug !

73
Roland

[NN7D]

Got an answer from Terry. Indeed, the Callsign Locator field in the cluster is getting the grid data from the Country file and is based on the center of the country. It is used to estimate the SP and LP bearings in the event that no locator is found during lookup. So that explains the difference.

And, It would be too data lookup intensive to try to do an external lookup for accurate grid data on each cluster spot received.

Therefore, best to ignore the Callsign Locator field in the cluster. If grid info is desired, click on spot and use the Grid data in the main UI.

Doug - W7DRM

[KD0ZV]

Thanks Doug,

Hopefully they will remove it because no info is better than bad info

The SP LP results have always been disappointing as I never know if can trust them or not. I certainly can not get a beam heading for US and Canada. All of US has a beam heading of 230 and Canada 342 for me. Should be something that says if they are in the same center of country as I am then do not display the LP/SP because its just more bad info.

Rich

[HB9VQQ]

Therefore, best to ignore the Callsign Locator field in the cluster

All right, makes sense. Just wanted to understand the mechanics behind it. Perfectly fine with me. Thanks for clarification much appreciated Doug.

Cheers
Roland

[HB9VQQ]

Rich,

All of US has a beam heading of 230 and Canada 342 for me

What's your 3dB Beamwidth of your directional antenna ? Mine is at least 70 degrees (depending on band).
However if you click on a Call in cluster window you will get accurate AZ anyways.

Unbenannt.JPG (47.81 KiB) Viewed 3414 times

[KD0ZV]

Dont even have a beam so I am just whining

Actually, where I noticed it was when looking at LP/SP for new beverages.

No big deal. Just wish it did not show incorrect value.

Rich

[G4POP]

Dont even have a beam so I am just whining

Actually, where I noticed it was when looking at LP/SP for new beverages.

No big deal. Just wish it did not show incorrect value.

Rich

But it does not show an incorrect value if the locator is available from lookup of an inserted call sign?

Plus its a close approximation for when there is no locator found on lookup to at least HELP you know which way to point your beam or which of your beverages to select.

Its been like this since the birth of Version 1, nothing has changed

We cant lookup every call that appears in the cluster for a more accurate locator, because apart from the extra load slowing the cluster down dramatically, can you imaging the complaints from QRZ etc during a contest is everyone's cluster was checking every call received? especially when using skimmers - They would shoot us!

[KD0ZV]

OK understand about how intensive it will be.

Yes, its correct if I insert the callsign.

And living in exact middle of the US its no where close for US and Canadian stations. I mean US could be anywhere from 1 -360 degrees. And it always shows 230 now.

I just shut if off in the cluster. And yes it was that way on V1. I questioned it then.

Rich

[G4POP]

And living in exact middle of the US its no where close for US and Canadian stations. I mean US could be anywhere from 1 -360 degrees. And it always shows 230 now.

Suggest a better way of determining a more accurate bearing for cluster spots when an on line lookup fails, without creating major CPU/Memory usage and we will consider it?

Meanwhile, like the TV you can turn that column off if you dont want to see it!

[KD0ZV]

Meanwhile, like the TV you can turn that column off if you dont want to see it!

Yes, have shut off LP/SP and the grid locator as they are not correct.

Thanks Terry

Rich