Documentation

Full Usage Guide

This page is the complete guide for users who want deeper control of imports, session handling, map interpretation, export workflows, and deployment behavior.

Standard Workflow

Open the tool page and upload a CSV with Meshtastic log data.
The parser keeps only payload rows that include seq N, then validates coordinates.
Detected sessions appear in a configuration dialog where you select sessions and sender location behavior.
After confirmation, points are drawn on the map, color-coded by SNR (or by session if toggled).
Use popups to inspect each point and add notes tied to the session + sequence pair.
Export JSON when you want to save a portable package for later reload or sharing.

CSV Requirements and Flexibility

The parser supports common Meshtastic column naming variants. Required logical fields are:

Receiver latitude and longitude (rx lat, rx long, etc.).
Sender latitude and longitude (sender lat, sender long, etc.).
Payload column containing sequence markers like seq 5.

Helpful optional fields include sender name, sender ID, date, and time.

date,time,from,sender name,sender lat,sender long,rx lat,rx long,rx snr,payload
8/5/2025,21:03:24,3665043712,Meshtastic 2100,36.0228279,-84.249108,36.0228279,-84.249108,6.25,seq 5

How Session Detection Works

Data is first grouped by sender node ID.
Within each node, a lower sequence number after a higher one starts a new session.
A time gap larger than 30 minutes also starts a new session.
Sender GPS drift alone does not split sessions, because this often happens naturally while testing.

JSON Export / Import Format

Exported files are standard JSON that include sessions and notes:

{
  "sessions": [ ... ],
  "notes": {
    "1_15": "Yagi pointed NE",
    "session_1": "Windy day"
  },
  "exportDate": "2026-02-28T15:30:00.000Z"
}

Imported files must include a top-level sessions array to load correctly.

Best Practices for Reliable Tests

Start each field run with a clear sequence reset if possible.
Record antenna changes in notes so comparison is easier later.
Use consistent TX power/channel settings for cleaner results.
Export JSON right after each test day to preserve your data bundle.
Keep browser localStorage backed up by exporting, since browser data can be cleared.