[Dxbase] LoTW induced errors in DXbase

Mon Jun 14 21:28:49 EDT 2004

I think one of the reasons for the transposed zone numbers is LoTW Certificate process.
Generally it's convention to list CQ Zone and then ITU Zone.
At least I always do.
But in the Certificate process LoTW asks for ITU Zone first and then CQ Zone.
As for the incorrect zones. There are instances when countries can have multiple zones.
And of course, ITU being more recent, relatively, some people may just not know their
correct zone.
But it sure does make a mess out of your log statistics keeping that LoTW doesn't check
for accuracy in these uploads.
----- Original Message ----- 
From: "Stuart Santelmann KC1F" <kc1f at adelphia.net>
To: <Bill at NT1Y.com>; "DXbase Reflector" <dxbase at mailman.qth.net>
Cc: "Patton, David NN1N" <nn1n at arrl.org>
Sent: Monday, June 14, 2004 6:28 PM
Subject: Re: [Dxbase] LoTW induced errors in DXbase
>>>> > While doing this, I noticed that the Dxbase's LoTW import is doing strange
> > things to my logbook data. For example, I received 160m DXCC credit from
> > LoTW for an EA4KD QSO on 1996-Jan-10. Back in 1996, I had logged this QSO
> > with the proper CQ (14) and ITU (37) zones. The QSO record in LoTW,
> > however, had incorrect CQ (37) and ITU (14) zone data. (This happens a
> lot,
> > LoTW is full of bad zone data.) Dxbase seems to have entered this QSO
> into
> > my logbook a second time with the bad zone data and marked that one as
> LoTW
> > confirmed, the zone data for the original QSO remained as is (that is,
> > correct), but not indicated as LoTW confirmed.
>> Hi Bill and everyone:
>> I ran WA6AXE's checkmyzones.rpt - it seemed to work FB ! It flagged 174
> out of my 5500 or so LoTW QSLs, for about a 3 % rate. Just about all of
> these appear to be errors made by the DX station in entering their zone - a
> lot have transposed the CQ and ITU zone, like EA4KD did (BTW, DXbase did NOT
> create duplicate QSOs for me - maybe my clock and KD's were closer ?). Some
> entered the same zone for ITU and CQ. Some were apparently confused about
> which ITU zone they're in. Other errors were harder to explain. Finally,
> another interesting one is FO0AAA Clipperton. Both DXbase and the DXCC
> Countries list have it as CQ zone 7and ITU zone 10. The FO guys uploaded
> their logs with zone 32 and 63, respectively, which don't seem to be
> correct, at least one my map.
> I guess for time being, at least until LoTW is used for the WAZ award,
> that it doesn't really matter for awards purposes what the LoTW QSL has for
> a zone ?
>> 73
> Stu KC1F
>>> _______________________________________________
> Dxbase mailing list
> Dxbase at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dxbase
>