SOTA CSV to ADIF — a SOTA log into your logbook or LoTW
Convert a SOTA CSV log (V2) to ADIF: activations, chases and summit-to-summit QSOs with MY_SOTA_REF and SOTA_REF, dates read day first, ready for LoTW, QRZ, Club Log or your logger. In your browser, nothing uploaded.
About this conversion
The SOTA database and many SOTA logging apps save logs as CSV V2 lines, but LoTW, QRZ and everyday loggers want ADIF. Drop the .csv and every line becomes a QSO: the date (always day first — 01/11/26 is 1 November), the time, the call, the band (and the frequency, when the line has one such as 14.285MHz), the mode, your callsign as STATION_CALLSIGN, your summit as MY_SOTA_REF and theirs as SOTA_REF, the note as COMMENT. A V2SWL line gets SWL = Y.
Just want to look inside it?
The same tool without converting anything: open the file and read it.
The same log, other ways
The log stays open after it is read, so the format is picked at the end: the same file can leave here as ADX (.adx), Excel (.xlsx), CSV, JSON, Cabrillo (.log) or POTA (.adi). Before that you can filter it by band, mode, year, country or QSL status and save only those QSOs.
Questions
- What about DATA and DV?
- DV becomes DIGITALVOICE. DATA has no ADIF mode of its own — SOTA writes it for every data mode — so it is kept as written and the page tells you; set the real mode (FT8, PSK31…) with Edit fields before uploading to LoTW.
- Which SOTA files does it read?
- V2 lines from any SOTA tool or from the database’s downloads, separated by commas, semicolons or tabs; dates as dd/mm/yy, dd/mm/yyyy, dd.mm.yyyy, yyyymmdd or yyyy-mm-dd. Old lines without the V2 marker are listed and left out — the database no longer takes them either.
- Band names such as VLF or Microwave?
- Each covers several ADIF bands, so the band is left empty and the SOTA name kept in APP_SOTA_BAND; the page says how many.