[Dx4win] [Van spam verdacht] Wish list, again -- LOTW Import

[ON4AOI]

Hi Randy and others,

Here my comments and explanation why I like it this way,
Some improvements from Paul will certainly reduce the amount
and sometimes why I hate it But this is due USER mistakes.

> A couple of weeks ago, I happened to be scrolling through the logbook
> window and realized that the log file was terribly cluttered with
> large amounts of redundant information in the Notes for this QSO
> field. I decided to see if I could clean up a lot of this stuff. To
> my horror, I found in excess of 3000 records that needed to have this
> material expunged.

This could have been avoided if you didn´t check the ¨Include QSL details¨
on LoTW 
Download Report like Jim AD1C responded earlier today. But stuff like
WAS-GRID
Won´t be downloaded............. and that is also not good.

>>This is easily solved, but BEFORE the fact.
>>Before you download the lotwreport.adi file from ARRL,
>>there is a check box (normally UNCHECKED) that allows you to include extra
>>information in the downloaded lotwreport.adi file.
>>You must be checking that box, because that is what is adding all the
extra data into your log.
>>73 - Jim AD1C

> What do I mean by redundant? If you look at what happens when the
> program imports a LOTW report, you'll understand. To give a near
> worst-case example, let's say I get a LOTW QSL for a QSO I made with
> my friend KU8E in the CQ WPX contest. Since the only exchange in WPX
> consists of a 599 and serial number, the original contest QSO record
> will have only the received serial number in the Received log field
> and the Notes for this QSO field will say "Freq=xx,xxxKHz, WPX CW
> YYYY". (This is the result of using AD1C's very nice ADIF2DXQ
> software -- thanks, Jim!).

The freq and other txt are a result of Jim AD1C his nice ADIF2DXQ conversion
program and are placed by DX4WIN in the Notes for this call, but If you
don´t 
like to have these comments in it you can use the freeware program I posted
earlier
this week and cut away the unneeded items (delete columm) almost forgot that
it was
you that announced the problem with . and , so you know how to handle that
program,
I use for editing files Textpad instead of wordpad because it can do much
more
You can create macros to select what you need to search for and replace with
what you like.
My adif imports from contest logs have been done with rewritten adif filters
So WYSIWYG (What you see is what you get) 

   
> assuming Jeff has provided all the possible information, the
> following will be appended to the text in the Notes for this QSO
> field: "LOTW: State=GA County=Harris Grid=EM72 CQZone<>5".
> 
> What's redundant here? Practically everything! The "LOTW:" part isn't
> needed, since the record import sets the Upl Cnf flag. The 'State=GA
> County=Harris" aren't needed, since the record import populates the
> State and County fields. Similarly, the Grid field is also populated,
> so the "Grid=EM72" isn't needed.
> 
> The "CQZone<>5" part IS useful information, given that the initial
> import of the contest QSO caused DX4WIN to populate the Zone field
> with a 4 based on the "8" in the call. Unfortunately, DX4WIN does NOT
> update the Zone from the imported data. This may not be all bad,
> since there are a good many LOTW users who mistakenly enter their
> IARU zone in the CQ zone box when they upload their log files and
> thus provide the wrong zone in their QSL record.


I find that the start with ¨LoTW:¨ in notes is very usefull in dx4win
Because with F8 looking up ¨LOTW: STATE¨ will only show up those qso´s where

Both are present, same for other items.

>"LOTW: State=GA County=Harris Grid=EM72 CQZone<>5" is written in the notes
for this call because one of the items was incorrect-- in this case it is
CQZone 5
like you explained. When all downloaded data is correct and put in the
correct
field there is NO LOTW: in the notes for this call.
I am sure that Paul is reading this and will probably come up with something
That for instance only shows the corrupt items like LOTW: CQZone<>5, wrong
Grid
This part needs the user his attention because there is a difference between
the log
And the import.

I agree that with massive import this is a big job to correct but I prefer
To have it in my log then somewhere on a report sheet. This get lost or
deleted
And your log stays bugged. I have 41k in my log and earlier this week I did
a full download of all my LOTW confirmations(6500) (did it because I had
more confirmed
due a conflict), exported my log changed UPL CFN to N 
imported in a new file and then imported the lotw adif.
First lookup with F8 in Notes with LOTW: showed 1700 problems
Used my textpad editor on a new filtered export (only those 1700 where
exported) 
After searching and replace on items like described b4 I imported again with
overwrite
Qso´s and this reduced my LOTW report problems to 321 qso´s now. (+/-
2hours)
181 where gridlocators because in my log was JO21ba and the upload showed
JO21 only
Selected only those with f8 and with backspace and F10 it took about 10
minutes
100 others where LOCATORS that didn´t match some of them there shack is in
the middle
Of the ocean, fixed it with QRZ.com when states and county were equal.
Now I am still stucked with 40 problems and these ARE USER FAULTS because in
my log
They lived in CO - DENVER county in 1991 and moved to a new qth in NY but
uploaded
There FULL log with data from the new qth and not from 18 years ago,
Never received paper qsl so can´t check it.

A multiple QSO operation with cleanup ¨LOTW: comments¨ would be an option
but will
This be a good option ? you remain with an incorrect log. 
After a hugh import the lotw: comments are much smaller and can be corrected
with F8 backspace F10 very quickly

This is why I am contra the 1 button LOTW upload/download some people may
wish,
>From time to time you make a small expedition or have a special prefix/call
etc
And you want to upload them to lotw, creating a unique name log is not a
problem
Having a certificate isn´t a problem also, Lets say that Paul should ad this
feature
With a setup in preferences.(TQSL password etc) but
afterwards..................
Just wondering how many times this 1 button upload will be incorrect if you
forgot to change
to the correct certificate?


Guy ON4AOI