-
Notifications
You must be signed in to change notification settings - Fork 21
QSO Export
QLog can export QSOs in two ways:
- Directly from the Logbook via the context menu. Only marked QSOs are exported.
- Menu
Logbook
→Export
. This option contains 2 export sub-options-
Generic
Export based on the filter, all QSOs that meet the filter settings are exported from the log -
QSLs
Export - QSOs are exported that have set conditions as specified in the filters, and at the same time, the QSL Sent status is Requested (R
) or Queued (Q
).
-
The following export formats are supported:
- ADI -
.adi
format as defined by ADIF format - ADX -
.adx
format as defined by ADIF Format - CSV - CSV file - header + data, using a fixed delimiter
,
- JSON - QLog-specific format described below.
- POTA - POTA-Specific export described below.
It is possible to specify exported values (Exported Columns) from the log. QLog contains predefined sets of exported columns. However, these column sets are editable. Any edited options are automatically saved for future use. The available column sets are:
-
All
- exports all columns from the log (cannot be edited) -
Minimal
- a minimum set of columns defined by ADIF specification. -
POTA
- a minimum set of column requested by POTA. -
QSL-specific
- a minimal set of columns accepted ADIF specification, enriched with RST. This is a quick option forQSLs
Export. -
Custom 1
,2
,3
- user-defined groups are free for use.
The POTA Formatter exports selected QSOs that are POTA-related, meaning they have the POTA fields filled in. The exported QSOs are then sorted into two groups:
- Hunter Export This includes QSOs that do not have the "My POTA" field filled in but were conducted with a POTA station.
- Activator Export This export is necessary for reporting as a POTA activator. Each POTA location is exported to a separate file, as required by the POTA ADIF specifications.
The export process generates multiple files:
- The primary file, selected by the user, will contain the Hunter Export QSOs.
- If any QSOs are exported as activator, these files will be created in the same directory but will have different file names to distinguish the POTA reference (more Submitting Logs to POTA)
The export process also involves modifying ADIF fields according to the specifications outlined in the POTA ADIF documentation.
QLog JSON Export format has following structure, as show example below
{
"header": {
"adif_ver": "3.1.4",
"created_timestamp": "20230624 182016",
"programid": "QLog",
"programversion": "0.25.0"
},
"records": [
{
"call": "EA6MR",
"mode": "SSB",
"qso_date": "20230617",
"time_on": "164100"
}
]
}
The JSON contains header and an array of records (QSOs). The header has the same structure as the ADI header. The Records contain QSOs with the same structure and field names as the ADI format.