My ARRL Challenge count was up to date since my last submission to the ARRL in August 2008. Now my Challenge count is 20 to 30 countries less. 16123 QSO are in the system and were imported so that matches. How can I correct this?
Is there and error TXT file that I can view? Errors were found during the transfer but no way to print them.
Would be nice to print out the DXCC list that MugLug printed out in the windows tab.
Very hard to compare both the on line LOTW screen and the MugLug DXCC list.
Any ideas on pointing me in the right direction?
As a side note, I have looked at 9 logging programs and used 8. I concluded that ADIF transfers dispite of ADIf I or II proto-call each one handles country labels differently and all ways some thing gets left off. My last program I used and created my master ADIF was Logger32. This whole data transfer issue no matter who's program your using is not an easy task to correct errors and there are issues when transferring and uploading ADIF files.
Jim
Import ADIF Issues
Import ADIF Issues
Jim K9TF
Re: Import ADIF Issues
Well Jim,
importing and migrating a large numbers of QSOs may make trouble. Even when there are QSOs in the log, made for a long time ago. The current used dxcc table represents current valid dxccs only, deleted countries are not included!
I know that the import is not perfect, but we can improve it further. To help you, I have to explain how RUMlog works during an import.
First we have to have a look on the ADIF file. Are there tags provided for dxcc, itu and cq zones? May look like this: <dxcc:3>130 <cqz:2>17 <ituz:2>30
When these three data are available, RUMlog will use these information. When one is missing, RUMlog will calculate the country using the dxcc tables. So these tables must be up to date. For example K7K in October 1997 will be counted as USA, W not as Kure Island, KH7K when not correct in the list.
There is another problem: When RUMlog use the in the ADIF provided dxcc info, you may run into trouble in the future, when editing an entry. RUMlog may then calculate the dxcc wrong. It is always the best, to keep the database up to date.
First you have to search your 'missing' dxccs. Use the search function. Menu-->Window-->Search Make the appropriate settings and press the 'Query' button. Also you can save the results to a (printable) text file, or to the clipboard.
In the future I could add a function to update the dxcc table automatically, when you trust the ADIF data. The problem I see is, the import will take more time for x-checking the dxcc.
Another way should be, I modify the dxcc tables using the old logs when there is the dxcc tag included. Maybe it is possible to get your 'master' adif log? I would keep it secret.
Just I found a logical issue in the import routine: When the dxcc is provided in the ADIF but not the ITU or CQ zone, then RUMlog will overwrite the dxcc with the own calculated one. I will correct this in the next update.
importing and migrating a large numbers of QSOs may make trouble. Even when there are QSOs in the log, made for a long time ago. The current used dxcc table represents current valid dxccs only, deleted countries are not included!
I know that the import is not perfect, but we can improve it further. To help you, I have to explain how RUMlog works during an import.
First we have to have a look on the ADIF file. Are there tags provided for dxcc, itu and cq zones? May look like this: <dxcc:3>130 <cqz:2>17 <ituz:2>30
When these three data are available, RUMlog will use these information. When one is missing, RUMlog will calculate the country using the dxcc tables. So these tables must be up to date. For example K7K in October 1997 will be counted as USA, W not as Kure Island, KH7K when not correct in the list.
There is another problem: When RUMlog use the in the ADIF provided dxcc info, you may run into trouble in the future, when editing an entry. RUMlog may then calculate the dxcc wrong. It is always the best, to keep the database up to date.
First you have to search your 'missing' dxccs. Use the search function. Menu-->Window-->Search Make the appropriate settings and press the 'Query' button. Also you can save the results to a (printable) text file, or to the clipboard.
- DXCC-Search.tiff (71.93 KiB) Viewed 9631 times
- DXCC-Search.tiff (71.93 KiB) Viewed 9631 times
Another way should be, I modify the dxcc tables using the old logs when there is the dxcc tag included. Maybe it is possible to get your 'master' adif log? I would keep it secret.
Just I found a logical issue in the import routine: When the dxcc is provided in the ADIF but not the ITU or CQ zone, then RUMlog will overwrite the dxcc with the own calculated one. I will correct this in the next update.
73 and best dx de Tom, DL2RUM
Re: Import ADIF Issues
The ones that are missing are CURRENT DXCC entities. Guess I will have go through it line my line. Not other way.
Please check your definitions on DXCC entities on the tables you just showed me. check 3C0 Pajalu ARRL lists it as Annobon.
If I see anything that appears wrong to me or eases this pain stacking task I will post it. I have been through this a few times. I wish ADIF board standardize these exceptions.
Please check your definitions on DXCC entities on the tables you just showed me. check 3C0 Pajalu ARRL lists it as Annobon.
If I see anything that appears wrong to me or eases this pain stacking task I will post it. I have been through this a few times. I wish ADIF board standardize these exceptions.
Jim K9TF
Re: Import ADIF Issues
How does RumLog deal with deleted countries when it come across them? I think I have 6 or 7 of these.
Jim K9TF
Re: Import ADIF Issues
Deleted countries are not in the list, but you could add deleted countries into the list yourself. Currently RUMlog will count it as 'unknown'. Due to the dxcc database structure, RUMlog is very flexible when the database is correct and complete. It should be no problem to keep it up to date during daily logging. But when you have a 20 years long log it's hard.K9TF wrote:How does RumLog deal with deleted countries when it come across them? I think I have 6 or 7 of these.
Once again: When your master ADIF file contains the dxcc tag, I could try to automate the updating.
Thanks for the hint. I've changed it. Just found, Annabom was renamed in Pagalu in 1974 and renamed back in Annabom in 1979.Please check your definitions on DXCC entities on the tables you just showed me. check 3C0 Pajalu ARRL lists it as Annobon.
73 and best dx de Tom, DL2RUM
Re: Import ADIF Issues
Jim,
I added a tool to find your lost countries, but your help is needed and appreciated. Download from here: http://dl2rum.de/rumsoft/EditDXCC-ImportHelper.zip
A step by step guide is included. Currently only differences in the dxcc computations are listed.
I added a tool to find your lost countries, but your help is needed and appreciated. Download from here: http://dl2rum.de/rumsoft/EditDXCC-ImportHelper.zip
A step by step guide is included. Currently only differences in the dxcc computations are listed.
- dxcc.tiff (515.53 KiB) Viewed 9598 times
- dxcc.tiff (515.53 KiB) Viewed 9598 times
73 and best dx de Tom, DL2RUM
Re: Import ADIF Issues
I'm having a different import issue. I just had a hard disk failure, and I'm trying to restore the log data from the ADIF file I had created (with RUMLog). The import process seems to be taking forever, though.
At first, I was trying to import the entire ADIF file with 8,309 QSOs, but when that didn't seem to be working, I created a new file with just the 316 QSOs I've logged this year. Importing even these 316 contacts has taken nearly an hour already, and it's still not complete.
I don't recall the import taking this long when I started using RUMLog. Am I doing anything wrong?
73, Dan KB6NU
At first, I was trying to import the entire ADIF file with 8,309 QSOs, but when that didn't seem to be working, I created a new file with just the 316 QSOs I've logged this year. Importing even these 316 contacts has taken nearly an hour already, and it's still not complete.
I don't recall the import taking this long when I started using RUMLog. Am I doing anything wrong?
73, Dan KB6NU
Re: Import ADIF Issues
Hi Dan,
that's not normal. Do you use the latest RUMlog version? There were some major speed improvements for the ADIF log import. When you use the latest RUMlog (3.10.1), I would ask you to send me your ADIF file via PN. So I can have a look.
that's not normal. Do you use the latest RUMlog version? There were some major speed improvements for the ADIF log import. When you use the latest RUMlog (3.10.1), I would ask you to send me your ADIF file via PN. So I can have a look.
73 and best dx de Tom, DL2RUM