[Dx4win] LoTW QSOs not found, but they are there
David Kozinn, K2DBK
k2dbk at arrl.net
Sun Feb 14 11:11:26 EST 2010
Thank you Arunad, that is exactly what the problem is.
The non-matches were all US and the states in the download file didn't
match what's in my log. In addition, one of them was a 6m contact and
the grid information in the downloaded file was different as well. What
I did was to remove the state & grid info in my log and re-import the
downloaded file and everything matched this time. I did get a warning
that information in 2 QSOs had been updated.
I am using version 8.02 as well. Perhaps in a future version the
"review" feature can be extended to show more fields so this kind of
things would be more obvious.
Again, thank you very much!
On 2/14/2010 3:42 AM, LY2IJ wrote:
> Hi David,
>
> I found it in 8.02 - not sure about ver 8.03 - didn't download old
> LoTW reports latelly.
>
> As I understood it happens when county or state info is
> different in LOG and in LoTW data - then I had "not found".
> It happens if somebody uploads their LOG with one QTH info and
> latter tries to fix to other QTH info for same QSO.
>
> 73
> Arunad LY2IJ
>
>
> I just downloaded a bunch of confirmations from LoTW. In addition to the
> "already confirmed" (my fault, the range went back too far) which aren't
> an issue, I got a couple of "not found in log" QSLs. What's really odd
> is that when I use the "review QSOs not found" it finds as "potential
> matches" the exact QSO that it claims isn't there. In other words, it's
> showing the matching QSO and nothing is highlighted in red to indicate
> the "near match".
>
>
>
> ______________________________________________________________
> Dx4win mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Dx4win at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
>
--
73,
David, K2DBK
http://k2dbk.blogspot.com
http://k2dbk.com
twitter: @k2dbk
More information about the Dx4win
mailing list