|
ADIF Overview
Winlog32 can import QSO data exported by other logging software in ADIF.
ADIF is the only file type that can be imported, the file usually has a file extension type .ADI e.g. "ADIFLog.ADI".
Menu/File/Import
Understanding ADIF
'Amateur Data Interchange Format' (ADIF), is a standard format developed to allow an easy transfer of QSO data
between different types of logging software and is now also used by other facilities such as on-line Logbooks.
Not all ADIF tags (fields) are supported between logging programs,
Winlog32 has a limited number of fields and two of which are multi-purpose,
not all tags will be used when importing data from another log program.
The most important and basic QSO data should always be interpreted correctly between any software.
An ADIF file is in plain ASCII text, it can be viewed in a text editor such as Windows Notepad
The original ADIF (ADIF/1) standard has been superceeded by a more elaborate ADIF2 & 3 specifications, which has among
other things enumeration of many specialised data fields.
Winlog32 supports the ADIF/1 standard but some aspects of ADIF3 functionality have been included in both
importing and exporting where this can be utilised.
An ADIF file usually has a header containing some basic information about the file
e.g. which software generated it, date it was created, number of QSO etc.
The header is not a requirement but nevertheless helpful.
ADIF QSO data viewed in a text editor (Notepad)
This example shows two typical QSOs in ADIF format, this example was exported by Winlog32.
Data is contained within 'tags', callsign is contained within the 'call' tag thus "<CALL:5>G0CUZ"
The 'call' tag is followed by a Colon (:) separator and the length of the data string, e.g. '5', so any additional characters or
seperating spaces are ignored between tags.
The tags can be in any order and each QSO ends with "<EOR>"
Not all ADIF files are formatted to make easy viewing, this example from an eQSL ADIF download.
On close inspection this file still conforms to the ADIF specification,
just not easy to view, however both of the above files do not present any problems to the ADIF parsing routines.
Although it is hardly ever necessary, great care must be taken if editing an ADIF file,
don't attempt editing without fully understanding the requirements.
It is beyond the scope of this help file to explain the ADIF tags, their meaning and use but
this information is available here.....
The ADIF3 standard
|