adam/meshview
1
0
Fork 0
mirror of https://github.com/pablorevilla-meshtastic/meshview.git synced 2026-08-07 17:33:13 +02:00
Code Issues Packages Projects Releases Wiki Activity

Added visivility on maps of nodes that overlap

Browse Source
This commit is contained in:
pablorevilla-meshtastic
2026-02-12 11:33:24 -08:00
parent fc44f49f2d
commit 2002e093af
6 changed files with 68 additions and 261 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/COVERAGE.md
-22
View File
@@ -32,27 +32,5 @@ and the last point above the threshold forms the outline.
- No terrain or building data is used (area mode only).
- Results are sensitive to power, height, and threshold.
- Environmental factors can cause large real-world deviations.
- Observed coverage depends on gateway locations and recent traffic volume.
## Observed coverage (real data)
Meshview can also draw an **observed coverage** perimeter based on real packet
sightings. This uses packets **from the node** and the gateways that heard them.
We filter to **direct/1-hop** sightings (`hop_start - hop_limit <= 1`) and then:
1. Compute distance + bearing from the sender to each gateway with location.
2. Bucket by bearing (default 5°).
3. Keep the **farthest** gateway in each bearing bucket.
4. Connect those points into a perimeter polygon.
This gives a **real-world envelope** that reflects terrain, antenna placement,
and environment. It improves over time as more packets are observed.
Tuning knobs:
- `max_hops` (default 1)
- `bearing_step` (default 10°)
- `packets_limit` (default 50 most recent packets)