You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings from an area with a growing mesh who are big fans of your work.
We currently have people cycling and hiking around the city to try and make their first connection to a node, and some dedicated people looking at planning links between well-positioned solar power nodes.
One feature that would be helpful to both of these types of users is a display option that limits the nodes displayed by node Role. As the number of nodes grow, we think having the option to choose to display, for example, just ROUTER / ROUTER_CLIENT and exclude CLIENT will give us a nice clean map so we can help the people who want to work with the more 'fixed'/'permanent' nodes.
Initial impressions was that this might best be done in the layers widget.
Open to any and all discussion :)
The text was updated successfully, but these errors were encountered:
fifieldt
added a commit
to fifieldt/meshtastic-map
that referenced
this issue
May 20, 2024
Greetings from an area with a growing mesh who are big fans of your work.
We currently have people cycling and hiking around the city to try and make their first connection to a node, and some dedicated people looking at planning links between well-positioned solar power nodes.
One feature that would be helpful to both of these types of users is a display option that limits the nodes displayed by node Role. As the number of nodes grow, we think having the option to choose to display, for example, just ROUTER / ROUTER_CLIENT and exclude CLIENT will give us a nice clean map so we can help the people who want to work with the more 'fixed'/'permanent' nodes.
Initial impressions was that this might best be done in the layers widget.
Open to any and all discussion :)
The text was updated successfully, but these errors were encountered: