ADIF LOG AND (CSV) UPLOADER TO WAB SQUARES MAP (BETA TEST)

Using the WAB Map Uploader

Turn your log into a map of every WAB square you've worked, in under a minute.

Privacy

What this does

Upload an ADIF file exported from your logging software — or a simple CSV file, if your software doesn't tag WAB squares — and the page draws a map of every Worked All Britain square, coloured in wherever your log shows a contact.

Nothing is uploaded to a server or saved anywhere. Your file is read entirely inside your own browser, and the map disappears the moment you close or reload the page.

Process

Three steps

Step one

Get your file ready

Export your log (or just the QSOs you want) as an ADIF file from your logging software — usually ending in .adi or .adif. No SIG_INFO or REGION field to hand? A plain CSV works too — see the CSV format below.

Step two

Upload it here

Drag either an ADIF or a CSV file onto the page, or choose one from your computer. It's read straight away — nothing is sent anywhere.

Step three

Explore your map

Worked squares are shaded in. Click any square to see who you worked there, on which band and mode.

Reading the map

What the colours mean

Worked

At least one QSO in your file names this square — via SIG_INFO or REGION in an ADIF file, or the square column in a CSV.

New (last 10 days)

Worked for the first time within the last 10 days — fades to green automatically once that window passes.

Not worked

No QSO in your file is tagged with this square yet.

Option one — ADIF

The field that matters: SIG_INFO (or REGION)

The map can only find a square if your log records it in one of two ADIF fields. Most logging software uses SIG_INFO, alongside SIG to name the award:

  • SIG_INFO — the square reference, e.g. NT81
  • SIG — which award it belongs to, e.g. WAB

Some software instead puts the square straight into the REGION field with no SIG field at all — the map checks REGION too, so either way works.

<CALL:6>M0ICR/P <SIG:3>WAB <SIG_INFO:4>NT81 <EOR> the square the map reads names the award

Don't know how to set SIG_INFO (or REGION) in your logging software? Every program puts this somewhere different — some have a dedicated "Award" or "Special Interest Activity" field on the QSO entry screen, others use a plain "Region" field, and some need it added to a custom field or a per-QSO note before export. Check your own logging application's help documentation or user manual for terms like SIG, SIG_INFO, Region, Award, or Special Interest Activity — we can't give exact steps here since it depends entirely on which software you use.

Don't have any of those fields, or find it easier to build a plain list? Skip to the CSV format ↓

Option two — CSV

Prefer a spreadsheet? The CSV format

If your logging software doesn't have a SIG_INFO, SIG, or REGION field — or you'd rather build a simple list by hand or in a spreadsheet — upload a CSV file instead. One row per QSO, in exactly this column order:

  • date — as YYYYMMDD, e.g. 20260903
  • square — the WAB reference, e.g. NT81

The other three columns — callsign, band, and mode — can stay in whatever format your log already uses.

callsign,date,square,band,mode G4XXX, 20260903 , SU12 ,40M,SSB date, as YYYYMMDD the square the map reads

Example file:

callsign,date,square,band,mode
G4XXX,20260903,SU12,40M,SSB
M0ICR/P,20260827,TF12,2M,FT8

A header row is optional — if the first line starts with "callsign", it's skipped automatically, so you can leave it in or out. Every other row needs exactly five columns in this order, with the date as eight digits. A row that doesn't match — the wrong number of columns, a date that isn't YYYYMMDD, or a square the map doesn't recognise — is skipped on its own rather than stopping the whole upload, and you'll see exactly which rows were skipped and why.

Troubleshooting

If nothing shows up

The map says no valid WAB square was found

For an ADIF file, this almost always means neither SIG_INFO nor REGION was set (or set to a real WAB square) for any QSO. Check the field is being exported at all — some programs only include it if you've filled it in for that specific contact. For a CSV file, it means none of your rows passed validation — the message will show you why, row by row.

A square I worked isn't showing as worked

Check the exact reference — in SIG_INFO/REGION for ADIF, or the square column for CSV — matches a real WAB square (e.g. NT81, not a six-figure reference or a postcode). A misspelled or malformed reference is skipped rather than guessed at; for CSV, it'll show up by line number in the skipped-rows message so you can see exactly which row needs fixing.

Some of my CSV rows were skipped

The banner above the map lists why, row by row — usually a missing or extra column, a date that isn't in YYYYMMDD format, or a square the map doesn't recognise. The rest of your valid rows still make it onto the map; only the flagged rows are left out.

My dates look wrong after editing the CSV in Excel

Excel often reformats an eight-digit date column into its own date format, or a serial number, the moment you open and save the file — even if you never touched that column. Before re-uploading, either check the file in a plain text editor, or format the date column as Text in Excel before typing the dates in.

My square sits on a country border

A handful of squares (like NT81, on the England/Scotland border) officially count as two separate squares. The uploader has an optional tickbox to let you specify which country each one belongs to — leave it unticked and both sides will simply show as worked together. This applies whether your file is ADIF or CSV.

Upload an ADIF file to see your worked WAB squares.

Nothing is uploaded to a server or saved anywhere — your file is read and processed entirely in your own browser, and the map disappears the moment you leave or reload this page.

Drag a file here, or

Your WAB square must be in the SIG_INFO or REGION field of the ADIF file.