Enodia

Wardriving on foot, without GPS. A talking Wi-Fi scanner, a paper notebook, and a map built from your own walks.

Why Enodia?

The city is full of radios. Enodia uses them as landmarks.

Walk down a street and networks appear, signals grow stronger, fade and disappear. A Linux laptop in your backpack records that changing landscape and speaks through your headphones.

At each crossing, press the headset button: “Mark 1.” “Mark 2.” Write the crossing beside the mark number in a paper notebook. Without a button, write the crossing and the time you hear instead. The log keeps the moment. The notebook gives it a place.

Back home, Enodia joins the two: scans placed along your route, estimates of where access points stand, and fingerprints you can keep. Walk there again and a new scan can tell you where you are: between these crossings, this far along.

Capture, reconciliation and localisation work offline, without GPS or an external geolocation database.

Get started

You need Linux, Python 3.10+, and a Wi-Fi interface managed by iwd, NetworkManager or wpa_supplicant, with permission to scan through D-Bus. For speech, install espeak-ng or SVOX Pico. Without a voice engine, Enodia prints its announcements.

Install from source with uv:

git clone https://github.com/carlosplanchon/enodia.git
cd enodia
uv sync

For a guided terminal menu covering the whole workflow:

uv run enodia --assistant

Before walking, follow machine setup to keep the laptop awake with its lid closed and enable the headset button.

See it work

Try the bundled example without scanning any radios:

uv run enodia --locate samples/agraciada-query.jsonl \
  --map samples/agraciada-map.jsonl --voice none

You are between "Avenida Agraciada y Doctor Salvador García Pintos" and "Avenida Agraciada y San Fructuoso", 63% of the way
  around [-34.88028, -56.19569]
  5 fingerprints agree, best similarity 100%, spread 11% of the stretch (17 m)
  from evidence last gathered 2026-09-17 17:03

The street names, coordinates and geometry are real OpenStreetMap data. The radio observations are synthetic. This demonstrates the workflow, not measured accuracy on a real walk. Inputs and reproduction commands.

Your first walk

1. Check the machine, then start a short outing.

uv run enodia --preflight --log walk.jsonl
uv run enodia --say-status --log walk.jsonl

Resolve preflight failures before leaving. Check that you hear announcements with the lid closed. Use a new log filename for each outing.

2. Mark the crossings.

Mark the first crossing, each crossing along the way, and the last one. Write each name beside its announced mark number, or beside the spoken time if you have no button. Two or three blocks are enough to try the whole process. Press Ctrl+C when you finish.

3. Transcribe the notebook into notebook.txt.

#1 Avenida Agraciada y Doctor Salvador García Pintos
#2 Avenida Agraciada y San Fructuoso

#1 means button mark 1. For timed notes, replace it with a time such as 17:45:00. Keep crossing names consistent between outings.

Coordinates are optional: append @ latitude, longitude after a crossing name. Without them, positions are fractions of the stretch between two crossings.

4. Reconcile the walk and add it to your map.

uv run enodia --reconcile walk.jsonl notebook.txt
uv run enodia --map-add walk.jsonl notebook.txt

Reconciliation places scans between crossings and estimates access-point positions. Adding the walk to the map keeps its scans as fingerprints.

On a later visit, ask where you are:

uv run enodia --locate

Go further

• Draw the route. Add coordinates by hand or look up crossings with --geocode. Use --streets for street geometry and export with --csv, --geojson or --svg. Geocoding is the only command that accesses the internet, and it supports an explicit proxy.
• Check the estimates. --check-pace compares inferred movement with the clock, --check-passes compares repeated passes, and --check-map holds out one pass down one stretch at a time to test localisation.
• Share an outing. --export-public produces a pseudonymised log and notebook. Review both before publishing. Stable fingerprints and route geometry can still identify a place.

See the CLI reference for command syntax and options.

Limits

Enodia is experimental. Field use so far covers one real outing. Its pace, access-point and localisation estimates are tested on synthetic observations, and their accuracy on real streets remains to be established.

The map covers places you have already walked and ages as routers move or disappear. A map recognising the same outing it was built from proves little. Access-point positions are estimates, and scans follow straight lines between crossings unless you supply street geometry.

Fresh Wi-Fi scans send probe requests. --preflight checks scan-address randomisation settings but does not change them. Logs and maps contain network identifiers and location information.

Documentation

• Machine setup: the lid, the Wi-Fi daemon, the voice and headset permissions.
• CLI reference: every flag, by the command you reach for it with.
• File formats: the notebook you write and the log Enodia writes.
• Methodology: positioning, fingerprints and what the self-checks measure.
• Design notes: engineering decisions and the failure behind each one.
• From Python: the same operations as function calls.

License

MIT.