What do you want to add?
Shaded polygons on the Meshradar map that approximate local nets: groups of nodes that appear to communicate as a localized mesh. The polygons should be a toggleable map layer. Clicking inside a polygon opens detail for that region: inferred preset and frequency slot / MHz when available, plus aggregate stats for that local net (for example packets per minute, active nodes, protocol mix).
Why is this useful?
Not every area matches a single default preset or slot (for example US LongFast / slot 20). When traveling or onboarding new users, this makes which local RF “island” you are looking at obvious without guessing from individual node dots.
Does this affect:
Extra notes
Likely cloud map + API work (clustering/aggregation + tile or on-demand endpoint). Edge-only parsing is not required unless we also surface the same view on the local Meshpoint dashboard later. Requested by kendelmccarley re: MR Cloud Map
What do you want to add?
Shaded polygons on the Meshradar map that approximate local nets: groups of nodes that appear to communicate as a localized mesh. The polygons should be a toggleable map layer. Clicking inside a polygon opens detail for that region: inferred preset and frequency slot / MHz when available, plus aggregate stats for that local net (for example packets per minute, active nodes, protocol mix).
Why is this useful?
Not every area matches a single default preset or slot (for example US LongFast / slot 20). When traveling or onboarding new users, this makes which local RF “island” you are looking at obvious without guessing from individual node dots.
Does this affect:
Extra notes
Likely cloud map + API work (clustering/aggregation + tile or on-demand endpoint). Edge-only parsing is not required unless we also surface the same view on the local Meshpoint dashboard later. Requested by kendelmccarley re: MR Cloud Map