[DXBase] LOTW

2003年12月17日 13:17:09 -0500

Bill and John bring up a good point.
I have also had lots of "repeat" QSLs in LoTW downloads that have a new QSL 
date and seem to reflect either a change in the other station's information 
or just a duplicate because he uploaded the same info again. In all cases, 
the present DXBase import utility will reject the "QSO" as a duplicate 
entry... we don't really have a "QSL" import system yet.
So this becomes another piece of the specification for the DXBase import of 
this QSL information. I would assume a more recent QSL record would 
contain a "more correct" description of the station data so it should 
overwrite any prior information.
I have about 5300 QSLs in the LoTW system which I am now importing into a 
test DXBase log to track new countries, states etc. Many of the QSLs are 
multiple records from contacts with the same station in different contests 
etc. My last download to update my database was about 250 QSLs of which 
about 150 were "duplicates". Most of those duplicates seemed to be a 
simple change in the QSL record date which means the other station simply 
uploaded the same log information again. In some cases this has happened 
several times with the same station.
Since the LoTW system will always use the most recent "match", I will need 
my LoTW QSL information to be the most recent data. So a "blind update" of 
the new record seems to be what is needed from the DXBase import utility.
Other information errors I encounter:
1. IOTA identification as OC 220 when DXBase wants to see OC-220 (original 
ADIF did not put in the dash) DXBase does reject this QSO.
2. Alaska "counties" don't seem to fit. The QSO is kept but the county is 
rejected. I'm not a county expert so I really don't know what is correct.
3. IARU zones (USA) are not correct. This error was also in the original 
ADIF and the accuracy is really the responsibility of the other station. I 
don't expect DXBase to correct (or reject) it.
I understand that the LoTW Awards will be made available in a couple of 
weeks. This is when we can actually do something with this LoTW data. I 
am hoping that DXBase will have some sort of utility we can use to work 
with our master log data in a comparable time... (??)
73, Hopefully optimistic .. George .. W1ZT
At 11:23 AM 12/17/2003, FireBrick wrote:
>This has happened to me a few times already.
>Instead of UPDATING, they reload their entire log.
>>Sometimes it's to correct incorrect zone or grid data.
>It's no big major problem.
>I'm sure the DXB utility to take the qslreport info and
>merge it with our logs will just realize they are repeats.
>>>----- Original Message -----
>From: "OZ4RT, J Arnvig" <[email protected]>
>To: <[email protected]>
>Sent: Wednesday, December 17, 2003 7:51 AM
>Subject: Re: [DXBase] LOTW
>>> > If you reload the entire log, everybody who already got a qsl from you
>will get
> > another one, and have to compare the two to see what is changed, if
>anything.
> > DXBase will reject the dupe when he tries to import it.
> >
> > 73 ... John, OZ4RT
> >
> > ----- Original Message -----
> > From: "Robert Morrow Mail on Outlook" <[email protected]>
> > To: "DXBase List'" <[email protected]>
> > Sent: onsdag, december 17, 2003 13:27
> > Subject: [DXBase] LOTW
> >
> >
> > | Hello
> > |
> > | I loaded my log into LOTW several months ago. Now I would like to load
>the
> > | contacts made since. Do I reload the entire logbook or just load the
>latest
> > | contacts and it will be added to the data already their.
> > | 73's
> > | Bob & Carol K9MIE