k8mh
April 2, 2021, 3:07pm
#1
Jarrett
Any chance f modifying the output format of the ADI file to include a space delimiter between the different fields?
call:6 KE8GOH<qso_date:8>20210402<qso_date_off:8>20210402
call:6 KE8GOH <qso_date:8>20210402 <qso_date_off:8>20210402
thanks
marc
K8MH
KD2E
April 2, 2021, 3:24pm
#2
that would then not be in accordance with the file format I was given for submission.
k8mh
April 2, 2021, 4:11pm
#3
FLE uses a inserts a space between fields. This works with POTA and WWFF uploads currently (I have no clue if they parse the spaces out or not, my guess is they ignore white space).
N3FJP and TQSL both put each field on a separate line. That also works for both programs uploading.
73’s
K8MH
I’m going off of the ADIF spec here: Released ADIF Version 3.1.1, updated 2020/09/02
And specifically:
A QSO Record describing a QSO with WN4AZY made on May 13, 1996 at 1305Z could look like this
<call:6>WN4AZY<band:3>20M<mode:4>RTTY<qso_date:8>19960513<time_on:4>1305<eor>
or like this:
<qso_date:8>19960513
<time_on:4>1305
<call:6>WN4AZY
<band:3>20M
<mode:4>RTTY
<eor>
Is the ask, @k8mh to make the ADIF file more readable? If so, I think the newline version is something I can pivot to using.
k8mh
April 4, 2021, 1:19pm
#5
Yes, to make readability better. Also easier to find fields to edit the adi file, which I sometimes do to convert POTA to WWFF and vice versa.
This has been fixed in 0.9.9! You can read about it here: 0.9.9 Released - 4/4/2021
Jarrett
closed
April 5, 2021, 10:19pm
#7
This topic was automatically closed after 24 hours. New replies are no longer allowed.