Why this matters
In disasters and other connectivity outages, people on the ground often see road blockages, landslides, bridge damage, or other map-relevant changes before reliable Internet access is restored. Traditional reporting channels fail when cellular networks are down or overloaded.
This post shares a community-oriented experiment: using a LoRa mesh (Meshtastic) to send simple field reports from phones (via Bluetooth to a LoRa device) to a gateway that later publishes them as OpenStreetMap Notes once Internet is available.
Scope & safety: this is not an emergency response system. Please do not include personal data (PII) or life-critical requests. The goal is to support mapping workflows.
What we built (high level)
OSM Mesh Notes Gateway turns offline messages into OSM Notes:
- A field volunteer carries a GNSS-enabled LoRa device (e.g., T‑Echo) and connects their phone via Bluetooth using the Meshtastic app.
- They send a short message starting with
#osmnote. - The message travels across the LoRa mesh to a node connected by USB to a Raspberry Pi gateway.
- The gateway validates that the device’s last GNSS fix is recent (for mobility), queues the report if offline, and creates an OSM Note when Internet is available.
- The gateway replies by direct message (DM) with an acknowledgement and privacy reminder.
Key ideas that make it work in the field
### 1) GNSS recency checks (mobility-aware) Because position updates and text messages may arrive separately in a mesh, the gateway uses the latest known GNSS position per device and enforces strict time thresholds (e.g., 15s ideal, 60s max) to avoid placing notes far from the real location (especially in vehicles).
2) Store-and-forward queue
If the gateway has no Internet, reports are stored locally (SQLite) and retried periodically. Users get a local queue ID like Q-0007.

