Not to make everyone's head explode, or bore everyone, but here are the
results of my importing my .adi file from LoTW:
I had 4791 good domestic QSLs from LoTW (I'm an HF contester) out of about
126K QSOs that I've put onto LoTW from domestic operations and Dxpeditions.
My FS/KC1F logs are on LoTW from 1989/90, BTW, if anyone needs them. Out of
the 4791 imported to DXB, I got 156 "warnings", where the QSO in DXbase was
updated to show LoTW confirmed, but where there was some kind of data error
(I'm sure it's on the League's or someone else's end - I trust Jack and the
crew !).
All of the 156 QSOs appear to be contest QSOs, made by CT, if that matters.
The great majority appear to be where DXbase was looking for a "state" from
a Canadian station, with predictable results. All of the rest, except for
about 5, were county errors for Alaskan stations (KL7AC, KL7RA, KL1V, WL7M
and NL7G have indicated that they are in counties not shown in DXbase - if
anyone cares I can give you the details), and the remaining few were
apparently similar county errors from Virginia and a couple of other states.
"Digital" QSOs seem to be disproportionately represented in the errors. txt
file.
Finally, in the cases where the county error was noted, LoTW did NOT cause
DXbase to change the county in my DXbase log, I guess because it wasn't
obvious what to change it to.
Not sure what all of this means, but it may be of some value to someone...
Stu KC1F
