PyHamCTY 1.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,128 @@
1
+ The Contest Country Files #3631 were released on 15 September 2026.
2
+
3
+ The following information can be found at:
4
+
5
+ https://www.country-files.com/contest/
6
+
7
+ __________________________________________________________________
8
+
9
+ This is the home of the contest country files. These files are used by
10
+ amateur radio contest logging software (and other related programs) to
11
+ help determine country multipliers from a callsign. The files are
12
+ updated regularly throughout the year and changes are announced on the
13
+ various contest and logging software reflectors.
14
+
15
+ To download the file(s) you need, hover your mouse pointer over the
16
+ word Contest in the menu bar above, and wait until the drop-down lists
17
+ appears. Then click on the link that corresponds to the software you
18
+ are using. Also read “Download Instructions” in the next section below.
19
+ __________________________________________________________________
20
+
21
+ Download Instructions
22
+
23
+ Clicking on any of the “Pingback” links at the bottom of this page will
24
+ take you to the release announcement for that version of the country
25
+ file. For a given release announcement, click on on any of the
26
+ highlighted hyperlinks to the right of the word “Download:” to download
27
+ the files associated with that release. You web browser should prompt
28
+ you to save (download) the file. If the file is displayed in the
29
+ browser window instead, return to this page (using your browser’s Back
30
+ button) and follow these instructions to save it:
31
+
32
+ Chrome: Right-click on the file name and choose “Save link as…”
33
+
34
+ Firefox: Right-click on the file name and choose “Save Link As…”
35
+
36
+ Internet Explorer: Right-click on the file name and choose “Save
37
+ Target As…”
38
+
39
+ Netscape Navigator: Hold the SHIFT key down while clicking on the
40
+ hyperlink (file name) and your browser will prompt you to save the
41
+ file.
42
+
43
+ Safari: Hold the CTRL key down while clicking on the hyperlink (file
44
+ name) and choose “Download Linked File As…”
45
+
46
+ NOTE: To download a ZIP file containing all the files for older
47
+ versions of the country files, follow this link. To download all the
48
+ files associated with that release, click on the hyperlink containing
49
+ the date and version, for example:
50
+
51
+ 10 May 2013 (CTY-2306)
52
+
53
+ NOTE: There are two different versions of CTY.DAT, CTY_WT.DAT,
54
+ CTY_WT_MOD.DAT and WL_CTY.DAT. Beginning with CTY-1805, full callsigns
55
+ in the file are prefixed with the ‘=’ character. Some older logging
56
+ programs will ignore these callsigns, so “old” format versions of the
57
+ files (without the ‘=’) are available. If you click on the appropriate
58
+ link below for your software, you will get the correct version of
59
+ country file.
60
+ __________________________________________________________________
61
+
62
+ Version Information
63
+
64
+ To see the country file change (revision) history, follow this link,
65
+ then click on the “Continue Reading ->” link underneath heading for any
66
+ of the releases.
67
+
68
+ Once the file is downloaded and installed, there are several ways to
69
+ tell what version of the country file you have:
70
+ 1. In your logging program, try to log the callsign “VERSION” (on a DX
71
+ cluster node, use the SH/H VERSION or SH/SUN VERSION command). Each
72
+ version of the country files will return a different country
73
+ (except for Win-Test, see #3 below). That country will be indicated
74
+ in the release notes for that version.
75
+ 2. Open the country file using a text editor like Notepad. Find the
76
+ entry for Canada, VE. In the list of prefixes/callsigns, you’ll
77
+ find a “callsign” that looks like:VERyyyymmdd where “yyyymmdd” is
78
+ the date of the release. For example, CTY-1812 was released on 10
79
+ November, 2008 so the version string in this case is “VER20081110”.
80
+ 3. The Win-Test files (cty_wt.dat and cty_wt_mod.dat) have their own
81
+ version information at the top of the file. You can see the version
82
+ number only by going to Options | Data Files | Country Files. You
83
+ can not log the callsign VERSION, it will just come up as Canada,
84
+ regardless of the country file version.
85
+
86
+ Except for Win-Test, the CTY file name (i.e. CTY-1812) can not be found
87
+ in the file.
88
+ __________________________________________________________________
89
+
90
+ A Note about USA Callsign Exceptions
91
+
92
+ Many USA callsigns are not in the CQ or ITU zone indicated by the
93
+ number in the callsign. For example, AD1C is in CQ Zone 4, not Zone 5.
94
+ The country files do list a number of these callsigns with the correct
95
+ zone. However, because there are tens of thousands of such callsigns,
96
+ only the most active contesters are included. Here’s how the list is
97
+ created:
98
+ 1. Using the Super Check Partial Database of active contesters, build
99
+ a list of callsigns that are found in 100 or more logs. 100 is an
100
+ arbitrary number, but it tends to limit the number of callsign/zone
101
+ exceptions to around 500, which seems like a reasonable number of
102
+ active contesters (as compared to the total size of the country
103
+ file).
104
+ 2. For each callsign that met the criteria in #1 above, predict the CQ
105
+ and ITU zones based on the number in the callsign. For example, ‘1’
106
+ is CQ zone 5, ‘5’ is ITU zone 7, etc.
107
+ 3. For each callsign that met the criteria in #1 above, look up the
108
+ callsign in the current FCC database, and determine the CQ and ITU
109
+ zones based on the state (as listed). For example, Wyoming is CQ
110
+ Zone 4, California is ITU zone 3. The ITU zone is determined from
111
+ the state only for states that reside entirely within a single ITU
112
+ zone (like Indiana, not Illinois). When a state contains multiple
113
+ ITU zones, a ZIP code database is used to estimate a more precise
114
+ location relative to the ITU zone border.
115
+ 4. If the CQ or ITU zone from step #2 does NOT match the CQ or ITU
116
+ zone from step #3, add an exception to the country file, showing
117
+ the actual CQ and/or ITU zones.
118
+
119
+ That’s the process, plain and simple. It’s fully automated, and rewards
120
+ the most active contesters. If you want to “get on the list”, then “get
121
+ on the air”!
122
+
123
+ If you do not live in or operate from the state listed as your callbook
124
+ address, let me know if it would result in a change to your CQ or ITU
125
+ zone. Many states cross ITU zone boundaries, so it’s harder to get the
126
+ ITU zone exceptions correct. If your ITU (or CQ) zone is incorrect, let
127
+ me know and it will be fixed in the next release.
128
+
@@ -0,0 +1,23 @@
1
+ The Contest Country Files #3631 were released on 15 September 2026.
2
+
3
+ Copyright © 1994-
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a
6
+ copy of this software and associated documentation files (the
7
+ “Software”), to deal in the Software without restriction, including
8
+ without limitation the rights to use, copy, modify, merge, publish,
9
+ distribute, sublicense, and/or sell copies of the Software, and to
10
+ permit persons to whom the Software is furnished to do so, subject to
11
+ the following conditions:
12
+
13
+ The above copyright notice and this permission notice shall be included
14
+ in all copies or substantial portions of the Software.
15
+
16
+ THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
17
+ OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
18
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
19
+ IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
20
+ CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
21
+ TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
22
+ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
23
+