Logbook software

There is a LOT of logbook software for amateur radio. Much of it only works in windows and is somewhat dated with old interfaces and missing features. This is both a survey of existing software and a feature list of what we want if we write or fix one.

see also Ucfdlog

Existing software

(L) linux
(W) Windows
(M) Mac OS X

• fldigi / fllog (LWMavypgdqr)
• wsjtx (built in logger) (LW?r)
• HRD (W??yp?q?r)

cqrlog (L?aypcduqxr/vf)

many great features, very fast; old style UI, can't easily sort columns, doesn't re-edit logs, uses own db

n1ywb python hamtools (?y/amq)

basic tools in python, possibly a good foundation to start from

simple logbook tools (aevu)

(python) convert between CSV and ADIF to use a regular spreadsheet to edit in grid format

pyqso (L?vp/aqx)

focused on keeping logs separate, good contesting features possibly; log import is very slow and drops columns

ARRL Trusted QSL "TQSL" (LWMapu/ec)

ARRL logbook of the world primary interface; complete contest stats via online webpages

xlog (Lampdfqr/evc)

very large number of importable formats; doesn't support sorting arbitrary columns; missing state column!!

indexes of software

• http://radio.linux.org.au/?sectpat=logging

Required Features

features after (/) are partially implemented (or buggy) (+)not required for android

• (a) adif import
• (e) edit random ADIF files without losing data in them, autodetect and accept random columns
• view and edit individual QSO records
• +(v) tabular view of logs: add columns, hide columns, (delete empty columns), sort any column, filter by any criteria, contest filters
• (y) (cty.dat file) identify calls by country from country file]
• +(m) read open source map data; filter/plot contacts on map (grid square, contest entitity, etc.), make printable maps
• (p) handle live logging of phone contacts
• +(g) live log from fldigi using FLlog protocol
• +(t) live log from other software by sniffing ADI files (tail -f)
• (c) contests: filter relevant QSLs, list missing entities, (show on map)
• (d) duplicate check by hilighting calls already contacted; adjustable filters as per contest rules
• (f) advanced dup: show partial matches of previous similar calls for fast contest dup check
• +(u) (maybe) read and write data to online log bureaus (LoTW, eQSL, ??)
• +(q) lookup via external services (or internal database copy) hamqth eqsl qrz etc.
• +(x) extra features: greyline, contest stats summary, dx cluster
• +(r) rig control (read requencies, etc.)

Android In-house App

Planning

• Local DB options
  • SQLite
• Remote DB Options (Synchronization method)
  • MySQL
  • FLDIGI Log Server
  • In-house Log Server
  • Other protocol?
• Import/Export Options
  • ADIF (will not lose data)
  • CSV (Maybe some other time)
• Formfactors
  • Phones
  • Tablets
• Initially supported QSO Fields
  • Callsign
  • Frequency
  • Date/Time
  • RST
  • Contest exchange
  • GridSq
  • Trivial to add more...
• Commons Library
  • App will be a wrapper with a common shared library
  • Repo Options
    • Github
    • Club Git Repo
  • License Options
    • MIT
    • Other license that requires attribution
• Log Records List Actions
  • Add Entry (Primary action)
  • Sort (by any collected field)
    • By callsign
    • By frequency
    • By grid square
    • By timestamp (default)
    • ? By call sign suffix
    • Trivial to add more (b/c of SQL)
  • Filter
    • By band
    • By grid square
    • By state / country
    • Contests
  • Search
    • All supported/visible record fields
• Minimal Fields for Log Records List (For small screens)
  • Callsign
  • Frequency
  • Time/Date
  • Mode
  • remove fields if a field filter is active to save space