[Feature]: Integration with Coverage option in MeshCore MQTT Live Map

[yellowcooln]

Platform

MeshMapper Web

What feature do you want?

Looking to incorporate MeshMapper as an option alongside my Live Map coverage option. https://live.bostonme.sh/

Why do you need it?

Currently, my app uses nullrouten0/meshcore-coverage-map to integrate with our live map. I’m looking to add MeshMapper support as we plan to migrate to MeshMapper going forward.

How important is this?

Medium - Nice to have

Anything else?

This is the current requirement for my Live Map. But I am able to change and integrate another way.

My Live Map currently expects the following for coverage map integration:

1. Environment Variable

COVERAGE_API_URL=https://their-coverage-app-host

---

2. API Endpoint

The coverage application must expose:

GET /get-samples

It must return JSON in one of the following formats:

• An array of samples:

  [ ... ]

• Or an object containing an array under keys:

  { "keys": [ ... ] }

---

3. Sample Identifier

Each sample must include at least one of:

• hash
• name
• id

The value must be a geohash-like string.
The Live Map uses the first 6 characters as the tile key.

---

4. Optional Sample Fields

These fields enhance popup display and coloring logic:

• observed (boolean)
• path (array)
• time
• snr
• rssi

Alternatively, the same fields may be nested under:

metadata.observed
metadata.path
metadata.time
metadata.snr
metadata.rssi

Both flat and metadata-wrapped formats are supported.

[yellowcooln]

Greater Boston Mesh and CTMesh have fully switched to MeshMapper and are looking to get this integrated if possible.

https://meshcore-map.ctmesh.org/

[esayles]

This would definitely be nice to have and it would greatly increase the usability of the coverage feature on that map, particularly for users who are interested in knowing about coverage samples but are not interested in wardriving. Depending on how this is implemented, it could save some computational effort on the meshmapper servers as well: for users who only want to see coverage and don't need as much fine-grained detail, this API endpoint only needs to report a selection of all the information that's available on the MM web UI.