[Dx4win] Measuring the LoTW import process

[Paul van der Eijk]

Larry,

You should have a file with a .notfound file extension. This file
contains a report explaining why certain QSOs were not confirmed but
appeared as confirmed in the ADIF file. If you 'disagree' with the
explanation, zip up your log and adif file and mail it to me and I will
have a look.

--Paul, KK4HD

Larry Gauthier (K8UT) wrote:
> Today I downloaded an LoTW report from the ARRL web site and imported the 
> files into my DX4Win log. When the process was completed, I somehow had 20 
> unaccounted for LoTW QSOs. Here's the details:
>
> Before the download and import, I set a filter to get a count of the 
> existing LoTW confirmed QSOs. I had 8105 confirmed LoTW QSLs. I downloaded 
> an LoTW file from the ARRL with 294 QSOs in it. The DX4Win import program 
> reported that it had confirmed 264 uploaded QSOs. After importing, another 
> filter count reported that I now had 8369 confirmed LoTW QSLs. That makes 
> sense: 8105 existing confirms, plus 264 new confirms, equals a new total of 
> 8369 LoTW confirms. No problem.
>
> BUT... the downloaded LoTW file had 294 QSL records. DX4Win only accepted 
> confirmations for 264 of the 294. What was wrong with the other 20 records 
> in the LoTW file? Because LoTW's server ONLY matches on QSOs that I have 
> already uploaded, it would be impossible to receive back from LoTW any 
> records that are not already in my logbook. Right? How do I identify the 20 
> "unaccepted" records out of the 294?
>
> Has anybody else noticed this problem?
>
> -larry
> K8UT 
>
> _______________________________________________
> Dx4win mailing list
> Dx4win at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com 
> Version: 8.0.176 / Virus Database: 270.10.16/1925 - Release Date: 1/30/2009 7:37 AM
>
>