[Feature wish] show paths, and quickly show message senders, on map. #105

Open
opened 2026-10-27 15:38:45 +01:00 by adam · 4 comments
Owner

I hereby raise a feature wish for a feature that the "Ripple" firmware has:
To show paths of received messages/ adverts on the map.

If location information is missing, skip those nodes and e.g. indicate by a dashed line with overlayed repeater IDs of repeaters missing information (e.g. [1e] [d5] on the dashed line).

If repeater identification is ambiguous, because we know more than one repeater with the same one-byte-ID, draw all alternatives (maybe with a less strong colour).

Also, tapping anywhere (message view, contacts, ...) on a sender or node, it would be nice to have a context menu with details and options to show on the map in that context menu.

Regards!

I hereby raise a feature wish for a feature that the "Ripple" firmware has: To show paths of received messages/ adverts on the map. If location information is missing, skip those nodes and e.g. indicate by a dashed line with overlayed repeater IDs of repeaters missing information (e.g. `[1e] [d5]` on the dashed line). If repeater identification is ambiguous, because we know more than one repeater with the same one-byte-ID, draw all alternatives (maybe with a less strong colour). Also, tapping anywhere (message view, contacts, ...) on a sender or node, it would be nice to have a context menu with details and options to show on the map in that context menu. Regards! <!-- github-sync-id:3970116109 -->
Author
Owner
[According to release nodes implemented in v0.9.12](https://github.com/dabeani/meshcoreterm/releases/tag/v0.9.12#:~:text=route%20visualization), but [still buggy/ not working](https://github.com/dabeani/meshcoreterm/issues/201). <!-- github-comment-id:4291949191 -->
Author
Owner

Note: #274 has a nice visual idea-mock-up of this feature.

Note: #274 has a nice visual idea-mock-up of this feature. <!-- github-comment-id:4611921393 -->
Author
Owner

OK, I now accidentally got on T-Deck (FW version v0.9.12.3) a path showing on the map.

  • I had to press the text of the scope of the incoming message.

    Please add a button "map" to make clear where to tap!

  • It does not show the stretch between last repeater and device (although the device is shown on the map with a blue dot), and also not the path from the sending node (although the position is known).

OK, I now _accidentally_ got on T-Deck (FW version v0.9.12.3) a path showing on the map. * I had to press the text of the _scope_ of the incoming message. *Please add a button "map" to make clear where to tap!* * It does not show the stretch between last repeater and device (although the device is shown on the map with a blue dot), and also not the path from the sending node (although the position is known). <!-- github-comment-id:4624333657 -->
Author
Owner

@dabeani, still improvement suggestions:

  • Display the first and last node,
  • make it clear when nodes are omitted (because no location is known) instaead of "just drawing a normal line": E.g. draw the line dashed and draw a small badge [n] on the line where n is the number of omitted hops (when the location of the first or last hop is not known, aksi mark it somehow, e.g. by a short dashed line stub in a random direction?),
  • when multiple nodes match, make it clear by e.g. drawing dashed lines to all alternatives (and filter out really far away alternatives).

Regards!

@dabeani, still improvement suggestions: * Display the first and last node, * make it clear when nodes are omitted (because no location is known) instaead of "just drawing a normal line": E.g. draw the line dashed and draw a small badge `[n]` on the line where `n` is the number of omitted hops (when the location of the first or last hop is not known, aksi mark it somehow, e.g. by a short dashed line stub in a random direction?), * when multiple nodes match, make it clear by e.g. drawing dashed lines to all alternatives (and filter out really far away alternatives). Regards! <!-- github-comment-id:6089783312 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#105