[DXBase] DXBase 2005 LOTW, Orion rig control, VUCC award tracking, Propagation mode & spot filtering

Sun, 2 May 2004 13:57:31 -0000

> I have discovered two issues with DXB 2005, which I installed yesterday:

> LOTW IMPORT OVERWRITING GOOD DATA WITH BAD: I am concerned that the way
DXB
> 2005 processes imported LOTW data may overwrite accurate data with
incorrect
> data. The DXB help file states that DXB will update IOTA, State, County,
CQ
> zone and ITU zone from the imported LOTW data. There is a substantial
> amount of inaccurate information in the LOTW database, especially zone
data.
> Lots of people don't know the difference between ITU and CQ zones and have
> recorded their LOTW zone data (especially ITU) incorrectly. LOTW database
> does not verify zone data (not sure about grid loc/state and other
potential
> data errors).

Hi Bill:
I've been pondering this since yesterday. I agree that it wouldn't be good
for incorrect imported LoTW data to automatically beat up your correct
information, take its lunch money, etc. However, these LoTW QSOs are
apparently able to be confirmed, or else we wouldn't be able to download
them from the League, right ? So, apparently SOME data not matching is not
enough to prevent a QSL. And, if it IS a valid QSL, whose zone information
do they use for the confirmation ? What you think is accurate ? what the
other guy says his zone is ? And, finally, I can tell you that it's a
virtual certainty that what DXbase tells you the ITU zone is for a FEW
places such as Asiatic Russia could be wrong, as some of the
prefix-plus-first-letter-of-the-suffixes land in more than one ITU zone. In
other words, you could receive a LoTW QSL from of these guys where the ITU
zone disagrees with DXbase, and they'd be RIGHT, not wrong, and the default
DXbase technique would help, not hurt. I guess the only way around this
issue is to use Joe Glockner's new program and examine each possible QSO
error.
 My head hurts...
 Stu KC1F