-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit QSO complains about ITU zone when it shouldn't #569
Comments
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. |
Thank you for responding quickly. I looked through the code and found where you are getting this information from https://www.country-files.com/bigcty/cty.csv. 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? Thanks for all your work on this code. |
if ITU/CQ should be checked based on the provided information, the task would be entirely different. Here’s why:
But I’m open to any pull request that aims to improve this. |
Wonder if it would make sense to maybe reword the message and that may limit any confusion. Possibly like 'Yellow marked may have incorrect data please confirm' or something along those lines. |
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: