[Feature Request]: new multimap option

[aid7c1]

Checklist

• I have used the search function for OPEN ISSUES to see if someone else has already submitted the same feature request.

• I have also used the search function for CLOSED ISSUES to see if the feature was already implemented and is just waiting to be released, or if the feature was rejected.

• I will describe the request with as much detail as possible.

• This request contains only one single feature, not a list of multiple (related) features.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

Contact Details

No response

Feature or improvement you want

First of all, thank you for the Meshtastic Android application.

This feature request is related to the existing requests for custom geo-layer sources (#5806) and map layer management/grouping (#4897).

I would like to suggest extending the map functionality with a coverage-oriented view that helps users understand not only where individual nodes are located, but also where network presence is strongest and where coverage gaps exist.

Proposed features:

1. Coverage heatmap

   • Optional heatmap layer showing node density and/or recent activity.
   • Visual indication of areas with strong or weak Meshtastic presence.
   • Different display modes for live nodes, recently seen nodes, or MQTT-connected nodes.

2. Community network overlays

   • Optional overlays from external community-driven LoRa mapping projects.
   • Examples could include LoRa Italia and other publicly available mesh or LoRa coverage maps.
   • Different colors or layers for each network.

3. Topographic map support

   • The feature would be especially useful when combined with topographic map layers.
   • Terrain and elevation have a major impact on LoRa propagation, so viewing coverage together with hills, mountains, valleys, and ridgelines would make the map much more useful for planning deployments and links.

Benefits:

• Easier identification of coverage gaps.
• Better planning of new node installations.
• Improved understanding of how terrain affects connectivity.
• Better visibility of nearby community networks.
• More strategic deployment of nodes to expand the mesh.

The goal is not protocol interoperability between different networks, but rather providing a richer map visualization to help users understand the overall radio landscape in their area.

Why should this be added?

No response

Screenshots / Drawings / Technical details

No response

[jamesarich]

How do you propose we do this? Where is this data coming from? How is it supplied? What does the ux look like? Would we be able to do this with appropriate legal license compatibility?