Consider adding a feature where it takes a nodes data, SNR, RSSI, average number heard by, average number it hears. and makes a suggestion to client, client base, router, router late. ad disclaimers about height and better positions for routers. Pull all this data from the California nodes. Pull the average for each node type, maybe use those averages as the thresholds for the recommendations settings. When a user clicks on their node, there could be some suggestion symbol ⓘ. then a prompt from clicking it or something. Other data to consider is prominence from the surrounding 5-10 miles, does it consider how many more nodes the messages typically hop? to remove outliers Id consider removing the bottom 5% of nodes on certain metrics, ie number of nodes heard by can hear. average SNR or RSSI.
Consider adding a feature where it takes a nodes data, SNR, RSSI, average number heard by, average number it hears. and makes a suggestion to client, client base, router, router late. ad disclaimers about height and better positions for routers. Pull all this data from the California nodes. Pull the average for each node type, maybe use those averages as the thresholds for the recommendations settings. When a user clicks on their node, there could be some suggestion symbol ⓘ. then a prompt from clicking it or something. Other data to consider is prominence from the surrounding 5-10 miles, does it consider how many more nodes the messages typically hop? to remove outliers Id consider removing the bottom 5% of nodes on certain metrics, ie number of nodes heard by can hear. average SNR or RSSI.