Skip to main content

Meshtastic part 4: GPS, maps and choosing what to share

Beginner to intermediate · A position report is useful, but location privacy matters

Meshtastic can send position information over the radio mesh, and some nodes or gateways can also report position information to Internet-connected services.

That can be useful for hiking, field teams, vehicles, remote weather equipment and mapping experiments. It can also unintentionally reveal a home, work site, regular route or sensitive deployment.

You do not need to publish a location to use Meshtastic messaging.

Where does position information come from?​

Depending on hardware and configuration, a Meshtastic device can obtain a position from:

SourceWhen it makes senseWhat to remember
Built-in GPS / GNSS receiverPortable nodes with a supported satellite receiverNeeds usable satellite reception; a GPS fix isn't the same as Internet access
Connected phoneA node that can receive a location supplied by its phone/appAvailability and update behavior depend on app, permissions and active connection
Fixed positionStationary antenna, house or remote sensor siteCan be set from a previous fix or entered manually; don't publish your exact home location without considering privacy
No location sharedMessaging without position reportingOften a perfectly good choice

A GPS receiver obtains positioning signals from satellites. GPS itself does not require cellular Internet, though some phones may use online assistance to get a faster fix. A phone being offline from cellular service does not, by itself, prevent every possible GPS measurement.

Read the official Position Configuration.

What is a position packet?​

A position packet is a short radio message representing location and potentially related information such as altitude. Other compatible nodes may receive it as part of normal mesh traffic.

The app can show nodes on a map if it has suitable location data and an appropriate map display. A map is a presentation layer, not proof that a particular remote node was heard directly.

When Internet gateways or public maps are involved, ask whether the displayed position was received by local RF, forwarded by another radio, or supplied through MQTT.

Fixed position versus moving tracker​

A weather station mounted to a tower generally doesn't need repeated GPS fixes to tell the world it hasn't moved. If you decide to share a location, a fixed-position setting may fit its purpose.

A hiker or vehicle may benefit from a GPS-equipped node with a moving location. Meshtastic includes smart broadcasting, which can adjust when updates are sent based on movement and other conditions.

Increasing location update frequency has tradeoffs: battery, airtime, privacy and congestion. Faster is not always more useful, especially when many people share the same mesh.

Position precision: why it matters​

controls how precisely a location may be shared in supported channel settings. Reduced precision can let others understand the general region without revealing a precise property or parking place.

But lower precision is not perfect anonymity. Repeated approximate locations, other node information and external datasets can sometimes still reveal more than intended.

Think about three different questions:

  1. Do I transmit position over RF? What does the channel configuration permit and what is the current broadcast behavior?
  2. Who can read position on this channel? Channel keys, precision options and network participants matter.
  3. Does a gateway republish data to MQTT or an online map? That is a separate disclosure path and may use different reporting options.

Don't assume that turning off one map display prevents every listener or gateway from observing packets transmitted on a radio channel.

MQTT map reporting is a separate setting​

Meshtastic's MQTT module includes a map-reporting feature that can periodically publish unencrypted reports to a broker when enabled. The official documentation says these reports can include node name/ID, approximate location and altitude, firmware information, hardware model and other configuration/status details.

Some public brokers apply their own limits to position precision. Do not rely on a public server's policy to protect information you're not comfortable transmitting. Private brokers and third-party maps can behave differently.

Read the official MQTT configuration before enabling it.

Private locations: a few responsible defaults​

  • A beginner doesn't need to post their exact home coordinates to the forum to ask an antenna question; approximate terrain and directions are often enough.
  • Treat a location-sharing decision as intentional, especially for stationary repeaters, private homes and places where equipment is unattended.
  • Before publishing online maps or sharing channel QR codes, understand what information recipients can learn.
  • When using a node with a phone, review app location permissions as well as Meshtastic's radio-position settings.
  • For a remote sensor station, position may be less valuable than the actual temperature, pressure or battery telemetry.
  • Avoid exposing other people's locations without consent.

A safe location experiment​

  1. Use your own devices. Check if the node has GNSS or receives a position from the phone.
  2. Read the current location-sharing settings and choose a suitable degree of precision or disable sharing.
  3. If you choose to share a position, use a test setup that does not disclose private information.
  4. Disable MQTT for the first test, so a second node's reported position is received locally by RF.
  5. Compare the second node's reported coordinates and age of the last update.
  6. If desired, add a controlled MQTT uplink and see how an Internet map differs from the local node list.
  7. Disable public sharing again if you were only testing.

A coordinate displayed by the app is not necessarily current; look at its age, source and precision.

Common mistakes​

What you noticePossible explanation
Location doesn't update indoorsPoor GNSS reception or no phone-location input
Node stays at the same point after movingFixed-position setting, stale last fix or update interval
Public map sees a node the local radio doesn'tInternet reporting is different from RF reception
Public map's position seems offsetReduced precision or map-reporting rules
Unexpectedly short battery lifeGPS acquisition, update frequency, screen, RF or other power use
Location has not appeared for a long timePosition not enabled/shared, no suitable fix, privacy configuration, or missing packet

Sources and next steps​

Next explore environmental telemetry, MQTT and off-grid tradeoffs, or resilience tests.

Questions about location without revealing your address? Join the forum.