GridTracker for POTA hunting

GridTracker (GT2) visualizes WSJT-X decodes on a map, tracks which grids and entities you have worked, and — for POTA — can spot activators you work to pota.app when configured.

Docs: GridTracker 2 manual · GridTracker2 and POTA

What GridTracker is (and is not)

GridTracker maintains a local working log synced from WSJT-X UDP traffic. Official docs are explicit: GridTracker is not your primary logger. Neither is WSJT-X’s internal ADIF. Use Polo, N3FJP, or another master log for activation uploads; use GridTracker for situational awareness.

Strengths for field and home hunting:

• Map view of decodes and known grid boundaries
• “Worked today / this band / this mode” coloring for POTA stations
• Optional automatic POTA spot when you log a park activator from WSJT-X
• Call roster columns for POTA references

POTA setup (summary)

From GridTracker POTA integration docs:

1. Settings → Logging: enable Log? on the GridTracker line so GT maintains local QSO history for worked-before logic.
2. Settings → Features → Online: enable POTA Hunting. A POTA button appears on the main menu to toggle park icons on the map.
3. Call Roster → More Controls → Wanted: enable POTA; drag the POTA column into view.

POTA map data refreshes about every five minutes. Activators not yet on the map may still be on the air — always cross-check pota.app.

Automatic spotting

When you log a POTA station from WSJT-X (with valid park info in the decode or exchange), GridTracker can post a spot to pota.app. Success appears in the menu message scroll. If park info was missing, GT will not spot — and future CQ POTA calls may still show in the roster without worked-before suppression.

Treat auto-spot as a courtesy, not a substitute for the activator’s own spot.

UDP connection

Default: WSJT-X sends to 127.0.0.1:2237. GridTracker listens. No change needed on a single-PC setup.

With JTAlert also running, see JTAlert — running both.

To forward QSOs to a real logger, use Settings → Logging export lines (QRZ, LoTW, HRD, etc.) — configure once at home; verify credentials before field use.

Using GT while hunting POTA

1. Open WSJT-X on the spotted FT8 frequency (or search CQ POTA decodes).
2. Watch GridTracker map/roster for park ID and “already worked today” status.
3. Work the station on an offset TX frequency — see WSJT-X hunter notes.
4. Confirm the QSO in your master logger if you chase awards beyond POTA hunter stats.

GridTracker’s worked-before rules vary with how different loggers record POTA — GT uses its local log precisely because activator programs disagree on ADIF details.

Habits / gotchas / checklist (GridTracker)

• WSJT-X UDP 127.0.0.1:2237. GT is not the master log.
• POTA Hunting enabled; roster POTA column visible. Map lags ~5 minutes — still check pota.app.
• Auto-spot is a courtesy, not a substitute for the activator’s own spot.
• One LoTW upload path. If JTAlert also forwards, pick one.
• Activator in a park: optional. Spot yourself and keep MY_SIG_INFO in Polo/N3FJP.

Activators

GridTracker shines for hunters and home stations. Activators in a park may run GT on a laptop to see who is calling, but the priority is still: spot yourself, run a master log with MY_SIG_INFO, manage the pileup. See Calling CQ.

Related

• WSJT-X · JTAlert · Hunt