GMA — Global Mountain Activity

GMA module

Activation of summits and mountains under Global Mountain Activity (cqgma.org). Structurally parallel to POTA/SOTA/WWFF/BOTA/LLOTA/WCA — Activator/Hunter, worldwide summit DB, live spots from the own GMA feed, map, awards.

Quick Overview

• Activator / Hunter modes with multi-summit hopping
• Summit auto-complete from the worldwide summit database (33,761 refs)
• S2S detection (Summit-to-Summit)
• GMA spots feed: from cqgma.org's own spots feed — summit, name and coordinates come directly (no DX-cluster pattern, no confusion)
• Cross-ref auto-suggestion: when creating a session the summit's WWFF/SOTA reference is suggested automatically (live from cqgma.org)
• GMA Map with summit pins (mountain icon) + DX pins + lines
• GMA awards with Activator/Hunter counter, S2S + programs

Data Source: GMA (cqgma.org)

The summit data comes from the machine-readable GMA database:

• Source: cqgma.org (gmamap/load_gma.php, per region) — 33,761 summits worldwide with a DACH focus (~7,100 in Germany). Included: the GMA code, the summit point value, coordinates and a computed Maidenhead locator.
• Bundle snapshot: the DB ships as a snapshot in the app bundle and is available immediately — no auto-download (the source serves data per region, not as a single bulk endpoint; updates ship with the next app release).
• Storage: local SQLite under ~/Documents/HAM-Tools/Cache/.
• CSV import as an override for your own / more recent lists under Settings → Data.

Ref Format

The GMA code carries the association and region before the running number:

DA/AL-001    Allgäu Alps (DL)      ·  22 points  ·  JN57CG
HB/SO-012    Solothurn (Switzerland)
EA1/AT-1004  Asturias (Spain)

The <association>/<region> prefix with the slash distinguishes GMA from POTA/LLOTA. Against SOTA/BOTA (same slash pattern) the app separates via the own GMA spots feed and program context — not via the spot pattern.

Creating a GMA Session

1. Settings → Data → GMA Reference Database — the bundle snapshot is active immediately; a CSV import as an override is optionally possible
2. Top bar → New Log → GMA Session → wizard
3. Pick Activator / Hunter
4. Your own summit (Activator) with auto-complete (name or GMA code, e.g. DA/AL-)
5. Cross-ref suggestion: if the summit carries a WWFF/SOTA reference, the app suggests it automatically as a dual program (live from cqgma.org)
6. Optional: hopping summits as a comma list

Logging a QSO

• Status bar with summit ref + name
• Their Summit field with DB lookup for S2S
• Enter saves directly
• Dupe marking like in the other programs

Activation rule

The GMA rule requires ≥ 4 QSOs per summit to score points. The app shows this as a hint/counter — there is no hard block.

GMA Spots Tab

The "GMA Spots" tab shows cqgma.org's own spots feed:

• Own endpoint (api/spots/dspgma25.php) — unlike WCA/WWFF the DX cluster is not filtered by a pattern. The feed carries summit, name and coordinates directly.
• No confusion risk with SOTA/BOTA: because the refs come from the GMA feed itself, no collision-prone pattern match is needed
• Filter as with the other programs: band, mode, prefix
• Copy button + CAT QSY analogously
• Note: the feed also aggregates the closely related WWFF activity

GMA Map

• Summit pins (mountain icon mountain.2.circle.fill, forest green)
• DX pins with mode color
• S2S indicator in the sidebar row and info popup

Awards Tab

Sub-tab GMA with stats:

• Activator summits (+ QSOs)
• Hunter summits (+ QSOs)
• Summit-to-Summit (S2S)
• Programs (unique association prefixes like DA, OE, HB, EA1, …)

ADIF Export

GMA is exported with MY_SIG=GMA + MY_SIG_INFO (or SIG/SIG_INFO for hunted summits):

<MY_SIG:3>GMA <MY_SIG_INFO:9>DA/AL-001 <MY_GMA_REF:9>DA/AL-001

In addition the app writes its own APP_HAMTOOLS_* fields for a lossless re-import roundtrip — third-party software ignores them.

Multi-Ref Split

Multiple summits in one session → the export writes one ADIF file per summit, each with a single MY_SIG_INFO (filename scheme HB9HJI@DA-AL-001 20260616.adi; the slash becomes - in the filename). Bundled via the ADIFCore.OutdoorExporter library (like POTA/WWFF/BOTA/LLOTA/WCA).

Dual Program (GMA + POTA/SOTA/WWFF/BOTA/LLOTA/WCA) 🆕

Summits often sit inside a WWFF area or are also a SOTA summit. When creating a session the GMA wizard suggests the matching WWFF/SOTA ref automatically (from the cqgma.org lookup) — every logged QSO is then tagged for all of them:

• "Export ADIF" writes a separate file set per ADIF program
• With a SOTA ref, the "SOTA CSV…" button appears additionally

Details and example: POTA → Dual Program.

Known Limitations

• Self-spotting / upload not in the app yet (submission via ADIF)
• The GMA spots feed is an HTML table without an official JSON API — a layout change at cqgma.org may require the parser to be updated
• The GMA cross-ref section is in the GMA wizard itself; to additionally tag an existing POTA/SOTA/WWFF/BOTA/LLOTA/WCA session as GMA, use "Edit cross-refs" (pencil button) on the log

Comparison of the Seven Award Programs

Aspect	POTA	SOTA	WWFF	BOTA	LLOTA	WCA	GMA
Activation from	10 QSOs	4 QSOs	44 QSOs	1 QSO	10 QSOs	50 QSOs*	4 QSOs*
Refs	K-1234	HB/BE-001	DLFF-0001	B/DL-0123	CL-0001	HB-00003	DA/AL-001
Points	✗	1–10 + winter bonus	✗	✗	✗	✗	per summit
Data source	open API	open API	URL + file	open API	open API	GMA bundle	GMA bundle
Spots	dedicated	dedicated	DX cluster filter	DX + DB match	dedicated	DX + DB match	dedicated
ADIF	standard	standard	standard	MY_SIG=WWBOTA	MY_SIG=LLOTA	MY_SIG=WCA	MY_SIG=GMA

* hint/counter, no hard block.