QRZ.COM
ad: Alphaant-1
ad: L-HROutlet
ad: l-rl
ad: Ham.Live-2
ad: Left-3
ad: abrind-2
ad: ChoYong-2
ad: l-BCInc
ad: L-MFJ
ad: Left-2
Latest Awards
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued
United States Awards Issued

Logbook 3.0 Documentation

ADIF Standard and How We Use It

QRZ Logbook is built around the Amateur Data Interchange Format standard or ADIF for short. This standard helps to ensure that data can easily be transfered between various logging applications with ease.

 

How does QRZ Logbook use the ADIF standard?

We use the standard to define the fields available in the logbook and constrain any enumerated fields to the correct set of acceptable values.

 

Does QRZ Logbook Support All of the Fields defined by the ADIF standard?

No at this time we do not. However fields that we do not support are preserved during import and are included in future exports.

 

Lossless ADIF

If you import an ADIF to most online logbooks, any data not needed by that system is discarded, When you later export an ADIF, any additional ADIF fields you had were lost. QRZ Logbook stores that data and exports it with each ADIF export.​

 

What can I do if my favorite mode or contest is not listed in the drop downs?

We list all of the modes and contests enumerated in the ADIF standard. If you would like to see a new mode or contest added you will need to contact the ADIF group and petition for its inclusion in the standard.

 

Application Defined Fields

We try to avoid application defined fields as much as possible however we do have a couple of fields that have little meaning outside the QRZ ecosystem.

Field Date Type* Description
app_qrzlog_logid Number References the internal ID of a log record in the QRZ system.
app_qrzlog_qsldate Date This field contains the first date on which we saw a QRZ accepted confirmation for this contact. This could have been a confirmation as a result of matching contacts in the QRZ system or a credit imported from Logbook of The World
app_qrzlog_status Character

The current QRZ confirmation status of a record

C - Confirmed
A - Reserved for future use
N - Not Confirmed
2 - Confirmation Requested
S - Confirmation Requested, Request Seen
R - Confirmation Requested, Request Rejected

* Data Types as defined here

 


This page was last updated February 4, 2021 00:59