[Dx4win] Lotwreport.notfound file

[John Shaw]

Ok Jim I hadn't read you application note. Yes I usually do just accept the
date offered which is the date of the last download I'm not entirely
convinced that explains all the . Entries I get, for example the last
download generated 205 . Reports and 13 X reports, the previous ones report
similar numbers.  Assuming I did the download at 23:59utc and captured a
days worth of cross over's, I wouldn't mind 205 LoTW cfms a day X 365 =
74825 LoTW cfms a year, I only have 109,000 + QSO's in the LoTW system.

More to the point than how these QSO's become eligible for report the fact
remains regardless to if they are re submits from the other party or worse a
system shortfall in timing of reports, there is no logical action to take so
why does DX4WIN report them?

73 John ZL1BYZ.


-----Original Message-----
From: jjreisert at gmail.com [mailto:jjreisert at gmail.com] On Behalf Of Jim
Reisert AD1C
Sent: Wednesday, 2 March 2011 13:04
To: John Shaw
Cc: dx4win at mailman.qth.net
Subject: Re: [Dx4win] Lotwreport.notfound file

On Tue, Mar 1, 2011 at 4:20 PM, John Shaw <jnshaw at internet.co.nz> wrote:

> You are correct with the . In the left column.  Not much we can do 
> about that, if people keep uploading their whole logs over and over 
> they will keep showing up on this list.  For those LoTW users who do 
> this, you may not think it a problem but it can be.

This problem isn't caused by "people ... uploading their whole logs over and
over".  If I upload an identical QSO that is already in LoTW, it won't be
considered a new match.

I tried to explain what really causes this problem in my application note on
LoTW.  I'll explain it again here.