Page 1 of 1
ADIF import to Log4OM V2 - QSO date and time
Posted: 08 Aug 2020, 01:42
by K2GAV
I'm importing from HRD Logbook to Log4OM. I've selected and ADIF output that only uses ADIF standard fields and not any HRD custom fields. All my QSOs have a <QSO date>, <time on> and <time off> in the output ADIF file from HRD.
When I import to Log4OM V2, all the QSO Date fields contain the <QSO date> and <time on> fields appended, and all the QSO end date fields are blank. I'd like to retain all my QSO <time off> data when transferring into Log4OM V2. Is there a way to achieve this?
Re: ADIF import to Log4OM V2 - QSO date and time
Posted: 08 Aug 2020, 05:51
by G4POP
Please email me your ADIF file from HRD so that I can check this one out
Send to g4pop (AT) arrl.net
While thinking about HRD I recall that a long time ago we made some special import provisions for HRD files so please also send me a full ADIF export from HRD including the HRD specific fields.
Make reference to this thread or explain the issue because by the time I receive something from you I will probably forgotten the subject of your issue.
Re: ADIF import to Log4OM V2 - QSO date and time
Posted: 08 Aug 2020, 16:42
by K2GAV
Okay Terry. I won't send you my entire log becuause I have over 36,000 entries in it! Since every contact in my HRD logbook has a QSO start and end time, I'll select about 10 and export the standard ADIF file without the special HRD fields (that's a choice in HRD).
Re: ADIF import to Log4OM V2 - QSO date and time
Posted: 08 Aug 2020, 17:25
by G4POP
K2GAV wrote: 08 Aug 2020, 16:42
Okay Terry. I won't send you my entire log becuause I have over 36,000 entries in it! Since every contact in my HRD logbook has a QSO start and end time, I'll select about 10 and export the standard ADIF file without the special HRD fields (that's a choice in HRD).
Ted
I received your file and the reason is because the HRD ADIF does not contain an END Date, without that we cannot record an end time
The ADIF fields can be viewed at the ADIF site here
https://adif.org/310/ADIF_310.htm as you can see there is a qso_date and a qso_date_off field
I added a qso_date_off field to one of your example QSO's and it imports perfectly, we cant guess the end date especially when it can span two days