forked from 7h0ma5/QLog
-
Notifications
You must be signed in to change notification settings - Fork 20
QSO Export
Ladislav Foldyna edited this page Jul 1, 2023
·
1 revision
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.
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. -
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.
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.