Log4OM

I tried with .ADIF, as .ADI, .adif and as .adi ..... always the same popup. This file is ADIF formatted ....... Pictures say more then words ..... B.t.w. i use V2.1 (see first picture) ...

Hi terry,

have send you an email with a download link ..... It´s my "test.adi" that i tried to import with ADIF Master and it´s the original log (with all the doubles and tripples) of my swedish friend

73´s, Juergen

Juergen,
The ADIF file that you sent me had been made in ADIFMaster and it opens in that program for me.

The file contained 37,678 QSO's and when imported into Log4OM there were 26,391 unique QSO's after Log4OM removed the duplicates.

The import duplicates report contained 600 pages of duplicates - Over 11,000 duplicates, he must have had serious issues with his last program!

I can't offer any further help for removing any duplicates that remain other than systematic manual editing

I sometimes use CSVed for removing doublets - but ADIF must be exported to CSV/text (easy done with LM8).

Jürgen: you should try BV7 (it delete ALL doublets based on CALL and QRG - afterwards a pure "first QSO" log can be created - (my log with 30k QSOs was reduced to <10k)
Or try DXlab - during import it checks based on a "delay" of 3min (can be configured) if a qso is dupe - very nice function.
The same can be based on different definitions on QRG 8e.g one Log takes 20m or 14.000 - the next do it fullflavored like 14.056.7) - this often prevent the detection on dupes during import - it depends too on the LogSW.

I have had a "bad" ADIF file in former times to check any Logprogram based on importchallenge (8k dupes) and found only a small number of LogSW which handle such challenges as I needed - now I have a cleaned log and change the workflow how to update my favorite SW for logging

(ADIF is one of the worst solution to create unuseful files - but we must live with this ...)

The import duplicates report contained 600 pages of duplicates - Over 11,000 duplicates, he must have had serious issues with his last program!

I can't offer any further help for removing any duplicates that remain other than systematic manual editing

Hi Terry,

thank´s for testing. Have had the same results here. After Impirting (original was a HRD Logbook File) i´ve had also lost over 11.000 QSO and a new log with 26.391. But if you look into May 2011 (only may 2011) you´ll find around 700 or 800 "Doublets" more. Those have a start time between up 10 to 50 seconds of the original entry and not be deleted while importing. All those entries i´ve deleted by manual work (log shows now 25.6xx qso). That´s why i ask for an option that kills doublets within a period of -/- 1 or 2 minute/s difference from the original entry when all other data (call, date, band (not frequency), mode e.g. are equal ......

For now your test shows me that my work with this log was o.k ...... So i´ve send a correct fixed log to it´s owner

@ Peter

will give BV7 a try when the next guy like to have checked his log ... but would be vy easier if L4O can handle this

So let's ask the question?

How many other users would like a user set "OPTION" to match the exact minute of a QSO to provide tighter dupe rejection during an ADIF import?

It must be a user option because we have to keep the existing time rules to conform to ADIF, LOTW and EQSL practices.

If there is enough interest I will ask Daniele if it could be done and then poll the Alpha and Beta teams

Actually the "doublets" are discarded by the duplicated key on database (very fast, done at database level).
Adding a +- specified interval will require some code on ADIF import, that will result in something slow that will affect all ADIF imports.

I will think about a possible solution, eventually as "post-production" activity (after ADIF load)

Cute term "Doublets" I have a 140 ft long version fed by 450 Ohm ladder line that works very well on all bands

Mine is only 2 x 13,5 m (folded in my attic) and fed by homemade 600 Ohm ladder. Doublets like this are much better then doublets in ADIF