The purpose of the ADIF file format is to provide a standard format for amateur data. The standard format of the data can then be shared between various amateur programs and contests.
ADIF file syntax consists of four components; field-name, field-length, field-type, and its field-value. For example, field-name of “DATE”, has a field-length of “8” characters, has a field-type of date (yyyymmdd), and has a field-value of “20160625”. E.g., 20160123
The field-name may include the characters A-Z, 0-9, and _, but must begin with a letter. The field-type is optional. E.g., 20160123
The following is an actual ADIF file record from our KS DAY special event. We used our club’s copy of N3FJP software and just happens to be from the CW station on 40m. It contains header information (occurs 1 time), and a record which contain a group of fields for each QSO contacted. A record consists of all the fields between and including “CALL” and “EOR” (End of Record). So, if you had 30 QSOs, you’d have 30 records plus a header.
ADIF file starts here…
ADIF Export from N3FJP's Amateur Contact Log 5.2
Written by G. Scott Davis
www.n3fjp.com
Log exported on: 1/24/2016 6:50:50 PM
N3FJP's Amateur Contact Log
5.2
N3FJP's Amateur Contact Log
5.2
AA5SKV
20160123
163700
163800
40M
KS0KS
NA
USA
291
KS,Johnson
04
7.044
JRC
07
CW
CW
John
KS0KS
100
AA5
N
N
599
599
LA
LA
KS0KS
The above record information is repeated for each QSO made. I hope this clarifies any mysteries surrounding the ADIF file.