rouggy/OpsLog
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 78 Wiki Activity

chore(udp): log the ADIF record, not just its size

Browse Source 
"Was the grid in what WSJT-X sent, or did OpsLog put it there?" is the first
question asked when a contact is logged in the wrong square, and a byte count
cannot answer it. An expedition logged at its licence holder's home QTH stayed
undiagnosable for exactly that reason.

One line per QSO, around 280 bytes, whitespace collapsed so the record sits on
a single line.
This commit is contained in:
rouggy
2026-08-13 09:13:27 +02:00
parent 385e8c4c86
commit ed3c132f70
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
app.go
+7 -1
View File
@@ -12133,7 +12133,13 @@ func (a *App) consumeUDPEvents() {
})
}
case ev.LoggedADIF != "":
applog.Printf("udp: emit udp:logged_qso (%d bytes ADIF)\n", len(ev.LoggedADIF))
// The RECORD, not just its size. "Was the grid in what WSJT-X sent, or
// did OpsLog put it there?" is the first question asked when a contact
// is logged in the wrong square, and a byte count cannot answer it —
// an expedition logged at its licence holder's home QTH stayed
// undiagnosable for exactly that reason. One line per QSO, ~280 bytes.
applog.Printf("udp: emit udp:logged_qso (%d bytes) %s\n",
len(ev.LoggedADIF), strings.Join(strings.Fields(ev.LoggedADIF), " "))
wruntime.EventsEmit(a.ctx, "udp:logged_qso", map[string]any{
"config_id": ev.ConfigID,
"service": string(ev.Service),