[Dx4win] Zone conflicts after importing the log from CQWW

[Jim Reisert AD1C]

On Mon, Oct 31, 2011 at 5:47 AM, Mel SM0MPV <sm0mpv at 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

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us