Some other very confusing ones are KH2RU (a Guam call) used by a ham living in Puerto Rico (KP4) and AH2C who used to be very active in Guam now living in Florida. I used to talk to Leo several times a week in Guam when I was in DU land. When you enter KH2RU into DX4WIN it correctly comes up as Puerto Rico KP4 but is a little disconcerting as it is not what you expect. AH2C still logs as Guam KH2 but Leo may not be very active anymore since leaving Guam so it may not be an issue.
Alan, K7ACZ (who is REALLY in call area 7, zone 3) -----Original Message----- From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of Jim Reisert AD1C Sent: Monday, October 31, 2011 9:21 AM To: Mel SM0MPV Cc: dx4win Subject: Re: [Dx4win] Zone conflicts after importing the log from CQWW On Mon, Oct 31, 2011 at 5:47 AM, Mel SM0MPV <sm0...@stockholm.bonet.se> wrote: > When importing my log from CQWW i got 23 conflicting zones reports. The are > all concerning stations within zone 4 and 5. Some might be my error but > other not, e.g. K5ZD reported zone 5 but when importing the zone was > changed to 4. Is there a way to check these? There are several exceptions to the CQ zone rule for USA call areas: 1. Wyoming is W7, but is CQ Zone 4 2. West Virginia is W8, but is CQ Zone 5 3. Alabama, Tennessee and Kentucky are W4, but CQ Zone 4 This does NOT take into account calls like K5ZD in W1 (zone 5) or AD1C is W0 (zone 4). When you fill in the STATE field in your log, DX4WIN will determine the correct CQ zone. Because the number of import errors is small, do an F8 search for Import in the "Notes for this QSO field", open the F3 window, and enter the US STATE from the callbook into your DX4WIN log for each of those QSOs. DX4WIN has a large number of callsign exceptions for KH, KL and KP (etc.) calls that are in the USA (DXCC entity) and callsigns *without* KH, KL or KP that are NOT in one of those DXCC entities (i.e. Ron KP2N is Florida, USA and if you try to log that call, it will come up as USA). If any of your import errors fall into this category, let me know so I can add them to the callsign exception database. 73 - Jim AD1C ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
