search

foldynl / QLog

Amateur radio logbook software
GNU General Public License v3.0
140 stars 18 forks source link

Wrong import of adif file of another log program #455

Open ik1vqy opened 1 month ago

ik1vqy commented 1 month ago

Good evening I probably found an error in importing adif logs. When importing a log in adif format from another program, errors are always reported in the same serial numbers of the log itself, even if in reality the errors are not in the original log. Example: [QSO#7001]: Error - A minimum set of fields are missing (start_time, call, band, mode, station_callsign) (2019-03-31; ; SSB) [QSO#10001]: Error - A minimum set of fields are missing (start_time, call, band, mode, station_callsign) (2021-10-24; ; SSB) [QSO#12001]: Error - A minimum set of fields are missing (start_time, call, band, mode, station_callsign) (2024-04-02; ; SSB) If these are removed, in the new import of the correct log, the same reports are re-presented in the same serial numbers, even if the corresponding callsign has changed. Furthermore, if callsigns are detected that do not correspond to DXCC countries, these are not imported into the QLog log. I think they should be imported anyway, but simply not counted in DXCC. In fact, it can happen that pre-existing DXCC entities no longer exist, but when they existed, the connections had been made and were valid.

errors

Thanks and Best 73's

aa5sh commented 1 month ago

I think I had similiar errors if I didn't have a Station Profile selected here. Do you have one selected? I could be wrong but I remember getting errors for every log like that and I believe it was the Station Profile being selected that corrected it: image

ik1vqy commented 1 month ago

Hi, and thanks for the answer. I flag My Profile and also My Rig (sometimes... just to try...) but it doesn't work. There is always the same error and always in the same serial numbers : [QSO#7001], [QSO#10001], [QSO#12001], and sometimes also other numbers but always with the "001" as terminal. I don't know why... regards

foldynl commented 4 weeks ago

please, could you send us the impacted ADI records ?

ik1vqy commented 4 weeks ago

Good Afternoon Here are my adif Logs packed in zip format. The "LogHX3-IK1VQY.adi" file is exported from LogHX3 program. The "QLog-IK1VQY.adi" file is exported from QLog program and has not 14 records, the ones that the program has not imported signed as "errors" (see the image before). Both the programs are running on Windows 11, but also QLog running on Linux (MXLinux 23.3) has the same issue. Thanks Best regards Alfredo IK1VQY

LogHX3-IK1VQY.zip QLog-IK1VQY.zip

aa5sh commented 4 weeks ago

Odd I tried an import into a test db and the first time I got similar results as you above. But I imported the file a second time it didn't error out on the last three entries. I tried in a fresh test directory and I didn't get the last 3 errors. I think those are generated because those lines don't have a STATION_CALLSIGN ADIF entry. But there are other lines that don't have it so I'm not sure what is going on there..

As for the DXCC - Ladislav - I wonder if someone doesn't have the Override DXCC checkbox selected should QLog try to lookup DXCC unless it is missing? Maybe put a change similar to this in LogFormat.cpp.

image

foldynl commented 4 weeks ago

Please, could you send me a screenshot of the setting for your station profile "Home"?

foldynl commented 4 weeks ago

please, add also a screenshot of the Help->About Dialog.

ik1vqy commented 4 weeks ago

Good Afternoon Here are my screenshots Immagine 2024-09-09 122500 Immagine 2024-09-09 122543 Immagine 2024-09-09 122649

Best regards

foldynl commented 3 weeks ago

I am afraid that it will be necessary to clean the data in LogHX or attempt to export it as ADX. Here's what I found:

1) The LogHX export contains a large number of invalid entries, such as incorrect CQZ numbers (often 0, which is not defined), Mode is often marked as ????, and other data inconsistencies. This is not as serious as the next point.

2) Some QTH entries contain non-ASCII characters what is not allowed in case of ADI file. Mixing UTF8 (2B charts) and ASCII (1B) chars causes unpredictable value - example HG7T's Name etc.

Personally, I don't fully understand the error yet - the issue is still under investigation. However, this input file is so damaged that even if QLog managed to load it, I wouldn't trust the data very much.

If possible, try generating an ADX file from LogHX (if that's an option) and try importing it to QLog. The ADX file supports non-ASCII characters. Maybe that will help the situation.

Regarding the old DXCC entities, yes, that would be nice-to-have, but it's not the main issue with the import.

foldynl commented 3 weeks ago

It is opened a new issue for old DXCC Entity import issue - #459

ik1vqy commented 3 weeks ago

HI Many thanks for the work. I will try several ways to correct the log and I will try to import it. I tried to correct the records that QLog said to have not enough data direcly in LogHX and I exported only that records in an adif file. Then I have imported this file in QLog and the records were loaded correcly! OK! If instead I export the whole log in adif file the same errors re-appear... Mistery!

Best regards