Log4OM

1. DXCC awards are calculated from DXCC entity and confirmation status so you won't see dxcc awards in ADIF

2. Special awards like DOC, WAB, WWFF etc are program specific and that is why we insist on an ADIF version 3 export from version 1 because that format of adif contains PROGRAM SPECIFIC FIELDS that include that information.

hi Juergen
thank for you reply.

Unfortunately I have in the lotw something less than 80.000 qso and the download process never download all qsos.

The download process terminates without error but it download about 10.000 qsos; there are no filters to have batch of qso too.

Up to now I do not have other workaround
thanks and have a nice we

Don

ik2egl wrote: 07 Mar 2020, 15:04 hi Juergen
thank for you reply.

Unfortunately I have in the lotw something less than 80.000 qso and the download process never download all qsos.

The download process terminates without error but it download about 10.000 qsos; there are no filters to have batch of qso too.

Up to now I do not have other workaround
thanks and have a nice we

Don

Did you try two downloads with consecutive date ranges, like

01/01/1960 to 31/12/1990

then

01/01/1991 to 07/03/2020

Hi Yurghen/Terry
your procedure to read from lotw qsl status works; I need to do some check manually, but it depends from old paper qsl (lotw arrived later for me).

I imported log directly from lotw with this utility http://www.rickmurphy.net/lotwquery.htm and then I import with log2om2 and situation changed (I have granted fleg)

I have another question on log reading: during the importing (creating new DB but not flagging APPLY COUNTRY CORRECTION) I have messages as below

18:08:47: Callsign: 9J2LA Date: 07/03/2020 11:10:42 Band: 12m Mode: SSB Log4OM suggest change from 0 to 482
18:08:47: Callsign: K3LR Date: 07/03/2020 03:06:38 Band: 160m Mode: SSB Log4OM suggest change from 0 to 291
18:08:47: Callsign: NR3X Date: 07/03/2020 03:05:30 Band: 160m Mode: SSB Log4OM suggest change from 0 to 291
18:08:47: Callsign: W3WPL Date: 07/03/2020 02:59:28 Band: 160m Mode: SSB Log4OM suggest change from 0 to 291
18:08:47: Callsign: 9J2LA Date: 07/03/2020 02:54:57 Band: 80m Mode: CW Log4OM suggest change from 0 to 482
18:08:47: Callsign: TZ4AM Date: 07/03/2020 02:50:59 Band: 80m Mode: CW Country changed from Mali to Mali (same DXCC)

what does it means ?
thanks

Don

It's suggesting that some Qso's have the wrong countty/DXCC number you should check them

Hi Terry
fine, I will reimport flagging APPLY COUNTRY CORRECTION
tnx

morning all
some issuess

DXCC list mislagment

I am checking dxcc import from lotw and I founded that dxcc list in log4om2 is not aligned with LOTW dxcc list

As conseguence of that, log4 om countries are not correctly updated when automatically checked with lotw.

DXCC prefix
in the DXX list I do not see the prefix for each country, as it was in the LOG4OM; it is very useful

Interface improvement: when updating DXCC status (submitted or granted in the QSO, the BOXed containing the list of dxcc statuses are veri small and upgrading is not easy at all. there are some duplicate, with some but with some different name (DCCC_XX or DXCC-XXX)


Maybe I need to move this issues to another thread ?

Different names are related to the different ways some applications save the DXCC references.
Do you have more info about "wrong dxcc codes"?

Morning Daniele
let me attach
1) the ARRL dxcc list
2) the DXCC mode list

they are the official world wide accepted references

let me know if I ccab give you additional help

Don

ik2egl wrote: 10 Mar 2020, 05:17
they are the official world wide accepted reference

But only for ARRL and DXCC awards and operations there are hundreds of others worldwide with other parameters.

The only specification that is close to being international is ADIF which is what we mainly use