[Dx4win] LoTW import errors

[Jim Reisert AD1C]

On Tue, Dec 7, 2010 at 5:38 PM, F.R. Ashley <gdadx2 at clearwire.net> wrote:

> 1. How do I handle JT65A errors?  It is one of the modes, and it is loggged
> correctly by both me and the other ham.

What is the error and how/where is it reported?

> 2. How do I handle errors in which the other ham has moved since our QSO?
> Error says wrong state, etc.

There are two cases here - which one is yours?

1.  You entered callbook info for the call *long after* the QSO took
place, such that the callbook info isn't correct for the QSO you had.
Example:  I moved from MA to CO in June 2007.  If you use today's
callbook to populate states for QSOs that took place in 2007, you'll
get my state wrong.

2.  His/her LoTW certificate is wrong.  Tell him/her!  I had to work
with someone in WV because his was wrong.

> 3. How do I handle county errors when the the county comes from a callbook
> CD and the ham hasnt moved?  Accept the LoTW Co?

The callbook is unreliable.  It bases the county on city and ZIP code,
which often comes up with the wrong answer (a P.O. box may be MANY
MILES away from the  ham station).  Trust what the other ham sent or
put in his certificate (or QSL card).

Note that #2 and #3 contradict each other.  #2 says don't trust the
certificate.  #3 says to do so.

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us