Optimize ADIF Export to Exclude Redundant TX Frequency

[oliverbross]

Feature Description

Problem:
Currently, QLog includes the FREQ_TX field in ADIF exports even when the TX frequency is identical to the RX frequency (and split mode is inactive). This creates unnecessary redundancy in exported logs and can cause display inconsistencies when importing into other logging software (e.g., CloudLog, WaveLog).

Observed Behavior in Other Software:
Tested with RumLog, KLog, MacLoggerDX, SwissLog, Log4OM, and others:

• These applications only export FREQ_TX in ADIF if:
  1. The TX frequency differs from RX (e.g., split operation), or
  2. Split mode is explicitly enabled.
• Otherwise, the ADIF contains only FREQ (RX), avoiding duplicate data.

Impact:

• Redundant FREQ_TX fields inflate file size and may trigger warnings in third-party tools.
• Inconsistent with standard logging software behavior.

Proposed Solution:
Modify QLog’s ADIF export logic to:

1. Omit FREQ_TX if:
   • FREQ_TX is blank/unset or matches FREQ_RX, and
   • Split mode is not active.
2. Include FREQ_TX only when:
   • TX/RX frequencies differ, or
   • Split mode is enabled.

Implementation Example (Pseudocode):

if (freq_tx != freq_rx) or (split_mode_enabled):
    adif_output.write("<FREQ_TX:{}>".format(freq_tx))

Benefits:

• Aligns with industry-standard ADIF handling.
• Reduces file clutter and improves interoperability.
• Minimal code changes required.

References:

• ADIF standard (v3.1.4): Recommends omitting redundant fields.
• Behavior verified in RumLogNG, Log4OM v2, and others.

[foldynl]

It's not important whether another software does this or not. What important is how the fields is specified in the ADIF. And here I have to agree with you — it seems that FREQ_RX should only be included in the case of split or crossband operation.

I need to check the history of this change, but I believe this should be updated as you suggest.

Nevertheless, I still maintain that this field, when received in another application, should be displayed in a user-friendly wa - it means that if the FREQ and FREQ_RX are the same then display only one record.

[oliverbross]

I completely agree with your observation, Lada. While most logging software likely avoids this issue by simply omitting the FREQ_TX field in simplex mode, QLog's more rigorous ADIF implementation exposes this edge case.

As we've discussed, this behavior appears because:

• 99%+ of contacts are simplex – Most developers didn't account for this since redundant fields rarely surface
• ADIF best practices – The standard explicitly recommends omitting redundant fields (Section 3.1.4)
• Implementation variance – Other solutions likely filter FREQ_TX pre-export when FREQ_TX == FREQ_RX

The solution aligns with both technical logic and standards compliance: only include FREQ_TX when:

• Operating split
• TX/RX frequencies differ

This minor adjustment would:
✔️ Maintain data integrity
✔️ Reduce file sizes
✔️ Improve interoperability
✔️ Follow ADIF guidelines