SOTA — Summits On The Air
New in 1.8 (May 2026)
The SOTA module is complete. Local summit DB, Activator/Chaser workflow, live spots feed, map, awards. Structurally parallel to the POTA module.
Quick Overview
- Activator / Chaser modes selectable when creating a SOTA session
- Summit auto-complete from the official sotadata.org.uk database (~181,000 summits worldwide, local SQLite, one-time ~15 MB download)
- One summit per session: summits are activated one after the other; create a new session for the next summit from 1.56
- Activation pills per summit and UTC day with live display in the QSO form
- Winter bonus display: for summits with bonus points the status bar shows
10+3pduring the winter window (NH: Dec 1 – Mar 15, SH: Jun 1 – Sep 15) - S2S detection (Summit-to-Summit): Their Summit field with points lookup
- SOTA spots feed: live stream from
api2.sota.org.ukinstead of regular DX cluster spots, with filter, Copy button and optional CAT QSY - SOTA-Map tab: summit pins (with elevation + points in the tooltip) + DX pins + lines summit → DX, S2S indicator per QSO
- SOTA awards in the Awards tab: Activator summits, Activator points, Chaser summits, Chaser points, S2S count, aggregated across all logs
- SOTA CSV export for sotadata.org.uk with validation and preview
- ADIF conformance:
MY_SOTA_REF,SOTA_REF,MY_SIG=SOTA,MY_SIG_INFO, plus the proprietaryAPP_HAMTOOLS_THEIR_SOTA_POINTSfor re-import without a summit DB lookup
Load the Summit DB Once
Before your first activation the summit DB has to be downloaded:
- Settings → Data → SOTA Summit database
- Click "Load now" (later "Refresh") → download of
summitslist.csv - Parsing takes ~3-5 sec, after that the database is ready in
~/Documents/HAM-Tools/Cache/summits.sqlite - Refresh reminder "older data - update recommended" after 30 days (the summit list is relatively stable)
Creating a SOTA Session
- Log name in the top bar → "New" → "Create new log" → log type "SOTA session" opens the SOTA wizard. Alternatively in the QSO panel "Outdoor" → "SOTA" (switches to the last SOTA log; without a SOTA log the wizard opens)
- If SOTA logs already exist, the wizard starts on "Open existing"; "Create new" leads to the form
- Role: pick Activator or Chaser
- Enter "My Summit" (Activator) — auto-complete searches the summit DB by ref or name, showing elevation and points per suggestion
- A session covers one summit from 1.56. Up to 1.55 there was a "More summits (hopping)" field; it assigned every QSO to all summits, and the CSV export listed it under each summit. Older sessions with several summits stay unchanged: the form points this out, new QSOs only count for the first summit, and the CSV export warns about QSOs with several summits.
- Adjust "Session name" (suggested) and optionally "My call (for this log)"
- "Create" → the log is created, the SOTA form goes active
Logging a QSO
As soon as a SOTA log is active, the QSO panel renders the lean SOTA form:
- Status bar shows UTC · frequency/band · mode · power · log name · my summit with points (e.g.
Activator · HB/BE-001 · 10+3pwith winter bonus) - Their Call with QRZ/HamQTH lookup (auto-fill after ~600 ms)
- Their Summit (S2S/chaser): known refs show ✓ name, elevation and points; unknown refs are saved anyway with a notice. The points are stored in the QSO as
theirSotaPoints - Activation pills: per summit and UTC day, e.g. "3/4" (orange) → "5/4 ✓ 10+3p" (green), plus S2S count and "Σ points"; the tooltip says "Activation valid (≥ 4 distinct stations)" — one call on four bands is one station, and points are credited once per summit and year (within the loaded log) from 1.57. Chasers see "N Summits · Σ p · S2S n", points once per summit and UTC day
- Dupe marking: same call+band+mode in the log → orange message "⚠ Duplicate saved" instead of green "✓ QSO saved" (an activation pile-up on one frequency stays clearly recognizable)
SOTA Spots Tab
When a SOTA log is active, the lower DXClusters tab is labelled "SOTA-Spots" and shows the SOTA spots feed:
- Polling every 60 sec from
api2.sota.org.uk/api/spots/50/allwhile the tab is open; button for a manual refresh - Filter: band, mode, association prefix (
HB,DM,G/LD…) - "Manual only" toggle hides automatic spots (RBNHole, sotl.as)
- Sort by clicking any column header (default: newest first)
- Copy (button, double-click or context menu "Copy to the SOTA form") fills Activator call + summit ref + frequency into the SOTA form. When CAT is connected and "QSY with Copy" is on, the rig jumps to the spot frequency and mode
SOTA Map
- Dedicated "SOTA-Map" tab in the lower tab bar (mountain icon)
- Summit pins for all summit refs of the QSOs in the active log
- DX pins for worked stations with grid resolution; "· N without position" counts QSOs without grid and callbook entry
- Lines summit → DX optional (checkbox "QSO lines"), up to 500 QSOs — above that a notice asks you to narrow the band filter
- Band filter persistent across app restarts
- Sidebar "QSOs in the log" lists all QSOs; a click selects the QSO and zooms in from 1.56
- Hover info (call · band · mode · country · name) stays while the pointer is on the QSO dot from 1.56
- Clicking a QSO dot opens the info popup with a mode color dot + S2S counter summit (if present) in SOTA orange
Awards Tab
The Awards tab has a dedicated SOTA sub-tab (automatically selected as soon as a SOTA log is active):
- Activator summits: unique refs from
mySotaRef+mySotaRefs - Activator points: sum of all valid activations (≥ 4 distinct stations per summit and UTC day, points once per summit and year), including winter bonus
- Chaser summits: unique
theirSotaRefvalues - Chaser points: sum of
theirSotaPointsacross all QSOs - Summit-to-Summit: QSOs with both fields set
SOTA CSV Export
sotadata.org.uk expects CSV rather than ADIF. "SOTA CSV…" in the log bar (with a selection: "SOTA CSV (N)…") opens the export dialog:
- Role: "Activator (my Summit)" or "Chaser (their summits)", prefilled from the log
- Scope: "QSOs in scope", "Omitted" and number of Summits
- Validation: errors block "Export", warnings do not
- Preview of the first CSV lines
- With a selection in the QSO table only that selection is exported
- File:
CALL@HB_BE-001 YYYYMMDD.csvorCALL chaser YYYYMMDD.csvin~/Documents/HAM-Tools/Exports/, then "Show in Finder"
"Export" is blocked; QSOs without an assigned summit are reported as omitted; a write error is shown in the dialog and "Export" can be triggered again.
ADIF Export
Wherever SOTA QSOs are written as ADIF, the app writes these fields:
<CALL:6>DL1ABC <BAND:3>20m <MODE:3>SSB
<MY_SIG:4>SOTA <MY_SIG_INFO:9>HB/BE-001 <MY_SOTA_REF:9>HB/BE-001
<MY_GRIDSQUARE:6>JN46PN
<SIG:4>SOTA <SIG_INFO:9>HB/AG-001 <SOTA_REF:9>HB/AG-001
<APP_HAMTOOLS_THEIR_SOTA_POINTS:1>1
<EOR>MY_SIG=SOTA+MY_SOTA_REFfor the ActivatorSIG=SOTA+SOTA_REFfor Chaser/S2SAPP_HAMTOOLS_THEIR_SOTA_POINTSis proprietary — enables re-import without another summit DB lookupAPP_HAMTOOLS_MY_SOTA_REFS(proprietary, from 1.53) keeps the full list for older sessions with several summits, for backup and re-import;MY_SOTA_REFstays a single referenceMY_GRIDSQUAREfrom the log's "My locator", otherwise from Settings → Station (locator per log, from 1.56)
Dual Program (SOTA + POTA/WWFF/BOTA) from 1.17
Many summits sit inside a POTA park and/or WWFF area. When creating a session (activator), the SOTA wizard offers optional fields for POTA, WWFF, BOTA, LLOTA, WCA and GMA refs — every logged QSO is then tagged for all programs:
- "SOTA CSV…" exports for sotadata.org.uk as usual
- "Export ADIF" appears additionally and writes a separate file set per ADIF program (conformant for pota.app / wwff.co / wwbota.net, exactly one
MY_SIGeach) - To change them later: pencil button next to the summit in the status bar → "Edit dual-program refs" → "Save" (applies retroactively to the whole session)
- Counters of the other programs appear as chips next to the activation pills
Details and example: POTA → Dual Program.
Known Limitations
- Upload to sotadata.org.uk is not built in: export via "SOTA CSV…" and upload the file on sotadata.org.uk.
- Self-spotting (posting your own spot on SOTAwatch) is not available yet.
Comparison SOTA ↔ POTA
| Aspect | SOTA | POTA |
|---|---|---|
| Data source | sotadata.org.uk CSV | pota.app CSV |
| Refs | HB/BE-001 (assoc/region code) | K-1234, HB-0001 |
| Modes | Activator / Chaser | Activator / Hunter |
| Activation valid from | 4 QSOs | 10 QSOs |
| Points system | 1–10 base + 3 winter bonus | no points (park count) |
| S2S / P2P | Summit-to-Summit | Park-to-Park |
| Spots API | api2.sota.org.uk (MHz) | api.pota.app (kHz) |
| ADIF field | MY_SOTA_REF / SOTA_REF | MY_POTA_REF / POTA_REF |
Operating style
Both programs work similarly — anyone who knows POTA finds their way around SOTA right away. The app reflects that: identical tab bar, identical form layout, identical map style.