Export & Backup
Goal: export logs to ADIF, back up every setting, and browse your track history.
No matching section — try another keyword.
No matches elsewhere in the guide.
ADIF export#
- Entry: Settings → Export ADIF.
- The frequency is configurable (ADIF is the standard amateur log interchange format).
- The file imports straight into any other logging program.
Check: open the export anywhere — callsign, date and mode fields should all be there.
Backup & restore#
- Export (Settings → Backup → export): configuration (station, beacon, map, filters, sources, server…) plus local data into one JSON; images are optional.
- Import: pick the file (or paste from the clipboard) → restart the app to apply.
- New device order: install → import → restart → re-check server and Passcode under Settings → Connection.
Whitelisted import: only keys inside that group’s whitelist are accepted, so a file from someone else cannot rewrite internal settings; a backup from a newer version is rejected with “update first”. The file contains your callsign, server passwords and API keys — keep it safe.
Platform differences: Android uses the system picker (Downloads), Windows saves to Documents, web uses the clipboard. Reading is capped at 32 MB.
Track history & playback#
- Entry: Settings → Track history.
- Saved per local day (
tracklog/YYYY-MM-DD.json) with lat/lng, speed, course, altitude and accuracy — it survives a restart. - One screen per day: distance, average and top speed, moving time, point count; delete a day or clear all. Moving time only counts segments that genuinely moved — a two-hour lunch stop is not billed as driving.
- Tap a day to replay it: same tile stack as the main map (same cache, same correction), the line grows as it plays, draggable progress, 0.5×–4× speed, follow view; stops over 45 s fast-forward.
- How to read that line on the map: the on-screen track samples GPS at 1 s and keeps a point when it moved far enough or five seconds passed with real movement — so corners are not cut into diagonals and slow walks are not sparse. The points actually sent to the server are marked with small orange diamonds: count them and check the spacing at a glance (track points get thinned and capped; the diamonds do not, because they already went out).
It is deliberately separate from the on-screen “my track”, which only serves this session and disappears on exit; history is the archive — exportable and replayable.