You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two locations that I operate from in Texas and New Mexico. If I edit a QSO, it will complain about the ITU zone for my station not being correct. How does it make this determination? The gridsquare entry is correct.
The text was updated successfully, but these errors were encountered:
ITUz is derived from the callsign and the DXCC Entity database (CTY-file). Unfortunately, for large countries like the USA, this method is not accurate. The yellow warning is more about to display an alert the operator to check if it is correct.
It is not a big deal to me. An easy solution is to ignore the "error" if the fields (including gridsquare) are in agreement with the saved station profile. Perhaps only check them when the station profile is added or modified?
if ITU/CQ should be checked based on the provided information, the task would be entirely different. Here’s why:
You would need to precisely define the boundaries of ITU/CQ zones. This is not as straightforward as it may seem at first glance. Once that's established, the zones can be determined based on the grid.
If grid is unknown but only the QTH (city) is known, it would require updating the location of all cities worldwide. The world isn’t limited to US territories ;-)
But I’m open to any pull request that aims to improve this.
I have two locations that I operate from in Texas and New Mexico. If I edit a QSO, it will complain about the ITU zone for my station not being correct. How does it make this determination? The gridsquare entry is correct.
The text was updated successfully, but these errors were encountered: