On the map page, if multiple nodes have the exact same coordinates either intentionally or due to proximity (and Meshtastic's anonymizing algorithm), the map page will only show one of the nodes from that location. Requested feature would be that if multiple nodes have the same location, that the data supplied to the map page fuzz/randomize the location of each slightly so they are close, but not exactly in the same location. They would then be shown as a little cluster. Not having the exact location displayed should be fine since Meshtastic is already anonymizing the location of nodes on the default channel anyway.
On the map page, if multiple nodes have the exact same coordinates either intentionally or due to proximity (and Meshtastic's anonymizing algorithm), the map page will only show one of the nodes from that location. Requested feature would be that if multiple nodes have the same location, that the data supplied to the map page fuzz/randomize the location of each slightly so they are close, but not exactly in the same location. They would then be shown as a little cluster. Not having the exact location displayed should be fine since Meshtastic is already anonymizing the location of nodes on the default channel anyway.
<!-- github-sync-id:3359646917 -->
This seems to keep them from overlapping in my local install. In the map.html template:
```
lat: {{ ((node.last_lat / 10**7) + (range(-9,9) | random) / 10000) | round(7) }},
long: {{ ((node.last_long / 10**7) + (range(-9,9) | random) / 10000) |round(7) if node.last_long is not none else "null" }},
```
<!-- github-comment-id:3229123122 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On the map page, if multiple nodes have the exact same coordinates either intentionally or due to proximity (and Meshtastic's anonymizing algorithm), the map page will only show one of the nodes from that location. Requested feature would be that if multiple nodes have the same location, that the data supplied to the map page fuzz/randomize the location of each slightly so they are close, but not exactly in the same location. They would then be shown as a little cluster. Not having the exact location displayed should be fine since Meshtastic is already anonymizing the location of nodes on the default channel anyway.
This seems to keep them from overlapping in my local install. In the map.html template:
I like the idea and the code... thank you for your contribution. I will added to the next commit!