ADIF format, what is needed to be valid?

[W4INF]

I am writing a program to generate an ADIF log file from other formats, I am wondering if anyone knows what is the CRITICAL fields needed to make an ADIF line "proper"?

Items such as callsign and date and time are obvious... but does it HAVE to contain ? and ? and ? to be "proper"?

I hope I am making sense..

Thanks,
Andrew

[KG4RUL]

The complete specs are here:

ADIF2 - http://www.adif.org/adif219.htm

I am assuming what you are asking about is the section headed "Physical Specifications".

[W4INF]

Thanks Dennis! That was a big help! I have specs for 1.0, but could not find 2.1.9, that will help!

I did find an answer to my question just after posting:

Quote[/b] ]4. File Definitions:

A log record is the data resulting from logging one QSO. ADIF does not specify a minimum required set of fields for log data. Although a record should contain at least :

Call
QSO_Date
Time_On
Band
Mode



Thanks agn,
Andrew

[W4INF]

I am guessing, TIME_ON is the time the QSO started... ? ? ?

[N8UZE]

Quote[/b] (W4INF @ Jan. 01 2008,08:52)]I am guessing, TIME_ON is the time the QSO started... # ? ? ?
Yes.

[K4AVL]

The freq is not required, I believe, but this is an example of a bare minimum adif file, which is good enough for LOTW:


<CALL:5>K9XXX
<BAND:3>80M
<MODE:3>SSB
<QSO_DATE:8>20071117
<TIME_ON:6>013000
<FREQ:5>3.913
<EOR>
<CALL:4>K2XXX
<BAND:3>80M
<MODE:3>SSB
<QSO_DATE:8>20071117
<TIME_ON:6>022100
<FREQ:6>3.9405
<EOR>

[K4AVL]

Also, looking at the above, there are two zeros added to the Zulu minutes, 013000 for 0130
and a colon code for each required field :5 :3 etc.
But I see that in my log the colon codes often differ for the same field, what's up with this?
Regarding "time on", I know it's a required field, but do hams in general log the start time of the QSO as the time to put in their log when doing it manually on paper?. It seems that when using PSK and some automatic logging programs that the end time (when you send 73, etc., and have it log automatically) is the time that gets put in the log when you use a computer to do it. What's the best rule of thumb here, for long QSO like 20 minutes or more, to make sure it agrees with the other ham for LOTW, etc?

[KR2D]

Quote[/b] (k4avl @ Jan. 01 2008,17:05)]and a colon code for each required field :5 :3 etc.
But I see that in my log the colon codes often differ for the same field, what's up with this?
The number after the colon is the length of the data string that follows. ADIF is a simple type/length/value format.

From the spec:

Quote[/b] ]Each data field is preceded by a field name and length enclosed in angle brackets. The name and length are separated by a colon.

[W4INF]

Quote[/b] (k4avl @ Dec. 31 2007,16:05)]Also, looking at the above, there are two zeros added to the Zulu minutes, 013000 for 0130
and a colon code for each required field :5 :3 etc.
No, no, negative... TIME_ON can be HHMM or HHMMSS, no colon to separate, the colon after TIME_ON with the number, tells the ADIF reader how many characters to read after the section name.

<TIME_ON:4>0423
and
<TIME_ON:6>042332

Both are valid entries. Thats 4:23am, but the time is in 24 hour format, therefore:

<TIME_ON:4>1645 -> 4:45pm

Thanks to all that answered up... Been a BIG help!

Andrew